[
http://jira.jboss.com/jira/browse/JBESB-1511?page=all ]
Kevin Conner closed JBESB-1511.
-------------------------------
Resolution: Done
The ESB now signals the jBPM process in an asynchronous manner, any such failures should
be retried by jBPM.
The constraint violation is a symptom of the optimistic locking in jBPM and may still
occur.
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