Issue

• Why does a clientBindUrl of 0.0.0.0 fail to get replaced with the IP address in JBoss EAP 5.x?
• We have a clientBindUrl defined for a EJB as sslsocket://0.0.0.0:23843.  In JBoss EAP 4.3.x, when we use the InitialContext and look up the remote bean, the proxy object that is returned contains a url property which has the value sslsocket://127.0.0.1:23843.
• In JBoss EAP 5.1,  when we use the initialContext and look up the remote bean, the proxy object does not have the updated url, but the same value as the clientBindURL defined in the bean (sslsocket://0.0.0.0:23843).  This causes a connection failure on the client side due to the IP address being 0.0.0.0.
• Is there some configuration that is missed in JBoss EAP 5.1 or has this functionality changed?