Hi All.
I have already searched the forum but haven't found any answer. Please, I
would appreciate any suggestions. I have the following problem :
I've got two session beans. The first one has a method with Required
transaction attribute and the second one has a method with RequiresNew
transaction attribute. The following code hags - because the first
transaction is blocking the second one.
// the following code hangs
class SessionBean {
public void hasRequiredAttribute() {
.. . . . . . .
// it hangs here !!
anotherSessionBean.hasRequiresNewAttribute(); // method 2
} //of method
} //of class
It looks like SERIALIZABLE isolation level is set - in the first method
(Required attribute) I just query the data (just SELECT) but it locks the
bean. Does JBoss always use "pessimistic concurrency" at the server level ?
My DB is Oracle and it has its default isolation level set to
READ_COMMITTED. With this isolation level, the above problem should not
have occured. How can I determine what isolation level is being implemented
in JBoss? Or how can I change that? I think it should be possible to
change it in oracle-service.xml. But it looks it doesn't work or I do that
wrong. Also I have tried to set it for a SESSION - didn't help.
Thanks a lot.
Mark
-------------------------------------------------------
This SF.NET email is sponsored by: The Best Geek Holiday Gifts!
Time is running out! Thinkgeek.com has the coolest gifts for
your favorite geek. Let your fingers do the typing. Visit Now.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
