[jbpm-issues] [JBoss JIRA] Commented: (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
[
https://jira.jboss.org/jira/browse/JBPM-2138?page=com.atlassian.jira.plug...
]
Mauro Molinari commented on JBPM-2138:
--------------------------------------
We encountered this bug and it's blocking for us. We patched jBPM to cut at 4000 chars
in a really simple way:
public void setException(Throwable throwable)
{
StringWriter stringWriter = new StringWriter();
throwable.printStackTrace(new PrintWriter(stringWriter));
exception = stringWriter.toString();
if(exception.length() > 4000)
{
final String cutMessage = "\\nStack trace cut (longer than 4000 chars)";
exception =
exception.substring(0, 4000 - cutMessage.length()).concat(cutMessage);
}
}
I know this is a very dumb solution, however it works reasonably well in most cases.
Please consider this (or a better fix) to be included in jBPM next release, as the
workaround isn't really a workaround, in the sense that a patch to jBPM is actually
needed...
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://jira.jboss.org/jira/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
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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira