Hello, I´ve a question about how to avoid a application deadlock in the following situation:
Having two applications (x and y) using two entities (a and b) in many-to-many relation. x accesses a by primary key and then b from a. y accesses b by primary key and then a from b. If x and y access the same entities at the same time we have a deadlock. Since both applications are jms driven it is not a very big problem because we get a rollback an a try again. But we get a lot of error messages ... I´m looking for a smarter solution. It would be very easy if it will be prossible to lock the entity a and its dependent b entities in an atomic operation. Y will then wait until x finished its transaction. But how can I write such a finder method? EJBQL does not help? regards, Michael View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884350#3884350 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884350 ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
