Old bug, use 3.2.7.
Interesting, I can't seem to create the connection leak in 3.2.5 in
a development environment, yet it happens very consistently in production, so it must be related to the heavy load on the server.
I noticed in the change log that the AvailableConnectionCount was fixed as far as how the JMX console displays the count.
I assume that it was more far spread than just a display issue in JMX console since when the count went to 0 it started JBOSS throws exceptions, "No ManagedConnections .."
The change log seemed to indicate that it was just a display issue, but it seems to be more than that.
Anyways, since I can't duplicate the connection leak in dev, I really have no easy way to find out if the new version works correctly.
I also noticed that you recommended going to 3.2.7, what about 4.0.1 ?
Is there a reason that you recommend 3.2.7 over 4.0.1?
The connection leak was caused by a subtle synchronization bug in the core connection pool code.
I fixed this bug in the jboss_3_2 and jboss_4_0 brach, so both branches have a working connection pool.
Maybe it might be easier for you to upgrade from 3.2.5 to 3.2.7, as this is only a minor version upgrade. If an upgrade to 4.0.1 is possible, than just used the newer version -> you have the choice :-)
Even I have been facing this issue.Is it a problem with JBOSS 3.2.5??
I am using jboss-4.0.1sp1 and still my "AvailableConnectionCount" become "0" after two to three days. After "AvailableConnectionCount" become "0" I am getting No Managed Connections. Any thoughts or suggestions?