I have a JavaEE application currently deployed on Glassfish for which I have written a load test that can, in less than one hour (for now - speed improvements to the crash are coming) exhaust the JMS connection pool and break Glassfish with the insanely bad message
In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.
I would like to see which of my JavaEE components leak JMS connections. For memory, I could use a profiler, as well as I could use it for JDBC connections, I guess. But what is the best tool to track opened/closed JMS connections and the components that create them and don't release them ?