Re: camel-mail validation process

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: camel-mail validation process

Claus Ibsen-2
Hi

You can try to turn of peek with peek=false
On Mon, Sep 17, 2018 at 4:12 PM Marco Pampaloni
<[hidden email]> wrote:

>
> Hi everyone, I've been trying to write down a camel route that listens to a
> mailbox and downloads the messages when needed... The problem is that the
> server contains about 5k mails and it looks like a sort of validation
> process takes place before the fetch.
>  It takes a really long time to complete (probably evaluating 1-2 mail per
> second). Is this really necessary? Is there a way to disable this behaviour?
>
> I tried setting fetchSize and maxMessagesPerPoll to low values, but after
> inspecting the code on github, it turned out that they both get used after
> this "validation process". You can check this out here:
> https://github.com/apache/camel/blob/master/components/camel-mail/src/main/java/org/apache/camel/component/mail/MailConsumer.java
>
> At the end of the retrieveMessages method you can see a loop that scans the
> retrieved messages, which is genetaring the previously described behaviour.
>
> Can anybody help?
>
> --
> Marco Pampaloni



--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Reply | Threaded
Open this post in threaded view
|

Re: camel-mail validation process

m.pampaloni
Unfortunately, it does not work

Il giorno mar 18 set 2018 alle ore 16:41 Claus Ibsen <[hidden email]>
ha scritto:

> Hi
>
> You can try to turn of peek with peek=false
> On Mon, Sep 17, 2018 at 4:12 PM Marco Pampaloni
> <[hidden email]> wrote:
> >
> > Hi everyone, I've been trying to write down a camel route that listens
> to a
> > mailbox and downloads the messages when needed... The problem is that the
> > server contains about 5k mails and it looks like a sort of validation
> > process takes place before the fetch.
> >  It takes a really long time to complete (probably evaluating 1-2 mail
> per
> > second). Is this really necessary? Is there a way to disable this
> behaviour?
> >
> > I tried setting fetchSize and maxMessagesPerPoll to low values, but after
> > inspecting the code on github, it turned out that they both get used
> after
> > this "validation process". You can check this out here:
> >
> https://github.com/apache/camel/blob/master/components/camel-mail/src/main/java/org/apache/camel/component/mail/MailConsumer.java
> >
> > At the end of the retrieveMessages method you can see a loop that scans
> the
> > retrieved messages, which is genetaring the previously described
> behaviour.
> >
> > Can anybody help?
> >
> > --
> > Marco Pampaloni
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


--
Marco Pampaloni