Bug 842547 - HornetQ based human task service doesn't listens on IPs, it listens only to localhost
Summary: HornetQ based human task service doesn't listens on IPs, it listens only to l...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-24 07:25 UTC by Toshiya Kobayashi
Modified: 2025-02-10 03:20 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:20:22 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPM-3720 0 Major Resolved HornetQ based human task service doesn't listens on IPs, it listens only to localhost 2015-05-22 21:10:55 UTC

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
Comment 10 Red Hat Bugzilla 2025-02-10 03:20:22 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.