February 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2771) continue=async on <start> causes NullPointerException

by Martin Porter (JIRA)

continue=async on <start> causes NullPointerException ----------------------------------------------------- Key: JBPM-2771 URL: https://jira.jboss.org/jira/browse/JBPM-2771 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Environment: Any Reporter: Martin Porter Adding continue="async" on a <start> of a process will cause a NullPointerException when you attempt to start the process. We need this to prevent the caller waiting when the process instance is created but it does not work. Currently we use a workaround to call a <java> activity which prints a message to the log and does the async continuation. -- 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

14 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-2802) Measure test coverage

by Alejandro Guizar (JIRA)

Measure test coverage --------------------- Key: JBPM-2802 URL: https://jira.jboss.org/jira/browse/JBPM-2802 Project: jBPM Issue Type: Task Components: Runtime Engine Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.2.9 Leverage the cobertura maven plugin to get a quantitative test coverage report. http://mojo.codehaus.org/cobertura-maven-plugin/ -- 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

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2263) Multiple timers in node cause EventSource reset

by Asaf Shakarchi (JIRA)

Multiple timers in node cause EventSource reset ----------------------------------------------- Key: JBPM-2263 URL: https://jira.jboss.org/jira/browse/JBPM-2263 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.6.SP1 Reporter: Asaf Shakarchi When having multiple timers in a node, the 2nd timer and all after 'lose' the relationship between the timer->graphElement, thus, timers are being persisted without the relationship with the graphElement, that causes serious problems in job execution time, Here's a deep detail explaination (considering there are two timers in one task node) When entering a node, the 'EVENTTYPE_NODE_ENTER' event gets fired, which causes two 'create timer actions' to be created via CreateTimerAction, one per timer, In GraphElement->fireEvent() there's the following piece of code: ... fireAndPropagateEvent(eventType, executionContext); } finally { executionContext.setEventSource(null); } ... This part seems to clean up the eventSource, but that causes the 2nd timer and above to 'lose' the association to the graphElement(Node ID) the timer was created from, I assume its not taken into consideration that the create timer fires another 'inner' event that causes the eventSource to be reset: CreateTimerAction->createTimer(..) { graphElement.fireEvent(Event.EVENTTYPE_TIMER_CREATE, executionContext); } For now, we commented out the GraphElement->fireEvent->'executionContext.setEventSource(null);' line, but I don't really understand the impact of that, If that line is important, I think it's better to perform the cleanup only in case the fire event is not invoked in an 'inner' fire event call, or find another approach, Thanks. -- 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

14 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-2799) JBPM4.1 Exceptional Handling.

by Atul Joshi (JIRA)

JBPM4.1 Exceptional Handling. ----------------------------- Key: JBPM-2799 URL: https://jira.jboss.org/jira/browse/JBPM-2799 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1 Environment: WindowXP, JBOSS Reporter: Atul Joshi Priority: Critical Fix For: jBPM 4.3 In the process design I have added five system activity (Java Node), If i got the Error/Exception in the 5th System Activity , the JBPM Engine will rollback all the activitis and can't submited the the design process, also jbpm engine not commited the activity history table too , After sucessfully executing the activities, History table should update with all activities in the process. -- 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

14 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2045) Database maintenance scripts

by Len DiMaggio (JIRA)

Database maintenance scripts ---------------------------- Key: JBPM-2045 URL: https://jira.jboss.org/jira/browse/JBPM-2045 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Productization Affects Versions: jBPM 3.2.5 GA Reporter: Len DiMaggio Project JIRA for SOA-P platform JIRA: https://jira.jboss.org/jira/browse/SOA-310 -- 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

14 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2420) fold AddressResolver into IdentitySession

by Tom Baeyens (JIRA)

fold AddressResolver into IdentitySession ----------------------------------------- Key: JBPM-2420 URL: https://jira.jboss.org/jira/browse/JBPM-2420 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 -- 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

14 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-2778) accept-propagated-events doesn't affect script

by Toshiya Kobayashi (JIRA)

accept-propagated-events doesn't affect script ---------------------------------------------- Key: JBPM-2778 URL: https://jira.jboss.org/jira/browse/JBPM-2778 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.8 Reporter: Toshiya Kobayashi In case that I set accept-propagation-events="false" on both action and script, the script is executed on the propagated event while the action is not executed. According to jBPM Reference Guide, the script should not be executed. http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html-single/... ======== {yes|no|true|false}. Default is yes|true. If set to false, the action will only be executed on events that were fired on this action's element. for more information, see Section 7.5.4, "Event propagation" ======== Actually, org.jbpm.graph.action.Script overrides org.jbpm.graph.def.Action.read() method and doesn't recognize "accept-propagated-events" attribute. -- 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

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2780) Graceful stop of JobExecutor

by Bernd Ruecker (JIRA)

Graceful stop of JobExecutor ---------------------------- Key: JBPM-2780 URL: https://jira.jboss.org/jira/browse/JBPM-2780 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.8 Reporter: Bernd Ruecker Assignee: Alejandro Guizar Currently when stopping the JobExecutor it stops all running JobExecutorThreads by calling "stop()" on them. This interrups the thread. In a scenario where you want to do a "clean" stop (e.g. shutdown the server), there should be a mechanism to stop the JobExecutor, but let it finish currently executed jobs and wait for it. For the implementation it is not hard, I could provide a patch for it as well. Since a customer currently needs it, it would be nice to commit it to the next released jbpm 3.2.x version. -- 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

14 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-2793) process cannot "end" because foreign key constraint fails

by Bwi Chen (JIRA)

process cannot "end" because foreign key constraint fails --------------------------------------------------------- Key: JBPM-2793 URL: https://jira.jboss.org/jira/browse/JBPM-2793 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.3 Environment: Windows xp, jdk1.6, mysql5.1 Reporter: Bwi Chen i created a process and it include three sub-processes(fork), when any one of sub-processes reject, the main process will go to End. exception:Cannot delete or update a parent row: a foreign key constraint fails it happen because jbpm do not delete tasks of sub-processes(others, and thay not end yet). when i delete the relation from db, it won't happen. but many task info still in db. it should fixed in 4.0, but it did not. https://jira.jboss.org/jira/browse/JBPM-2491 -- 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

14 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2560) Task definition does not have some properties set from jPDL task element

by Phil Bingley (JIRA)

Task definition does not have some properties set from jPDL task element ------------------------------------------------------------------------ Key: JBPM-2560 URL: https://jira.jboss.org/jira/browse/JBPM-2560 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.1 Environment: jBPM 4.1 Reporter: Phil Bingley The duedate and priority values in a jPDL task definition are not set on the task definition when parsed. This means that the due date is not automatically set when the task is created, nor the priority. -- 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

14 years, 10 months

6
28
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues February 2010