[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2544) Exception handling for javax.persistence.OptimisticLockException fails the second time

Exception handling for javax.persistence.OptimisticLockException fails the second time -------------------------------------------------------------------------------------- Key: JBSEAM-2544 URL: http://jira.jboss.com/jira/browse/JBSEAM-2544 Project: JBoss Seam Issue Type: Bug Components: Exception Handling Affects Versions: 2.0.1.CR2 Reporter: Christian Bauer Priority: Blocker Fix For: 2.0.2.GA, 2.1.0.GA Install the wiki, run it in dev profile. <exception class="javax.persistence.OptimisticLockException"> <end-conversation/> <!-- TODO: This fails randomly, it works only once and then we don't get the message anymore?! --> <redirect view-id="/message.xhtml"> <message severity="WARN">#{messages['lacewiki.msg.OptimisticLockError']}</message> </redirect> </exception> Generate this exception by editing directory 'BBB' in two browser tabs, click Update in one of them, then click Update in the other. If you are lucky, you will now be on the message page with a proper error message. If you don't have a message, that's the bug. If you get a message, try again and repeat the concurrent update procedure. It will fail at some point, I needed no more than three attempts. Occasionally I get this exception (always doing the same clicks!): javax.el.ELException: /message.xhtml: Property 'handledException' not found on type org.jboss.seam.Namespace com.sun.facelets.compiler.TextInstruction.write(TextInstruction.java:48) Once you get that exception, it will never work again and you will always get this exception (I think). There are several open issues related to exception handling and message passing, this probably duplicates them. My guess is that we have a serious race condition somewhere in the exception handling code.