We maybe need to introduce some clean shutdown mechanism into consumers; so we can tell all the consumers we're about to shutdown; then they can gracefully stop processing the current route's message - then we actually stop the consumers (then the endpoints & components etc). Stopping routes midway through (eg cancelling timers) could lead to other kinds of warning messages. I guess the downside of this could make shutdown take a while to complete - also if routes invoke other routes you still could have issues where one route wants to send to another route which is now closed.
So its always gonna be pretty hard to shut down Camel cleanly without any error messages at all. Maybe we just hide error messages once shutdown starts? :) On 25/03/2009, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Tue, Mar 24, 2009 at 3:42 PM, Markus Reil <gistenju...@gmx.de> wrote: >> >> Hi, >> >> thanks for your help. >> But I am still experiencing the same problem. The sleep does not get >> interrupted (2.0-M1). >> Do you have any idea why this happens? Let me know if you need more >> information. > Can you show the complete route? And point out where the message is > when you shutdown. > > >> >> Thanks, >> Markus >> -- >> View this message in context: >> http://www.nabble.com/Delayer%3A-%22Transport-disposed%22-at-JVM-Shutdown-tp22202167p22681944.html >> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com. >> >> > > > > -- > Claus Ibsen > Apache Camel Committer > > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
