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 Bernd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922326#3922326 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922326 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
