June 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2139) Concurrency problems with the Join node despite lock="pessimistic"

by George Mournos (JIRA)

Concurrency problems with the Join node despite lock="pessimistic" ------------------------------------------------------------------ Key: JBPM-2139 URL: https://jira.jboss.org/jira/browse/JBPM-2139 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Environment: jbpm 3.2.6, weblogic 9.2.1, oracle 10g Reporter: George Mournos We are evaluating jbpm for concurrency. We created a test case with a lot of concurrency. The test process has: * a fork * 10 nodes with async="true" and * a join with lock="pessimistic". In some of the parallel nodes we get the exception: Caused by: org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.graph.exe.Token#121] We checked that the lock mode is persisted correctly and that the join node actually does the lock.UPGRADE. We attach the testcase, the test process definition, and the full stacktrace. We enforced a stricter locking strategy, namely locking the process instance for as long as the command executor was working and the test worked ok. However, we finally dropped this solution because it was creating a lot of row locks and could lead to transaction timeouts and finally chose another solution. All of our business logic is in nodes with async="true" and goes through the jms executor. We serialize consumption of jms messages belonging to the same process instance by using a JMS extention of Weblogic, called UnitOfOrder. WLMessageProducer messageProducer = (WLMessageProducer)session.createProducer(destination); messageProducer.setUnitOfOrder(processInstance + ""); This workaround could be useful to people working on weblogic. -- 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

13 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2167) Group Task Assignment problem- Unable to see task avalaible to all users present in group on console

by Swati S (JIRA)

Group Task Assignment problem- Unable to see task avalaible to all users present in group on console ---------------------------------------------------------------------------------------------------- Key: JBPM-2167 URL: https://jira.jboss.org/jira/browse/JBPM-2167 Project: JBoss jBPM Issue Type: Support Patch Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 3.2.3 Reporter: Swati S Hi, I'm using 3.2.3 version. I'm using group(testgroup) in task node assignment expression. I have 3 users in "testgroup" but I dont see this task is available to any of the user from group. In pooledActor attibute I see group name but in personal /group task I am unable to see. If I assign one of the user role and If I change assignment expression to group(testuser)-->member(mynewrole) then this task gets assigned to user and can see in personal task list. If I add same role to another user then it gives delegationException. I want this task to be visible on task list of all users from group. Can anyone help me with that? I tried using AssignmentHanlderClass. uses assignable.setPooledActors() here again in the pooledActor attribute Users list is available but I dont see task available on each of these user's personal task list. Your help will be appreciated. Thanks & Regards, Swati -- 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

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2227) JPDL does not update source.xml when project.

by Sujatha Bharathan (JIRA)

JPDL does not update source.xml when project. --------------------------------------------- Key: JBPM-2227 URL: https://jira.jboss.org/jira/browse/JBPM-2227 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: GPD Environment: Window XP with service pack 3 Reporter: Sujatha Bharathan When i update a task node in my JPDL diagram and create a reminder and set it to 24 hours and said repeat as yes and and the reminder works fine. But when i update the reminder ..say 2 minutes - the original source xml still states 24 hours. I had to manually edit it every time i make changes in the reminder in the task node. Has anybody had this issue before? Whenever a reminder email is sent it follows the template definition task-assign from the jbpm.mail.templates.xml - is there a way i can customise and create a reminder differently by specifying different mail templates? How do I then link the task to this template( i dont see any template linking at task node level) Looking forward to your reply -- 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

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2308) 3.2.3 release notes are out of date

by Tom Muldoon (JIRA)

3.2.3 release notes are out of date ----------------------------------- Key: JBPM-2308 URL: https://jira.jboss.org/jira/browse/JBPM-2308 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.3 Reporter: Tom Muldoon The release notes contained within the jbpm-jpdl-3.2.3.zip provide migration notes (from 3.1.x to 3.2.x) that are no longer relevant... - The DUEDATE_ should not be declared as a timestamp; it should be declared as a datetime - The LOCKTIME_ should not be declared as a timestamp; it should be declared as a datetime - The RETRIES_ value should be set to 1 (not 0) as part of the insert statement (which migrates the data from jbpm_timer to jbmp_job) - Foreign keys should be created -- 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

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2327) Docs on asynchronous continuations are misleading

by Martin Putz (JIRA)

