anonymous wrote : So is it possible that the actual reason for the rollback is being swallowed up by EJB3 trying to register synchronizations?
Exactly. I thought I had already made that bit clear in this or another thread. anonymous wrote : From what I can (finally) tell, I have a Session scoped SFSB that is throwing an exception in a method (not so unusual!). This exception causes the SFSB to be removed by/from the container, which in turn causes it to be removed from Seam. Exactly, all according to spec. In addition, the tx gets marked for rollback, again according to spec. anonymous wrote : Instead of hearing about the ACTUAL exception, however, I just hear about this damn transaction already rolledback trace. To get any useful information out of this I'm going to have to intercept all of my methods and print stack traces my self. This is a debugging nightmare. Yes and this is a bug, as I have stated numerously in this and other threads. Unfortunately, getting a bug fixed in both EJB3 and HEM, rolling into an AS release, and finally rolling into a Seam release is _not_ something that can be done in a couple of days. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3940257#3940257 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3940257 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
