Registry Error When JBOSS bind to 0.0.0.0 ----------------------------------------- Key: JBESB-3561 URL: https://issues.jboss.org/browse/JBESB-3561 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 5.0 Environment: JBoss Enterprise SOA Platform 5.0.1 Reporter: Anurag Debnath When the server hosting ESB is started with flag -b 0.0.0.0, the UDDI registry puts services under this address and are thus unreachable by remote ServiceInvokers. Tested by deploying 'HelloWorld' quickstart and examining UDDI through the UDDI console. * Start server with no flags. Examing UDDI registry will show service is bound to '127.0.0.1' * Start server with -b 123.123.123.123. UDDI registry will show service bound to '123.123.123.123' * Start server with -b 0.0.0.0 UDDI registry will show service bound to '0.0.0.0' (unreachable remotely) * Start server with -b 0.0.0.0 -Djboss.esb.bind.address=123.123.123.123 UDDI registry will show service bound to '0.0.0.0' * Start server with -b 0.0.0.0 and JAVA_OPTS including "jboss.esb.bind.address=123.123.123.123" UDDI registry will show service bound to '0.0.0.0' Proposed fix is a system property read by org.jboss.soa.esb.helpers.NamingContextPool that specifies the desired octet to plug into java.naming.provider.url.

AS5 binding service refers to jboss.bind.address instead of jboss.esb.bind.address ---------------------------------------------------------------------------------- Key: JBESB-3561 URL: https://issues.jboss.org/browse/JBESB-3561 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 4.7 CP1 Environment: JBoss Enterprise SOA Platform 5.0.1 Reporter: Anurag Debnath When the server hosting ESB is started with flag -b 0.0.0.0, the UDDI registry puts services under this address and are thus unreachable by remote ServiceInvokers. Tested by deploying 'HelloWorld' quickstart and examining UDDI through the UDDI console. * Start server with no flags. Examing UDDI registry will show service is bound to '127.0.0.1' * Start server with -b 123.123.123.123. UDDI registry will show service bound to '123.123.123.123' * Start server with -b 0.0.0.0 UDDI registry will show service bound to '0.0.0.0' (unreachable remotely) * Start server with -b 0.0.0.0 -Djboss.esb.bind.address=123.123.123.123 UDDI registry will show service bound to '0.0.0.0' * Start server with -b 0.0.0.0 and JAVA_OPTS including "jboss.esb.bind.address=123.123.123.123" UDDI registry will show service bound to '0.0.0.0' Proposed fix is a system property read by org.jboss.soa.esb.helpers.NamingContextPool that specifies the desired octet to plug into java.naming.provider.url.

AS5 binding service refers to jboss.bind.address instead of jboss.esb.bind.address ---------------------------------------------------------------------------------- Key: JBESB-3561 URL: https://issues.jboss.org/browse/JBESB-3561 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 4.7 CP1 Environment: JBoss Enterprise SOA Platform 5.0.1 Reporter: Anurag Debnath When the server hosting ESB is started with flag -b 0.0.0.0, the UDDI registry puts services under this address and are thus unreachable by remote ServiceInvokers. Tested by deploying 'HelloWorld' quickstart and examining UDDI through the UDDI console. * Start server with no flags. Examing UDDI registry will show service is bound to '127.0.0.1' * Start server with -b 123.123.123.123. UDDI registry will show service bound to '123.123.123.123' * Start server with -b 0.0.0.0 UDDI registry will show service bound to '0.0.0.0' (unreachable remotely) * Start server with -b 0.0.0.0 -Djboss.esb.bind.address=123.123.123.123 UDDI registry will show service bound to '0.0.0.0' * Start server with -b 0.0.0.0 and JAVA_OPTS including "jboss.esb.bind.address=123.123.123.123" UDDI registry will show service bound to '0.0.0.0' Proposed fix is a system property read by org.jboss.soa.esb.helpers.NamingContextPool that specifies the desired octet to plug into java.naming.provider.url.

AS5 binding service refers to jboss.bind.address instead of jboss.esb.bind.address ---------------------------------------------------------------------------------- Key: JBESB-3561 URL: https://issues.jboss.org/browse/JBESB-3561 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 4.7 CP1 Environment: JBoss Enterprise SOA Platform 5.0.1 Reporter: Anurag Debnath When the server hosting ESB is started with flag -b 0.0.0.0, the UDDI registry puts services under this address and are thus unreachable by remote ServiceInvokers. Tested by deploying 'HelloWorld' quickstart and examining UDDI through the UDDI console. * Start server with no flags. Examing UDDI registry will show service is bound to '127.0.0.1' * Start server with -b 123.123.123.123. UDDI registry will show service bound to '123.123.123.123' * Start server with -b 0.0.0.0 UDDI registry will show service bound to '0.0.0.0' (unreachable remotely) * Start server with -b 0.0.0.0 -Djboss.esb.bind.address=123.123.123.123 UDDI registry will show service bound to '0.0.0.0' * Start server with -b 0.0.0.0 and JAVA_OPTS including "jboss.esb.bind.address=123.123.123.123" UDDI registry will show service bound to '0.0.0.0' Proposed fix is a system property read by org.jboss.soa.esb.helpers.NamingContextPool that specifies the desired octet to plug into java.naming.provider.url.