[jbpm-issues] [JBoss JIRA] Resolved: (JBPM-2297) Fork activities don't save child executions

Fork activities don't save child executions ------------------------------------------- Key: JBPM-2297 URL: https://jira.jboss.org/jira/browse/JBPM-2297 Project: JBoss jBPM Issue Type: Bug Security Level: Public(Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0.0.Beta2 Reporter: Alexis Seigneurin Assignee: Joram Barrez Attachments: ForkActivity.patch, sbox-creation.jpdl.xml When you create a fork activity, child executions are not saved in the session. The consequence is that, at some point, an execution with ID 0 is searched in the database: Exception in thread "main" org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [org.jbpm.jpdl.internal.model.JpdlExecution#0] at org.hibernate.impl.SessionFactoryImpl$1.handleEntityNotFound(SessionFactoryImpl.java:375) at org.hibernate.proxy.AbstractLazyInitializer.checkTargetState(AbstractLazyInitializer.java:79) at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:68) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:111) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:140) at org.jbpm.jpdl.internal.model.JpdlExecution$$EnhancerByCGLIB$$9a4d98d.createTask(<generated>) at org.jbpm.jpdl.internal.activity.TaskActivity.execute(TaskActivity.java:49) at org.jbpm.pvm.internal.model.op.ExecuteActivity.perform(ExecuteActivity.java:57) at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperationSync(ExecutionImpl.java:589) at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperation(ExecutionImpl.java:562) at org.jbpm.pvm.internal.model.ExecutionImpl.take(ExecutionImpl.java:444) at org.jbpm.pvm.internal.model.ExecutionImpl.take(ExecutionImpl.java:448) at org.jbpm.jpdl.internal.activity.ForkActivity.execute(ForkActivity.java:61) at org.jbpm.pvm.internal.model.op.ExecuteActivity.perform(ExecuteActivity.java:57) at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperationSync(ExecutionImpl.java:589) at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperation(ExecutionImpl.java:562) at org.jbpm.pvm.internal.model.ExecutionImpl.start(ExecutionImpl.java:201) at org.jbpm.pvm.internal.cmd.StartProcessInstanceInLatestCmd.execute(StartProcessInstanceInLatestCmd.java:63) at org.jbpm.pvm.internal.cmd.StartProcessInstanceInLatestCmd.execute(StartProcessInstanceInLatestCmd.java:39) at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42) at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:54) at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54) at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55) at org.jbpm.pvm.internal.svc.ExecutionServiceImpl.startProcessInstanceByKey(ExecutionServiceImpl.java:72) To fix the issue, in the ForkActivity class, the childExecution instances which are created must be saved. I attached a patch (though I guess there is another way to perform the save by using commands).