October 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2508) report initialization crashes the console

by Tom Baeyens (JIRA)

report initialization crashes the console ----------------------------------------- Key: JBPM-2508 URL: https://jira.jboss.org/jira/browse/JBPM-2508 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Tom Baeyens Assignee: Heiko Braun Fix For: jBPM 4.2 First time when the reports are accessed, the request times out and the console cannot show the reports. Reports cannot be made visible afterwards. Workaround: log out and log back in. -- 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

4
8
0 / 0

[JBoss JIRA] Created: (JBPM-2143) jBPM creates two indices for each foreign key column on MySQL

by Jiri Pechanec (JIRA)

jBPM creates two indices for each foreign key column on MySQL ------------------------------------------------------------- Key: JBPM-2143 URL: https://jira.jboss.org/jira/browse/JBPM-2143 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.2.5.SP5 Reporter: Jiri Pechanec The SQL scripts for MySQL contains two independent index creations for each indexed foreign key column - see sample create index IDX_LOG_SOURCENODE on JBPM_LOG (SOURCENODE_); alter table JBPM_LOG add index FK_LOG_SOURCENODE (SOURCENODE_), add constraint FK_LOG_SOURCENODE foreign key (SOURCENODE_) references JBPM_NODE (ID_); -- 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

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-2608) JobSession.findJobsWithOverdueLockTime returns incorrect list of overdue jobs for LockMonitorThread

by Martin Putz (JIRA)

JobSession.findJobsWithOverdueLockTime returns incorrect list of overdue jobs for LockMonitorThread --------------------------------------------------------------------------------------------------- Key: JBPM-2608 URL: https://jira.jboss.org/jira/browse/JBPM-2608 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.7, jBPM 3.2.8 Reporter: Martin Putz Assignee: Alejandro Guizar Fix For: jBPM 3.2.9 In org.jbpm.job.executor.LockMonitorThread#unlockOverdueJobs(), the list of overdue jobs to be unlocked is queried the following way: Date threshold = new Date(System.currentTimeMillis() - maxLockTime - lockBufferTime); List overdueJobs = jbpmContext.getJobSession().findJobsWithOverdueLockTime(threshold); But the query is incorrect, as it returns all jobs where the lockTime is bigger than the threshold, which means that the job has been locked shorter than (maxLockTime + lockBufferTime): <query name="JobSession.findJobsWithOverdueLockTime"> <![CDATA[ select job from org.jbpm.job.Job as job where job.lockTime > :threshold ]]> </query> As a result, the LockMonitorThread will set the lockTime and lockOwner to null, where the same Job instance is also updated by a JobExecutorThread, which will lead to a StaleObjectStateException: ERROR [org.hibernate.event.def.AbstractFlushingEventListener] (JbpmJobExector:LockMonitorThread@169.1.1.1) Could not synchronize database state with session org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.job.ExecuteActionJob#123] The 'where' clause in the query needs to be reversed: Index: modules/core/src/main/resources/org/jbpm/db/hibernate.queries.hbm.xml =================================================================== --- modules/core/src/main/resources/org/jbpm/db/hibernate.queries.hbm.xml (revision 5825) +++ modules/core/src/main/resources/org/jbpm/db/hibernate.queries.hbm.xml (working copy) @@ -385,7 +385,7 @@ <![CDATA[ select job from org.jbpm.job.Job as job - where job.lockTime > :threshold + where job.lockTime < :threshold ]]> </query> -- 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

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2616) clean up JpdlDeployer

by Tom Baeyens (JIRA)

clean up JpdlDeployer --------------------- Key: JBPM-2616 URL: https://jira.jboss.org/jira/browse/JBPM-2616 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.3 still quite some dead code in there. i think about most of it :-) -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2491) Deleting a ProcessInstance having a running Sub-ProcessInstance fails

by Flavio Donzé (JIRA)

