com.oracle.bpel.client.delivery.ReceiveTimeOutException

Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.</faultstring> <detail> <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">ke3r34do2</ns1:hostname> </detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> ------------------ when i test the same service in other instance which is a stand-alone server, it is giving the result. The process is in such a way that it takes the sequence of products, do some orchestration and return the response. When i test the service with 45 products, it is failing in stage, and the same input is working in test instance. In stage instance, it is working with a maximum number of products is 36, if it more than that number, we are getting the fault. If i look into the audit trail of the instance, it is sometimes saying that the assign activity is pending or the java embedding activity is pending.It is not even going to the catch or catchAll branch, And the error message in the audit trail is as below... ------------- There is a system exception while performing the BPEL instance, the reason is "Cannot deserialize DOM element. Failed to deserialize the DOM element from binary format, the document id . The exception reported is ". Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point.less ORABPEL-09222 Cannot deserialize DOM element. Failed to deserialize the DOM element from binary format, the document id . The exception reported is

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 web42

  • via Oracle Community by NarsingPumandla, 11 months ago
    > </soapenv:Body> </soapenv:Envelope> ------------------ when i test the same service in other instance which is a stand-alone server, it is giving the result. The process is in such a way that it takes the sequence of products, do some orchestration and return
  • via Oracle Community by NarsingPumandla, 1 year ago
    > </soapenv:Body> </soapenv:Envelope> ------------------ when i test the same service in other instance which is a stand-alone server, it is giving the result. The process is in such a way that it takes the sequence of products, do some orchestration and return
  • via oracle.com by Unknown author, 1 year ago
    Waiting for response has timed out. The conversation id is null. Please check the process instance f or detail.
  • Stack trace

    • com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.</faultstring> <detail> <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">ke3r34do2<
    • s1:hostname> </detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> ------------------ when i test the same service in other instance which is a stand-alone server, it is giving the result. The process is in such a way that it takes the sequence of products, do some orchestration and return the response. When i test the service with 45 products, it is failing in stage, and the same input is working in test instance. In stage instance, it is working with a maximum number of products is 36, if it more than that number, we are getting the fault. If i look into the audit trail of the instance, it is sometimes saying that the assign activity is pending or the java embedding activity is pending.It is not even going to the catch or catchAll branch, And the error message in the audit trail is as below... ------------- There is a system exception while performing the BPEL instance, the reason is "Cannot deserialize DOM element. Failed to deserialize the DOM element from binary format, the document id . The exception reported is ". Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point.less ORABPEL-09222 Cannot deserialize DOM element. Failed to deserialize the DOM element from binary format, the document id . The exception reported is at com.collaxa.cube.xml.dom.XMLElement__CXPM.create(XMLElement__CXPM.java:141) at com.collaxa.cube.engine.core.PersistenceService.getObjectFromMoniker(PersistenceService.java:1208) at com.collaxa.cube.engine.core.PersistenceService.get(PersistenceService.java:591) at com.collaxa.cube.engine.core.PersistenceService.load(PersistenceService.java:419) at com.collaxa.cube.engine.types.bpel.CXElementVariable__CXPM.create(CXElementVariable__CXPM.java:61) at com.collaxa.cube.engine.core.PersistenceService.getObjectFromMoniker(PersistenceService.java:1208) at com.collaxa.cube.engine.core.PersistenceService.get(PersistenceService.java:591) at com.collaxa.cube.engine.core.BaseScope.getLocalVariant(BaseScope.java:138) at com.collaxa.cube.engine.core.Scope.getVariantRV(Scope.java:529) at com.collaxa.cube.engine.core.Scope.getObjectRV(Scope.java:474) at com.collaxa.cube.engine.core.Scope.getObject(Scope.java:874) at com.collaxa.cube.engine.ext.wmp.BPELAssignWMP.performCopyTo(BPELAssignWMP.java:974) at com.collaxa.cube.engine.ext.wmp.BPELAssignWMP.__executeStatements(BPELAssignWMP.java:215) at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:199) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3714) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1657) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:325) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5787) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1724) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.handleWorkItem(CubeEngineBean.java:348) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean_2rw8jy_ELOImpl.handleWorkItem(CubeEngineBean_2rw8jy_ELOImpl.java:309) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handle(PerformMessageHandler.java:45) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141) at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)

    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

    You’re the first here who have seen this exception.