November 2010 - 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

14 years

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2790) "org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction" exception occures during/after join of forked concurrent nodes

by Pavel Macik (JIRA)

"org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction" exception occures during/after join of forked concurrent nodes ----------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBPM-2790 URL: https://jira.jboss.org/jira/browse/JBPM-2790 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.7 Reporter: Pavel Macik Priority: Critical See linked SOA-1942... -- 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

2
11
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

14 years

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

14 years

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

14 years

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

14 years

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

14 years

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2428) BPM process action class loading issue

by Marek Baluch (JIRA)

BPM process action class loading issue -------------------------------------- Key: JBPM-2428 URL: https://jira.jboss.org/jira/browse/JBPM-2428 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.5.SP5 Environment: SOA-P 4.3 CP01 JBoss server config = PRODUCTION Reporter: Marek Baluch Attachments: jbpm_classloader_anomaly.tar.gz Class loader which loaded a class instance which is stored in the process variable is different then the classloader that loaded the same class in ActionHandler. This issue will occure only if the process is undeployed after one or more runs and redeployed without restarting the server. Even deleting process instances using the JBPM Console didn't help. Steps to reproduce (use the quickstart in the attachment) ============================================ ant deploy ant deployProcess ant startProcess ant undeploy start the quickstart ant deploy ant deployProcess ant startProcess A simple restart of the server after the first undeploy fixes the problem and the exception won't be reproduced. First run output =========== 2009-07-15 11:40:26,407 INFO [STDOUT] ********** CandidateIntakeAction - Candidate object populated ********** 2009-07-15 11:40:26,407 INFO [STDOUT] Candidate name = Fidel 2009-07-15 11:40:26,407 INFO [STDOUT] Candidate surname = Castro 2009-07-15 11:40:26,407 INFO [STDOUT] Candidate email = fidel.castro(a)gmail.com 2009-07-15 11:40:26,407 INFO [STDOUT] ************************************************************************ 2009-07-15 11:40:26,515 INFO [STDOUT] ********** SimpleBPMActionHandler ********** 2009-07-15 11:40:26,515 INFO [STDOUT] Object loaded with classloader: org.jboss.mx.loading.UnifiedClassLoader3@1769b56{ url=file:/home/mbaluch/work/build/jboss-soa-p.4.3.0.GA_CP01_CR7/jboss-as/server/production/deploy/Quickstart_jbpm_classloader_anomaly.esb/ ,addedOrder=60} 2009-07-15 11:40:26,516 INFO [STDOUT] Given classloader for class Candidate: org.jboss.mx.loading.UnifiedClassLoader3@1769b56{ url=file:/home/mbaluch/work/build/jboss-soa-p.4.3.0.GA_CP01_CR7/jboss-as/server/production/deploy/Quickstart_jbpm_classloader_anomaly.esb/ ,addedOrder=60} 2009-07-15 11:40:26,516 INFO [STDOUT] ******************************************** Second run output ============== 2009-07-15 11:40:46,849 INFO [STDOUT] ********** CandidateIntakeAction - Candidate object populated ********** 2009-07-15 11:40:46,849 INFO [STDOUT] Candidate name = Fidel 2009-07-15 11:40:46,849 INFO [STDOUT] Candidate surname = Castro 2009-07-15 11:40:46,849 INFO [STDOUT] Candidate email = fidel.castro(a)gmail.com 2009-07-15 11:40:46,849 INFO [STDOUT] ************************************************************************ 2009-07-15 11:40:47,041 INFO [STDOUT] ********** SimpleBPMActionHandler ********** 2009-07-15 11:40:47,041 INFO [STDOUT] Object loaded with classloader: org.jboss.mx.loading.UnifiedClassLoader3@1769b56{ url=null ,addedOrder=60} 2009-07-15 11:40:47,041 INFO [STDOUT] Given classloader for class Candidate: org.jboss.mx.loading.UnifiedClassLoader3@1300751{ url=file:/home/mbaluch/work/build/jboss-soa-p.4.3.0.GA_CP01_CR7/jboss-as/server/production/deploy/Quickstart_jbpm_classloader_anomaly.esb/ ,addedOrder=61} 2009-07-15 11:40:47,041 INFO [STDOUT] !!! Classloader conflict between ClassName.class.getClassLoader() and instanceOfClassName.getClass().getClassLoader() !!! 2009-07-15 11:40:47,041 INFO [STDOUT] !!! Process will throw a ClassCastException !!! 2009-07-15 11:40:47,042 ERROR [org.jbpm.graph.def.GraphElement] action threw exception: org.jboss.soa.esb.xml2pojo.object.Candidate java.lang.ClassCastException: org.jboss.soa.esb.xml2pojo.object.Candidate <Stack-Trace> ... -- 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

