camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tide08 <>
Subject ScheduledPollConsumer - poll() behavior?
Date Thu, 18 Mar 2010 07:40:45 GMT


I am writing custom component and I need a polling consumer but I am not
sure, if the approach I am taking is correct. I need create
scheduledPollingConsumer which polls external system to receive messages. 

Looking at other components SchedulePollingConsumers implement poll() method
which works with "known" number of messages i.e. Mail, File - each know what
number of messages to work with inside of poll()

int count = folder.getMessageCount();

But in my scenario, there is no way to know it until you receive "null"
message from external system. So as I understand in my scenario, if there
are tonnes of messages, this consumer will keep running indefinitely. How
would this affect threadpool?

How are ScheduledPollingConsumer supposed to behave? Consume as much in
polling interval? or consume restrictively so that the scheduled run ends
before the next schedule? 

Please advice. Thanks!

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message