[ https://jira.jboss.org/jira/browse/JBPM-2570?page=com.atlassian.jira.plug... ] Ronald van Kuijk updated JBPM-2570: ----------------------------------- Summary: Problem with Fork/Join (was: Problemas con Fork/Join) Description: I am having some problems with the Forks / join when I swimlane assigned. and I give it right yet. Perhaps you can think of something. I have a simple graph with 5 tasks. Task 1, Task 2 Task 3 Task 4 and Task 5. I also have a fork and two joins. The situation is like this: Start the process and the first thing is to launch a running 3 tasks Fork, Task 1, 2 and 3. swimlane which have different partners. of these 3 tasks, the Tarea1 and Tarea2 Join converge on the 1 that the join 1 continues the thread to the task 4. Task 4 has a transaction to Join 2, which is responsible for closing the task 3 (originally released with Tarea1 and Tarea2 but queaun not closed). When the proposal in Task 3 and 4 should continue to flow. Theoretically, it seems to be fine. Practically, it works the Fork / Join if you do not assign swimlane. But when the 3 swimlane assign different initial tasks T1 T2 and T3 gives problems, it is leaving me to close the first Fork. Because Tarea1 and have different Tarea2 swimlane (is giving me an error of foreign calve between the table of active jobs and the swimlane). From what I see, you want to delete the active task table after finishing a task, but not deleted from the table should swimlane and emerges as the foreign key error. This is the error. Could not delete: [org.jbpm.pvm.internal.task.SwimlaneImpl # 164]; nested exception is org.hibernate.exception.ConstraintViolationException was: Estoy teniendo unos problemas con los Forks/join cuando tengo swimlanes asignados. y no doy en el clavo aún. Quizá se te ocurra algo. Tengo un grafo sencillo, con 5 tareas. tarea 1, tarea 2 tarea 3 , tarea 4 y tarea 5. tambien tengo un fork y dos joins. La situacion es asi: Arranca el proceso y lo primero que hace es lanzar un Fork que ejecuta 3 tareas, Tarea 1 , 2 y 3. las cuales tienen diferentes swimlanes asociados. de esas 3 tareas, la Tarea1 y la Tarea2 convergen en el Join 1, que el join 1 continua el hilo hacia la tarea 4. La tarea 4 tiene una transaccion a un Join 2, que se encarga de cerrar la tarea 3 (inicialmente lanzada con la Tarea1 y la Tarea2, pero queaun no esta cerrada). una vez finaliada la tarea 3 y la 4 deberia continuar el flujo. Teoricamente, parece estar bien. Practicamente, funciona el Fork/Join si no le asigno swimlanes. Pero al momento de asignarle diferentes swimlanes las 3 tareas iniciales T1 T2 y T3 da problemas, no me esta dejando cerrar el primer Fork. Porque la Tarea1 y la Tarea2 tienen diferentes swimlanes (me esta dando un error de calve foranea entre la tabla de las tareas activas y la de los swimlanes). Por lo que veo, quiere borrar de la tabla de tareas activas una tarea luego de terminarla, pero no la borra de la tabla de swimlanes como deberia y surge el error de la clave foranea. Este es el error. could not delete: [org.jbpm.pvm.internal.task.SwimlaneImpl#164]; nested exception is org.hibernate.exception.ConstraintViolationException Translated description with Google... please next time post in English or use google translate yourself. -- 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-2570?page=com.atlassian.jira.plug... ] Alejandro Guizar updated JBPM-2570: ----------------------------------- Description: I am having some problems with the Forks / join when I have assigned swimlanes, and I can't figure it out yet. Perhaps you can think of something. I have a simple graph with 5 tasks. Task 1, Task 2 Task 3 Task 4 and Task 5. I also have a fork and two joins. The situation is like this: The process starts and the first thing it does is to launch a Fork that runs 3 tasks, Task 1, 2 and 3. which have different swimlanes associated to them. of these 3 tasks, Task 1 and Task 2 converge on Join 1, which continues the thread to task 4. Task 4 has a transition to Join 2, which is responsible for closing task 3 (originally launched with Task 1 and Task 2 but not yet closed). Once task 3 and 4 finish, the flow should continue. Theoretically, it seems to be fine. Practically, the Fork / Join work if I do not assign swimlanes. But when I assign different swimlanes to the initial tasks T1 T2 and T3 the process gives problems, it won't let me close the first fork. Because Task 1 and Task 2 have different swimlanes (it is giving me a foreign key error between the active task table and the swimlane table). From what I see, it wants to delete from the active task table after finishing a task, but it does not delete from the swimlane table, thus the foreign key error emerges. This is the error. Could not delete: [org.jbpm.pvm.internal.task.SwimlaneImpl # 164]; nested exception is org.hibernate.exception.ConstraintViolationException was: I am having some problems with the Forks / join when I swimlane assigned. and I give it right yet. Perhaps you can think of something. I have a simple graph with 5 tasks. Task 1, Task 2 Task 3 Task 4 and Task 5. I also have a fork and two joins. The situation is like this: Start the process and the first thing is to launch a running 3 tasks Fork, Task 1, 2 and 3. swimlane which have different partners. of these 3 tasks, the Tarea1 and Tarea2 Join converge on the 1 that the join 1 continues the thread to the task 4. Task 4 has a transaction to Join 2, which is responsible for closing the task 3 (originally released with Tarea1 and Tarea2 but queaun not closed). When the proposal in Task 3 and 4 should continue to flow. Theoretically, it seems to be fine. Practically, it works the Fork / Join if you do not assign swimlane. But when the 3 swimlane assign different initial tasks T1 T2 and T3 gives problems, it is leaving me to close the first Fork. Because Tarea1 and have different Tarea2 swimlane (is giving me an error of foreign calve between the table of active jobs and the swimlane). From what I see, you want to delete the active task table after finishing a task, but not deleted from the table should swimlane and emerges as the foreign key error. This is the error. Could not delete: [org.jbpm.pvm.internal.task.SwimlaneImpl # 164]; nested exception is org.hibernate.exception.ConstraintViolationException Provided human translation :) The process definition is somewhat esoteric, the kind you see in BPM demos to show how twisted your model can be, but rarely in real usage. I'd suggest a second fork be introduced after Fork 1 but before Task 1 and Task 2 to correctly balance Join 1. The current Fork implementation won't cope with the process definition as stated in the description. -- 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-2570?page=com.atlassian.jira.plug... ] Sebastian Castellanos commented on JBPM-2570: --------------------------------------------- Thanks Alejandro. I tried your solution but still does not work and even another problem When I put one seconds Fork, Fork1 after and before the Task 1 and Task 2, when the process reaches alk Fork, launched 3 tasks instead of two. (Task 1, Task 2 and Task 1 again). This repeating task 1. I think that happens when you put two nested Forks without closing the first. Be trying to solve this. Of course, thank you very much. Greetings. Sebastian. -- 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-2570?page=com.atlassian.jira.plug... ] Alejandro Guizar commented on JBPM-2570: ---------------------------------------- Sebastian, I might have gone overboard when describing your process as 'esoteric'. I am very interested in taking jBPM to its limits and being able to model advanced processes as yours. I am reopening this issue, but I'd appreciate your help in coming up to define a concrete unit test that I can incorporate into the test suite. -- 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-2570?page=com.atlassian.jira.plug... ] Ronald van Kuijk commented on JBPM-2570: ---------------------------------------- Hmm... I really need your unittest, since even without the fix from JBPM-2749, I can close 3 and 4 (9 in your example) in different orders and 5 (8 in your example) is always fine without any exceptions. Maybe it has been fixed by other check-ins. -- 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-2570?page=com.atlassian.jira.plug... ] Ronald van Kuijk commented on JBPM-2570: ---------------------------------------- Alex, With a lack of a unittest and with one I kind of created myself, it works. Joram did some checkins for fork/join behaviour in BPMNl, so I'd resolve this in one way or another as 'fixed' or whatever... Sebastian has not provided any info for about a month. I'll check in this test with a name refering to this 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-2570?page=com.atlassian.jira.plug... ] Huisheng Xu updated JBPM-2570: ------------------------------ Attachment: JBPM-2570.patch cannot reproduce, attach a testcase to verify the reult. -- 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/browse/JBPM-2570?page=com.atlassian.jira.plugin.sy... ] Alejandro Guizar resolved JBPM-2570. ------------------------------------ Resolution: Done Changing resolution from "cannot reproduce" to "done" as the issue did exist at some point, but was fixed by other updates. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira