Details
Minor Description
We found this problem in Karaf camel command, but think it should also exist in other camel command usecases.
In Karaf
karaf@root()> camel:context-list Context Status Total # Failed # Inflight # Uptime ------- ------ ------- -------- ---------- ------ camel-1 Started 0 0 0 1.366 seconds karaf@root()> camel:context-suspend camel-1 karaf@root()> camel:context-list Context Status Total # Failed # Inflight # Uptime ------- ------ ------- -------- ---------- ------ camel-1 Suspended 0 0 0 7.554 seconds karaf@root()> camel:context-start camel-1 karaf@root()> camel:context-list Context Status Total # Failed # Inflight # Uptime ------- ------ ------- -------- ---------- ------ camel-1 Started 0 0 0 2 minutes
So after start a suspended context, there is still one in context-list. But in JMX tree there are two camel-1 context. This mismatch should be addressed. Either improve ContextList command or if it's a suspended context, throw a RuntimeException and let users resume it other than starting it.