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.
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
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.