I have a case where the transaction is marked rollback during the course of a complex process. But I still have to read from the DB and do some more processing. During that a new DB connection is opened (for read-only purposes) behind the scenes and thats where the connection manager complains:
| Caused by: javax.resource.ResourceException: Transaction is not active: tx=Trans | actionImpl:XidImpl[FormatId=257, GlobalId=sg1317z.corproot.net/1761318, BranchQu | al=, localId=1761318] | at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedCo | nnection(TxConnectionManager.java:290) | at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateC | onnection(BaseConnectionManager2.java:379) | at org.jboss.resource.connectionmanager.BaseConnectionManager2$Connectio | nManagerProxy.allocateConnection(BaseConnectionManager2.java:812) | at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wrapp | erDataSource.java:88) | ... 188 more I think the connection manager should allow to use a transaction that is marked rollback because it's perfectly legal to read from the DB even if the tx is going to be rolled back. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099167#4099167 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099167 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
