I can't get the clientside threadpools, which is intialized by swiftmq, to terminate at all. My JMS client is running under a Resin 2.17 application server, and I really need to get those pools to terminate on WAR-redeploy events to avoid a leak. Same issue occurs if I do testing using some simple JMS accessor code similar to the samples provided with swiftmq. I would assume that closing JMS resources should do the trick, but that does not seem to be the case. Am I missing something here?