April 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2092) Byte Array Should Be In Default Cache Configuration

by Brad Davis (JIRA)

Byte Array Should Be In Default Cache Configuration --------------------------------------------------- Key: JBPM-2092 URL: https://jira.jboss.org/jira/browse/JBPM-2092 Project: JBoss jBPM Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: Core Engine, Documentation Affects Versions: jBPM 3.3.1 GA Reporter: Brad Davis The hibernate configuration should cache byte array by default. It is missing from the caching configuration. This leads to major performance issues when deploying handler logic classes [java action handlers and decision handlers for example] to the database. -- 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

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2093) Stabilize EjbSchedulerTest.testScheduleFork under MySQL

by Alejandro Guizar (JIRA)

Stabilize EjbSchedulerTest.testScheduleFork under MySQL ------------------------------------------------------- Key: JBPM-2093 URL: https://jira.jboss.org/jira/browse/JBPM-2093 Project: JBoss jBPM Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.2.6 GA , jBPM-3.2.5.SP3 Environment: JBoss 5.0.0.GA MySQL 5.0.67 Sun JDK 1.5.0.16 Reporter: Alejandro Guizar testScheduleFork fails with: org.jbpm.JbpmException: event 'process-end' did not occur within 300000 ms at org.jbpm.graph.def.EventCallback.waitForEvent(EventCallback.java:125) at org.jbpm.graph.def.EventCallback.waitForEvent(EventCallback.java:106) at org.jbpm.enterprise.ejbtimer.EjbSchedulerTest.testScheduleFork(EjbSchedulerTest.java:265) -- 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

15 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1367) Add QA for oracle

by Thomas Diesler (JIRA)

Add QA for oracle ----------------- Key: JBPM-1367 URL: http://jira.jboss.com/jira/browse/JBPM-1367 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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

15 years, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (JBPM-1286) Provide minimal console test coverage

by Thomas Diesler (JIRA)

Provide minimal console test coverage ------------------------------------- Key: JBPM-1286 URL: http://jira.jboss.com/jira/browse/JBPM-1286 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: jPDL 3 Reporter: Thomas Diesler Fix For: jBPM jPDL 3.2.4 -- 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

15 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2119) Work around the need for an extra column to persist field Join.parentLockMode

by Alejandro Guizar (JIRA)

Work around the need for an extra column to persist field Join.parentLockMode ----------------------------------------------------------------------------- Key: JBPM-2119 URL: https://jira.jboss.org/jira/browse/JBPM-2119 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM-3.2.5.SP4 Reporter: Alejandro Guizar Assignee: Alejandro Guizar Priority: Blocker Fix For: jBPM 3.2.7 GA In JBPM-1755, a new column PARENTLOCKMODE_ was added to table JBPM_NODE for persisting field Join.parentLockMode. Turns out the schema change is a barrier for our customers to upgrade to newer versions. The proposed solution is to provide two different mappings for the Join class, with and without the column. The provided Hibernate configuration will include the mapping without the column by default. Interested parties may inclde the version with the column in their own Hibernate configuration. -- 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

15 years, 5 months

1
6
0 / 0

[JBoss JIRA] Created: (JBPM-2189) Restarting server creates a new version of Process Definitions

by Uday (JIRA)

Restarting server creates a new version of Process Definitions -------------------------------------------------------------- Key: JBPM-2189 URL: https://jira.jboss.org/jira/browse/JBPM-2189 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Uday Assignee: Heiko Braun Fix For: GWT Console 1.0.x Ability to view process image at the global level and per process instance -- 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

15 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2062) remove version specification in module pom dependencies

by Tom Baeyens (JIRA)

remove version specification in module pom dependencies ------------------------------------------------------- Key: JBPM-2062 URL: https://jira.jboss.org/jira/browse/JBPM-2062 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens currently, the dependencies on jbpm modules have the version specified when they are used. this is also done in the parent pom so that is actually not necessary. the fix is that the version specification in the module poms should be 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

