I can't find anything anywhere about this, so I guess I have to ask here.
I've got about ten different CamelContexts running in Karaf. After adding
camel-disruptor, I've found that if I have to shut down Karaf, it hangs for
five minutes before finally letting go. I saw that this is the default
settings for Camel, and the information about configuring the
ShutdownStrategy are nonexistent. There's a brief mention of how to obtain
it from _a_ CamelContext, but I have no idea how that applies to the other
nine CamelContexts.
How can I configure this so that it only waits for a few seconds before
forceful termination? Since other services running in Karaf will have
already shut down by this point, the fact that Camel is still accepting
requests (CXF-RS) while claiming it can't shut down due to handling
requests is complete nonsense as well. Every message it accepts times out
due to no longer having an ActiveMQ connection.
I've got about ten different CamelContexts running in Karaf. After adding
camel-disruptor, I've found that if I have to shut down Karaf, it hangs for
five minutes before finally letting go. I saw that this is the default
settings for Camel, and the information about configuring the
ShutdownStrategy are nonexistent. There's a brief mention of how to obtain
it from _a_ CamelContext, but I have no idea how that applies to the other
nine CamelContexts.
How can I configure this so that it only waits for a few seconds before
forceful termination? Since other services running in Karaf will have
already shut down by this point, the fact that Camel is still accepting
requests (CXF-RS) while claiming it can't shut down due to handling
requests is complete nonsense as well. Every message it accepts times out
due to no longer having an ActiveMQ connection.