We encountered the same "connection leak" problem with JBoss 3.2.5 and after hours of debugging found a synchronization bug within the MangedConnectionPool code....
This bug has been fixed in the CVS, so build a JBoss3.2.6RC2 right now from the CVS or wait until JBoss 3.2.6 release scheduled for 9th october.
What this issue address in 3.2.6? We are running JBoss 3.2.6 under heavy load with 1.5GB for the JVM and finding that the JVM heap keeps growing and we are having to reboot the servers daily to keep from having JBoss generate out-of-memory errors.
We have set the acccept count to 10 and the max processes to 300, our model has the average user spending 3 minutes to access a series of 12 web pages without heavy graphics (pulling a total of 45kB of data). The load is distributed among 3 machines, averaging 5% CPU Utilization and the JVM heap is growing 50MB every hour while 300-400 users are completing the process every minute.
Where can we start to look for answers?
thanks in advance,