15 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2040) Inconsistent behaviour depending on the ordering of events (fork+end state+join)

by Thomas Diesler (JIRA)

Inconsistent behaviour depending on the ordering of events (fork+end state+join) -------------------------------------------------------------------------------- Key: JBPM-2040 URL: https://jira.jboss.org/jira/browse/JBPM-2040 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.2.3 Reporter: Mauro Molinari Assignee: Thomas Diesler Given the following process definition: <?xml version="1.0" encoding="UTF-8"?> <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="Complex"> <description> Complex description </description> <start-state name="start-state1"> <transition to="task-node1"></transition> </start-state> <task-node name="task-node3"> <task name="Task3_1"> <assignment actor-id="1"></assignment> </task> <transition to="end-state1"></transition> </task-node> <node name="node1"> <transition to="task-node3"></transition> </node> <join name="join1"> <transition to="node1"></transition> </join> <fork name="fork1"> <transition to="task-node2"></transition> <transition to="node2" name="to node2"></transition> <transition to="state1" name="to state1"></transition> </fork> <task-node name="task-node2"> <task name="Task2_1"> <assignment actor-id="1"></assignment> </task> <task name="Task2_2"> <assignment actor-id="1"></assignment> </task> <transition to="join1"></transition> </task-node> <task-node name="task-node1"> <task name="Task1_1"> <assignment actor-id="1"></assignment> </task> <transition to="fork1"></transition> </task-node> <node name="node2"> <transition to="end-state2"></transition> </node> <state name="state1"> <transition to="end-state2"></transition> </state> <end-state name="end-state1"></end-state> <end-state name="end-state2"></end-state> </process-definition> Try to do this: - create a process instance and start it - a Task1_1 instance is created: end it - the root token halts at the fork and three children tokens are created 1) the first causes the creation of a Task2_1 instance and of a Task2_2 instance 2) the second halts at the state1 state 3) the third dies at the end-state2 state Now, there are two cases: CASE A) - signal the second token: it then goes on and dies at end-state2 state - end Task2_1 and Task2_2 instances so that the first token goes on and reaches the join - now, the root token is restored and goes through node1 and task-node3 nodes, causing the creation of a Task3_1 instance This is what I would expect! CASE B) - end Task2_1 and Task2_2 instances so that the first token goes on and reaches the join - signal the second token: it then goes on and dies at end-state2 state - now, the root token is ended, halting the process instance! This is not the expected behaviour, as I would expect that the root token is restored because now all the sibling tokens of those that have reached the join node are ended, so the parent token (= the root token) should be restored and should continue to node1 and subsequent nodes. Moreover, I would not expect that the behaviour is different depending on the ordering of the actions "signal the state1 token" and "signal the task-node2 token". My suspect is this: in case B) the join node is not "triggered" anymore after Task2_1 and Task2_2 are ended, so it can't restore the parent node. Moreover, when the second children token is signalled, it reaches end-state2: jBPM then realizes that all of the sibling tokens are also ended, so it wrongly decides that the parent token should also be ended. -- 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

15 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-2014) Provide equivalent activities as in jBPM3

by Heiko Braun (JIRA)

Provide equivalent activities as in jBPM3 ----------------------------------------- Key: JBPM-2014 URL: https://jira.jboss.org/jira/browse/JBPM-2014 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine Reporter: Heiko Braun Assignee: Heiko Braun jBPM4 should have at least the same functional scope then jBPM3. -- 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

15 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1968) Console integration for jbpm3 doesn't write start instance logs

by Heiko Braun (JIRA)

Console integration for jbpm3 doesn't write start instance logs --------------------------------------------------------------- Key: JBPM-1968 URL: https://jira.jboss.org/jira/browse/JBPM-1968 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 3.3.2 GA -- 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

15 years, 6 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues April 2009