[jbpm-issues] [JBoss JIRA] Resolved: (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

JBPM_LOG table column 'exception' is too small, throws RE: ORA-01461: can bind a LONG value only for insert into a LONG column ------------------------------------------------------------------------------------------------------------------------------ Key: JBPM-2138 URL: https://issues.jboss.org/browse/JBPM-2138 Project: jBPM Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 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 Environment: jbpm 3.2.6 on an oracle server, any application server or OS Reporter: George Mournos Assignee: Alejandro Guizar Labels: jbpm3, exception, column, log Attachments: Patch per JBTM-2138.patch 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).