[
https://jira.jboss.org/jira/browse/JBPM-2570?page=com.atlassian.jira.plug...
]
Ronald van Kuijk resolved JBPM-2570.
------------------------------------
Resolution: Incomplete Description
In addition, I close this issue marking it "incomplete" since it lacks a
unittest, is not discussed in the forum, contains a vague summary, is not tested with 4.1
etc...
Problem with Fork/Join
----------------------
Key: JBPM-2570
URL:
https://jira.jboss.org/jira/browse/JBPM-2570
Project: jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0
Environment: Windows xp, eclipse Version: 3.4.2 , using hibernate and spring.
Reporter: Sebastian Castellanos
Fix For: jBPM 4.x
Attachments: a.jpdl.xml
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
--
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