Hide Forgot
Created attachment 1139087 [details] DataCorrection DB Error Description of problem: Deploying and executing bigapp DataCorection task results in H2 SQL error Version-Release number of selected component (if applicable): BPMS 6.3.0.ER1 How reproducible: Always Steps to Reproduce: 1. deploy bigapp repo and run example mortgage applicant witn JWS3 and H2 database 2. when DataCorrection task is generated, there is a H2 SQL error 3. See attached screenshot Actual results: SQL error Expected results: DataCorrection task is commited to Database Additional info:
JWS2 with H2 database is affected too.
Created attachment 1139114 [details] EWS2 catalina.out
Created attachment 1139115 [details] EWS3 catalina.out
Other databases affected with "Cannot commit transaction - ERROR: value too long for type character varying(4000)" modal dialog and catalina.out error log. Mysql55, Postgre84/93 with JWS2/3 and bigapp repo clonned.
Created attachment 1139117 [details] Mysql57 modal dialog
Created attachment 1139118 [details] mysql57 catalina.out
Created attachment 1139119 [details] Postgre84 modal dialog
Created attachment 1139120 [details] Postgre84 catalina.out
It looks like the String value of TaskVariableImpl.value needs to be checked (and preemptively shortened) before any persists or commits. We have similar code in other areas of the human-task code.
Any idea why this would only occur on JWS?
this certainly would fail on all contaienrs/servers as this was caused by too big variable size that was attempted to be stored in task variable log which max size is set to 4000 chars. I included same mechanism as we have for process variables - trim the content in case it's too long and issue warning into logs jbpm master: https://github.com/droolsjbpm/jbpm/commit/dd02ae909d7f105c117670887ead36af655ed3eb 6.4.x: https://github.com/droolsjbpm/jbpm/commit/cdceb70fc250994116620dc54d9261acf7bdfde1
BPMS 6.3.0.ER3