2:32 p.m.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0, jBPM 4.1
Reporter: Alexis Seigneurin
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to end1"
/>
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
2:34 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Alexis Seigneurin updated JBPM-2537:
------------------------------------
Attachment: workflow-test-jbpm4.1.zip
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Attachments: workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
2:36 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Alexis Seigneurin updated JBPM-2537:
------------------------------------
Attachment: screenshot-1.jpg
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
1:24 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Tom Baeyens updated JBPM-2537:
------------------------------
Fix Version/s: jBPM 4.3
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
1:26 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Joram Barrez commented on JBPM-2537:
------------------------------------
Indeed, this is an issue.
Added a testcase to the test suite, see TaskTimerTest. Uncomment the last 2 lines to make
the task fail on trunk. Uncomment ofc when fixed.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
2 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2537:
----------------------------------------
Should behaviour be identical to jBPM 3? I think it should. That is the most logical.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
2:21 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Joram Barrez commented on JBPM-2537:
------------------------------------
The most logical is not necessarily what was in 3 ;-)
But you are right: in 3, the task is kept open, but it can't be completed anymore. The
only option is than to delete the task. Imo, this makes sense.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
3:19 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2537:
----------------------------------------
hahha... sorry, I also meant that you could make it configurable per task with an
attribute in jPDL. Then you have the choice
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
8:11 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2537:
----------------------------------------
See the duplicate issue (#JBPM-2537) for an additional test
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
8:50 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
I would appreciate it if this could be fixed in 4.2 since I consider this a real
show-stopper.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
7:55 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
So if the default behaviour was to keep the task open but allow to delete and if this
still makes sense as stated by Jorama, why not target this at 4.2? The problem with this
that you are modelling something fine and really usual but it will lead you to an
undeleteable and uncompleteable task. AFAIK the executionId is stored within the task
object but since the execution is deleted anyway afterwards when the scope is back to the
main execution what's the problem with allowing the task to be deleted?
I consider this to be as important as to be fixed in 4.2.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
7:59 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
See the discussion in the forum:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=161642
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
10:07 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
Should be closed since this is fixed in jBPM 4.2. See the changelog and JBPM-2559.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
10:24 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
Is the behaviour which is desired here already implemented for the group activity or what
will happen to an open user task (user activity) within a group activity when a time
fires? See JBPM-2413
http://docs.jboss.com/jbpm/v4/devguide/html_single/#grouptimer
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
10:44 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Tom Baeyens updated JBPM-2537:
------------------------------
Priority: Critical (was: Major)
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Priority: Critical
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
2:27 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Joram Barrez commented on JBPM-2537:
------------------------------------
See http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263548#... for
latest discussions
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Priority: Critical
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
11:06 a.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Tom Baeyens reassigned JBPM-2537:
---------------------------------
Assignee: Tom Baeyens
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
11:08 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-2537:
-----------------------------------
notes for my own memory:
2 aspects to this:
1) by default tasks should get closed properly when a timer fires, task is cancelled or
any other abnormal task ending.
2) verify that upon abnormal ending of a task, the history should contain from when till
when it was open and to whom it was assigned and what the abnormal reason for termination
of that task was.
(upgrade tests will probably fail after this gets fixed)
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
6:50 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
Joram checked in the attached text into the cvs. but a clearer test case can be found in
the duplicated issue linked from this one.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
11:33 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
Joram checked in the attached tests into the repository but a clearer and simpler test
case can be found in the duplicated issue linked from this one.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.3
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
4:22 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Tom Baeyens updated JBPM-2537:
------------------------------
Fix Version/s: jBPM 4.4
(was: jBPM 4.3)
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
9:20 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2537:
----------------------------------------
My results so far, please comment:
Deleting a task via task.delete() is not an option if a task belongs to an execution. So a
task.timeout() is introduced and a HistoryTask.STATE_TIMEDOUT as well.
All relevant data mentioned by Tom is in the history database, including the outcome taken
by the timer (never know where that might come in handy)
There is only one problem. The timer generally signals the execution (as can be done by
the user). The only param that is passed on is the outcome. So it is impossible to
differentiate between a timeout and a normal signal of the execution.
Personally I'd like to have an additional param that a signal is the cause of a
timeout. The signal name now is equal to the transition name. No help at all here... So
giving a specific and different reason when just signalling the execution is not possible.
Thoughts? Using the params map in the signal?
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
10 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2537:
----------------------------------------
The params map is treated as variables, so I can add one to it, and remove it in the
TaskActivity, but that does not count for other Activities (well, I could change them but
that is a really ugly abuse).
But everything really feels like a hack. Maybe something with the Signal or
AtomicOperation should be done but that is for others to find out.... Think this one is
(currently) over my head to solve in a neat way.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
9:14 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
Any news from Tom on this? This issue has been unsolved for a while and this might be
important for the implementation of BPMN2. Does the spec say someething about the
behaviour (transition with a timer coming from a user activity not performed) in BPMN2?
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
10:27 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
You have announced in the forums to post your patch here, Ronald. It would be very kind of
you if you could do this because I'd like to have a look at it. I personally like your
idea (additional parameter) though I have no idea if this has effects on other things.
This issue has been a long-term one. I am really wondering how people implement escalation
right now in projects. Are they all just re-assigning tasks in case of a timeout?
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
9:11 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk updated JBPM-2537:
-----------------------------------
Attachment: jbpm-2537-patch
Not an official patch since it 'abuses' a parameter list (for variables, but no
sweat, it is not stored, but removed before it can be stored). If others could try, then
the direction is good and it just needs a little more work.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
12:22 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
The TaskActivity is signaled when the task belonging to its execution is completed. I see
a paramter signalName in the parameter-list of the signal-funciton. What is this parameter
used for? Is a signal-name passend when you complete a task regularly?
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
9:22 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2537:
----------------------------------------
The TaskActivity is ended when the timer belonging to it is completed. The parameter list
is the 'abuse' I mentioned. It is normally for passing variables to the task. Now
I set one, and remove it afterwards. That is where an additional official parameter should
be introduced. The thing is that that would touch/influence much more. So I want to be
sure the basics work at least We could indeed also 'abuse' the signal name one
way or another. Take a look... be creative. I know you can do that ;-)
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
7:28 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
Can you give an example where the use of an additional parameter would influence
something?
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
8:06 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2537:
----------------------------------------
The timer does not know what it is signalling. It could be every one of the activities. So
if the signature of the signal method is changed in any way, it has to be changed for all
activities. Also the ones that are already developed by others. The same is true for e.g.
wrapping the current signal method in a timeout method. Maybe we can check via some kind
of reflection if a specific method is there and if not, use the current method. It's
all about the ExternalActivityBehaviour interface.
But to some extend, abusing this parameter variable is just as wrong. If existing
implemented activities doe not strip the JBPM_TIMEOUT of, there is an additional variable.
Or using the signal name to append/prepend something... or....
So in any case, we are most likely going to break backwards compatibility... unless I miss
something
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
8:15 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2537:
----------------------------------------
HHHHHOOOOOOOOOOO, there is an option.... the timer DOES know what it is executing for....
execution.getActivity.getActivityBehaviour() returns the class type of the activity....
This was one of my greatest puzzles when implementing parts of BPMN2.
So we could add the timeout method to the ExternalBehaviour or only 'abuse' the
parameter list or... and just have this take place when signalling the taskActivity...
Personally I'd opt for the timeout method...
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
8:32 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
So in case a time fires and finds that AcitivityBehaviour is a TaskActivity it will invoke
a method on the class implementing the behaviour which then performs the necessary steps?
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
11:22 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
I tried adding a new timeout-method and it seems I can really use
getActivity.getActivityBehaviour() to get the ActivityImpl and afterwards I can check if
with getType() which kind of activity is this. But I end up in the Timer implementation of
the PVM. Would be a bad idea to cast to a jPDL-class there to call the method. I am
confused.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
11:51 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
Using the ExternalActivityBehaviour seems to be a bad idea. Could it be that we need a new
Interface for this? The first is used throughout the code and it does not make sense to
implement a timeout-method in all the places the interface is used.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, screenshot-1.jpg, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
12:56 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider updated JBPM-2537:
--------------------------------------
Attachment: jbpm-2537-patch-method.patch
experimental patch for this issue with uses a separate timeout-method
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch, screenshot-1.jpg,
workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
1 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider updated JBPM-2537:
--------------------------------------
Attachment: process.jpdl.xml
process definition for extended test case
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, process.jpdl.xml, screenshot-1.jpg,
workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
1 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider updated JBPM-2537:
--------------------------------------
Attachment: jbpm-2537-patch-method.patch
the last one was missing the new class TaskTimeout
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, process.jpdl.xml, screenshot-1.jpg,
workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
1:02 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider updated JBPM-2537:
--------------------------------------
Attachment: TaskTimeoutTest.java
unit-test for the patch
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, process.jpdl.xml, screenshot-1.jpg, TaskTimeoutTest.java,
workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
1:04 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
Ronald, Tom or Joram: Can anyone of you guys have a look? This is experimental to try out
Ronald's idea. I think we need an additional interface because the one I changed is
used at 2 or 3 places where it does not make sense to implement the timeout-method.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, process.jpdl.xml, screenshot-1.jpg, TaskTimeoutTest.java,
workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
1:11 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
Okay, I don't know yet why but the patch makes 5 of the timer tests fail.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, process.jpdl.xml, screenshot-1.jpg, TaskTimeoutTest.java,
workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
2:07 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
different idea to solve this:
- tasks belonging to an exceution cannot be deleted
- after the time fires the task can neither be completed (anyway not wanted because of
wrong history records) nor deleted
- the delete-method of tasks checks if the belong to an execution and only permits
deletion if they don't
Would it be possible to extend the delete-method in a way that it checks if the task
belongs to an active execution? If this is not the case deletion could be allowed and
additionally an event could be fired creating a HistoryTask marking the task as
"timed out".
Just an idea. I think I like the extra method better.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, process.jpdl.xml, screenshot-1.jpg, TaskTimeoutTest.java,
workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
3:04 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2537:
----------------------------------------
Sebastian,
Can you make a zip with all the full classes you changed. Eclipse seems to have a bit of a
problem processing the patch.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, process.jpdl.xml, screenshot-1.jpg, TaskTimeoutTest.java,
workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
3:27 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider updated JBPM-2537:
--------------------------------------
Attachment: kukeltje.zip
I created the patch with TortoiseSVN for Windows.
Here's the zip. It's unfortunately a big mess and does not include the directory
structure.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
3:57 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
Ronald's remarks (for the records and as a reminder for me):
What could be done is
- add the timeout method to the externalBehaviourInterface
- Implement the timout method in the JpdlExternalActivity where it just calls the signal
with the same signature
- In those classes that need to override it implement it...
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
8:52 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Per Christian Henden commented on JBPM-2537:
--------------------------------------------
I have a similar issue with tasks created in a fork having their related execution ended
when one of the fork's flows reaches an end activity. Then I'm also left with
tasks that cannot be deleted.
If these tasks were automatically deleted or I could delete them myself using taskservice
that would be helpful to me.
Will the changes proposed above fix my issue too?
See my forum post at http://community.jboss.org/message/527080 for a more verbose
explanation. Basically I suggest that
org.jbpm.pvm.internal.history.events.TaskDelete should allow the deletion of tasks with a
related execution when that execution has ended.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
9:15 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
Hello Per Christian!
The proposed patch does not solve your problem since it deals with the same symptom but a
different situation. And in the case described here the deletion of a task would mean a
loss of information. However I think tasks whose execution has ended should be deleteable
to deal with situations like yours where they have become obsolete.
Sebastian
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
1:39 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2537:
----------------------------------------
Ok, I have a 'new fix'... What I did was:
- Create a TimeoutActivityBehaviour interface in the api module.
- Changed some methods in the ExecutionImpl (backwards compatible) and added a timeout
method.
// This processes normal signals and timeouts
private void signal(String signal, Map<String, ?> parameters, boolean timeout) {
checkActive();
if (getProcessDefinition().isSuspended()) {
throw new JbpmException("process definition
"+getProcessDefinition().getId()+" is suspended");
}
propagation = Propagation.EXPLICIT;
if (getActivity()!=null) {
performAtomicOperation(new Signal(signal, parameters, timeout));
} else if (transition!=null) {
performAtomicOperation(AtomicOperation.TRANSITION_START_ACTIVITY);
} else {
throw new JbpmException("execution is not in a activity or in a
transition");
}
}
public void signal(String signal, Map<String, ?> parameters) {
signal(signal, parameters, false);
}
public void timeout(String signalName) {
signal(signalName, (Map<String,?>)null, true);
}
- The Signal got an additional constructor with a boolean to for timeout
public Signal(String signalName, Map<String, ?> parameters, boolean timeout) {
this.signalName = signalName;
this.parameters = parameters;
this.timeout = timeout;
}
and in the 'perform' of the Signal I look if the activitybehaviour implements the
TimeoutActivityBehaviour and based on that result either call the timeout method that
needs to be implemented in the specific activity (TaskActivity in this case) or backwards
compatible just call 'signal'.
- The jpdl TaskActivity implements the interface and so the timeout method which calls the
timeout method on the TaskImpl where it puts the specific task in history, deletes it
etc... Just where it should be (PVM)
Advantages:
- Fully backwards compatible, no changes to other classes needed
- Only use api classes in the PVM, no jpdl ones
- This could (I think) be easily extended to have a 'error' behaviour thing to so
eventlisteners that do something in case of a low level error could be implemented by
means of signals as well.
- ...
Disadvantages:
- Tell me, I could not find any (yet)
Ronald
p.s. Patch will be added later, have to merge things first (2 week lag)
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
3:18 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
Thumbs up for your work, Ronald. I am waiting for the patch to try it. :)
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
5:09 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2537:
----------------------------------------
You know what is 'funny'... if an execution is signalled that contains a task, the
same problem occurs. This was in fact what a timeout did. I could have changed the
behaviour for both cases to just delete the task and all should have been fixed with just
2 lines of code. But personally I do not like that. So now I'm into fixing the other
thing where I want to actually 'cancel' the task and also let that show up in the
history as 'cancelled' and NOT 'completed'. Or should we prevent the
execution that contains a task to be signalled directly and throw an error?
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
5:56 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2537:
-------------------------------------------
I saw you created an extra issue for the last part. I like the way you solved this
problem. Regarding your question I am not sure. For me your question leads to a second
one: Apart from the timeout which is going to be implemented is there a use where it makes
sense to signal an execution containing a task? Please correct me if I am wrong: For each
user task in a process instance an own execution is created, right? So this execution just
belongs to this task. As a consequence I can't see a use case for this and thus
I'd go for the "throw-an-error"-way.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
8:25 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk updated JBPM-2537:
-----------------------------------
Attachment: 20100227-JBPM-2753
Patch added... give it a try (oh, it's a 'workspace' patch so you need to have
all jBPM modules imported, but you will most likely have)
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: 20100227-JBPM-2753, jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
11:57 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2537:
----------------------------------------
The other issue is JBPM-2807, so comments on that should go there. (copied yours
Sebastian)
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Reporter: Alexis Seigneurin
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.4
Attachments: 20100227-JBPM-2753, jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
8:45 p.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Maciej Swiderski reassigned JBPM-2537:
--------------------------------------
Assignee: Maciej Swiderski (was: Tom Baeyens)
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0, jBPM 4.1
Reporter: Alexis Seigneurin
Assignee: Maciej Swiderski
Priority: Critical
Fix For: jBPM 4.4
Attachments: 20100227-JBPM-2753, jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
8:47 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Maciej Swiderski updated JBPM-2537:
-----------------------------------
Attachment: JBPM-2537-JBPM-2807.patch
Here comes the patch for both issues jbpm-2537 and jbpm-2807.
After applying this patch all tests went well so please review it and comment it.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0, jBPM 4.1
Reporter: Alexis Seigneurin
Assignee: Maciej Swiderski
Priority: Critical
Fix For: jBPM 4.4
Attachments: 20100227-JBPM-2753, JBPM-2537-JBPM-2807.patch, jbpm-2537-patch,
jbpm-2537-patch-method.patch, jbpm-2537-patch-method.patch, kukeltje.zip,
process.jpdl.xml, screenshot-1.jpg, TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
8:48 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Maciej Swiderski commented on JBPM-2537:
----------------------------------------
and patch file name for simplicity: JBPM-2537-JBPM-2807.patch
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0, jBPM 4.1
Reporter: Alexis Seigneurin
Assignee: Maciej Swiderski
Priority: Critical
Fix For: jBPM 4.4
Attachments: 20100227-JBPM-2753, JBPM-2537-JBPM-2807.patch, jbpm-2537-patch,
jbpm-2537-patch-method.patch, jbpm-2537-patch-method.patch, kukeltje.zip,
process.jpdl.xml, screenshot-1.jpg, TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
6:56 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Maciej Swiderski updated JBPM-2537:
-----------------------------------
JBoss Forum Reference: http://community.jboss.org/message/541376
Added forum discussion for reference
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0, jBPM 4.1
Reporter: Alexis Seigneurin
Assignee: Maciej Swiderski
Priority: Critical
Fix For: jBPM 4.4
Attachments: 20100227-JBPM-2753, JBPM-2537-JBPM-2807.patch, jbpm-2537-patch,
jbpm-2537-patch-method.patch, jbpm-2537-patch-method.patch, kukeltje.zip,
process.jpdl.xml, screenshot-1.jpg, TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
7 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Maciej Swiderski updated JBPM-2537:
-----------------------------------
Attachment: JBPM-2537-JBPM-2807v2.patch
Attaching a patch that reduces code duplication regarding history events. Reuse TaskCancel
for both timeout and cancel operation that accepts state as argument.
Patch file name is: JBPM-2637-JPM-2807v2.patch
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0, jBPM 4.1
Reporter: Alexis Seigneurin
Assignee: Maciej Swiderski
Priority: Critical
Fix For: jBPM 4.4
Attachments: 20100227-JBPM-2753, JBPM-2537-JBPM-2807.patch,
JBPM-2537-JBPM-2807v2.patch, jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
10:49 p.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Alejandro Guizar reassigned JBPM-2537:
--------------------------------------
Assignee: Alejandro Guizar (was: Maciej Swiderski)
Assigning for review.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0, jBPM 4.1
Reporter: Alexis Seigneurin
Assignee: Alejandro Guizar
Priority: Critical
Fix For: jBPM 4.4
Attachments: 20100227-JBPM-2753, JBPM-2537-JBPM-2807.patch,
JBPM-2537-JBPM-2807v2.patch, jbpm-2537-patch, jbpm-2537-patch-method.patch,
jbpm-2537-patch-method.patch, kukeltje.zip, process.jpdl.xml, screenshot-1.jpg,
TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
2:35 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/jira/browse/JBPM-2537?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2537:
-----------------------------------
Attachment: jbpm-2357-20100507.diff
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0, jBPM 4.1
Reporter: Alexis Seigneurin
Assignee: Alejandro Guizar
Priority: Critical
Fix For: jBPM 4.4
Attachments: 20100227-JBPM-2753, jbpm-2357-20100507.diff,
JBPM-2537-JBPM-2807.patch, JBPM-2537-JBPM-2807v2.patch, jbpm-2537-patch,
jbpm-2537-patch-method.patch, jbpm-2537-patch-method.patch, kukeltje.zip,
process.jpdl.xml, screenshot-1.jpg, TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
10:10 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/browse/JBPM-2537?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar updated JBPM-2537:
-----------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Mark incomplete task as obsolete before leaving it after expiration or external signal.
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0, jBPM 4.1
Reporter: Alexis Seigneurin
Assignee: Alejandro Guizar
Priority: Critical
Fix For: jBPM 4.4
Attachments: 20100227-JBPM-2753, jbpm-2357-20100507.diff,
JBPM-2537-JBPM-2807.patch, JBPM-2537-JBPM-2807v2.patch, jbpm-2537-patch,
jbpm-2537-patch-method.patch, jbpm-2537-patch-method.patch, kukeltje.zip,
process.jpdl.xml, screenshot-1.jpg, TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
10:10 a.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2537) A triggered timer does not end the task which is left
[
https://jira.jboss.org/browse/JBPM-2537?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar resolved JBPM-2537.
------------------------------------
Resolution: Done
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0, jBPM 4.1
Reporter: Alexis Seigneurin
Assignee: Alejandro Guizar
Priority: Critical
Fix For: jBPM 4.4
Attachments: 20100227-JBPM-2753, jbpm-2357-20100507.diff,
JBPM-2537-JBPM-2807.patch, JBPM-2537-JBPM-2807v2.patch, jbpm-2537-patch,
jbpm-2537-patch-method.patch, jbpm-2537-patch-method.patch, kukeltje.zip,
process.jpdl.xml, screenshot-1.jpg, TaskTimeoutTest.java, workflow-test-jbpm4.1.zip
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
In my process definition, "task1" has a transition with a due date. When this
timer is triggered by the job executor, the transition takes the process to
"task2" but "task1" still looks active. For instance, when I run a
"task query", instead of only finding "task2", both "task1"
and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3"
to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1"
/>
<transition g="-45,-18" name="to java1"
to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52"
method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2"
/>
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to
end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not
listed by the task query, which makes me think that, once "task1" is left, it
should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution
does not seem applicable to JBPM 4.x.
I will attached the whole source code.
--
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
5154
days inactive
5405
days old
60 comments
8 participants
participants (8)
-
Alejandro Guizar (JIRA) -
Alexis Seigneurin (JIRA)
-
Joram Barrez (JIRA)
-
Maciej Swiderski (JIRA)
-
Per Christian Henden (JIRA)
-
Ronald van Kuijk (JIRA)
-
Sebastian Schneider (JIRA)
-
Tom Baeyens (JIRA)