Docs on asynchronous continuations are misleading ------------------------------------------------- Key: JBPM-2327 URL: https://jira.jboss.org/jira/browse/JBPM-2327 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.5.SP5 Reporter: Martin Putz Chapter 4.3.4 of the User Guide states: There are 3 places where execution can be continued asynchronously: * Just before the node's execute method. Which is after entering the node. * When execution is about to be propagated over a transition. Which is before leaving a node. * Every action can be executed asynchonously as well. http://docs.jboss.org/jbpm/v3.2/userguide/html/graphorientedprogramming.h... Only the first case is implemented, therefore the docs should be cleaned up and the other points removed. -- 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

13 years, 5 months

5
8
0 / 0

[JBoss JIRA] Created: (JBPM-2358) When a task is started no log is generated

by Osvaldo Pina (JIRA)

When a task is started no log is generated ------------------------------------------ Key: JBPM-2358 URL: https://jira.jboss.org/jira/browse/JBPM-2358 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.6.SP1, jBPM 3.3.1 GA Reporter: Osvaldo Pina When a task instance is started no log is generated, considering that the natural lifecycle of a task is to be created, started and then to be ended, as it is writing in the documentation, it does no seem to be right that the task creations and task ends are logged but task starts are not. -- 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

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1170) Multiple Timers with same name on Node end prematurely

by David Roberts (JIRA)

Multiple Timers with same name on Node end prematurely ------------------------------------------------------ Key: JBPM-1170 URL: http://jira.jboss.com/jira/browse/JBPM-1170 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.2 Environment: Jbpm 3.2.2, Tomcat 5.028, MySQL 5.0 Reporter: David Roberts Assigned To: Tom Baeyens When you have multiple Tasks on a Node, and each task has a Timer called, for example, "Reminder". Lets say each timer is set to repeat every 24 hours. If you complete one of the Tasks on the node, the Timer called "Reminder" on that task instance ends, but so does every other timer for all other tasks on that node with the name "Reminder". Surely this should not happen? You could avoid this by naming each Timer differenty, example "Reminder 1", "Reminder 2". But the problem may still happen if you have multiple task instances of the SAME task. Then the name of the Reminders will still be the same, so they will all end when completing one of the task instances. -- 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

13 years, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (JBPM-1166) fix SEAM timer transaction integration

by Tom Baeyens (JIRA)

fix SEAM timer transaction integration -------------------------------------- Key: JBPM-1166 URL: http://jira.jboss.com/jira/browse/JBPM-1166 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens -- 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

13 years, 5 months

4
19
0 / 0

[JBoss JIRA] Created: (JBPM-1140) Empty <handler> element in <decision> cause org.jbpm.graph.def.DelegationException

by Rafa? ?ukowski (JIRA)

Empty <handler> element in <decision> cause org.jbpm.graph.def.DelegationException ---------------------------------------------------------------------------------- Key: JBPM-1140 URL: http://jira.jboss.com/jira/browse/JBPM-1140 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Rafa? ?ukowski Assigned To: Tom Baeyens Priority: Trivial That is my first issue, forgive me any mistakes and possible redundancy or duplication;) Using graphical designer I've created process file with empty <handler> : <decision name="decision1"> <handler></handler> <transition to="optional" name="to optional"></transition><transition to="first" name="to optional"></transition> </decision> And this is not working (org.jbpm.graph.def.DelegationException). After deleting <handler></handler> process is running correctly. Don't know if this is error in engine or in designer. Maby this kind of decision node is incorrect, and then designer should avoid this situation. My opinion is that engine should ignore empty handlers and go on without errors... -- 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

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1118) Unexpected behavier of LoggingConfigDbTest

by Jan-Philipp Bolle (JIRA)

Unexpected behavier of LoggingConfigDbTest ------------------------------------------ Key: JBPM-1118 URL: http://jira.jboss.com/jira/browse/JBPM-1118 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Jan-Philipp Bolle Assigned To: Tom Baeyens Priority: Trivial It looks like that the LoggingConfigDbTest is not working. I added in nologging.jbpm.cfg.xml the org.jbpm.logging.db.DbLoggingServiceFactory. Now I assume that the test must fail because jBPM is configured to use the loggingservice. But the test still work (is green). -- 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

13 years, 5 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2009