August 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2888) executions stuck in join activity

by Alejandro Guizar (JIRA)

executions stuck in join activity --------------------------------- Key: JBPM-2888 URL: https://jira.jboss.org/browse/JBPM-2888 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 4.x The fork node starts the execution of both the branches in parallel by using inbuilt jBPM messaging. We have observed that the job executor picks up both the jobs and starts executing them concurrently. However the workflow never enters the join state. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBPM-2881) IllegalStateException: Loading StandardTransaction on tomcat 6

by Heiko Braun (JIRA)

IllegalStateException: Loading StandardTransaction on tomcat 6 -------------------------------------------------------------- Key: JBPM-2881 URL: https://jira.jboss.org/browse/JBPM-2881 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Heiko Braun Fix For: jBPM 4.4 Jun 3, 2010 2:11:51 PM org.hibernate.impl.SessionFactoryObjectFactory addInstance INFO: Not binding factory to JNDI, no JNDI name configured Jun 3, 2010 2:11:53 PM org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load org.jbpm.pvm.internal.tx.Sta ndardTransaction. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to at tempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1402) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1361) at org.jbpm.pvm.internal.util.ReflectUtil.classForName(ReflectUtil.java:453) at org.jbpm.pvm.internal.wire.descriptor.ObjectDescriptor.construct(ObjectDescriptor.java:141) at org.jbpm.pvm.internal.wire.WireContext.construct(WireContext.java:487) at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:466) at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:455) at org.jbpm.pvm.internal.wire.WireContext.get(WireContext.java:429) at org.jbpm.pvm.internal.wire.WireContext.get(WireContext.java:339) at org.jbpm.pvm.internal.wire.WireContext.get(WireContext.java:706) at org.jbpm.pvm.internal.env.BasicEnvironment.get(BasicEnvironment.java:132) at org.jbpm.pvm.internal.env.BasicEnvironment.get(BasicEnvironment.java:123) at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:46) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
11
0 / 0

[JBoss JIRA] Created: (JBPM-2310) introduce load testing

by Tom Baeyens (JIRA)

introduce load testing ---------------------- Key: JBPM-2310 URL: https://jira.jboss.org/jira/browse/JBPM-2310 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

14 years, 2 months

4
9
0 / 0

[JBoss JIRA] Created: (JBPM-2766) close InitialContexts

by Tom Baeyens (JIRA)

close InitialContexts --------------------- Key: JBPM-2766 URL: https://jira.jboss.org/jira/browse/JBPM-2766 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.x -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2406) prune and document jpdl dependencies in pom

by Tom Baeyens (JIRA)

