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
  1. 0

    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).
  2. 0

    BPEL Transaction Inactive : Instance terminated without handling the Error

    Oracle Community | 2 years ago | Balaji Radhakrishnan
    java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.. 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 "-242" 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. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
  3. 0

    How to create WebLogic JCA connection factory ?

    Oracle Community | 6 years ago | 852806
    java.sql.BatchUpdateException: ORA-00942: table or view does not exist . Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "942" 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. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    BPEL Transaction Inactive : Instance terminated without handling the Error

    Oracle Community | 2 years ago | Balaji Radhakrishnan
    java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.. 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 "-242" 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.
  6. 0

    Business service failed to insert the data in DB2

    Oracle Community | 5 years ago | 924244
    java.sql.BatchUpdateException: [IBM][CLI Driver][DB2/LINUXX8664] SQL0798N A value cannot be specified for co umn "SEARCH_ID" which is defined as GENERATED ALWAYS. SQLSTATE=428C9 . Please see the logs for the full DBAdapter logging output prior to this exception. ConnectionFactory property platform lassName was set to org.eclipse.persistence.platform.database.oracle.Oracle10Platform but the database you are connecti g to is DB2/LINUXX8664. Please validate your platformClassName setting. This mismatch can cause the adapter to trigge runtime exceptions or execute SQL that is invalid for the database you are connected to. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCo es with value "--798" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these omposite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties ar integers.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    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