Bug 842547

Summary: HornetQ based human task service doesn't listens on IPs, it listens only to localhost
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Toshiya Kobayashi <tkobayas>
Component: jBPM 5Assignee: Kris Verlaenen <kverlaen>
Status: VERIFIED --- QA Contact: Marek Baluch <mbaluch>
Severity: high Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.0.GACC: alazarot
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the HornetQ task server only listened to the localhost making it impossible to connect to a remote service. This has been resolved by allowing configurable bind for host and IP for the the HornetQ task server. It is now possible to bind the HornetQ task server to a custom host and IP.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Toshiya Kobayashi 2012-07-24 07:25:10 UTC
Description of problem:

Backport the fix for https://issues.jboss.org/browse/JBPM-3720

Hornetq based human task service always listens to localhost. If we need to connect to a remote srvice using API its not possible, hence HornetQ based human task service should also have its host/ip configurable similar to its port.

Actual results:

Listen address is not configurable in jbpm-human-task.war. It always listens to localhost.

Expected results:

hornetq.host is configurable in jbpm-human-task.war/WEB-INF/web.xml and Human Task Service listens to configured address.

Comment 3 Maciej Swiderski 2012-08-23 16:35:44 UTC
backported into 5.2.x branch

Comment 4 Jiri Svitak 2012-09-25 10:31:39 UTC
Verified in BRMS 5.3.1 ER1.

Comment 5 lcarlon 2012-10-22 02:58:25 UTC
Docs text edited for inclusion in the release notes document. Thanks for providing the text, Maciej.

- Lee