Make sure that you're bean's methods are defined as transaction Requires or RequiresNew (or Mandatory)
thanks for ur reply, but i didn't get what do u mean. you mean trans-attribute in ejb-jar.xml.
I have encounter similar problem as well.
It appears that the bean issue an update SQL
statement without performing a commit afterward.
When you client keep calling the same bean,
the Jboss would allocate addition db connections
from the pools.
Yes, that should work.
Another possibility: make sure you're closing all of your JDBC resources (Connection, Statement, any ResultSet objects). It's usually best to do this in a finally clause at the end of a try block around your database code.
You should change to commit option A, B, or D in jboss.xml file or standardjboss.xml file. It will work.
Commit option determines caching and whether updates made by other apps are visible, not anything about when and if commits happen. Since the connection pools were running low most likely the connections were not getting closed before tx commit.