java.sql.BatchUpdateException: ORA-02049: timeout: distributed transaction waiting for lock . Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-2049" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ]] [2012-04-30T05:37:57.430+00:00] [soa_ms_1] [ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-6] [userId: <anonymous>] [ecid: afc045960fbe82d9:1030c9fe:136c518bccd:-8000-00000000001c16f1,0:1:100109689] [APP: soa-infra] Failed to handle dispatch message ... exception ORABPEL-05002[[ Message handle error. error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled. failure to handle a fault thrown from a scope, by any blocks in the scope chain. This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope. A top-level fault handler should be added to the flow to handle faults not caught from within the flow. This error contained an exception thrown by the message handler. Check the exception trace in the log (with logging level set to debug mode). ORABPEL-05002 Message handle error. error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled. failure to handle a fault thrown from a scope, by any blocks in the scope chain. This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope. A top-level fault handler should be added to the flow to handle faults not caught from within the flow. This error contained an exception thrown by the message handler. Check the exception trace in the log (with logging level set to debug mode).

Oracle Community | Roseanne | 5 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 1

    ORA-02049: timeout: distributed transaction waiting for lock

    Oracle Community | 5 years ago | Roseanne
    java.sql.BatchUpdateException: ORA-02049: timeout: distributed transaction waiting for lock . Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-2049" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ]] [2012-04-30T05:37:57.430+00:00] [soa_ms_1] [ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-6] [userId: <anonymous>] [ecid: afc045960fbe82d9:1030c9fe:136c518bccd:-8000-00000000001c16f1,0:1:100109689] [APP: soa-infra] Failed to handle dispatch message ... exception ORABPEL-05002[[ Message handle error. error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled. failure to handle a fault thrown from a scope, by any blocks in the scope chain. This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope. A top-level fault handler should be added to the flow to handle faults not caught from within the flow. This error contained an exception thrown by the message handler. Check the exception trace in the log (with logging level set to debug mode). ORABPEL-05002 Message handle error. error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled. failure to handle a fault thrown from a scope, by any blocks in the scope chain. This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope. A top-level fault handler should be added to the flow to handle faults not caught from within the flow. This error contained an exception thrown by the message handler. Check the exception trace in the log (with logging level set to debug mode).

    Root Cause Analysis

    1. java.sql.BatchUpdateException

      ORA-02049: timeout: distributed transaction waiting for lock . Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-2049" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ]] [2012-04-30T05:37:57.430+00:00] [soa_ms_1] [ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-6] [userId: <anonymous>] [ecid: afc045960fbe82d9:1030c9fe:136c518bccd:-8000-00000000001c16f1,0:1:100109689] [APP: soa-infra] Failed to handle dispatch message ... exception ORABPEL-05002[[ Message handle error. error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled. failure to handle a fault thrown from a scope, by any blocks in the scope chain. This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope. A top-level fault handler should be added to the flow to handle faults not caught from within the flow. This error contained an exception thrown by the message handler. Check the exception trace in the log (with logging level set to debug mode). ORABPEL-05002 Message handle error. error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled. failure to handle a fault thrown from a scope, by any blocks in the scope chain. This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope. A top-level fault handler should be added to the flow to handle faults not caught from within the flow. This error contained an exception thrown by the message handler. Check the exception trace in the log (with logging level set to debug mode).

      at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage()
    2. com.collaxa.cube
      BaseDispatchTask.run
      1. com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:207)
      2. com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
      3. com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
      3 frames
    3. Java RT
      Thread.run
      1. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      2. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      3. java.lang.Thread.run(Thread.java:662)
      3 frames