As for it being a 'bug' in JBoss, I was never able to reproduce what you are
talking about. However, it has been awhile since I have looked at it, so I may
go back and give it another shot.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957388#3957388
Rep
It's been a while since we communicated on this topic and the silence on
replies confirms that this is a genuine bug with JBoss connection pooling. In
the meantime, I wrote persistence management code to take care of the
allocation of connections dynamically whilst still using the EJB layer and
