Affects: Release Notes Workaround Description: Change EsbPropertyServiceXSLTConfig in conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml so that it contains the following <parameter> <map keyClass="java.lang.String" valueClass="java.lang.String"> <entry> <key>esbHost</key> <value>${jboss.esb.bind.address}</value> </entry> </map> </parameter> (jboss.esb.bind.address instead of jboss.bind.address) project_key: SOA If starting the server using '-b 0.0.0.0' then the binding service overrides the esb host binding which results in inaccessible entries in the UDDI registry (using address 0.0.0.0). The workaround contains the simple fix to the binding configuration.
Link: Added: This issue depends JBESB-3561
Affects: Added: [Release Notes]
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: In JBoss ESB, the binding service refers to "jboss.bind.address" instead of "jboss.esb.bind.address". Work around this by accessing the EsbPropertyServiceXSLTConfig property in conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml and inserting the code listed on this topic's Bugzilla page.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.