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? Thanks John View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872085#3872085 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872085 ------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