prune and document jpdl dependencies in pom ------------------------------------------- Key: JBPM-2406 URL: https://jira.jboss.org/jira/browse/JBPM-2406 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Fix For: jBPM 4.1 currently there are too many dependencies. [INFO] ------------------------------------------------------------------------ [INFO] Building jBPM 4 - jPDL [INFO] task-segment: [dependency:tree] [INFO] ------------------------------------------------------------------------ [INFO] [dependency:tree] [INFO] org.jbpm.jbpm4:jbpm-jpdl:jar:4.0 [INFO] +- org.jbpm.jbpm4:jbpm-pvm:jar:4.0:compile [INFO] | +- org.jbpm.jbpm4:jbpm-api:jar:4.0:compile [INFO] | | \- jboss:jboss-j2ee:jar:4.2.2.GA:compile [INFO] | +- org.jbpm.jbpm4:jbpm-log:jar:4.0:compile [INFO] | +- org.jbpm.jbpm4:jbpm-test-base:jar:4.0:compile [INFO] | | \- org.hibernate:hibernate-core:jar:3.3.1.GA:compile [INFO] | | +- antlr:antlr:jar:2.7.6:compile [INFO] | | \- commons-collections:commons-collections:jar:3.1:compile [INFO] | +- org.apache.ant:ant:jar:1.7.0:compile [INFO] | | \- org.apache.ant:ant-launcher:jar:1.7.0:compile [INFO] | +- log4j:log4j:jar:1.2.14:compile [INFO] | +- juel:juel:jar:2.1.0:compile [INFO] | +- juel:juel-impl:jar:2.1.0:compile [INFO] | +- juel:juel-engine:jar:2.1.0:compile [INFO] | +- org.slf4j:slf4j-api:jar:1.5.2:compile [INFO] | +- org.slf4j:slf4j-jdk14:jar:1.5.2:compile [INFO] | +- org.jboss.identity.idm:idm-core:jar:1.0.0.Beta1:compile [INFO] | | +- org.jboss.identity.idm:idm-common:jar:1.0.0.Beta1:compile [INFO] | | +- org.jboss.identity.idm:idm-api:jar:1.0.0.Beta1:compile [INFO] | | +- org.jboss.identity.idm:idm-spi:jar:1.0.0.Beta1:compile [INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.1.8:compile [INFO] | | \- javax.xml.bind:jaxb-api:jar:2.1:compile [INFO] | | \- javax.xml.stream:stax-api:jar:1.0-2:compile [INFO] | +- org.jboss.identity.idm:idm-hibernate:jar:1.0.0.Beta1:compile [INFO] | | +- javassist:javassist:jar:3.4.GA:compile [INFO] | | +- org.hibernate:hibernate-cglib-repack:jar:2.1_3:compile [INFO] | | \- org.slf4j:slf4j-log4j12:jar:1.5.2:compile [INFO] | +- org.hibernate:hibernate-entitymanager:jar:3.4.0.GA:compile [INFO] | | +- org.hibernate:ejb3-persistence:jar:1.0.2.GA:compile [INFO] | | +- org.hibernate:hibernate-commons-annotations:jar:3.1.0.GA:compile [INFO] | | +- org.hibernate:hibernate-annotations:jar:3.4.0.GA:compile [INFO] | | +- dom4j:dom4j:jar:1.6.1:compile [INFO] | | | \- xml-apis:xml-apis:jar:1.0.b2:compile [INFO] | | \- javax.transaction:jta:jar:1.1:compile [INFO] | +- org.livetribe:livetribe-jsr223:jar:2.0.5:compile [INFO] | \- javax.mail:mail:jar:1.4.1:compile [INFO] | \- javax.activation:activation:jar:1.1:compile [INFO] +- junit:junit:jar:3.8.1:compile [INFO] \- hsqldb:hsqldb:jar:1.8.0.7:test [INFO] ------------------------------------------------------------------------ -- 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, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2556) identify minimal runtime library dependencies

by Tom Baeyens (JIRA)

identify minimal runtime library dependencies --------------------------------------------- Key: JBPM-2556 URL: https://jira.jboss.org/jira/browse/JBPM-2556 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.x feedback from a customer: " after trying hard today, I got jBPM4 running in OSGi equinox. I only tested a little functionality with a simple persistent jPDL workflow using HSQL in-memory db. The problem was that the SAXFactory provider could not be configured properly and resulted in a classloader violation exception. Solution was actually simple: I removed all 3rd party libraries that have something to do with XML (e.g. xml-apis.jar) and ship with jBPM4 and from the bundle-classpath. Now I wonder, if the JBPM4 team has an overview of the necessary smallest dependency set for 3rd-party libs in order to OSGi-tify jBPM and these dependend-jars and get the unnecessary rubbish out of the classpath. Hope they can provide some feedback about that. ------------------ I forgot to send you my current MANIFEST which is working with the small example: Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: WFTEST Bundle-SymbolicName: WFTEST Bundle-Version: 1.0.0.qualifier Bundle-Activator: wftest.Activator Bundle-ActivationPolicy: lazy Bundle-RequiredExecutionEnvironment: JavaSE-1.6 Import-Package: org.osgi.framework;version="1.3.0" Bundle-ClassPath: lib/activation.jar, lib/antlr.jar, lib/avalon-framework.jar, lib/commons-collections.jar, lib/commons-logging.jar, lib/dom4j.jar, lib/ejb3-persistence.jar, lib/hibernate-annotations.jar, lib/hibernate-cglib-repack.jar, lib/hibernate-commons-annotations.jar, lib/hibernate-core.jar, lib/hibernate-entitymanager.jar, lib/hsqldb.jar, lib/idm-api.jar, lib/idm-common.jar, lib/idm-core.jar, lib/idm-hibernate.jar, lib/idm-spi.jar, lib/javassist.jar, lib/jaxb-api.jar, lib/jaxb-impl.jar, lib/jboss-common-core.jar, lib/jboss-j2ee.jar, lib/jboss-logging-spi.jar, lib/jbosscache-core.jar, lib/jbpm-console-form-plugin.jar, lib/jbpm-console-graphView-plugin.jar, lib/jbpm-console-integration.jar, lib/jbpm-console-reports.jar, lib/jbpm-examples-tests.jar, lib/jbpm-jboss4.jar, lib/jbpm-jboss5.jar, lib/jbpm-spi.jar, lib/jbpm-test-db-tests.jar, lib/jbpm-tomcat6.jar, lib/jbpm.jar, lib/jgroups.jar, lib/jta.jar, lib/jtds.jar, lib/juel-engine.jar, lib/juel-impl.jar, lib/juel.jar, lib/junit.jar, lib/livetribe-jsr223.jar, lib/log4j.jar, lib/logkit.jar, lib/mail.jar, lib/mysql-connector-java.jar, lib/postgresql.jar, lib/servlet-api.jar, lib/slf4j-api.jar, lib/slf4j-jdk14.jar, lib/slf4j-log4j12.jar, lib/standalone-compiler.jar, lib/subethasmtp-smtp.jar, lib/subethasmtp-wiser.jar, . I guess several of these jars could be removed and the remaining could be wrapped in OSGi-Bundle jars. ------------------ " -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2550) jbpm 4.1 Fork and Join gives some exception. Details given belo

