ID Generation for Oracle or DB2 Database when using out of the box JobExecutor causes Integrity Constraint violations with subprocesses --------------------------------------------------------------------------------------------------------------------------------------- Key: JBPM-2798 URL: https://jira.jboss.org/jira/browse/JBPM-2798 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Environment: WLS 11g, Oracle 11g, jBPM 4.3 Reporter: Martin Porter When using jBPM in default configuration with out of the box JobExecutors (2 threads) we see issues with ID generation causing Integrity Constraint violations. There is a long thread related to this as also this behaviour has been seen with DB2 as well as Oracle. The link to the thread is:- http://community.jboss.org/message/522625#522625 This seems to be related to the use of Subprocesses. It has been witnessed that removing the subprocesses solves the issue. Unfortunately we cannot do that. We solved the issue by implementing our own ID generator using an Oracle Sequence. I have attached the code to this case. It would be nice to have this added to the trunk code if possible. We have been testing with it and it solved all of our problems. Note that this was NOT running in cluster configuration and the problems occur on a single server instance with the default (non modifed) JobExecutor configuration. Regards martin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira