Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-2138

JBPM_LOG table column 'exception' is too small, throws RE: ORA-01461: can bind a LONG value only for insert into a LONG column

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • jBPM 3.2.5 GA , jBPM-3.2.5.SP1, jBPM-3.2.5.SP2, jBPM 3.2.6 GA , jBPM-3.2.5.SP3, jBPM 3.2.6.SP1, jBPM-3.2.5.SP4, jBPM 3.2.5.SP5
    • None
    • Workaround Exists
    • Hide

      JBPM_LOG table column 'exception' is too small, it could become a clob.
      Alternatively, we could take care to trim to long stacktraces before inserting (method setException in class ActionLog)

      Show
      JBPM_LOG table column 'exception' is too small, it could become a clob. Alternatively, we could take care to trim to long stacktraces before inserting (method setException in class ActionLog)

      If an action throws an exception, the stack trace is logged in the JBPM_LOG table.
      However, in case of a very long stack trace (longer than 4000 characters), this throws an oracle Exception.
      "RE: ORA-01461: can bind a LONG value only for insert into a LONG column"

      The bug is difficult to trace, since the exception is only thrown at hibernate session.flush() and not at the actual insert...

      Actual exception stacktrace that presented the problem was the exception stacktrace of weblogic, 7200 chars. (the jbpm action was executing business logic running in its own transaction).

        1. Patch per JBTM-2138.patch
          1 kB
          Mauro Molinari

              aguizar_jira Alejandro Guizar (Inactive)
              gmournos_jira George Mournos (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: