javax.transaction.SystemException

Commit can b e issued only when there are no requests awaiting responses. Currently there is one such request

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 web178

  • via Oracle Community by 3004, 1 year ago
    Commit can b e issued only when there are no requests awaiting responses. Currently there is one such request
  • Commit can be issued only when there are no requests awaiting responses. Currently there is one such request
  • Commit can be issued only when there are no requests awaiting responses. Currently there is one such request]
  • Stack trace

    • javax.transaction.SystemException: Commit can b e issued only when there are no requests awaiting responses. Currently there is one such request at weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:989) at weblogic.transaction.internal.TransactionImpl.enforceCheckedTransaction(TransactionImpl.java:1499) at weblogic.transaction.internal.TransactionImpl.checkIfCommitPossible(TransactionImpl.java:1477) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:230) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:208) at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:278) at com.ejb.sb.SBAccountBean_6uugr6_EOImpl.getAccountDetails(SBAccountBean_6uugr6_EOImpl.java:212) at java.lang.reflect.Method.invoke(Native Method) at weblogic.webservice.component.slsb.SLSBInvocationHandler.invoke(SLSBInvocationHandler.java:84) at weblogic.webservice.core.handler.InvokeHandler.handleRequest(InvokeHandler.java:78) at weblogic.webservice.core.HandlerChain.handleRequest(HandlerChain.java:131) at weblogic.webservice.core.DefaultOperation.process(DefaultOperation.java:539) at weblogic.webservice.core.DefaultWebService.invoke(DefaultWebService.java:264) at weblogic.webservice.server.servlet.ServletBase.serverSideInvoke(ServletBase.java:362) at weblogic.webservice.server.servlet.WebServiceServlet.serverSideInvoke(WebServiceServlet.java:269) at weblogic.webservice.server.servlet.ServletBase.doPost(ServletBase.java:346) at weblogic.webservice.server.servlet.WebServiceServlet.doPost(WebServiceServlet.java:237) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412) at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)

    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, 11 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 2 years ago
    Unknown user
    Once, 1 year ago