Hide Forgot
Date of First Response: 2008-09-19 05:55:29 project_key: SOA I see that jboss-as/docs/examples/binding-manager/sample-bindings.xml has ${jboss.esb.bind.address} instead of ${jboss.bind.address} on some places. Is this intentional and why? For me it breaks the EAP test suite run against SOA-P because jboss.esb.bind.address is missing as a property. But anyways I don't see any reason to have somewhere configured ${jboss.bind.address} and somewhere ${jboss.esb.bind.address}. I think it should be jboss.bind.address because it is set by the server startup process and the other one needs to be set manually. Btw you can look at JBPAPP-996 for some issues with the sample-bindings.xml in EAP. I'm not sure if these apply to SOA-P.
Of course it is intentional, that is why it is included. It was part of the work for JBESB-1804 and did work in previous versions although this seems to no longer be the case. It may be better if we stick to the actual issue rather than the description above and, for completeness, here is what I am seeing when I start the current server. I assume you are seeing the same thing. java.net.UnknownHostException: ${jboss.esb.bind.address}: ${jboss.esb.bind.address} at java.net.InetAddress.getAllByName0(InetAddress.java:1145) at java.net.InetAddress.getAllByName(InetAddress.java:1072) at java.net.InetAddress.getAllByName(InetAddress.java:1008) at java.net.InetAddress.getByName(InetAddress.java:958) at org.jboss.services.binding.ServiceBinding.setBindAddress(ServiceBinding.java:131) at org.jboss.services.binding.ServiceBinding.<init>(ServiceBinding.java:87) at org.jboss.services.binding.XMLServicesStore.parseBinding(XMLServicesStore.java:220) at org.jboss.services.binding.XMLServicesStore.parseConfig(XMLServicesStore.java:181) at org.jboss.services.binding.XMLServicesStore.parseServer(XMLServicesStore.java:147) at org.jboss.services.binding.XMLServicesStore.load(XMLServicesStore.java:121) at org.jboss.services.binding.ServiceBindingManager.initStore(ServiceBindingManager.java:346) at org.jboss.services.binding.ServiceBindingManager.applyServiceConfig(ServiceBindingManager.java:256)
Link: Added: This issue depends JBESB-2056
Yes, exactly!
verified in IR5