If you search the jira, you see several mentiones of this.
There are basically two robust ways to fix it:
- Change the colum type (to what depends on your dbms)
- Change the jBPM code to truncate the error in an intelligent way
The former is the most simple one.
Thank you Ronald