I have an MDB with the following pseudocode in its onMessage method:

public void onMessage(Message msg)
{
  // Entity bean = home.create(...)
  // bean.setX(...)
  // bean.setY(...)
}

Each of the three methods, create, setX, and setY have a trans-attribute
of "RequiresNew".  With only one client posting a message, a "deadlock
detected" exception is thrown when setX is invoked.  How can deadlock
occur when only one thread is active?

Thanks,
Jim




-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to