November 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2537) A triggered timer does not end the task which is left

by Alexis Seigneurin (JIRA)

A triggered timer does not end the task which is left ----------------------------------------------------- Key: JBPM-2537 URL: https://jira.jboss.org/jira/browse/JBPM-2537 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0, jBPM 4.1 Reporter: Alexis Seigneurin In my process definition, "task1" has a transition with a due date. When this timer is triggered by the job executor, the transition takes the process to "task2" but "task1" still looks active. For instance, when I run a "task query", instead of only finding "task2", both "task1" and "task2" are found. Here is my process definition: <?xml version="1.0" encoding="UTF-8"?> <process name="test1" xmlns="http://jbpm.org/4.0/jpdl"> <start g="-9,192,48,48" name="start1"> <transition g="-44,-18" name="to task3" to="task3" /> </start> <end g="490,192,48,48" name="end1" /> <task g="272,189,92,52" name="task1"> <transition g="-42,-18" name="to end1" to="end1" /> <transition g="-45,-18" name="to java1" to="reminder"> <timer duedate="10 seconds" /> </transition> </task> <java class="fr.idm.SimpleReminder" g="272,316,92,52" method="remind" name="reminder"> <transition to="task2" /> </java> <end g="626,319,48,48" name="end2" /> <task g="454,316,92,52" name="task2"> <transition g="-42,-18" name="to end2" to="end2" /> </task> <task g="113,189,92,52" name="task3"> <transition g="-44,-18" to="task1" name="to end1" /> </task> </process> For testing purpose, I introduced "task3" before "task1". It is not listed by the task query, which makes me think that, once "task1" is left, it should no longer be active. This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution does not seem applicable to JBPM 4.x. I will attached the whole source code. -- 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, 1 month

8
60
0 / 0

[JBoss JIRA] Created: (JBPM-2444) sub-process-key does not evaluate EL

by Robert Moskal (JIRA)

sub-process-key does not evaluate EL ------------------------------------ Key: JBPM-2444 URL: https://jira.jboss.org/jira/browse/JBPM-2444 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Reporter: Robert Moskal I thought that the sub-process-key (or id) could be an expression the way name could be in the 3.2 product. However, specifying something like this: <sub-process g="228,193,92,52" name="ConcreteWork" sub-process-key="#{SKYLINE_FLOW}"> Always results in the literal value being passed to SubProcessActivity subProcessKey. So, in the above example subProcessKey is "#{SKYLINE_FLOW}" -- 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, 1 month

5
9
0 / 0

[JBoss JIRA] Created: (JBPM-1162) Problem with exception handling within the Decision nodes

by Jon Folland (JIRA)

Problem with exception handling within the Decision nodes --------------------------------------------------------- Key: JBPM-1162 URL: http://jira.jboss.com/jira/browse/JBPM-1162 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: Vaio laptop running Windows Vista, Java 1.5, JBPM 3.2.2 Reporter: Jon Folland Assigned To: Tom Baeyens I believe there may be a bug in the Decision class where exception handling is concerned which causes this failure: If the line: String transitionName = decisionHandler.decide(executionContext); ... ...in the method public void execute(ExecutionContext executionContext) throws an exception, which is caught here in the same method: raiseException(exception, executionContext); We miss the block: if (transition==null) { transition = getDefaultLeavingTransition(); log.debug("decision didn't select transition, taking default "+transition); } So when executionContext.leaveNode(transition); is called at the bottom, there wil be no transition set. I believe we need to check for a tranistion==null condition regardless of whether an excpetion has been handled. Otherwise you will never be able to handle an exception in a Decision without another unhandled exception being thrown (which kind of defeits the point :-) -- 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

14 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2641) taskService.addTaskParticipatingUser adds multiple participations for a user

by Robert Moskal (JIRA)

taskService.addTaskParticipatingUser adds multiple participations for a user ---------------------------------------------------------------------------- Key: JBPM-2641 URL: https://jira.jboss.org/jira/browse/JBPM-2641 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Environment: JDK 1.6 HSQL Reporter: Robert Moskal Perhaps this is the intended behavior, but calling taskService.addTaskParticipatingUser with the same user creates multiple participates: taskService.addTaskParticipatingUser(_task.getId(), "boss_rigging", Participation.CANDIDATE); taskService.addTaskParticipatingUser(_task.getId(), "boss_rigging", Participation.CANDIDATE); assertEquals(1,taskService.createTaskQuery().candidate("boss_rigging").activityName("Investigate").list().size()); The query comes back with two tasks. This is somewhat surprising. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2596) Invalid types.xml doesn't result in a parsing error

by Sebastian Schneider (JIRA)

Invalid types.xml doesn't result in a parsing error ---------------------------------------------------- Key: JBPM-2596 URL: https://jira.jboss.org/jira/browse/JBPM-2596 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0, jBPM 4.1 Environment: not relevant Reporter: Sebastian Schneider An invalid types.xml should result in a parsing error and thus in an exception being thrown. -- 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, 1 month

4
9
0 / 0

[JBoss JIRA] Created: (JBPM-2642) A patch to support DB2 on zOS

by Richard L. Burton III (JIRA)

