Hi !!
Can you please provide some more inputs on - determining the suitability of the
'default combination of pessimistic EJB locking commit option A' for the
use-case. An example for analysing would be very helpful for me.
Few comments:
1. the default commit option is 'B' not 'A' - right ??
Which version of JBoss are you using?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3876963#3876963
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3876963
---
This SF.Net
Hi !!
I'am using JBoss 3.2.3 ...
Regards..
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3876973#3876973
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3876973
---
This
I am no expert in this area, but I've experienced a similar problem with our
application.
I have been using JBoss 2.4.3 and not 3.2.3 so my comments may not be
applicable but I too have experienced a similar problem where JBoss has not
thrown an ApplicationDeadlockException in a situation
One problem we face with transaction timeout is that when it is increased
application seem to hang on unix and linix installations
Problem description
We increased the transaction timeout to 1800(30 minutes) on the unix and linux
installations. It is jsp-struts-ejb application The normal flow
http://jira.jboss.com/jira/browse/JBAS-1509
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3872385#3872385
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872385
---
SF
