Hi all, I have a similar problem than the one previously quoted. I'm using the 1.1 release of the single distribution and everything works fine if my zookeeper and my service are not on the same host, it translate localhost into the real IP address. The problem is when my zookeper and my service are on the same host, the address stored in zookeeper is 127.0.0.1 and when another service (which is on a different host) want to connect to this one, it gets a ConnectionException because it can't find 127.0.0.1. Is there any way to avoid the service registering with 127.0.0.1.
Thanks, Julien bonthomme wrote: > > Hi All, > > Working with the Zookeeper discovery setup, and things are working as > long as I explicitly specify org.apache.cxf.ws.address in my service > decoration xml file. If I don't specify it, it will default to > localhost. Not unreasonable, but the problem is, localhost will be the > endpoint that gets registered with Zookeeper. So, when another box looks > for the interface, Zookeeper will tell it that it is on localhost (i.e. > the client itself), and that will fail. With this setup, do you have to > explicitly specify the endpoint, or is there some other default behavior > to leverage that will actually use the real IP of the registering > localhost when it gets entered into Zookeeper so other clients can find > it? > > Many thanks, > > Thom > > > -- View this message in context: http://old.nabble.com/Default-endpoint-via-Zookeeper-%28D-OSGi%29-%28repost-to-get-its-own-thread%2C-sorry-all%29-tp24869581p28217515.html Sent from the cxf-user mailing list archive at Nabble.com.
