Hi Alex, Thanks a lot for your response, even if it means bad news for me... We have to change our optimistic locking management for all our applications (the problem is more for other applications that don't run under jboss...)
However, I'm worrying because I just tried to remove the triggers on the tables, but the exception is still there!!!!!! How can it be possible? For more information, the entity bean concerned has "insert-before-postcreate" set to true because of relations and forein keys. Could it be linked to the problem? (If I remove this option, I've got another exception on missing foreign key...) About the changes between 3.2.2 and 4.0.1sp1, do you have any idea? Why some requests are delayed to commit time as they were not delayed before? Why these requests have not the same where clause: In ejb3.2.2: WHERE NUM_INTERNE_SITUATION=? In ejb4.0.1: WHERE NUM_INTERNE_SITUATION=? AND TSTAMP=? (with the same jar...) Thanks a lot in advance, Fred View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875928#3875928 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875928 ------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
