October 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2601) make sure upgrade on postgresql deletes the hibernate_sequence table

by Tom Baeyens (JIRA)

make sure upgrade on postgresql deletes the hibernate_sequence table -------------------------------------------------------------------- Key: JBPM-2601 URL: https://jira.jboss.org/jira/browse/JBPM-2601 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

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Assigned: (JBPM-1451) Check that jBPM can be run against all of the Tier 1 databases for SOA-P.

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1451?page=com.atlassian.jira.plug... ] Alejandro Guizar reassigned JBPM-1451: -------------------------------------- Assignee: Alejandro Guizar (was: Len DiMaggio) > Check that jBPM can be run against all of the Tier 1 databases for SOA-P. > ------------------------------------------------------------------------- > > Key: JBPM-1451 > URL: https://jira.jboss.org/jira/browse/JBPM-1451 > Project: jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Runtime Engine > Reporter: Mark Little > Assignee: Alejandro Guizar > Fix For: jBPM 3.2.8 > > > Do we need special initialisation scripts as well? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1451) Check that jBPM can be run against all of the Tier 1 databases for SOA-P.

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1451?page=com.atlassian.jira.plug... ] Alejandro Guizar resolved JBPM-1451. ------------------------------------ Resolution: Done As of 3.2.7 jBPM works with all tier-1 databases. > Check that jBPM can be run against all of the Tier 1 databases for SOA-P. > ------------------------------------------------------------------------- > > Key: JBPM-1451 > URL: https://jira.jboss.org/jira/browse/JBPM-1451 > Project: jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Runtime Engine > Reporter: Mark Little > Assignee: Len DiMaggio > Fix For: jBPM 3.2.8 > > > Do we need special initialisation scripts as well? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1451) Check that jBPM can be run against all of the Tier 1 databases for SOA-P.

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1451?page=com.atlassian.jira.plug... ] Alejandro Guizar updated JBPM-1451: ----------------------------------- Fix Version/s: jBPM 3.2.8 (was: jBPM 3.2.x) > Check that jBPM can be run against all of the Tier 1 databases for SOA-P. > ------------------------------------------------------------------------- > > Key: JBPM-1451 > URL: https://jira.jboss.org/jira/browse/JBPM-1451 > Project: jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Runtime Engine > Reporter: Mark Little > Assignee: Len DiMaggio > Fix For: jBPM 3.2.8 > > > Do we need special initialisation scripts as well? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2599) Unable to start new process

by Heiko Braun (JIRA)

Unable to start new process --------------------------- Key: JBPM-2599 URL: https://jira.jboss.org/jira/browse/JBPM-2599 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Fix For: jBPM 4.2 When i try to start a new process. I get this: Caused by: org.jbpm.api.JbpmException: invalid transaction state: STATUS_ACTIVE at org.jbpm.pvm.internal.tx.jta.JtaTransactionInterceptor.execute(JtaTransactionInterceptor.java:62) at org.jbpm.pvm.internal.tx.jta.JtaRetryInterceptor.executeWithoutRetry(JtaRetryInterceptor.java:56) at org.jbpm.pvm.internal.tx.jta.JtaRetryInterceptor.execute(JtaRetryInterceptor.java:48) at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53) at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40) at org.jbpm.pvm.internal.id.DatabaseDbidGenerator.acquireDbidBlock(DatabaseDbidGenerator.java:76) at org.jbpm.pvm.internal.id.DatabaseDbidGenerator.getNextId(DatabaseDbidGenerator.java:63) -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2593) processDefinition.getDescription() does not return the process definition description as defined in the process definition XML file

by Carl Allain (JIRA)

processDefinition.getDescription() does not return the process definition description as defined in the process definition XML file ----------------------------------------------------------------------------------------------------------------------------------- Key: JBPM-2593 URL: https://jira.jboss.org/jira/browse/JBPM-2593 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1 Reporter: Carl Allain Priority: Minor In my process defition file I have this ... <process description="This is the description of processdefA" key="processdefA" name="processdefA" xmlns="http://jbpm.org/4.0/jpdl"> ... I can create a process instance from it and all that, but I can't get at the description with the API (I got a processDefinition instance from the RepositoryService as usual): System.out.println("processDefinition.getDescription=" + processDefinition.getDescription()); // returns null while I have a description in my XML 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, 7 months

1
1
0 / 0

[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

14 years, 7 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

14 years, 7 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

14 years, 7 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

14 years, 7 months

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues October 2009