[jBPM] - jBPM5 - jbpm-gwt-console - java.lang.IllegalArgumentException: Could not connect task client
by Jim Dwyer
Jim Dwyer [http://community.jboss.org/people/JimDwyer] created the discussion
"jBPM5 - jbpm-gwt-console - java.lang.IllegalArgumentException: Could not connect task client"
To view the discussion, visit: http://community.jboss.org/message/627574#627574
--------------------------------------------------------------
I am getting the error below the first time I click on Processes/Execution History. Process/ProcessOverview, Task/Personal Tasks and Tasks/Group Tasks. It goes away after selecting each at least 1 time previously. I read in other posts about a "task service". Is there such a thing? I also read that this involved the h2.jar file. If so how? I am hoping somebody can shead some light on the this error. Jim * URL: ' http://localhost:8080/gwt-console-server/rs/process/definitions http://localhost:8080/gwt-console-server/rs/process/definitions' * Action: 'org.jboss.bpm.console.client.process.UpdateDefinitionsAction' * Exception: 'class com.google.gwt.http.client.RequestException' HTTP 500: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.jboss.resteasy.spi.UnhandledException: java.lang.RuntimeException: Could not initialize stateful knowledge session: Could not connect task client org.jboss.resteasy.core.SynchronousDispatcher.unwrapException(SynchronousDispatcher.java:345) org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:321) org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:214) org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:190) org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:534) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:496) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119) org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) root cause java.lang.RuntimeException: Could not initialize stateful knowledge session: Could not connect task client org.jbpm.integration.console.CommandDelegate.newStatefulKnowledgeSession(CommandDelegate.java:185) org.jbpm.integration.console.CommandDelegate.getSession(CommandDelegate.java:193) org.jbpm.integration.console.CommandDelegate.(CommandDelegate.java:71) org.jbpm.integration.console.ProcessManagement.(ProcessManagement.java:35) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:22) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:19) org.jboss.bpm.console.server.ProcessMgmtFacade.getProcessManagement(ProcessMgmtFacade.java:98) org.jboss.bpm.console.server.ProcessMgmtFacade.getDefinitionsJSON(ProcessMgmtFacade.java:122) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140) org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:255) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:220) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:209) org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:519) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:496) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119) org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) root cause java.lang.IllegalArgumentException: Could not connect task client org.jbpm.process.workitem.wsht.CommandBasedWSHumanTaskHandler.connect(CommandBasedWSHumanTaskHandler.java:88) org.jbpm.integration.console.CommandDelegate.newStatefulKnowledgeSession(CommandDelegate.java:181) org.jbpm.integration.console.CommandDelegate.getSession(CommandDelegate.java:193) org.jbpm.integration.console.CommandDelegate.(CommandDelegate.java:71) org.jbpm.integration.console.ProcessManagement.(ProcessManagement.java:35) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:22) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:19) org.jboss.bpm.console.server.ProcessMgmtFacade.getProcessManagement(ProcessMgmtFacade.java:98) org.jboss.bpm.console.server.ProcessMgmtFacade.getDefinitionsJSON(ProcessMgmtFacade.java:122) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140) org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:255) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:220) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:209) org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:519) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:496) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119) org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/627574#627574]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 6 months
[jBPM] - Wanted: Way to handle jbpm related files with guvnor
by hamsterdancer
hamsterdancer [http://community.jboss.org/people/hamsterdancer] created the discussion
"Wanted: Way to handle jbpm related files with guvnor"
To view the discussion, visit: http://community.jboss.org/message/627731#627731
--------------------------------------------------------------
Hi there,
I've got short a question and I'm not so sure where to ask it (here or on the guvnor site)... I'd like to handle all the jBPM concerning files for guvnor in my own application. It means, handling ordinary CRUD Operations. (The aim is to produce somewhere else some stuff for jbpm and put it on the correct place into guvnor for using it in jbpm and jbpm concerning parts like the designer... e.g. automatically putting some workitem definitions into guvnor, so that you can use it after in the designer)
The first Idea (which is really easy to handle) is using web dav, but then it has some problems with deleted files... there won't be really deleted. It means, although you're are not able to find them in guvnor, you're still able to access them with the direct URL. In addition to it, after you've tried to delete them, you're also not able to upload another file with the same name.
Another Idea was to do it with the REST Api of guvnor, but the way to handle files I don't like. It looks to complicated for such simple CRUD Operations (maybe because I don't have so much experience wit REST yet) But at least it is possible and easy to really delete files and packages.
So, I'd like to get some easy Ideas how to handle my jBPM files with guvnor.
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/627731#627731]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 6 months
[JBoss Messaging] - 1.4.8SP3 with Jboss 4.2.3GA
by Markus Lutum
Markus Lutum [http://community.jboss.org/people/mclu] created the discussion
"1.4.8SP3 with Jboss 4.2.3GA"
To view the discussion, visit: http://community.jboss.org/message/627695#627695
--------------------------------------------------------------
Hi!
I know there is no further comunity version after 1.4.5GA.
Currently we have some customers with problems and we think that some of them are solved in later versions.
My plan now is to check out the latest 1.4 branch version (last checkin was the release note for 1.4.8.SP3
Then build it with
integration.base=EAP4
(which I already did)
and give it a try with my current server instance
(which I have to test tomorrow)
QUESTIONS:
1. Has someone tried it already / Is this a (good) idea?
2. The generated doc said to use Remoting 2.5.4 SP3 brew. The build itself gets the thridparty lib with version 2.2.4 . What should be used?
3. Any other dependencies to take care ??
THX a lot
Markus Lutum
OV Software
Germany
PS: I know this is not the way I should go. Our plan currently is to migrate our app to Jboss 7.1 end of the year if remote JNDI is available.
Of couse we are using HornetQ then! But for now I have to find solutions for our current customers befor we are upgrading them to 7.1
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/627695#627695]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 6 months
[jBPM] - ReceiveTaskHandler handling multiple process intances with the same message-id
by Melih Cetin
Melih Cetin [http://community.jboss.org/people/mscetin] created the discussion
"ReceiveTaskHandler handling multiple process intances with the same message-id"
To view the discussion, visit: http://community.jboss.org/message/617949#617949
--------------------------------------------------------------
BPMN2 JUnit test for BPMN2-ReceiveTask is implemented as
ksession.getWorkItemManager().registerWorkItemHandler("Receive Task", receiveTaskHandler);
...
receiveTaskHandler.messageReceived("HelloMessage", "Hello john!");
I tried to use ReceiveTaskHandler class in a project to receive a notification from an external system for a specific process-instance and resume the process upon receipt of the message. I could not figure out how to specify the process-instance for which the received message is applicable.
JUinit test works fine as there is only one process instance in the session during the execution of this test. The source code for ReceiveTaskHandler is:
public class ReceiveTaskHandler implements WorkItemHandler {
// TODO: use correlation instead of message id
private Map<String, Long> waiting = new HashMap<String, Long>();
...
public void executeWorkItem(WorkItem workItem, WorkItemManager manager) {
String messageId = (String) workItem.getParameter("MessageId");
waiting.put(messageId, workItem.getId());
* // If waiting map previously contained a mapping for messageId, the old value is replaced !!!*
}
public void messageReceived(String messageId, Object message) {
Long workItemId = waiting.get(messageId);
if (workItemId == null) {
return;
}
Map<String, Object> results = new HashMap<String, Object>();
results.put("Message", message);
ksession.getWorkItemManager().completeWorkItem(workItemId, results);
}
...
}
The comment of // TODO: use correlation instead of message id at the top of the source file also gave the impression that the implementation is not complete. As an interim solution, I decided to extend ReceiveTaskHandler class as follows:
public class ReceiveTaskHandler extends org.jbpm.bpmn2.handler.ReceiveTaskHandler {
private Map<String, Long> waiting = new HashMap<String, Long>();
private KnowledgeRuntime ksession;
public ReceiveTaskHandler(KnowledgeRuntime ksession) {
super(ksession);
this.ksession = ksession;
}
private String constructKey(long processInstanceId, String messageId) {
return processInstanceId + "|" + messageId;
}
@Override
public void executeWorkItem(WorkItem workItem, WorkItemManager manager) {
long processInstanceId = workItem.getProcessInstanceId();
String messageId = (String) workItem.getParameter("MessageId");
waiting.put(constructKey(processInstanceId, messageId), workItem.getId());
// If waiting map previously contained a mapping for messageId, the old value is replaced !!!
}
@Override
public void messageReceived(String messageId, Object message) {
throw new UnsupportedOperationException(
"messageReceived(String messageId, Object message) method is not supported. " +
"Instead use messageReceived(long, String, Object) method" );
}
public void messageReceived(long processInstanceId, String messageId, Object message) {
Long workItemId = waiting.get(constructKey(processInstanceId, messageId));
if (workItemId == null) {
return;
}
Map<String, Object> results = new HashMap<String, Object>();
results.put("Message", message);
ksession.getWorkItemManager().completeWorkItem(workItemId, results);
}
}
I was wondering if "Receive Task" is the right task to use for waiting an external notification. If yes, then can any core jBPM contributor review the extension that I used locally and consider adding it to the next release of jBPM.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/617949#617949]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 6 months
