If Camel end uses add temporary routes on the fly, and then want those temp routes to be deleted, they need to shutdown the route.
And we should then unregister the associated JMX mbeans that the route solely uses. This can be a bit tricky to do as the current architecture will unregister mbeans on camel shutdown.
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||2.5.0 [ 12320 ]|
|Fix Version/s||Future [ 11977 ]|
|Resolution||Fixed [ 1 ]|
|Assignee||Claus Ibsen [ davsclaus ]|
[ You should be able to specify a route to not be enlisted in JMX.
And in XML
The trick is the current API in Camel enlists in JMX by default if its enabled. It could take a bit of refactoring to have it being able know that the route is not enlisted. For example the consumers/endpoints/services which is created by that particular route should also *not* be enlisted in JMX. And hence they need to be able to understand this, by asking their parent route if JMX is disabled or not.
|Project Import||Sat Nov 27 00:14:50 EST 2010 [ 1290834890113 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|