The AvailableConnections is actually the number of permits available to enter the pool. Its not necessarily the same thing as the checked out connections though it should be pretty similar and only transiently different.
If you can't reproduce the problem (with a test) or give logging then there's little more I can do. Even the CachedConnectionManager is not necessarily accurate since it uses a WeakHashMap (to avoid potential memory leaks). i.e. If you don't close a connection handle and it gets garbage collected then it will disappear from that information. You could try changing that class to use a normal HashMap. The potential memory leak is really bogus since if the connection is not getting removed from the map you've a more serious connection leak. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067875#4067875 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067875 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
