[jBPM] - completing human task - NoSuchFieldError: classLoader
by wishmaster7
wishmaster7 [https://community.jboss.org/people/wishmaster7] created the discussion
"completing human task - NoSuchFieldError: classLoader"
To view the discussion, visit: https://community.jboss.org/message/802416#802416
--------------------------------------------------------------
Hi all,
I have found something very strange when I complete a Human Task. Here is what I do:
Map<String, Object> result = new HashMap<String, Object>();
result.put("Result", action);
taskService.completeWithResults(taskId, userId, result);
and I have the following error:
java.lang.NoSuchFieldError: classLoader
at org.jbpm.task.utils.ContentMarshallerHelper.unmarshall(ContentMarshallerHelper.java:107)
at org.jbpm.process.workitem.wsht.GenericHTWorkItemHandler$TaskCompletedHandler.handleCompletedTask(GenericHTWorkItemHandler.java:260)
at org.jbpm.process.workitem.wsht.GenericHTWorkItemHandler$TaskCompletedHandler.execute(GenericHTWorkItemHandler.java:234)
at org.jbpm.task.service.local.LocalTaskService$SimpleEventTransport.trigger(LocalTaskService.java:329)
at org.jbpm.task.event.MessagingTaskEventListener.triggerPayload(MessagingTaskEventListener.java:76)
at org.jbpm.task.event.MessagingTaskEventListener.handleEvent(MessagingTaskEventListener.java:92)
at org.jbpm.task.event.MessagingTaskEventListener.taskCompleted(MessagingTaskEventListener.java:109)
at org.jbpm.task.event.TaskEventSupport.fireTaskCompleted(TaskEventSupport.java:49)
at org.jbpm.task.service.TaskServiceSession.postTaskCompleteOperation(TaskServiceSession.java:569)
at org.jbpm.task.service.TaskServiceSession.taskOperation(TaskServiceSession.java:495)
at org.jbpm.task.service.local.LocalTaskService.complete(LocalTaskService.java:83)
at org.jbpm.task.service.local.LocalTaskService.completeWithResults(LocalTaskService.java:91)
So, I search in the code, and I find :
MarshallerReaderContext context = null;
context.classLoader = ContentMarshallerHelper.class.getClassLoader();
BUT... (something I can't explain), MarshallerReaderContext has no classLoader. This throws the error above.
Someone knows? Any help would be apreciated.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802416#802416]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month
[Beginner's Corner] - Problem with connection factories
by kevin allan
kevin allan [https://community.jboss.org/people/keallan] created the discussion
"Problem with connection factories"
To view the discussion, visit: https://community.jboss.org/message/799991#799991
--------------------------------------------------------------
Hi All-
Newbie here. I've run into a situation while running jBoss 5.1. Not even sure where to start. I can't seem to resolve a connection issue. I get errors for both Tx connection factory component (jms-ds.xml) and errors pertaining to the messaging component (connection-factories-service.xml). I did a search for both and can access them. In going to the jBoss AS Admin Console, it shows under "connection factories" that the "jmsXA" connection factory is "down" and unavailable". Also that JMS destination queues are "down" and "unavailable". I suspect the latter is a result of the former. I've been trying to run this down for weeks and need some help.
Many thanks for contructive input.
Here is an error log from the connection factories:
1. java.lang.reflect.UndeclaredThrowableException: Failed to invoke method 'listStatistics' on component 'jboss.jca:name=JmsXA,service=ManagedConnectionPool' with parameters [].
at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.invoke(KernelBusRuntimeComponentDispatcher.java:201)
at org.jboss.profileservice.management.DelegatingComponentDispatcherImpl.invoke(DelegatingComponentDispatcherImpl.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aop.generatedproxies.AOPProxy$0.invoke(AOPProxy$0.java)
at org.jboss.profileservice.management.ManagedOperationDelegate.invoke(ManagedOperationDelegate.java:64)
at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:159)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalArgumentException: No such context: jboss.jca:name=JmsXA,service=ManagedConnectionPool
at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.execute(BasicKernelBus.java:51)
at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.invoke(BasicKernelBus.java:92)
at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.invoke(KernelBusRuntimeComponentDispatcher.java:186)
at org.jboss.profileservice.management.DelegatingComponentDispatcherImpl.invoke(DelegatingComponentDispatcherImpl.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aop.generatedproxies.AOPProxy$0.invoke(AOPProxy$0.java)
at org.jboss.profileservice.management.ManagedOperationDelegate.invoke(ManagedOperationDelegate.java:64)
at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:159)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72)
... 18 more
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/799991#799991]
Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month
[jBPM] - JBPM4.4 in a Web app
by mvermand
mvermand [https://community.jboss.org/people/mvermand] created the discussion
"JBPM4.4 in a Web app"
To view the discussion, visit: https://community.jboss.org/message/802479#802479
--------------------------------------------------------------
Hi,
I am trying to improve the way I use JBPM4.4 in a Web app (ADF @Weblogic).
Now, I have an initialization listener in the web app which instanciates an ENUM object holding reference to the different JBPM services (RepositoryService, TaskService...).
But no dedicated environment is created for the HTTP Request, so JBPM creates and closes a lot of hibernate transactions (in different environment instances).
This throws the use of the JBPM (ProcessDefinition) Cache over board.
I would like to create an Environment object ( environmentFactory.openEnvironment() ) in a Servlet Filter and keep/use this environment instance throughout the handling of the HTTP Request.
In this way I can get objects from the JBPM Cache.
Is this the correct way of doing?
Where can I find any documentation on this?
Regards,
Michiel
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802479#802479]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month
[jBPM] - Is Drools/JBPM Tooling for Eclipse broken with JPAKnowledgeService?
by Jim Beam
Jim Beam [https://community.jboss.org/people/jamesbeam] created the discussion
"Is Drools/JBPM Tooling for Eclipse broken with JPAKnowledgeService?"
To view the discussion, visit: https://community.jboss.org/message/802472#802472
--------------------------------------------------------------
I am trying to use the Drools/JBPM tooling to test a simple program with jBPM 5.4. I tried this in Eclipse Helios and Juno.
If I create the ksession using kbase.newStatefulKnowledgeSession() the drools views work as expected - the process and process instances show the correct information (after I click on the ksession in the variables window of course). However, this does NOT work if I create the the ksession using the JPAKnowledgeService.
Is this a known issue/limitation? Am I missing something?
code:
KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
kbuilder.add(ResourceFactory.newClassPathResource("Test.bpmn"),ResourceTypoe.BPMN2);
Environment env = KnowledgeBaseFactory.newEnvironment();
env.set(EnvironmentName.ENTITY_MANAGER_FACTORY,emf);
StatefulKnowledgeSession ksession = kbase.newStatuefulKnowledgeSession(); * <-- THIS WORKS FINE*
--- BUT --
StatefulKnowledgeSession ksession = JPAKnowledgeService.newStatefulKnowledgeSession(kbase,null,env);* <---THIS DOES NOT*
Note, when I use the JPAKnowledgeService, my app does function correctly (I see the session being updated in the database, etc).
Also, I tried creating the first ksession above first (calling it ksession2) and then setting ksession2=ksession, and everything works until the assignment, then the tooling stops responding.
Any thoughts on how to get this to work with
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802472#802472]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month
[Beginner's Corner] - Re: Configure Maven for JBoss AS 7, associating Maven with project, unable to create Ticket-Monster project. Unable to obtain central repository.
by Marc Gagnon
Marc Gagnon [https://community.jboss.org/people/MarcGagnonPincourt] created the discussion
"Re: Configure Maven for JBoss AS 7, associating Maven with project, unable to create Ticket-Monster project. Unable to obtain central repository."
To view the discussion, visit: https://community.jboss.org/message/802455#802455
--------------------------------------------------------------
Some people will hate me but the simple truth is that you should build the project using maven from the command line: eclipse is just an interface, not a build management tool.
When you have a command line builtd success, proceed with projects importation in eclipse.
This is not as fancy as tools developpers suggest it should be and this is more work than what it should be...
But once you master this basic recipe, you will always be in control (and when the "magic" IDE will fail, you will still be in control).
Once you master theses steps, if the IDE gets fixed, then retry with the proposed way of managing the projects: if it works then great! otherwise... back to the two steps process which will always work.
I know this is not the answer you were expecting, but at least you will never again be stuck with tools which fail to help you.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802455#802455]
Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month