September 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2523) document parameters in installation scripts

by Tom Baeyens (JIRA)

document parameters in installation scripts ------------------------------------------- Key: JBPM-2523 URL: https://jira.jboss.org/jira/browse/JBPM-2523 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.2 -- 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 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2548) remove deployment query name property to fix oracle name clob orderBy problem

by Tom Baeyens (JIRA)

remove deployment query name property to fix oracle name clob orderBy problem ----------------------------------------------------------------------------- Key: JBPM-2548 URL: https://jira.jboss.org/jira/browse/JBPM-2548 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.2 -- 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 months

1
4
0 / 0

[JBoss JIRA] Created: (JBPM-2487) Bug in GroupActivity.execute(ExecutionImpl execution)

by Michael Wohlfart (JIRA)

Bug in GroupActivity.execute(ExecutionImpl execution) ----------------------------------------------------- Key: JBPM-2487 URL: https://jira.jboss.org/jira/browse/JBPM-2487 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Reporter: Michael Wohlfart just browsing through the codebase and trying to understand the magic, I came across this in line 56 of GroupActivity.java: ExecutionImpl concurrentRoot = null; if (Execution.STATE_ACTIVE_ROOT.equals(execution.getState())) { concurrentRoot = execution; } else if (Execution.STATE_ACTIVE_ROOT.equals(execution.getState())) { concurrentRoot = execution.getParent(); } else { throw new JbpmException("illegal state"); } I assume getState() doesn't have any side effects, so I guess this is a bug -- 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 months

4
13
0 / 0

[JBoss JIRA] Created: (JBPM-2552) Deploying process definitions without Java classes leads to undeployable process definitions and breaks the console

by Sebastian Schneider (JIRA)

Deploying process definitions without Java classes leads to undeployable process definitions and breaks the console ------------------------------------------------------------------------------------------------------------------- Key: JBPM-2552 URL: https://jira.jboss.org/jira/browse/JBPM-2552 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1 Environment: Windows Server 2003 (x64), Tomcat 6.02 Reporter: Sebastian Schneider Priority: Minor If you use the deployment task supplied by jBPM in ant to deploy process definitions and you forget to take care of the deployment of the jar-file with the classes like decision handlers referenced in the process definition the deployment will be successful but you will run into trouble afterwards. You won't be able to view the list of available in process definitions in the jbpm-console but instead an exception is thrown: java.lang.ClassCastException: org.jbpm.jpdl.internal.model.JpdlProcessDefinition cannot be cast to java.util.List Using deleteDeployment or deleteDeploymentCascade offered by the RepositoryService you won't be able to remove the deployments since you run into the same exception. So this actually breaks your jbpm-installation. Putting the jar into the lib-Folder of Tomcat and a restart seem to help but it is strange that missing classes break the process definition overview and that the deployments cannot be deleted. -- 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 months

2
9
0 / 0

[JBoss JIRA] Created: (JBPM-2522) sql syntax error when removing processdefinition

by Sofie Ravyts (JIRA)

sql syntax error when removing processdefinition ------------------------------------------------ Key: JBPM-2522 URL: https://jira.jboss.org/jira/browse/JBPM-2522 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1 Environment: checked on latest jbpm4 trunk source files Reporter: Sofie Ravyts When calling repositoryService.deleteDeployment(deploymentId); I get the following sql syntax error: "Unknown column 'myprocess' in 'where clause'" This is the sql statement that gets executed: select deployment1_.OBJNAME_ as col_0_0_, deployment1_.DEPLOYMENT_ as col_1_0_ from JBPM4_DEPLOYMENT deployment0_, JBPM4_DEPLOYPROP deployment1_, JBPM4_DEPLOYPROP deployment2_, JBPM4_DEPLOYPROP deployment3_ where deployment1_.KEY_='pdid' and deployment1_.DEPLOYMENT_=deployment0_.DBID_ and deployment2_.KEY_='pdkey' and deployment2_.OBJNAME_=deployment1_.OBJNAME_ and deployment2_.DEPLOYMENT_=deployment0_.DBID_ and deployment3_.KEY_='pdversion' and deployment3_.OBJNAME_=deployment1_.OBJNAME_ and deployment3_.DEPLOYMENT_=deployment0_.DBID_ and deployment1_.DEPLOYMENT_=myprocess-4 There should be quotes around myprocess-4 to fix the sql statement => see ProcessDefinitionQueryImpl: if (deploymentId!=null) { appendWhereClause("idProperty.deployment.dbid = "+deploymentId+" ", hql); } should be (imho) if (deploymentId!=null) { appendWhereClause("idProperty.deployment.dbid = '"+deploymentId+"' ", hql); } -- 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 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2388) extend coverage of jpdl process conversion tool

