I am currently getting ApplicationDeadlockExceptions being thrown. I am
familiar with the reasons why deadlock can occur, however I am a little
confused as to when entity beans are being locked.
The stack trace for the exception shows that it originates from a method getY
on my entity bean X called from a session bean method. I have marked all get*
methods as being read-only. Y however is a CMR field, and the only method
called before X.getY in my session beans method is a finder that returns the X
entity bean. Does this mean the finder method is locking and also the getY
method on the X entity bean is locking?
sample code
public void MySessionMethod( String pk )
| {
| XLocal x = getXLocalHome().findByPrimaryKey(pk);
| YLocal y = x.getY();
| ...
| }
it is the x.getY() that is causing the ApplicationDeadlockException
Thanks in advance
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880894#3880894
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3880894
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
