Hi,
I have an entity bean with TX_REQUIRED as default method tx attribute and
one method with TX_NOT_SUPPORTED tx attribute.
I also have a session bean with TX_REQUIRED tx attribute. In one of the
session bean method I successively call two methods of my entity bean (one
has TX_REQUIRED and the other has TX_NOT_SUPPORTED tx attributes). The
xsecond call into the entity bean results in a deadlock (in Weblogic 5.1).
To sumarize:
public class MySessionBean implements SessionBean {
public void txRequiredMethod1() {
MyEntityBean entity = myEntityHome.findByPrimaryKey(...);
entity.txRequiredMethod();
entity.txNotSupportedMethod(); // deadlock
}
public void txRequiredMethod2() {
MyEntityBean entity = myEntityHome.findByPrimaryKey(...);
entity.txNotSupportedMethod();
entity.txRequiredMethod(); // deadlock
}
public void txRequiredMethod3() {
MyEntityBean entity = myEntityHome.findByPrimaryKey(...);
entity.txNotSupportedMethod(); // OK
}
}
What is the expected behaviour of such code? Is the deadlock normal?
The example above works in Orion but not in Weblogic.
Philippe.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
