messages coming out of some services like the AggregateProcessor.
Take a look at
https://github.com/chessami92/camel/compare/camel-2.13.x...features%2Fbetter-route-shutdown-deferral
to see the test that I added and how I fixed the problem in the
DefaultShutdownStrategy and let me know what you think
Do we have any idea why we are seeing this behavior? We continue to lose
messages every time we recycle our application because of the issue depicted
in the test despite our routes being created in the correct order.
--
View this message in context:
http://camel.465427.n5.nabble.com/Calculatio
I understand that the aggregator's messages do not count - they are checked
out during shutdown just fine.
The problem is the 'direct:testInput' route is actively processing a message
(represented by the delay(2*1000)), but the DefaultShutdownStrategy does not
count this message. It begins shutti
On Feb 19, 2014 10:42 AM, "chessami92 [via Camel]" <
ml-node+s465427n5747576...@n5.nabble.com> wrote:
> Any advice to give on this issue?
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
&
Any advice to give on this issue?
--
View this message in context:
http://camel.465427.n5.nabble.com/Calculation-of-in-flight-messages-in-DefaultShutdownStrategy-tp5747034p5747576.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hello there,
I am using camel 2.12.2, and I seem to be running into an issue where
messages are being dropped on graceful shutdown. I've given a sample
testng/mockito/groovy test that I think demonstrates the issue I am facing -
the DefaultShutdownStrategy calculates size to be zero when there is
