Bug 1005630 - Set default HornetQ Human Task Service listening host to ${jboss.bind.address}
Summary: Set default HornetQ Human Task Service listening host to ${jboss.bind.address}
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5
Version: BRMS 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-09 03:19 UTC by Toshiya Kobayashi
Modified: 2018-12-02 19:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-04 17:18:00 UTC
Type: Feature Request


Attachments (Terms of Use)

Description Toshiya Kobayashi 2013-09-09 03:19:01 UTC
Description of problem:

Currently HornetQ Human Task Service listens to localhost by default regardless of the value of ${jboss.bind.address}. Users have to change the behaviour by editing jbpm-human-task.war/WEB-INF/web.xml.

Listening to localhost when no value is configured is okay so we don't have to change the code base. But how about having ${jboss.bind.address} in web.xml by default?

Steps to Reproduce:
1. Start brms-standalone with -b option (e.g. bin/run.sh -b 10.64.217.146)

Actual results:

HornetQ Human Task Service listens to localhost.

web.xml:

      <!-- HornetQ configuration parameters -->
      <init-param>
	<param-name>hornetq.host</param-name>
	<param-value></param-value>
      </init-param>
      <init-param>
	<param-name>hornetq.port</param-name>
	<param-value></param-value>
      </init-param>

Expected results:

HornetQ Human Task Service listens to jboss.bind.address (e.g. 10.64.217.146)

web.xml:

      <!-- HornetQ configuration parameters -->
      <init-param>
	<param-name>hornetq.host</param-name>
	<param-value>${jboss.bind.address}</param-value>
      </init-param>
      <init-param>
	<param-name>hornetq.port</param-name>
	<param-value></param-value>
      </init-param>

Additional info:


Note You need to log in before you can comment on or make changes to this bug.