January 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2661) BPMN2: Exclusive gateway

by Joram Barrez (JIRA)

BPMN2: Exclusive gateway ------------------------ Key: JBPM-2661 URL: https://jira.jboss.org/jira/browse/JBPM-2661 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Joram Barrez Assignee: Joram Barrez Fix For: jBPM 4.3 * Verify what's currently in the codebase. * Enhance where needed * Document the usage of the construct. -- 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, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-2413) productize group activity

by Tom Baeyens (JIRA)

productize group activity ------------------------- Key: JBPM-2413 URL: https://jira.jboss.org/jira/browse/JBPM-2413 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, 9 months

5
12
0 / 0

[JBoss JIRA] Created: (JBPM-2767) JobExecutor doesn't roll back the transaction even if the action handler throws Exception

by Toshiya Kobayashi (JIRA)

JobExecutor doesn't roll back the transaction even if the action handler throws Exception ----------------------------------------------------------------------------------------- Key: JBPM-2767 URL: https://jira.jboss.org/jira/browse/JBPM-2767 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 Job execution of an async node is processed by JobExecutor, the transaction is not rolled back even if the action handler throws Exception/RuntimeException. The transaction is commtted and no retry happens. It looks inconsistent with docs: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html-single/... ============ If execution of a command message fails, the transaction will be rolled back. After that, a new transaction will be started that adds the error message to the message in the database. The command executor filters out all messages that contain an exception. ============ I've attatched a reproducer. - unzip jobexecution.zip - modify build.properties - ant deploypar - ant deploy - ant ejbclient (or access jbpm-console to start process instance) - access jbpm-console to check process instance's id which is created by the action handler (which should be rolled back) -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2637) TaskMgmtSession.findTaskInstancesByIds() fails if taskInstanceIds is an empty list

by Toshiya Kobayashi (JIRA)

TaskMgmtSession.findTaskInstancesByIds() fails if taskInstanceIds is an empty list ---------------------------------------------------------------------------------- Key: JBPM-2637 URL: https://jira.jboss.org/jira/browse/JBPM-2637 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.8, jBPM 3.2.7 Reporter: Toshiya Kobayashi org.jbpm.command.GetTaskListCommand.execute() throws JbpmPersistenceException if there is no pooled task instances for a given actor even if the actor has personally assigned task instaces. ===== org.jbpm.persistence.JbpmPersistenceException: couldn't get task instances by ids '[]' at org.jbpm.db.TaskMgmtSession.findTaskInstancesByIds(TaskMgmtSession.java:204) at org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(TaskMgmtSession.java:123) at org.jbpm.JbpmContext.getGroupTaskList(JbpmContext.java:194) at org.jbpm.command.GetTaskListCommand.execute(GetTaskListCommand.java:54) at sample.task.ws.TaskSampleWS.test(TaskSampleWS.java:52) ===== In case of CP01, GetTaskListCommand returns the personal task list without Exception. This behavior is caused by the change introduced by r4076 in org.jbpm.db.TaskMgmtSession.findTaskInstancesByIds(). r4705 === public List<TaskInstance> findTaskInstancesByIds(List<Long> taskInstanceIds) { List<TaskInstance> result; if (taskInstanceIds.isEmpty()) { result = Collections.emptyList(); } else { try { Query query = session.getNamedQuery("TaskMgmtSession.findTaskInstancesByIds"); query.setParameterList("taskInstanceIds", taskInstanceIds); result = CollectionUtil.checkList(query.list(), TaskInstance.class); } catch (Exception e) { handle(e); throw new JbpmException("couldn't get task instances by ids '" + taskInstanceIds + "'", e); } } return result; } === r4706 === public List findTaskInstancesByIds(List taskInstanceIds) { try { return session.getNamedQuery("TaskMgmtSession.findTaskInstancesByIds") .setParameterList("taskInstanceIds", taskInstanceIds) .list(); } catch (HibernateException e) { handle(e); throw new JbpmPersistenceException("couldn't get task instances by ids '" + taskInstanceIds + "'", e); } } === The change was related to JBPM-2205 and removed the empty check because the method Collections.emptyList() is not supported in jdk1.4. But I think an equivalent empty check should be restored. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBPM-2581) Problems with nested Forks

by Sebastian Castellanos (JIRA)

Problems with nested Forks --------------------------- Key: JBPM-2581 URL: https://jira.jboss.org/jira/browse/JBPM-2581 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0 Environment: Windows xp, Eclipse galileo and jbpm integred with spring and hibernate. Reporter: Sebastian Castellanos Priority: Critical First off, I apologize for not having made the unit tests, but do not have time at the moment and I think it is a conceptual problem and a unit test would not provide much. I am integrating jBPM version 4.1 and it proves there too. The situation is this: When launched a nested Fork1 another in the second Fork repeats one of its tasks. In the xml it becomes clear what the situation. Maybe it is a conceptual issue, and I who is mishandled. I would be grateful if I can help, as I searched in different places this situation and found no alternative but to post it here. Greetings. Sebastian. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

6
19
0 / 0

[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-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-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-2499) View ended ProcessInstance missing

by Hauke Rabe (JIRA)

View ended ProcessInstance missing ---------------------------------- Key: JBPM-2499 URL: https://jira.jboss.org/jira/browse/JBPM-2499 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.0 Reporter: Hauke Rabe Ended ProcessInstance are immediately deleted from db. Only history entries left, so the view should be extended. -- 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

5
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2010