Hide Forgot
Date of First Response: 2009-05-07 03:59:04 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/292971 project_key: SOA
Link: Added: This issue depends JBPM-2115
Link: Added: This issue depends JBPM-2116
Help Desk Ticket Reference: Added: https://enterprise.redhat.com/issue-tracker/292971
After switching to the new DB2 9.7 server in the QA lab, the core test suite does not hang anymore. http://hudson.qa.jboss.com/hudson/view/JBPM3/job/jbpm3-jdk15/31/
The issue is still there - test suite passes with version 9.7 With version 9.1 it hangs on test org.jbpm.jbpm2094.JBPM2094Test With version 8.2 it hangs on test org.jbpm.jbpm2094.JBPM2094Test too As EAP 4.3 is certified on 8.2 and 9.1 it is irrelevant for us that test passes on 9.7 because SOA-P WILL NOT be certified on that version - see http://www.jboss.com/products/platforms/application/testedconfigurations/ The branch under test was https://anonsvn.jboss.org/repos/jbpm/jbpm3/tags/jbpm-3.2.7.CR1
Since jBPM 3.2.7 runs fine with various other databases, this must be a version-specific issue. http://hudson.qa.jboss.com/hudson/view/JBPM3/job/jbpm3-jboss423/ It is hard to diagnose a hangup on a remote database given the lack of access to resource consumption data and logs. I'd like to have the help of someone who has worked with these versions of DB2 and has full access to the databases. Diagnosing the problems will not take a few hours, tough. If you agree we can exclude the failing tests and document the limitations on these versions of DB2.
Hey Len, SOA-1241 is definitely not a problem in DB2 9.7. I confirmed this in both my local installation and the QA lab. -Alejandro
According to engineering response, this should be closed as a "will not fix". Please do.
Won't fix, issue does not occur in DB2 9.7.
SOA-P 4.3 is based on EAP 4.3 which is certified on DB2 9.1 and 8.2.7 It means that SOA-P will not be certified on 9.7 and if the issue will not be fixed that it will not be ceritified on DB2 at all http://www.jboss.com/products/platforms/application/supportedconfigurations/#JEAP4.3
Link: Added: This issue is duplicated by SOA-2207
Here is anecdotal advice from the administrator of a sizable DB2 farm who has been involved with a jBPM project. Quote: I was just looking at lock-related issues regarding jBPM and DB2 and I came across JBPM-2115. I see that it is solved by either using DB2 9.7 or by starting a single job executor thread. The latter solution does not seem really desirable. The problem lies in transactions waiting to lock records on JBPM_LOG and JBPM_JOB. There is a way to increase transaction concurrency by skipping inserted records that have not been committed. Maybe it solves the above problems more substantially than throwing multithreading overboard. It is more specifically about the relatively harmless option DB2_SKIPINSERTED. More information can be found here: www.ibm.com/developerworks/db2/library/techarticle/dm-0509schuetz/ This is useful for 98% of the applications. Pay particular attention if problems occur, namely, if an application does not update records, but does delete/insert combinations instead. Then the changes are temporary lost because other transactions read the delete, but skip the insert.
Link: Added: This issue related SOA-2570
Is this issue still pertinent?
After talking with Jiri and Len, we've agreed to close this issue for the following reasons: - This issue concerns SOA-P 4.3 and DB2 8.2 - We no longer certify with DB2 8.x. - SOA-P 5.x is certified with DB2 9.7 only.