Can you try to add a dependsOn attribute on the camelContext to make sure the JaxUtilHelper is destroyed before the CamelContext?
Thanks for the help! But, i think the problem im having is the bean gets destroyed before the route shutdowns... Basically the route has queued up messages (seda, jms), and when i do a shutdown the beans gets killed then the routes keep going for a while even though the beans they pass thru are now dead.
The big changes is not Camel but Spring.
Camel 2.2 uses Spring 2.5.x by default.
Camel 2.6 uses Spring 3.0.x by default. (eg it was in fact Camel 2.4 that upgraded)
And the spring framework have changed how it handle the lifecycle of its beans. In fact it seems a bit worse than 2.5.
Thanks dave, any suggestions on how i could solve this problem?
Yeah try to instruct your spring beans to be dependent on camel, using the depends-on attribute.