Would something like this work ? In my custom camel component I will create and start the pool in the createEndpoint method. Further I would add an eventnotifier for CamelContextStoppedEvent to the context. In the eventnotifier I would then stop the pool.
The thinking from my side is to have a solution that would work independently how the context lifecycle is managed, it would only depend on my custom component (which is the user of the pool). -- View this message in context: http://camel.465427.n5.nabble.com/JMS-connections-survive-undeployment-tp5748197p5748213.html Sent from the Camel - Users mailing list archive at Nabble.com.
