[
http://jira.jboss.com/jira/browse/JBESB-1511?page=comments#action_12396353 ]
Kevin Conner commented on JBESB-1511:
-------------------------------------
To clarify, I said that it appears to be a race condition likely to be caused by
misconfiguration. :)
The constraint violation is being raised because of a duplicate primary key insertion in
the following tables,
JBPM_LOG, JBPM_TRANSITION, JBPM_DELEGATION and JBPM_TOKEN.
We need to check the mechanism used by hibernate when generating these keys.
The jBPM does not work with PostgreSQL/Oracle - constraint
violations
---------------------------------------------------------------------
Key: JBESB-1511
URL:
http://jira.jboss.com/jira/browse/JBESB-1511
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1
Environment: CR1 - embedded
Reporter: Jiri Pechanec
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP1
Attachments: server.log.gz
When ESB is under load, the jBPM operations can start to generate constraint violation
exceptions - see attached log file. According to Kevin C. it means that there can be race
condition when Hibernate generates primary keys.
This issue is present on PostgreSQL/Oracle but is not present on MySQL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira