Bug 876551 - DB2 & ee6 bundle & human tasks - SQLCODE=-302
DB2 & ee6 bundle & human tasks - SQLCODE=-302
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5, jBPM Console (Show other bugs)
BRMS 5.3.1
Unspecified Unspecified
unspecified Severity urgent
: CR1
: BRMS 5.3.1 GA
Assigned To: Shelly McGowan
Lukáš Petrovický
: Regression
Depends On:
  Show dependency treegraph
Reported: 2012-11-14 07:43 EST by Zuzana Krejčová
Modified: 2016-09-20 01:16 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
server log from the test suite (467.11 KB, text/plain)
2012-11-14 07:43 EST, Zuzana Krejčová
no flags Details
Guvnor repo export used to test the console (836.36 KB, text/xml)
2012-11-21 09:49 EST, Lukáš Petrovický
no flags Details
Log showing the DB2 SQL Error: "SQLCODE=-530, SQLSTATE=23503, SQLERRMC=DB2JBPM.TASK.FK27A9A56CE1EF3A" (78.56 KB, text/x-log)
2012-11-28 20:40 EST, Marco Rietveld
no flags Details

  None (edit)
Description Zuzana Krejčová 2012-11-14 07:43:20 EST
Created attachment 644796 [details]
server log from the test suite

Description of problem:
I'm using EAP 6.0 and BRMS ee6 deployable bundle with DB2-97 database. (I'm testing this via the Console.)
Whenever a new process instance is being created for a process with human task, the task is created but the process instance creation fails with DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.13.80.
Everything runs fine with EAP 5.1 and "basic" deployable bundle on DB2 and also with the ee6 bundle on other databases.

Version-Release number of selected component (if applicable):
BRMS 5.3.1 ER4

Steps to Reproduce:
1. Create a process with some human task.
2. Start a new instance of the process (via Console). 
3. Fill in the process taskform.

Actual results:
Server logs show DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, task can be accessed (completed, released) but process seems not to be created.

Additional info:
ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-localhost/ DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.13.80
WARN  [com.arjuna.ats.arjuna] (http-localhost/ ARJUNA012125: TwoPhaseCoordinator.beforeCompletion - failed for SynchronizationImple< 0:ffff0a105875:-2c7cda9e:50a369a0:33e, org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization@7636d845 >: javax.persistence.PersistenceException: org.hibernate.exception.DataException: DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.13.80
at org.jbpm.integration.console.CommandDelegate.startProcess(CommandDelegate.java:120) [jbpm-gwt-core-5.3.1.BRMS-ER4.jar:5.3.1.BRMS-ER4]
Comment 1 Marco Rietveld 2012-11-20 08:59:15 EST
Links/info found: 


Search for code 22001:


Initial thoughts: blob definition in the HT schema is not long enough and there's a value longer than the database field being stored. That's why the following annotation has been added in the HT schema: 

    @Lob @Column(length=65535)

This ensures that DB2 creates/uses a blob field in the database of the appropriate length, sinde DB2 has multiple different BLOB types and by default uses the smallest one (256? ). 

I can't find the appropriate info on an ibm page, but this confirms the blob/length problem: 


(Maybe length= needs to be bigger? )
Comment 2 Marco Rietveld 2012-11-21 09:34:44 EST
Zuzanna, could you attach the BPMN2 processes that you've used to reproduce this issue?
Comment 3 Lukáš Petrovický 2012-11-21 09:49:48 EST
Created attachment 649270 [details]
Guvnor repo export used to test the console

Attaching the repo export that we use to test the console with. The bug should be demonstrable on the Evaluation example.
Comment 5 Marco Rietveld 2012-11-28 20:40:55 EST
Created attachment 653911 [details]
Log showing the DB2 SQL Error: "SQLCODE=-530, SQLSTATE=23503, SQLERRMC=DB2JBPM.TASK.FK27A9A56CE1EF3A"

I've pushed the following commit to the 5.2.x which fixes the bug/error shown in the original server.log: 


The problem is that while the other Lob fields all had @Column annotations forcing DB2 to use an appropriately large Lob type for the specific field, the ProcessInstanceInfo class is mapped using XML. The <column length="..." /> needed to be added to the JPA 2 XML mapping used in the gwt-console-server EE6 war. 

However, once that was fixed, another error started showing up (see attached log: "server-SQLCODE-530-TASk-FK-ACTUAL-OWNER.log"). 

This log references a Foreign Key (constraint) that's placed on the Task.actualOwner_id field (which refers to the id field in the OrganizationalEntity table).
Comment 6 Marco Rietveld 2012-11-28 20:42:43 EST
Zuzana, could you confirm that

1. the 302/22001 error is now gone? 
2. you're also seeing the 530 error? 

Comment 7 Marco Rietveld 2012-11-29 04:54:10 EST
I was able to confirm that the FK constraint was due to the users not being present in the DB. 

I've rerun the process without any errors -- setting the BZ to modified.

Note You need to log in before you can comment on or make changes to this bug.