Ok, a few things: 1) Enable tracing for the JBossManagedConnectionPool in your log4j.xml configuration file. An example of how to do this already exists in the file, you simply have to uncomment the XML. 2) Post your *-ds.xml file. 3) Check the logs for statements such as "CLOSING A CONNECTION FOR YOU..." this indicates that resources are not being closed appropriately in your application code. 4) Generate a simple test case apart from your application that simply acquires a connection, does something trivial and closes the connection. This will go a long way to separating what might be application code versus the behavior of the pool itself. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993152#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...