Hallo, I'm experiencing a locking behaviour that I do not understand completely. I'm using: JBoss 3.2.5, Commit-Option: A locking-policy: QueuedPessimisticEJBLock
We have 2 EJBs (that are relevant here), user and document. document has a field user (to save which user created a document). All getter-Methods of user are made read-only and the bean is reentrant. When I create a document (in a transaction), in ejbpostcreate() I set the user via document.setuser(user). While this tx is running, I cannot access any of the getter methods of this user-Entity. When I change the user-bean to read-only, no locking occurs. But I want to create users and change them so I cannot use a read-only-bean. Now my question is: Is this behaviour of locking the userbean right (and why)? Any information would be highly appreciated. Silvio View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841377#3841377 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3841377 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
