Thanks! I'll try that as soon as 0.20.0 is released! This might also help with another issue I'm experiencing - The ThreadPoolExecutor in JmsConnection is producing non-daemon threads intentionally (I can see the comment, but still don't get the reason why to do it in your code.) Which means in case any QpidJMS Connection Executor thread gets stuck (on lock, indefinite timeout etc.) it prevents the device I'm using from clean shutdown. As I have no means of killing those threads from my code.
Any chances this might become configurable with default value set to nondaemon? -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-JMS-client-JmsConnection-close-hangs-tp7654565p7655299.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
