IIT Software wrote:
Of course, classloader-wide.
In that case I think that the correct placement for swiftmq.jar would be in some directory used by JVM-wide (or appserver-wide) classloader, not inside the web apps. Placing swiftmq.jar under the webapp classloader leads to memory leaks when undeploying the webapp, as Tomcat correctly notes.
Or, optionally, place swiftmq.jar under the webapp classloader, but provide some option for the swiftmq code to shutdown its threads. Is there any such option?