by Makarand Kulkarni (JIRA)

jbpm 4.1 Fork and Join gives some exception. Details given belo --------------------------------------------------------------- Key: JBPM-2550 URL: https://jira.jboss.org/jira/browse/JBPM-2550 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1 Environment: jbpm 4.1, jboss 5.0 and GPD designer with eclipse packaged with jbpm 4.1 Reporter: Makarand Kulkarni Fix For: jBPM 4.x Hi, JPDL ( SubProcessFill.jpdl )attached ( having fork,join with tasks ) with this ticket is giving following exception org.jboss.resteasy.spi.UnhandledException: org.hibernate.LazyInitializationException: could not initialize proxy - no Session Complete error stack is attached. --- One of my requirement is to assign task( taskform) to multiple users and wait in the process till all users completes the filling of task form. Tried subprocess but then taskform gets assigned to single user. Also tried candidategroups. Same problem here. Your help in this regard is highly appreciated. Waiting for your reply. -Regards Makarand -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2801) Support querying for Tasks by their executionId

by Per Christian Henden (JIRA)

Support querying for Tasks by their executionId ----------------------------------------------- Key: JBPM-2801 URL: https://jira.jboss.org/jira/browse/JBPM-2801 Project: jBPM Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: jBPM 4.x Reporter: Per Christian Henden Fix For: jBPM 4.x I have a case where I need to look up tasks in an EventListener. What's available to me is the EventListenerExecution (ExecutionImpl). I found no simple way of doing this. The attched patch adds the ability to query by executionId in a TaskQuery, exactly like in a HistoryTaskQuery. The simplest way to do this today (as far as I know) is: DbSession taskDbSession = EnvironmentImpl.getFromCurrent(DbSession.class); Task = taskDbSession.findTaskByExecution(execution); I dislike using the DbSession object this way, it would be better to use the JBPM API. Using HistoryTaskService (which is part of the API) is possible, but is too much work: //Find all tasks related to the current execution final List<HistoryTask> relatedTasks = processEngine.getHistoryService().createHistoryTaskQuery().executionId(execution.getId()).list(); //Find all active tasks of the current execution final List<HistoryTask> activeTasks = new ArrayList<HistoryTask>(); for (HistoryTask ht : relatedTasks) { if (ht.getState() == null) { activeTasks.add(ht); } } if (activeTasks.size() > 1) { throw new IllegalStateException("Got multiple matching tasks!"); } else if (activeTasks.isEmpty()) { throw new IllegalStateException("Got no matching tasks!"); } return activeTasks.get(0); With the new code: Task t = processEngine.getTaskService().createTaskQuery().executionId(execution).uniqueResult(); -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2697) split up devguide incubation chapter into multiple incubation chapters

by Tom Baeyens (JIRA)

split up devguide incubation chapter into multiple incubation chapters ---------------------------------------------------------------------- Key: JBPM-2697 URL: https://jira.jboss.org/jira/browse/JBPM-2697 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.4 The current incubation chapter in the dev guide is too big. So we must split it up. The most obvious way is to create multiple incubation chapters in the current dev guide. E.g. * Incubation: jPDL * Incubation: BPMN * Incubation: Instance migration * Incubation: Task forms * ... -- 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, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2772) EventListenerExection.getKey() always returns NULL for subprocesses.

by Martin Porter (JIRA)

EventListenerExection.getKey() always returns NULL for subprocesses. -------------------------------------------------------------------- Key: JBPM-2772 URL: https://jira.jboss.org/jira/browse/JBPM-2772 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Environment: All Reporter: Martin Porter It is not possible to retrieve the business key in an EventListener for a subprocess. The call to EventListenerExecition.getKey() always returns null. -- 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, 2 months

5
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues August 2010