The servlet listener ought to have callbacks for start|stop you can hook into and do what you need to do.
And stopping the pool after camel is best, as during shutdown of camel there is maybe inflight jms messaging occurring. On Sun, Mar 2, 2014 at 4:43 PM, helander <[email protected]> wrote: > Hi Claus, > > in order to stop it, I need to know when it is time to stop it. What would > be an appropriate way to do this? Currently I create/start the pool as part > of a custom camel component. Can I register something that gets executed > when the camel context stops, or could I have a destructor on my custom > component, or ...? > > /Lasse > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/JMS-connections-survive-undeployment-tp5748197p5748205.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
