com.ibm.ws.exception.WsException

DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: Cannot call 'cleanup' on a ManagedConnection while it is still in a transaction..

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web167

  • via Oracle Community by 843830, 9 months ago
    DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: Cannot call 'cleanup' on a ManagedConnection while it is still in a transaction..
  • via narkive.com by Unknown author, 1 year ago
    DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: Cannot call 'cleanup' on a ManagedConnection while it is still in a transaction..
  • DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: Cannot call 'cleanup' on a ManagedConnection while it is still in a transaction..
  • Stack trace

    • com.ibm.ws.exception.WsException: DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: Cannot call 'cleanup' on a ManagedConnection while it is still in a transaction.. at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:224) at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:175) at com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException(AdapterUtil.java:232) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions(WSRdbManagedConnectionImpl.java:3262) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup(WSRdbManagedConnectionImpl.java:2902) at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1331) at com.ibm.ejs.j2c.poolmanager.FreePool.cleanupAndDestroyMCWrapper(FreePool.java:618) at com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(FreePool.java:427) at com.ibm.ejs.j2c.poolmanager.PoolManager.release(PoolManager.java:1471) at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:1860) at com.ibm.ejs.j2c.LocalTransactionWrapper.enlist(LocalTransactionWrapper.java:662) at com.ibm.ejs.j2c.ConnectionEventListener.localTransactionStarted(ConnectionEventListener.java:574) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processLocalTransactionStartedEvent(WSRdbManagedConnectionImpl.java:1660) at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.beginLocalTransactionIfNecessary(WSJdbcConnection.java:447) at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.beginTransactionIfNecessary(WSJdbcConnection.java:608) at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.createStatement(WSJdbcConnection.java:1069) at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.createStatement(WSJdbcConnection.java:1048) at com.in1.util.BaseDBBean.queryOne(BaseDBBean.java:93) at com.in1.ap.business.para.DynamicPageUtil.getDp_define(DynamicPageUtil.java:74) at com.in1.ap.business.para.DynamicPageUtil.getDynamicPageInfo(DynamicPageUtil.java:34) at com.in1.ap.business.para.DynamicPage.getRemindList(DynamicPage.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    1 more bugmates