[Design of JBoss jBPM] - Job execution fails on JBoss 5.0.0.GA
by heiko.braun@jboss.com
| 13:32:12,680 ERROR [DispatcherThread] exception in job executor thread. waiting 640000 milliseconds
| org.jbpm.pvm.internal.wire.WireException: couldn't create object 'org.jbpm.pvm.internal.tx.jta.JtaTransaction': BaseClassLoader@93b72e{vfszip:/Users/hbraun/Desktop/jbpm-workspace/jbpm-4.0-SNAPSHOT/jboss-5.0.0.GA/server/default/deploy/jbpm/gwt-console-server.war} classLoader is not connected to a domain (probably undeployed?) for class org.jbpm.pvm.internal.tx.jta.JtaTransaction
| at org.jbpm.pvm.internal.wire.descriptor.ObjectDescriptor.construct(ObjectDescriptor.java:146)
| at org.jbpm.pvm.internal.wire.WireContext.construct(WireContext.java:473)
| at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:452)
| at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:441)
| at org.jbpm.pvm.internal.wire.WireContext.get(WireContext.java:421)
| at org.jbpm.pvm.internal.wire.WireContext.get(WireContext.java:331)
| at org.jbpm.pvm.internal.wire.WireContext.get(WireContext.java:707)
| at org.jbpm.pvm.internal.env.BasicEnvironment.get(BasicEnvironment.java:151)
| at org.jbpm.pvm.internal.env.BasicEnvironment.get(BasicEnvironment.java:142)
| at org.jbpm.pvm.internal.env.Environment.getFromCurrent(Environment.java:200)
| at org.jbpm.pvm.internal.env.Environment.getFromCurrent(Environment.java:189)
| at org.jbpm.pvm.internal.tx.jta.JtaRetryInterceptor.execute(JtaRetryInterceptor.java:41)
| at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54)
| at org.jbpm.pvm.internal.jobexecutor.DispatcherThread.acquireJobs(DispatcherThread.java:129)
| at org.jbpm.pvm.internal.jobexecutor.DispatcherThread.run(DispatcherThread.java:67)
| Caused by: java.lang.IllegalStateException: BaseClassLoader@93b72e{vfszip:/Users/hbraun/Desktop/jbpm-workspace/jbpm-4.0-SNAPSHOT/jboss-5.0.0.GA/server/default/deploy/jbpm/gwt-console-server.war} classLoader is not connected to a domain (probably undeployed?) for class org.jbpm.pvm.internal.tx.jta.JtaTransaction
| at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:730)
| at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:378)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
| at org.jbpm.pvm.internal.util.ReflectUtil.loadClass(ReflectUtil.java:47)
| at org.jbpm.pvm.internal.wire.descriptor.ObjectDescriptor.construct(ObjectDescriptor.java:144)
| ... 14 more
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240717#4240717
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240717
15 years, 4 months
[Design of JBoss jBPM] - Incomplete example setup
by heiko.braun@jboss.com
Seems as if the process resources (classes, etc) are still not deployed correctly.
| Caused by: org.jbpm.pvm.internal.wire.WireException: couldn't create object: couldn't load class org.jbpm.examples.custom.PrintDots
| at org.jbpm.pvm.internal.wire.descriptor.ObjectDescriptor.construct(ObjectDescriptor.java:146)
| at org.jbpm.pvm.internal.wire.WireContext.construct(WireContext.java:473)
| at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:452)
| at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:262)
| at org.jbpm.jpdl.internal.activity.CustomBinding.parse(CustomBinding.java:48)
| at org.jbpm.jpdl.internal.xml.JpdlParser.parseActivities(JpdlParser.java:266)
| at org.jbpm.jpdl.internal.xml.JpdlParser.parseDocumentElement(JpdlParser.java:214)
| at org.jbpm.pvm.internal.xml.Parser.parseDocument(Parser.java:475)
| at org.jbpm.pvm.internal.xml.Parser.execute(Parser.java:394)
| at org.jbpm.pvm.internal.xml.Parse.execute(Parse.java:157)
| at org.jbpm.jpdl.internal.repository.JpdlDeployer.deploy(JpdlDeployer.java:60)
| at org.jbpm.pvm.internal.repository.DeployerManager.deploy(DeployerManager.java:46)
| ... 57 more
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240709#4240709
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240709
15 years, 4 months
[Design of JBoss jBPM] - Re: interested in contributing ?
by caleb.powell
@cammunda I hadn't heard of the ChangeProcessInstanceVersionCommand. It wasn't mentioned in the User Guide so we never noticed it (this is a pity).
Based on what I have read though, our library is more powerful than this command (although to be fair, I have only take a quick look). The jbpm-migrator uses mappings provided by the developer to handle situations where a node has been removed. It will migrate all sub-processes, and it will also migrate the TaskContextInstance. It has the potential for much more, but we limited it's functionality to the essentials.
As for the version issue, I haven't had a chance to look at JBPM 4 at all, but I'm assuming it can be adapted for it. In any case, it's exists in our code base as a standalone component, so it could always be release as a separate download for those using version 3.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240573#4240573
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240573
15 years, 4 months