anonymous wrote : Right, but SEMPPL does tx management. In fact, that is *all* it does. If you want to do your own tx management, you don't need it.
As I read his thread, he did stop using SEMPPL and switched to the regular SeamPhaseListener + custom TX management because he could not resolve the exception. He was never simultaneously using SEMPPL + custom TX management. anonymous wrote : The only problem here is the known bug where EJB3 and Hibernate try to register synchronizations on a tx marked for rollback. | So is it possible that the actual reason for the rollback is being swallowed up by EJB3 trying to register synchronizations? >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. 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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3940212#3940212 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3940212 ------------------------------------------------------- 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