by Tom Baeyens (JIRA)

extend coverage of jpdl process conversion tool ----------------------------------------------- Key: JBPM-2388 URL: https://jira.jboss.org/jira/browse/JBPM-2388 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Jim Ma Fix For: jBPM 4.1 Further elaborate on the work started in jBPM 4.0 -- 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 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2036) StaleObjectStateException when timer firing leads to process end and timer has 'repeat' attribute set

by Martin Putz (JIRA)

StaleObjectStateException when timer firing leads to process end and timer has 'repeat' attribute set ----------------------------------------------------------------------------------------------------- Key: JBPM-2036 URL: https://jira.jboss.org/jira/browse/JBPM-2036 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.3.1 GA, jBPM-3.2.5.SP1 Reporter: Martin Putz Assignee: Alejandro Guizar Fix For: jBPM 3.2.6 GA With the following timer definition on a state node <state name='state1'> <timer name='timer-to-end-with-repeat' duedate='1 second' repeat='5 seconds'> <action class='org.jbpm.scheduler.exe.TimerDbTest$Signal' /> </timer> <transition name='to_end' to='end'/> </state> and the action class execute() method being public void execute(ExecutionContext executionContext) throws Exception { executionContext.leaveNode(); } leads to: 2009-02-10 21:38:45,404 16508 ERROR [org.hibernate.event.def.AbstractFlushingEventListener] (JbpmJobExecutor:127.0.0.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.Timer#86] at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1769) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2412) at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2312) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2612) at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:96) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:168) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at org.jbpm.persistence.db.DbPersistenceService.commit(DbPersistenceService.java:226) at org.jbpm.persistence.db.DbPersistenceService.endTransaction(DbPersistenceService.java:131) at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:197) at org.jbpm.svc.Services.close(Services.java:243) at org.jbpm.JbpmContext.close(JbpmContext.java:133) at org.jbpm.job.executor.JobExecutorThread.executeJob(JobExecutorThread.java:194) at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:61) If 'repeat' is not set, the process finishes just fine. -- 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 months

6
30
0 / 0

[JBoss JIRA] Created: (JBPM-2037) Release jBPM 3.2.7 GA

by Thomas Diesler (JIRA)

Release jBPM 3.2.7 GA --------------------- Key: JBPM-2037 URL: https://jira.jboss.org/jira/browse/JBPM-2037 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: jBPM 3.2.6 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, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-2290) Default config should use the db based implementations for messaging and scheduler service

by Martin Putz (JIRA)

Default config should use the db based implementations for messaging and scheduler service ------------------------------------------------------------------------------------------ Key: JBPM-2290 URL: https://jira.jboss.org/jira/browse/JBPM-2290 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 3.2.5.SP5 Reporter: Martin Putz Fix For: SOA 4.3 CP02 The default configuration in the jbpm-jpdl-3.2.5SP5 package defines the usage of the JmsMessageServiceFactory for the 'message' service and EntitySchedulerServiceFactory for the 'scheduler' service in /deploy/server/default/deploy/jbpm/jbpm-service.sar/jbpm.cfg.xml. The default configuration should use the db based implementations for these services instead, as it used to be in previous versions. -- 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 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2524) extract hibernate reference from jbpm.default.cfg.xml

by Tom Baeyens (JIRA)

extract hibernate reference from jbpm.default.cfg.xml ----------------------------------------------------- Key: JBPM-2524 URL: https://jira.jboss.org/jira/browse/JBPM-2524 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.2 make it easier to customize the 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, 2 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues September 2009