December 2007 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel

by Alexey Kostylev (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1072?page=comments#action_12392641 ] Alexey Kostylev commented on JBPM-1072: --------------------------------------- When using several JobExecutor instances with Oracle 10g I've got duplicate executions of the same job. > Concurrent JobExecutors can process the same job in parallel > ------------------------------------------------------------ > > Key: JBPM-1072 > URL: http://jira.jboss.com/jira/browse/JBPM-1072 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM jPDL 3.2.2 > Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > MySQL 5.0.22 > Reporter: Jiri Pechanec > Assigned To: Koen Aers > Attachments: expl.tar.gz > > > Attached is a simple test case that > 1) Deploys process definition with two nodes > 2) Starts 20 executor threads > 2) Starts the process instance that will asynchronously execute action on the second node > 4) The second node writes a record to the database > The test case needs to be executed multiple times to see the incorrect behaviour. > This is an example of run output > Isol 8 > Action 1 > Success 0 > Failure 0 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 > Action 2 1 > Action 2 1 > Action 2 > Action 2 1 > Explanation of the outcome > 9 job executors successfully executed the node action (same job) including database operation. All database operations were comitted (9 new records were created) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel

by Alexey Kostylev (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1072?page=comments#action_12392637 ] Alexey Kostylev commented on JBPM-1072: --------------------------------------- Is it possible to use several JobExecutors with non-transactional ActionHandlers? As I understand the problem is that the same job is loaded by several JobExecutors and one job is executed several time. When job makes some non-transactional action, as writing is file, this is not acceptable. May be pessimistic locking should help? > Concurrent JobExecutors can process the same job in parallel > ------------------------------------------------------------ > > Key: JBPM-1072 > URL: http://jira.jboss.com/jira/browse/JBPM-1072 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM jPDL 3.2.2 > Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > MySQL 5.0.22 > Reporter: Jiri Pechanec > Assigned To: Koen Aers > Attachments: expl.tar.gz > > > Attached is a simple test case that > 1) Deploys process definition with two nodes > 2) Starts 20 executor threads > 2) Starts the process instance that will asynchronously execute action on the second node > 4) The second node writes a record to the database > The test case needs to be executed multiple times to see the incorrect behaviour. > This is an example of run output > Isol 8 > Action 1 > Success 0 > Failure 0 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 > Action 2 1 > Action 2 1 > Action 2 > Action 2 1 > Explanation of the outcome > 9 job executors successfully executed the node action (same job) including database operation. All database operations were comitted (9 new records were created) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-807) Allow assignment of jBPM variables via EL evaluation

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-807?page=comments#action_12392354 ] Tom Baeyens commented on JBPM-807: ---------------------------------- pete, can you elaborate on this feature request a bit ? does it mean that variables should be settable through a value binding expression ? or does this just translate to a setVariable on the business process context ? > Allow assignment of jBPM variables via EL evaluation > ---------------------------------------------------- > > Key: JBPM-807 > URL: http://jira.jboss.com/jira/browse/JBPM-807 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Gavin King > Assigned To: Tom Baeyens > Priority: Critical > Fix For: jBPM jPDL 3.2.3 > > > A really major issue in terms of Seam integration with jBPM is to be able to have the process "remember" state coming from Seam, w/o the Seam component needing to outject the value. > What I want is to be able to say: > <assign variable="orderId" value="#{order.id}"/> > when a transition occurs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-895) null pointer when create new sub process definition

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-895?page=comments#action_12392307 ] Ronald van Kuijk commented on JBPM-895: --------------------------------------- Or use late binding via the binding='late' attribute. It has one additional feature in that you will always get the latest version of the subprocess for each process you start > null pointer when create new sub process definition > --------------------------------------------------- > > Key: JBPM-895 > URL: http://jira.jboss.com/jira/browse/JBPM-895 > Project: JBoss jBPM > Issue Type: Bug > Components: BPEL > Affects Versions: jBPM 3.1.3 > Reporter: Tom Nguyen > Assigned To: Tom Baeyens > Attachments: DbSubProcessResolver.java > > > I have a problem with my process composition > Exception happen when deploying process with sub process: > public void deployProcessDefinition() { > ProcessDefinition processDefinition = ProcessDefinition.parseXmlResource("main/processdefinition.xml"); > ProcessInstance instance = new ProcessInstance(processDefinition); > JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext(); > try { > jbpmContext.deployProcessDefinition(processDefinition); > } finally { > jbpmContext.close(); > } > } > java.lang.NullPointerException: can't create a process instance when processDefinition is null > at org.jbpm.graph.exe.ProcessInstance.<init>(ProcessInstance.java:87) > at org.jbpm.graph.exe.Token.createSubProcessInstance(Token.java:571) > at org.jbpm.graph.node.ProcessState.execute(ProcessState.java:109) > at org.jbpm.graph.def.Node.enter(Node.java:316) > <?xml version="1.0" encoding="UTF-8"?> > <process-definition > xmlns="urn:jbpm.org:jpdl-3.1" name="main"> > <start-state name="start"> > </start-state> > <end-state name="end"></end-state> > <process-state name="sub"> > <sub-process name="sub"/> > </process-state> > </process-definition> > This is my sub process: > <?xml version="1.0" encoding="UTF-8"?> > <process-definition > xmlns="urn:jbpm.org:jpdl-3.1" name="sub"> > <start-state name="start"> > </start-state> > <end-state name="end"></end-state> > </process-definition> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-895) null pointer when create new sub process definition

by Michael Thiele (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-895?page=comments#action_12392258 ] Michael Thiele commented on JBPM-895: ------------------------------------- I had a hard time solving this problem. It's not a bug, it's just not well designed... You don't have to do some kind of bug fix like replacing above said code. You have to make sure, that the sub-process is already deployed, when the main process is being parsed from your processdefinition.xml file. So things like this won't work: ProcessDefinition pdload_sub = ProcessDefinition.parseXmlResource("sub.xml"); ProcessDefinition pdload_caller = ProcessDefinition.parseXmlResource("main.xml"); context.deployProcessDefinition(pdload_sub); context.deployProcessDefinition(pdload_caller); Instead you have to do it that way: ProcessDefinition pdload_sub = ProcessDefinition.parseXmlResource("sub.xml"); context.deployProcessDefinition(pdload_sub); ProcessDefinition pdload_caller = ProcessDefinition.parseXmlResource("main.xml"); context.deployProcessDefinition(pdload_caller); That's sometimes not that easy, since these method calls can be distributed different classes etc., but keep in mind, that resolving the sub-process definition from the given name takes place during parsing, not during deployment of the main process! Besides what Tom B. posted is right for the issue description: parsing of the definition xml has to take place after a JbpmContext has been created. After deployment of the ProcessDefinition it will be persisted with the jbpmContext.close(); in the finally block. If you parse outside the try block (that is without having created a JbpmContext) JBPM won't find the persisted sub-process referenced in the main process definition. > null pointer when create new sub process definition > --------------------------------------------------- > > Key: JBPM-895 > URL: http://jira.jboss.com/jira/browse/JBPM-895 > Project: JBoss jBPM > Issue Type: Bug > Components: BPEL > Affects Versions: jBPM 3.1.3 > Reporter: Tom Nguyen > Assigned To: Tom Baeyens > Attachments: DbSubProcessResolver.java > > > I have a problem with my process composition > Exception happen when deploying process with sub process: > public void deployProcessDefinition() { > ProcessDefinition processDefinition = ProcessDefinition.parseXmlResource("main/processdefinition.xml"); > ProcessInstance instance = new ProcessInstance(processDefinition); > JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext(); > try { > jbpmContext.deployProcessDefinition(processDefinition); > } finally { > jbpmContext.close(); > } > } > java.lang.NullPointerException: can't create a process instance when processDefinition is null > at org.jbpm.graph.exe.ProcessInstance.<init>(ProcessInstance.java:87) > at org.jbpm.graph.exe.Token.createSubProcessInstance(Token.java:571) > at org.jbpm.graph.node.ProcessState.execute(ProcessState.java:109) > at org.jbpm.graph.def.Node.enter(Node.java:316) > <?xml version="1.0" encoding="UTF-8"?> > <process-definition > xmlns="urn:jbpm.org:jpdl-3.1" name="main"> > <start-state name="start"> > </start-state> > <end-state name="end"></end-state> > <process-state name="sub"> > <sub-process name="sub"/> > </process-state> > </process-definition> > This is my sub process: > <?xml version="1.0" encoding="UTF-8"?> > <process-definition > xmlns="urn:jbpm.org:jpdl-3.1" name="sub"> > <start-state name="start"> > </start-state> > <end-state name="end"></end-state> > </process-definition> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1022) 3.2.1 Admin Console: Any user sees all users tasks

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1022?page=comments#action_12392166 ] Ronald van Kuijk commented on JBPM-1022: ---------------------------------------- sorry, only in the 'admin' part....not for the user > 3.2.1 Admin Console: Any user sees all users tasks > --------------------------------------------------- > > Key: JBPM-1022 > URL: http://jira.jboss.com/jira/browse/JBPM-1022 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Burr Sutter > Assigned To: Ronald van Kuijk > Priority: Blocker > Fix For: jBPM jPDL 3.2.3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > In the current Admin Console, any given user will see all other users tasks. Plus a user can "take" another person's assigned tasks even when they are not an "administrator". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1022) 3.2.1 Admin Console: Any user sees all users tasks

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1022?page=comments#action_12392162 ] Ronald van Kuijk commented on JBPM-1022: ---------------------------------------- hmm.... In the implementation of retrieving tasklists, custom custom queries are used instead of the api.... I'll see if I can change this. > 3.2.1 Admin Console: Any user sees all users tasks > --------------------------------------------------- > > Key: JBPM-1022 > URL: http://jira.jboss.com/jira/browse/JBPM-1022 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Burr Sutter > Assigned To: Ronald van Kuijk > Priority: Blocker > Fix For: jBPM jPDL 3.2.3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > In the current Admin Console, any given user will see all other users tasks. Plus a user can "take" another person's assigned tasks even when they are not an "administrator". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1022) 3.2.1 Admin Console: Any user sees all users tasks

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1022?page=all ] Ronald van Kuijk updated JBPM-1022: ----------------------------------- Original Estimate: 2 days Remaining Estimate: 2 days hmmm... due to the complex combination of gravel and jbpm4jsf is it not that simple (for me) to solve. So therefor 2d implementation guestimate > 3.2.1 Admin Console: Any user sees all users tasks > --------------------------------------------------- > > Key: JBPM-1022 > URL: http://jira.jboss.com/jira/browse/JBPM-1022 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Burr Sutter > Assigned To: Ronald van Kuijk > Priority: Blocker > Fix For: jBPM jPDL 3.2.3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > In the current Admin Console, any given user will see all other users tasks. Plus a user can "take" another person's assigned tasks even when they are not an "administrator". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-987) display non GMT+0 time zones

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-987?page=all ] Ronald van Kuijk updated JBPM-987: ---------------------------------- Fix Version/s: jBPM 3.3 > display non GMT+0 time zones > ---------------------------- > > Key: JBPM-987 > URL: http://jira.jboss.com/jira/browse/JBPM-987 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2, jBPM jPDL 3.2.1 > Reporter: Jean-Louis Rastapoc > Assigned To: Ronald van Kuijk > Fix For: jBPM 3.3 > > > The web-console currently uses the default JSF timezone conversion and displays GMT+0. > Other time zones should be read from the client or be configurable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Assigned: (JBPM-987) display non GMT+0 time zones

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-987?page=all ] Ronald van Kuijk reassigned JBPM-987: ------------------------------------- Assignee: Ronald van Kuijk (was: Tom Baeyens) > display non GMT+0 time zones > ---------------------------- > > Key: JBPM-987 > URL: http://jira.jboss.com/jira/browse/JBPM-987 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2, jBPM jPDL 3.2.1 > Reporter: Jean-Louis Rastapoc > Assigned To: Ronald van Kuijk > Fix For: jBPM 3.3 > > > The web-console currently uses the default JSF timezone conversion and displays GMT+0. > Other time zones should be read from the client or be configurable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues December 2007