[matiasmct]

Same problem here. I've changed build.xml and default.jbpm.properties (jbpm.console.task.service.host=localhost) and the problem persists. Would be enough with stop and start demo to catch the new conf? I don't have any process listening in 5153...

Regards,

[iahi1998]

I believe that this issue is just an artifact of Eclipse starting before JBoss completes it's startup sequence. I've realized there's a seconds to minutes gap between the end of "ant start.demo" and when JBoss finishes the startup.

To check whether JBoss finised startup I ran:

tail -f jboss-as-7.1.1.Final/standalone/log/server.log

You will notice that lines keep getting appended to the log for quite a while after "ant stat.demo" finishes and Eclipse starts.

Futhermore, I ran:

$ netstat -c | grep 5153

to see when a service starts listening on 5153. Again, because of the delay in JBoss startup, it takes a while to see something like:

tcp6       0      0 localhost:53282         localhost:5153          ESTABLISHED
tcp6       0      0 localhost:5153          localhost:53282         ESTABLISHED

Once you see that the log doesn't have lines appended to it, and you see a service listening on 5153, you should be able to run the 10-Minute Tutorial: Using the Eclipse Tooling

My setup is jBPM 5.4.1 on Ubuntu Desktop 12.04, with Oracle Java 7, Apache-Ant 1.8.4. I followed the steps listed in Chapter 3. Installer. The only modification required to build.xml was changing the url pointing to Eclipse from:

"http://download.eclipse.org/technology/epp/downloads/release/helios/SR2/eclipse-java-helios-SR2-${download.type}.${download.extension}"

to

"http://archive.eclipse.org/technology/epp/downloads/release/helios/SR2/eclipse-java-helios-SR2-${download.type}.${download.extension}"

No other modifications were made to build.xml or conf/default.jbpm.console.properties

I hope this helps.

Message was edited by: iahi1998

[sumanraoj]

i made this change in the url for eclipse download and install.demo and start.demo works fine

also i have run following commands:

1)ant install.droolsjbpm-eclipse.into.eclipse

2)ant install.jBPM.runtime

I can see the JBPM runtime environment now ..was trying to run the sample project evaluation

still the same error

org.jbpm.workflow.instance.WorkflowRuntimeException: [com.sample.evaluation:1 - Self Evaluation:2] -- Could not connect task client: on ip: 127.0.0.1 - port: 5153

          at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:132)

          at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279)

          at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238)

          at org.jbpm.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:49)

          at org.jbpm.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:41)

          at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126)0    13/02 15:34:40,894[main] ERROR service.hornetq.HornetQTaskClientConnector.connect  - Unable to connect to server using configuration org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5153&host=127-0-0-1

          at org.jbpm.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:35)

          at org.jbpm.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:194)

          at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:309)

          at org.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:170)

          at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:140)

          at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1098)

          at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:320)

          at com.sample.ProcessTest.main(ProcessTest.java:31)

Caused by: java.lang.IllegalArgumentException: Could not connect task client: on ip: 127.0.0.1 - port: 5153

          at org.jbpm.process.workitem.wsht.GenericHTWorkItemHandler.connect(GenericHTWorkItemHandler.java:158)

          at org.jbpm.process.workitem.wsht.GenericHTWorkItemHandler.executeWorkItem(GenericHTWorkItemHandler.java:180)

          at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70)

          at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107)

          at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126)

          ... 13 more

[mhavrda]

Please correct the download.eclipse target in build.xml file in the jbpm-5.4.0.Final-installer-full.zip.

This is the correct URL.

http://archive.eclipse.org/technology/epp/downloads/release/helios/SR2/eclipse-java-helios-SR2-${download.type}.${download.extension}

[roxy1987]

Check if you are able to listen on port 5153? And after you start a process, add a line to dispose the client handler.

[sumanraoj]

Miloslav Havrda and roxy 1987 thanks for the reply..

i did change that url.

the problem was i did not start the human task...

thanks though

[matiasmct]

I continue with same problem. How to start human task?

Thanks!

[roxy1987]

You need to run the ant script start.demo. it will start up your jboss server and deploy your human task war file.. Human task war has a servlet which loads on startup and starts HornetQ server by default on 127.0.0.1:5153 for jbpm 5.4

Once this is up, you can try to run the evaluation example and see if it starts the process.

Regards.