[ https://jira.jboss.org/jira/browse/JBPM-2403?page=com.atlassian.jira.plug... ] Mark Kedzierski logged work on JBPM-2403: ----------------------------------------- Author: Mark Kedzierski Created on: 09/Jul/09 11:48 AM Start Date: 09/Jul/09 11:00 AM Worklog Time Spent: 30 minutes Work Description: Set the execution.id before the hibernate save. Seems to be fixed. the fork now works. Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 30 minutes -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2403?page=com.atlassian.jira.plug... ] Mark Kedzierski commented on JBPM-2403: --------------------------------------- my process looks like this: <fork g="670,397,48,48" name="fork1"> <transition name="fork_upgrade" to="Add Upgrade Work Item"/> <transition name="fork_conversion" to="Conversion Scheduled"/> </fork> ... <join name="join1" g="817,123,48,48" multiplicity="2"> <transition to="Set Status Completed"/> </join> I am running in JBoss 5.1.0.GA. Using Microsoft SQL Server (by the way I have db schema scripts for mssql). A recent commit to DefaultIdGenerator added a call to session.save to save the new child process. But the save call was happening before the id was set on the execution. This resulted in a UniqueConstraint exception when saving the child process. all i did set the child execution's id before the save occurs. I also fixed a separate fork/join issue which shouldn't work in your tests. i'll make a separate JIRA issue. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2403?page=com.atlassian.jira.plug... ] Tom Baeyens resolved JBPM-2403. ------------------------------- Fix Version/s: (was: jBPM 4.x) Resolution: Cannot Reproduce Bug -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2403?page=com.atlassian.jira.plug... ] Jay Key commented on JBPM-2403: ------------------------------- I'm seeing the same behaviour in a standalone test case. When I use the built-in hsqldb database, it works fine, but when I switch the test case to run agains MS SQL 2005, I get the ConstraintViolationException when transitioning to the fork. -- 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