Description of problem: Human task client cannot connect to the Human Task service. The connection attempt is failing with connection refused. The main cause is that the Human Task Service is not deployed in the application server (jbpm-human-task.war). Please note that deploying the war is not enough because there are also some missing jars. (e.g. trove4j-x.y.z.jar) Steps to Reproduce: 1. Run the bpm5Processor quickstart.
Looks like trove4j-x.y.z.jar is the only one needed. Tried to deploy the WAR taken from (http://jawa05.englab.brq.redhat.com/candidate/BRMS-5.3.0-ER6/brms-p-5.3.0.BRMS-ER6-deployable.zip), and add the missing jar but I'm still seeing exceptions: org.jbpm.process.workitem.wsht.CommandBasedWSHumanTaskHandler$AbortTaskResponseHandler cannot be cast to org.jbpm.task.service.TaskClientHandler$TaskSummaryResponseHandler At this moment I'm not sure about the cause. It's possible I picked wrong version of the WAR.
Created attachment 580380 [details] Path for this issue. Removing TestBlocker tag. Tom provided me with a patch which makes it possible to resume test development and testing. Patch attached.
The jbpm5 / esb integration will now require BRMS to be installed on top of SOA-P, so the Human Task WAR is no longer required within ESB or SOA-P - it will be provided in the bits that are installed from BRMS. Closing as WONTFIX.