Bug 781082 (SOA-3572)
| Summary: | Incorrect host used in ESB binding service | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Pavel Macik <pmacik> |
| Component: | JBossESB | Assignee: | Nobody <nobody> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.2.0 GA | CC: | tcunning |
| Target Milestone: | ER1 | ||
| Target Release: | 5.3.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-3572 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The incorrect host was used in the ESB binding service. The value of esbHost was set to jboss.bind.address instead of jboss.esb.bind.address.This caused a problem when the server was started with the -b 0.0.0.0 option,(allowing it to bind to any interface). To fix this problem, the name was changed and binding now works as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-02-10 03:14:55 UTC | 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: | |||
Workaround Description: Added: Edit conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml and replace the esbHost definitions so that they refer to jboss.esb.bind.address i.e.
<map keyClass="java.lang.String" valueClass="java.lang.String">
<entry>
<key>esbHost</key>
<value>${jboss.esb.bind.address}</value>
</entry>
</map>
and
<map keyClass="java.lang.String" valueClass="java.lang.String">
<entry>
<key>esbHost</key>
<value>${jboss.esb.bind.address}</value>
</entry>
<entry>
<key>webPort</key>
<value>${org.jboss.esb.web.port}</value>
</entry>
</map>
Workaround: Added: Workaround Exists
Tom Cunningham <tcunning> updated the status of jira JBESB-3733 to Resolved Tom Cunningham <tcunning> made a comment on jira JBESB-3733 Changed references to jboss.bind.address. Tom Cunningham <tcunning> updated the status of jira JBESB-3733 to Closed Tom Cunningham <tcunning> updated the status of jira JBESB-3733 to Reopened Tom Cunningham <tcunning> updated the status of jira JBESB-3733 to Resolved Tom Cunningham <tcunning> updated the status of jira JBESB-3733 to Closed Should be in ER1, see JBESB-3733 for details.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
The incorrect host was used in the ESB binding service. The value of esbHost was set to jboss.bind.address instead of jboss.esb.bind.address.This caused a problem when the server was started with the -b 0.0.0.0 option,(allowing it to bind to any interface). To fix this problem, the name was changed and binding now works as expected.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |
Workaround: Workaround Exists Workaround Description: Edit conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml and replace the esbHost definitions so that they refer to jboss.esb.bind.address i.e. <map keyClass="java.lang.String" valueClass="java.lang.String"> <entry> <key>esbHost</key> <value>${jboss.esb.bind.address}</value> </entry> </map> and <map keyClass="java.lang.String" valueClass="java.lang.String"> <entry> <key>esbHost</key> <value>${jboss.esb.bind.address}</value> </entry> <entry> <key>webPort</key> <value>${org.jboss.esb.web.port}</value> </entry> </map> project_key: SOA The binding information for the ESB services refers to jboss.bind.address as the value of esbHost rather than jboss.esb.bind.address. The difference between the two is evident when the server is started with the -b 0.0.0.0 option, i.e. binding to any interface, as the value of the processed esb.juddi.properties and jbossesb-properties.xml will contain 0.0.0.0 for juddi.server.baseurl and org.jboss.soa.esb.jndi.server.url respectively. The ESB should be using an explicit interface which is what the jboss.esb.bind.address represents.