Sorry forgot my system configurations:
W200 Server (1 GB Ram) + JBoss 3.2.5.
The JMX Console shows you the number of connections used, created, etc. for the Connection pool. Also, did you check if your database server has run out of connections?
We had the same issue. This is related to a bug in Jboss ConnectionPool.
The bug has been fixed in jboss 3.2.6
Well I upgraded to 3.2.6 but still have the same issue after around 15-19 hours of stress testing
Any other suggestions ?
1) Read the FAQ on how to enable "closing a connection for you" in the web layer
2) Use READ THIS FIRST to get TRACE information for org.jboss.resource
one part of which shows the evolution of the pool.
Additionally, read the FAQ on the other courses of this message, beyond not closing
connections. e.g. long GCs
link to the FAQ please.