Comments on: Ejb3 Basics: Bean Managed Transactions http://www.openscope.net/2010/01/14/bean-managed-transactions-bmt/ Practical java, unix, and xml Tue, 10 Jan 2012 10:15:58 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Ant http://www.openscope.net/2010/01/14/bean-managed-transactions-bmt/comment-page-1/#comment-611 Ant Fri, 11 Feb 2011 16:08:37 +0000 http://www.openscope.net/?p=272#comment-611 That's what I thought too. I think Andrew was talking about a different boundary later on in the application. I assumed he was talking about right here in the bmt exception context. I guess the problem he's talking about is more along the lines when you have a mixed case of BMT and CMT. I'll update the example and make a note. That’s what I thought too. I think Andrew was talking about a different boundary later on in the application. I assumed he was talking about right here in the bmt exception context. I guess the problem he’s talking about is more along the lines when you have a mixed case of BMT and CMT. I’ll update the example and make a note.

]]> By: Carl http://www.openscope.net/2010/01/14/bean-managed-transactions-bmt/comment-page-1/#comment-610 Carl Fri, 11 Feb 2011 09:39:46 +0000 http://www.openscope.net/?p=272#comment-610 from the javaEE spec: Methods Not Allowed in Bean-Managed Transactions Do not invoke the getRollbackOnly and setRollbackOnly methods of the EJBContext interface in bean-managed transactions. These methods should be used only in container-managed transactions. For bean-managed transactions, invoke the getStatus and rollback methods of the UserTransaction interface. So if I understand correctly setRollbackOnly is not allowed in the catch... from the javaEE spec:
Methods Not Allowed in Bean-Managed Transactions

Do not invoke the getRollbackOnly and setRollbackOnly methods of the EJBContext interface in bean-managed transactions. These methods should be used only in container-managed transactions. For bean-managed transactions, invoke the getStatus and rollback methods of the UserTransaction interface.

So if I understand correctly setRollbackOnly is not allowed in the catch…

]]> By: Ant http://www.openscope.net/2010/01/14/bean-managed-transactions-bmt/comment-page-1/#comment-9 Ant Sun, 17 Jan 2010 20:54:02 +0000 http://www.openscope.net/?p=272#comment-9 Awesome! Thanks for the clarification, I'll update the example with the right method. Awesome! Thanks for the clarification, I’ll update the example with the right method.

]]> By: Andrew Lee Rubinger http://www.openscope.net/2010/01/14/bean-managed-transactions-bmt/comment-page-1/#comment-8 Andrew Lee Rubinger Sun, 17 Jan 2010 20:15:17 +0000 http://www.openscope.net/?p=272#comment-8 In JBoss EJB3, CMT transaction timeouts are a default that are configurable via our vendor-specific APIs: http://community.jboss.org/wiki/TransactionTimeout Also, take care when using UserTransaction.rollback; in most cases I find that you'd instead be better off setting the Thread context to rollback at the appropriate boundary (utx.setRollbackOnly()). Else you may have other code in the call stack expecting a Tx association w/ the current Thread error out. In JBoss EJB3, CMT transaction timeouts are a default that are configurable via our vendor-specific APIs:

http://community.jboss.org/wiki/TransactionTimeout

Also, take care when using UserTransaction.rollback; in most cases I find that you’d instead be better off setting the Thread context to rollback at the appropriate boundary (utx.setRollbackOnly()). Else you may have other code in the call stack expecting a Tx association w/ the current Thread error out.

]]>