Deleting a ProcessInstance having a running Sub-ProcessInstance fails --------------------------------------------------------------------- Key: JBPM-2491 URL: https://jira.jboss.org/jira/browse/JBPM-2491 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Reporter: Flavio Donzé When trying to delete a ProcessInstance using ExecutionService.deleteProcessInstance() an SQLException is thrown if the ProcessInstance has a running Sub-ProcessInstance. Trying to delete the Sub-ProcessInstance first doesn't work either. The problem here are the foreign key constraints: Deleting the super process: org.postgresql.util.PSQLException: ERROR: update or delete on table "jbpm4_execution" violates foreign key constraint "fk_exec_superexec" on table "jbpm4_execution" Detail: Key (dbid_)=(176) is still referenced from table "jbpm4_execution". Deleting the sub process: org.postgresql.util.PSQLException: ERROR: update or delete on table "jbpm4_execution" violates foreign key constraint "fk_exec_subpi" on table "jbpm4_execution" Detail: Key (dbid_)=(179) is still referenced from table "jbpm4_execution". Maybe loosen up the sub>super constraint? -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2291) Process project creation wizard in JBDS 2.0 fails to create a complete sample project a jBPM runtime as provided in SOA-P 4.3CP01

by Tom Baeyens (JIRA)

Process project creation wizard in JBDS 2.0 fails to create a complete sample project a jBPM runtime as provided in SOA-P 4.3CP01 --------------------------------------------------------------------------------------------------------------------------------- Key: JBPM-2291 URL: https://jira.jboss.org/jira/browse/JBPM-2291 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Alejandro Guizar Fix For: SOA 4.3 CP02 Koen: "The jBPM designer and the runtime have one integration point: a configuration file called 'version.info.xml'. This file contains the version info of the runtime and the jar files that need to be on the classpath of a jbpm project in the gpd. If one of the jar files is not necessary anymore for various reasons, and it is removed from the runtime than it should also be removed from the file (if it is referenced in the file of course). " -- 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, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-2415) add declaration of process variables

by Tom Baeyens (JIRA)

add declaration of process variables ------------------------------------ Key: JBPM-2415 URL: https://jira.jboss.org/jira/browse/JBPM-2415 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 -- 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, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-2403) Fork Activity FIX. PVM trunk.

by Mark Kedzierski (JIRA)

Fork Activity FIX. PVM trunk. ------------------------------ Key: JBPM-2403 URL: https://jira.jboss.org/jira/browse/JBPM-2403 Project: JBoss jBPM Issue Type: Patch Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.x Environment: Windows, JBoss 5.1.0.GA Reporter: Mark Kedzierski Fix For: jBPM 4.x Fork activity is broken in the jbpm4 pvm module under the svn trunk. This is caused by a recent commit to org.jbpm.pvm.internal.model.DefaultIdGenerator. My patch is included. The hibernate save happens before the execution.id is set, resulting in a UniqueConstraintException on the commit. -- 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, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (JBPM-2606) Process files not suffixed with .jpdl.xml are not loaded correctly

by Paul Smith (JIRA)

Process files not suffixed with .jpdl.xml are not loaded correctly ------------------------------------------------------------------ Key: JBPM-2606 URL: https://jira.jboss.org/jira/browse/JBPM-2606 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.1 Environment: Windows XP using JBPM4.1 Reporter: Paul Smith If you try to deploy a process definition in a file that is not suffixed with .jpdl.xml then then the process is not deployed correctly. I have demonstrated this with the code in the attached jar file. There are two identical processes one called helloWorldOK and one called helloWorldBroken. One is in a file suffixed as .jpdl.xml and the other suffixed as _jpdl.xml. Both files seem to deploy correctly but when one tries to perform a startProcessInstanceByKey the process contained in the file suffixed by _jpdl.xml cannot be located. I have tried this with other file suffixes but it seems the file MUST be suffixed with .jpdl.xml. The name of the file should be irrelevant as all information is contained in the xml. -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2595) introduce an attribute "description" for transitions and show it in the process diagram

by Sebastian Schneider (JIRA)

introduce an attribute "description" for transitions and show it in the process diagram --------------------------------------------------------------------------------------- Key: JBPM-2595 URL: https://jira.jboss.org/jira/browse/JBPM-2595 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Sebastian Schneider Priority: Minor Fix For: jBPM 4.3 Normally I prefer to use short "kind of technical" names for the transitions but I would rather have a long name or a description in the process diagram which is shown by the console. So my suggestion is to add an attribute description to transitions and to display the transitions' descriptions instead of their names in the diagram. If the description is not set or empty the name could be displayed instead. By the term description I don't mean a long text but rather a long user friendly name for the transition in contrast to a short technical one. -- 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, 1 month

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues October 2009