A patch to support DB2 on zOS ----------------------------- Key: JBPM-2642 URL: https://jira.jboss.org/jira/browse/JBPM-2642 Project: jBPM Issue Type: Patch Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.8, jBPM 3.2.7 Environment: Java version: 1.6.0_16,Sun Microsystems Inc., OS-System: Windows XP 5.1,x86, jboss-soa-p.4.3.0, DB2, version: DSN09015, Hibernate 3.2.4.sp1.cp08 Reporter: Richard L. Burton III Priority: Blocker Attachments: findJobsWithOverdueLockTime.patch When using jBPM with DB2 on zOS the JobSession object throws an exception when trying to find jobs with overdue lock time. The exception thrown is: DB2 SQL error: SQLCODE: -180, SQLSTATE: 22007, SQLERRMC: 1 I attached a patch which corrects this problem. Currently JobSession#findJobsWithOverdueLockTime(Date) is using Query#setDate(..) instead of Query#setTimestamp(...) This isn't a problem when using the DB2 Universal version on windows, only on zOS. -- 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, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-2164) Document JbpmSchema API and ant task

by Taro Yasuma (JIRA)

Document JbpmSchema API and ant task ------------------------------------ Key: JBPM-2164 URL: https://jira.jboss.org/jira/browse/JBPM-2164 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.6.SP1 Reporter: Taro Yasuma Document JbpmSchema API and ant task. For instance, to drop jBPM schema you can use the two ways. Programatically: JbpmSchema.dropSchema() Through Ant: <jbpmschema output="${scriptsdir}/jbpm.jpdl.postgresql.sql" config="hibernate.cfg.postgresql.xml" action="drop" delimiter=";"/> We need to elaborate how to use those in our docs. -- 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, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-1158) Missing query JobSession.findJobsWithOverdueLockTime in hibernate.queries.hbm.xml

by Julien Kronegg (JIRA)

Missing query JobSession.findJobsWithOverdueLockTime in hibernate.queries.hbm.xml --------------------------------------------------------------------------------- Key: JBPM-1158 URL: http://jira.jboss.com/jira/browse/JBPM-1158 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: zip file downloaded from http://www.jboss.org/downloading/?projectId=jbossjbpm&url=http://download... Reporter: Julien Kronegg Assigned To: Tom Baeyens The org.jbpm.db.JobSession class has a findJobsWithOverdueLockTime(Date) method which use a query named "JobSession.findJobsWithOverdueLockTime". In similar methods of the same class, the queries are located in org.jbpm.db.hibernate.queries.hbm.xml, which is not the case for this query. The "JobSession.findJobsWithOverdueLockTime" string could not be found elsewhere in the project. Conclusion: the "JobSession.findJobsWithOverdueLockTime" query seems to be missing in hibernate.queries.hbm.xml (or the method should be removed from the class). -- 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

14 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1139) The ClassUtil class is not thread-safe

by Wojciech Gdela (JIRA)

The ClassUtil class is not thread-safe -------------------------------------- Key: JBPM-1139 URL: http://jira.jboss.com/jira/browse/JBPM-1139 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.3 Reporter: Wojciech Gdela Assigned To: Tom Baeyens Attachments: ClassUtil-concurrency-issue.zip The ClassUtil class is not thread-safe. The exception will occur when two thread simultanously try do deserialize variables from two different process definitions. Look at the code: {code} public ContextObjectInputStream(final InputStream in, ProcessInstance processInstance) throws IOException { super(in); this.setProcessInstance(processInstance); ClassUtil.setProcessInstance(processInstance); } ... protected Class resolveClass(final ObjectStreamClass desc) throws IOException, ClassNotFoundException { return ClassUtil.forName(desc.getName(), ContextObjectInputStream.class); } ... ContextObjectInputStream cois = new ContextObjectInputStream(bais, definition.createProcessInstance()); // when here another thread tries to execute the same code with another process instance there will be a problem return cois.readObject(); {/code} Further description of issue is in attached test case. -- 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

14 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2591) Simulation module has transitive dependency on commons-beanutils

by Alejandro Guizar (JIRA)

Simulation module has transitive dependency on commons-beanutils ---------------------------------------------------------------- Key: JBPM-2591 URL: https://jira.jboss.org/jira/browse/JBPM-2591 Project: jBPM Issue Type: Task Components: Runtime Engine Affects Versions: jBPM 3.2.8 Environment: hsqldb java14 linux Reporter: Alejandro Guizar Priority: Minor Fix For: jBPM 3.2.x A recent CI build failed due to: [INFO] Compilation failure /qa/hudson_ws/workspace/jbpm3-jboss405/database/hsqldb/jdk/java14/label/linux/jbpm/modules/simulation/src/main/java/org/jbpm/sim/def/JbpmSimulationModel.java:[10,36] package org.apache.commons.beanutils does not exist /qa/hudson_ws/workspace/jbpm3-jboss405/database/hsqldb/jdk/java14/label/linux/jbpm/modules/simulation/src/main/java/org/jbpm/sim/def/JbpmSimulationModel.java:[607,8] cannot find symbol symbol : variable PropertyUtils location: class org.jbpm.sim.def.JbpmSimulationModel /qa/hudson_ws/workspace/jbpm3-jboss405/database/hsqldb/jdk/java14/label/linux/jbpm/modules/simulation/src/main/java/org/jbpm/sim/def/JbpmSimulationModel.java:[609,23] cannot find symbol symbol : variable PropertyUtils location: class org.jbpm.sim.def.JbpmSimulationModel jbpm-simulation depends on jasperreports which in turn depends on commons-beanutils. Yet jbpm-simulation uses commons-beanutils directly, and should not rely on jasperreports' dependencies. -- 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, 1 month

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues November 2009