-
1. Re: updation problem in BMP
danch1 Nov 1, 2001 2:55 PM (in response to vkaladhar)Make sure that you're bean's methods are defined as transaction Requires or RequiresNew (or Mandatory)
-
2. Re: updation problem in BMP
vkaladhar Nov 1, 2001 10:53 PM (in response to vkaladhar)thanks for ur reply, but i didn't get what do u mean. you mean trans-attribute in ejb-jar.xml.
<trans-attribute>Required</trans-attribute> -
3. Re: updation problem in BMP
wai Nov 15, 2001 4:36 AM (in response to vkaladhar)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. -
4. Re: updation problem in BMP
danch1 Nov 15, 2001 3:21 PM (in response to vkaladhar)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. -
5. Re: updation problem in BMP
luctran Nov 15, 2001 8:27 PM (in response to vkaladhar)You should change to commit option A, B, or D in jboss.xml file or standardjboss.xml file. It will work.
-
6. Re: updation problem in BMP
davidjencks Nov 15, 2001 8:32 PM (in response to vkaladhar)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.