Hi
All the unit tests run with graceful shutdown by default, and all unit
tests with camel-jetty shut down with no issues.
The in flight repository do keep track of all in flights. I can only
think of if you use the aggregator or some custom code which
can cause the exchange to be completed in Camels point of view.
Can you post your entire route?
And as always report which version of Camel you are using? And try
with the latest stable and even with 2.3-SNAPSHOT.
On Wed, Apr 14, 2010 at 7:41 PM, Ilya S <devmailboxl...@gmail.com> wrote:
> Hi All,
>
> Fist of all, thank you for this great product!
> Every new release brings excellent new features just in time.
>
> I'm currently investigating Graceful Shutdown feature, and I'm am
> wondering if graceful shutdown is supported for Camel-Jetty component?
> I was able to successfully shut down JMS component. However,
> JettyHttpCoponent seems to have issues when shutting down.
>
> In my simple test (adopted from camel-example-spring-jms:ServerRoute
> example) I have a simple route that looks like this:
>
> from("jetty:http://0.0.0.0:8686/hello";)
> ..
> .. do work
> ...
> .to("jms:queue:numbers2?requestTimeout=50000")
> .to("multiplier");
>
>
> My producers simply send numbers to http endpoint..
>
>
> When I shutdown this context gracefully I'm getting all sort of
> exceptions from Jetty, and the context does not seem to wait until
> inflight exchanges have finished.
> I'm using the defaults everywhere (e.g. default shutdown strategy).
>
> Is shutdown supported for Jetty, and if so how should one configure
> jetty to initiate proper shutdown?
>
> Thank you,
>
> Ilya.
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
