[
https://issues.apache.org/jira/browse/CAMEL-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056497#comment-13056497
]
Claus Ibsen commented on CAMEL-4145:
------------------------------------
The consumer acts correctly when you use no timeout as it will do a NoWait,
which mean it checks if there was a message immediately available. For a
file/ftp thats not the case as it would have to go pool for that. You can't
expect a NoWait to connect to a remote FTP server, traverse a directory
structure, download the desired file, etc. All that takes time. NoWait is a
immediately check for any existing messages.
If you on the other hand use seda, then you can use a NoWait polling as the
seda queue may have messages ready at hand already.
However I think the default aggregator should set an empty message in case the
was no message to poll.
Likewise we should set the TO_ENDPOINT header, that is used to keep track of
endpoints that the message is being send to.
> pollEnrich DSL behaves differently depending on a possibly explicitly given
> timeout
> -----------------------------------------------------------------------------------
>
> Key: CAMEL-4145
> URL: https://issues.apache.org/jira/browse/CAMEL-4145
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.7.2
> Reporter: Babak Vahdat
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.8.0, 2.9.0
>
>
> For details see the user forum:
> http://camel.465427.n5.nabble.com/Is-this-pollEnrich-s-expected-behaviour-td4517089.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
