Red Hat Bugzilla – Bug 805638
jBPM Console ignores HT service host and port configuration
Last modified: 2012-05-31 22:58:12 EDT
Created attachment 571796 [details]
Description of problem:
In a scenario where jbpm-human-task.war is configured to start the HT service on a different host and port than the defaults (localhost:9123), the jBPM console is unable to connect to the task service.
Although it is possible to configure the task service address in gwt-console-server.war/WEB-INF/classes/jbpm.console.properties, the console crashes on the first access if the task service is not running on localhost:9123.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
jBPM Console crashes on the first access if the task service is not running on localhost:9123, even if the task service address is configured correctly in jbpm.console.properties (inside gwt-console-server.war)
jBPM Console should connect to task service running on any host and port if the address is specified in jbpm.console.properties. The transport protocol (mina,jms,hornetq) should be configurable too.
see server log for the exception trace
Pull request prepared and avilable at: https://github.com/droolsjbpm/jbpm/pull/63
Introduces number of configuration parameters via jbpm.console.properties to match configuration avilable for human task web application. It defaults to Mina to be backward compatible with previous versions of jBPM already out.
In addition to what is possible in terms of transports of human task web application console can be configured to use local task server without any remote communication.
Please use following pull request instead of #63 as it provides latest modifications: https://github.com/droolsjbpm/jbpm/pull/67
Merged, BRMS should update the jbpm.console.properties file to use HornetQ instead of Mina (in combination with the changes in the human task service war to switch that to HornetQ as well).
Update status to ON_QA. Please verify them against ER6.
Fix verified in ER8.