4 Replies Latest reply: Jan 14, 2013 8:22 AM by Kathar RSS

    Exception: ORABPEL-05007 is thrown when OSB throws fault to BPEL

    Kathar
      We are having a composite which connects to OSB using the direct binding. A Business fault is defined in the OSB direct binding sb proxy, we are trying to capture this business fault in BPEL when thrown by OSB.
      When we tested the OSB alone, we are seeing the business fault as a response. However BPEL is not receiving this fault and throws different exception, ORABPEL-05007.

      Should we have to raise a SR to resolve this? Thanks for your help in advance.

      Kathar
      --------------------------------------------------------------

      An internal exception has not been properly handled by the server.
      Set the logging level for all loggers to debug, and resubmit your request again. The server log should contain a more detailed exception report.
      Exception: ORABPEL-05007

      could not dispatch message because there is no active transaction.
      there is no active transaction while scheduling a message with the dispatcher.
      this usually happens if the underlying subsystem rollback back the transaction without bubbling up the system or transaction exception to the bpel layer.
      Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

      Handled As: com.collaxa.cube.CubeException
      ORABPEL-05007

      could not dispatch message because there is no active transaction.
      there is no active transaction while scheduling a message with the dispatcher.
      this usually happens if the underlying subsystem rollback back the transaction without bubbling up the system or transaction exception to the bpel layer.