Bug 777834 (SOA-360)

Summary: The jBPM does not work with PostgreSQL/Oracle - constraint violations
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Jiri Pechanec <jpechane>
Component: Documentation, JBossESBAssignee: Joshua Wulf <jwulf>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 CR1CC: lcarlon
Target Milestone: ---   
Target Release: 4.2 CR3   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-360
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-07 04:10:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jiri Pechanec 2008-01-23 13:48:40 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Date of First Response: 2008-02-04 07:47:31
project_key: SOA

See JBESB-1511
Comment 1 Jiri Pechanec 2008-01-23 13:48:47 UTC 
Link: Added: This issue depends JBESB-1511
Comment 2 Jiri Pechanec 2008-01-23 13:49:08 UTC 
Link: Added: This issue related SOA-84
Comment 3 Mark Little 2008-02-04 12:47:31 UTC 
The ESB issue will be closed soon, leaving this as a docs issue only.

Josh, please look at Kevin's comment in JBESB-1511 for an indication of what we need to document in the notes.
Comment 4 Mark Little 2008-02-04 12:47:49 UTC 
Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]
Comment 5 Kevin Conner 2008-02-05 16:22:36 UTC 
The ESB issue has been closed but we still need to document this as a symptom of the optimistic locking.
Comment 6 Joshua Wulf 2008-02-07 02:28:50 UTC 
 JBPM operations fail with constraint violation exceptions using Oracle/PostgreSQL

When the server is under load JBPM operations have been observed to fail with a constraint violation exception when using Oracle or PostgreSQL. This has not been observed with MySQL. We've made calls to JBPM from the SOA server asynchronous and JBPM should retry these failures. It is a consequence of JBPM's optimistic locking policy.

   Further Information: http://jira.jboss.com/jira/browse/JBESB-1511.