4
10
0 / 0

[JBoss JIRA] Created: (JBPM-2456) jbpm.cfg.xml : resource.hibernate.properties seems to be ignored.

by Davy Toch (JIRA)

jbpm.cfg.xml : resource.hibernate.properties seems to be ignored. ----------------------------------------------------------------- Key: JBPM-2456 URL: https://jira.jboss.org/jira/browse/JBPM-2456 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.6 GA Environment: WinXP Java 1.5 Reporter: Davy Toch Priority: Minor jbpm.cfg.xml has the following content: <jbpm-configuration> <string name='resource.hibernate.properties' value='/be/fgov/minfin/stirint/gen/common/resources/PropertyGetter.properties'/> <string name='resource.hibernate.cfg.xml' value='/be/fgov/minfin/stirint/gen/bpm/hibernate.cfg.xml'/> </jbpm-configuration> However the value given to the property resource.hibernate.properties seems to be ignored, because in the logs I get: ... [2009-07-28 23:30:42,953] [INFO ] [org.jbpm.JbpmConfiguration] [] : using configuration resource: jbpm.cfg.xml [2009-07-28 23:30:43,328] [INFO ] [org.hibernate.cfg.Environment] [] : Hibernate 3.2.6 [2009-07-28 23:30:43,328] [INFO ] [org.hibernate.cfg.Environment] [] : hibernate.properties not found [2009-07-28 23:30:43,343] [INFO ] [org.hibernate.cfg.Environment] [] : Bytecode provider name : cglib [2009-07-28 23:30:43,343] [INFO ] [org.hibernate.cfg.Environment] [] : using JDK 1.4 java.sql.Timestamp handling [2009-07-28 23:30:43,406] [INFO ] [org.hibernate.cfg.Configuration] [] : configuring from resource: /be/fgov/minfin/stirint/gen/bpm/hibernate.cfg.xml [2009-07-28 23:30:43,406] [INFO ] [org.hibernate.cfg.Configuration] [] : Configuration resource: /be/fgov/minfin/stirint/gen/bpm/hibernate.cfg.xml ... Also in hibernate.cfg.xml I refer to the property ${datasource} as datasource JNDI name which is defined in my PropertyGetter.properties, but apparently it's not replaced when I do a unit test. -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-2503) Maven pom file for jbpm-jpdl should define jackrabbit-core dependency as optional

by Marek Novotny (JIRA)

Maven pom file for jbpm-jpdl should define jackrabbit-core dependency as optional --------------------------------------------------------------------------------- Key: JBPM-2503 URL: https://jira.jboss.org/jira/browse/JBPM-2503 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.5.SP5 Reporter: Marek Novotny jackrabbit-core implementation of JCR should be defined as optional dependency, because any maven based project which doesn't need to use JCR jbpm feature downloads this dependency and also its transitive dependencies. If you look at http://maven.apache.org/guides/introduction/introduction-to-optional-and-..., there is clear description why use <optional>true</optional> in maven project. Please fix the jbpm-jpdl pom file. -- 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

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues November 2010