0 Replies Latest reply on Feb 8, 2006 12:14 PM by Bernd Ruecker

    Store long Exceptions in Logs cause problems with Oracle

    Bernd Ruecker Master

      We have a timer which has catched a exception. This Exception is then stored
      in the Database.

      When the timer then succeeds the Exception is copied to a JBPM_LOG Entry, and then Oracle throws a Exception:

      Caused by: java.sql.BatchUpdateException: ORA-01461: can bind a LONG value only for insert into a LONG column

      I think, this is because the Exception-Column can only take a VARCHAR2. Is there a possibility to get a bigger field? Or can we make a CLOB and Hibernate mappes it correctly by itself?

      Or I think in that case, jbpm should truncate the String, would be better than a exception...

      Or is this solved with jbpm 3.1 already?

      Thanks in advance