Hi,

I have an application that uses a few different routes, but basically it
picks up a file, extracts some records using splitter and sends them off to
a jms queue. When attempting to shut down the route I am informed my
messages are still inflight and so have to wait 5 minutes before it can be
shut down. Can I resolve/work around this? Am I misusing the Splitter EIP,
and does it require an Aggregator to be satisfied?

Route #1 - search for signal file - if found, dynamically create route #2
looking for matching data file name
Route #2 - pick up data file, process and send to direct:foo
Route #3 - pick up from direct:foo, use Splitter to split into records and
send each to seda queue
Route #4 - pick up from seda queue and write to jms (seda used as a
throttling mechanism, otherwise could obviously have sent directly to jms)
Shut down Route #2 (no longer required for this filename)

Route #2 is dynamic, the rest are configured in spring. The filename is used
as the id for Route #2

As I'm new to Camel, If anyone can suggest any efficiency improvements in my
flow please feel free :o)

Thanks



--
View this message in context: 
http://camel.465427.n5.nabble.com/Shutting-down-a-route-inflight-messages-and-splitter-tp5735716.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to