[esb-issues] [JBoss JIRA] Commented: (JBESB-1511) The jBPM does not work with PostgreSQL/Oracle - constraint violations

[Kevin Conner (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-1511?page=comments#action_12397310 ] 
            
Kevin Conner commented on JBESB-1511:
-------------------------------------

This is a symptom of concurrent accesses to jBPM.  The correct fix is to make the signalling of the process instance asynchronous and have the jBPM MessageService/JobExecutor handle transaction failures and retries.

The Command has been modified to use the same asynchronous mechanism used by JBESB-1483, thereby passing over responsibility for the signal (and all subsequent work) to jBPM.


> 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