Ok, I'm not sure of the proper terminology for these things, so I'll just hope this is enough info.
Domain: jboss.jca service: LocalTxCM name: fooDS
On that page, there are two links to other MBeans, CachedConnectionManager and ManagedConnectionPool.
Clicking through to the ManagedConnectionPool, I see that slowly but surely as time goes by, the AvailableConnectionCount approaches zero. If I ever do let it reach zero, the Help Desk email start up immediately with "I can't login!", etc, etc. All I need to do, at the bottom of the page, is click the 'Invoke' button for the flush() method. Then it shoots back up to 100. So I obviously have some sort of leak.
I used to have to do this at least 2-3 times per week. We've just deployed an upgrade, and all day yesterday the pool sat at 100. Ooops, this morning I see it's at 93. So there must still be some leaks.
Now I turn to CachedConnectionManager. There is an 'invoke' button for the method listInUseConnections(). Hopefully this will give me some clues as to where the "in use" (but actually leaked) connections are.
Holy doodle! The 'InUseConnections' attribute says 536!! And the listing I get is huge! (536 stack traces).
Our connection pool is supposed to be 100. But 'in use connections' are far in excess of that. What am I not understanding?
Joined: Apr 02, 2008
Just thought I'd bump this.
Is anyone experienced in finding connection leaks in JBoss-hosted (EJB) applications?
Googling, I see things that surround those classes I mentioned: CachedConnectionManager and ManagedConnectionPool
But I'm not sure why I'm getting 500+ listings when I click the 'InUseConnections'. Clearly this doesn't mean what I think it means.