Re: Rollbacks at database level throws exception in Geronimo
I had a similar problem with Geronimo 1.1 and with WASCE 1.1 when using the generic TranQL connector. I ended up using WASCE 1.1.0.1 instead because they have DB2 specific TranQL connectors. When I used those, the rollback worked as expected. On 11/28/06, Arunanthisivam Vimalathithen <[EMAIL PROTECTED]> wrote: Hi, I am using the provided TranQL connectors for the datasource and the problem I faced seemed to be connected with the TranQL connector which seems to be setting auto commit to true. I was asked to file a JIRA on this ( http://issues.apache.org/jira/browse/GERONIMO-2576). There have been not any responses to that and I also could not make any headway into the issue so far. Thanks and regards, Vimalan On 11/28/06, Meenakshi <[EMAIL PROTECTED]> wrote: > > Hi Arunanthisivam, > > Were you able to debug the problem? I am also facing a similar error > wherein I > have set autocommit to false in the application and I am using DB2 9.1 > universal JDBC drivers...and I get the same error..as below: > > com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10114][10307] Invalid > operation: Explicit COMMIT or ROLLBACK is not allowed when in > auto-commit mode. >at com.ibm.db2.jcc.c.p.rollback(p.java:752) >at com.ibm.db2.jcc.c.gc.rollback(gc.java:162) >at > com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions > (WSRdbManagedConnectionImpl.java :3663) >at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup > (WSRdbManagedConnectionImpl.java:3143) >at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1416) >at com.ibm.ejs.j2c.FreePool.returnToFreePool (FreePool.java:475) >at com.ibm.ejs.j2c.PoolManager.release(PoolManager.java:1598) >at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java > :2237) >at com.ibm.ejs.j2c.LocalTransactionWrapper.afterCompletion > (LocalTransactionWrapper.java:1228) >at > com.ibm.ws.LocalTransaction.LocalTranCoordImpl.informSynchronizations > (LocalTranCoordImpl.java:1488) >at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.cleanup > (LocalTranCoordImpl.java:1196) >at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.end > (LocalTranCoordImpl.java:1301) >at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:731) >at com.ibm.ejs.csi.BeanManaged.postInvoke (BeanManaged.java:343) >at com.ibm.ejs.csi.TransactionControlImpl.postInvoke > (TransactionControlImpl.java:581) >at com.ibm.ejs.container.EJSContainer.postInvoke > (EJSContainer.java:3876) >at com.ibm.ejs.container.EJSContainer.postInvoke > (EJSContainer.java:3698) >at > > com.ibm.websphere.startupservice.EJSRemoteStatefulAdminServiceStartup_36ac1ed1 > . > start(Unknown Source) >at com.ibm.websphere.startupservice._AppStartUp_Stub.start > (_AppStartUp_Stub.java:252) >at com.ibm.ws.startupservice.StartBeanInfo.start > (StartBeanInfo.java:287) >at com.ibm.ws.startupservice.StartUpModule.appStart > (StartUpModule.java:152) >at com.ibm.ws.startupservice.StartUpApplication.start > (StartUpApplication.java:105) >at com.ibm.ws.startupservice.StartUpService.stateChanged > (StartUpService.java:461) >at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged > (ApplicationMgrImpl.java:1247) >at > > com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent > (DeployedApplicationImpl.java:1112) >at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState > (DeployedApplicationImpl.java:232) >at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState > (DeployedApplicationImpl.java:227) >at com.ibm.ws.runtime.component.DeployedApplicationImpl.start > (DeployedApplicationImpl.java:826) >at > com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication > (ApplicationMgrImpl.java:948) >at > com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run > (ApplicationMgrImpl.java:2114) >at > com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run > (WsComponentImpl.java:340) >at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1499) > > Please let me know if you got the solution to the problem. > > Thanks, > Meenakshi > > > >
Re: Rollbacks at database level throws exception in Geronimo
Hi, I am using the provided TranQL connectors for the datasource and the problem I faced seemed to be connected with the TranQL connector which seems to be setting auto commit to true. I was asked to file a JIRA on this ( http://issues.apache.org/jira/browse/GERONIMO-2576). There have been not any responses to that and I also could not make any headway into the issue so far. Thanks and regards, Vimalan On 11/28/06, Meenakshi <[EMAIL PROTECTED]> wrote: Hi Arunanthisivam, Were you able to debug the problem? I am also facing a similar error wherein I have set autocommit to false in the application and I am using DB2 9.1 universal JDBC drivers...and I get the same error..as below: com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10114][10307] Invalid operation: Explicit COMMIT or ROLLBACK is not allowed when in auto-commit mode. at com.ibm.db2.jcc.c.p.rollback(p.java:752) at com.ibm.db2.jcc.c.gc.rollback(gc.java:162) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions (WSRdbManagedConnectionImpl.java:3663) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup (WSRdbManagedConnectionImpl.java:3143) at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1416) at com.ibm.ejs.j2c.FreePool.returnToFreePool(FreePool.java:475) at com.ibm.ejs.j2c.PoolManager.release(PoolManager.java:1598) at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java :2237) at com.ibm.ejs.j2c.LocalTransactionWrapper.afterCompletion (LocalTransactionWrapper.java:1228) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.informSynchronizations (LocalTranCoordImpl.java:1488) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.cleanup (LocalTranCoordImpl.java:1196) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.end (LocalTranCoordImpl.java:1301) at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:731) at com.ibm.ejs.csi.BeanManaged.postInvoke(BeanManaged.java:343) at com.ibm.ejs.csi.TransactionControlImpl.postInvoke (TransactionControlImpl.java:581) at com.ibm.ejs.container.EJSContainer.postInvoke (EJSContainer.java:3876) at com.ibm.ejs.container.EJSContainer.postInvoke (EJSContainer.java:3698) at com.ibm.websphere.startupservice.EJSRemoteStatefulAdminServiceStartup_36ac1ed1 . start(Unknown Source) at com.ibm.websphere.startupservice._AppStartUp_Stub.start (_AppStartUp_Stub.java:252) at com.ibm.ws.startupservice.StartBeanInfo.start (StartBeanInfo.java:287) at com.ibm.ws.startupservice.StartUpModule.appStart (StartUpModule.java:152) at com.ibm.ws.startupservice.StartUpApplication.start (StartUpApplication.java:105) at com.ibm.ws.startupservice.StartUpService.stateChanged (StartUpService.java:461) at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged (ApplicationMgrImpl.java:1247) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent (DeployedApplicationImpl.java:1112) at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState (DeployedApplicationImpl.java:232) at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState (DeployedApplicationImpl.java:227) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start (DeployedApplicationImpl.java:826) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication (ApplicationMgrImpl.java:948) at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run (ApplicationMgrImpl.java:2114) at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run (WsComponentImpl.java:340) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1499) Please let me know if you got the solution to the problem. Thanks, Meenakshi
Re: Rollbacks at database level throws exception in Geronimo
Hi Arunanthisivam, Were you able to debug the problem? I am also facing a similar error wherein I have set autocommit to false in the application and I am using DB2 9.1 universal JDBC drivers...and I get the same error..as below: com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10114][10307] Invalid operation: Explicit COMMIT or ROLLBACK is not allowed when in auto-commit mode. at com.ibm.db2.jcc.c.p.rollback(p.java:752) at com.ibm.db2.jcc.c.gc.rollback(gc.java:162) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions (WSRdbManagedConnectionImpl.java:3663) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup (WSRdbManagedConnectionImpl.java:3143) at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1416) at com.ibm.ejs.j2c.FreePool.returnToFreePool(FreePool.java:475) at com.ibm.ejs.j2c.PoolManager.release(PoolManager.java:1598) at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:2237) at com.ibm.ejs.j2c.LocalTransactionWrapper.afterCompletion (LocalTransactionWrapper.java:1228) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.informSynchronizations (LocalTranCoordImpl.java:1488) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.cleanup (LocalTranCoordImpl.java:1196) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.end (LocalTranCoordImpl.java:1301) at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:731) at com.ibm.ejs.csi.BeanManaged.postInvoke(BeanManaged.java:343) at com.ibm.ejs.csi.TransactionControlImpl.postInvoke (TransactionControlImpl.java:581) at com.ibm.ejs.container.EJSContainer.postInvoke (EJSContainer.java:3876) at com.ibm.ejs.container.EJSContainer.postInvoke (EJSContainer.java:3698) at com.ibm.websphere.startupservice.EJSRemoteStatefulAdminServiceStartup_36ac1ed1. start(Unknown Source) at com.ibm.websphere.startupservice._AppStartUp_Stub.start (_AppStartUp_Stub.java:252) at com.ibm.ws.startupservice.StartBeanInfo.start (StartBeanInfo.java:287) at com.ibm.ws.startupservice.StartUpModule.appStart (StartUpModule.java:152) at com.ibm.ws.startupservice.StartUpApplication.start (StartUpApplication.java:105) at com.ibm.ws.startupservice.StartUpService.stateChanged (StartUpService.java:461) at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged (ApplicationMgrImpl.java:1247) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent (DeployedApplicationImpl.java:1112) at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState (DeployedApplicationImpl.java:232) at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState (DeployedApplicationImpl.java:227) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start (DeployedApplicationImpl.java:826) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication (ApplicationMgrImpl.java:948) at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run (ApplicationMgrImpl.java:2114) at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run (WsComponentImpl.java:340) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1499) Please let me know if you got the solution to the problem. Thanks, Meenakshi
Re: Rollbacks at database level throws exception in Geronimo
Please create a JIRA. http://issues.apache.org/jira/browse/GERONIMO Thanks, vamsi On 11/16/06, Arunanthisivam Vimalathithen <[EMAIL PROTECTED]> wrote: Hi, I am sending this mail again as no one has answered my previous mail, I am restating the problem I am facing and also have attached a sample to recreate the problem. I have a stateless session EJB which accesses a DB2 datasource created using the tranql generic connector. This uses the container managed transaction. I am also using the DB2 9.1 universal JDBC drivers. For methods dealing with datasource related operations I have set sessionContext.setRollBackOnly() within the catch block of SQLException.This throws exceptions when there have to be rollbacks at the database level. For example trying to insert a duplicate record throws the following exception:- com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10114][10307] Invalid operation: Explicit COMMIT or ROLLBACK is not allowed when in auto-commit mode. I have created an example to illustrate this and have attached the source with this mail. I think this is something related to Tranql. Is there any way to turn auto commit off? Can anyone please suggest a way around this? I have stuck with this for some time now. Thanks and regards, Vimalan
Rollbacks at database level throws exception in Geronimo
Hi, I am sending this mail again as no one has answered my previous mail, I am restating the problem I am facing and also have attached a sample to recreate the problem. I have a stateless session EJB which accesses a DB2 datasource created using the tranql generic connector. This uses the container managed transaction. I am also using the DB2 9.1 universal JDBC drivers. For methods dealing with datasource related operations I have set sessionContext.setRollBackOnly() within the catch block of SQLException.This throws exceptions when there have to be rollbacks at the database level. For example trying to insert a duplicate record throws the following exception:- com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10114][10307] Invalid operation: Explicit COMMIT or ROLLBACK is not allowed when in auto-commit mode. I have created an example to illustrate this and have attached the source with this mail. I think this is something related to Tranql. Is there any way to turn auto commit off? Can anyone please suggest a way around this? I have stuck with this for some time now. Thanks and regards, Vimalan SessionTestBean.java Description: Binary data SessionTestClient.java Description: Binary data SessionTestRemote.java Description: Binary data SessionTestRemoteHome.java Description: Binary data http://www.openejb.org/xml/ns/openejb-jar-2.1";> http://geronimo.apache.org/xml/ns/deployment-1.1";> Test Test 1.0 car jdbc Test 1.0 car SessionTestBean SessionTestBean testDataSource jdbc/Test http://java.sun.com/dtd/ejb-jar_2_0.dtd";> Test SessionTestBean com.test.ejb.SessionTestRemoteHome com.test.ejb.SessionTestRemote com.test.ejb.SessionTestBean Stateless Container testDataSource javax.sql.DataSource Container Shareable SessionTestBean * SessionTestBean * Required
