Red Hat Bugzilla – Bug 809772
SessionInfo, Lob and DB2 --> SQLCODE=-302
Last modified: 2016-09-20 01:16:17 EDT
Created attachment 575083 [details]
stack trace in the server log
Description of problem:
Running jbpm console test with DB2 9.7 resulted in:
DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.12.55
Could not synchronize database state with session
org.hibernate.exception.DataException: could not update: [org.drools.persistence.info.SessionInfo#1]
The sql code specifies that "DB2 received data that was invalid or too large to fit in the corresponding column of the table."
Version-Release number of selected component (if applicable):
BRMS 5.3.0 ER5
It is quite probable this is due to the attribute:
private byte rulesByteArray
of the class SessionInfo in org.drools.persistence.info, which does not specify the size of the column. It seems as if the DB2 database defaults to 1M, which might not be enough - see link below.
Should be fixed as a side effect of bug 807595 comment 5.
Update status to ON_QA. Please verify them against ER6.
I see no change.
Lukas, you put it on MODIFIED about a month back, do you remember why?
(In reply to comment #6)
> I see no change.
> Lukas, you put it on MODIFIED about a month back, do you remember why?
See comment 3.
It looks like this failed the QA tests? If you could post any stack traces, other info or any ideas why it failed, that would be great.
(In reply to comment #8)
> It looks like this failed the QA tests? If you could post any stack traces,
> other info or any ideas why it failed, that would be great.
is the whole server log of a recent run with ER6. Hope it helps.
And sorry, I somehow didn't see the 3rd comment.
I hadn't modified the drools classes that had lob columns.
I've just pushed a commit to the community drools 5.2.x branch that fixes this:
Fixed string blobs as well, and pushed to community jbpm 5.2.x branch:
The fixed for this issue should be included in ER7. Please do verification on it.