1 Reply Latest reply on Jan 11, 2004 7:26 AM by Yaron Rosenbaum

    HA-JNDI client automatic discovery

    tonyn Newbie

      I'm using JBoss3.2.2 on 2 Windows servers, I've
      set the loopback attribute in the clustering-xml to true

      Now, when I set the JNDI provider url to emptystring at client side, it does not find the jndi server. It only
      works when I specify a server or list of servers in the
      url.
      Normally it should do a multicast and find out which server to connect to.

      When I debugged org.jnp.interfaces.NamingContext,
      I saw that it received a reply from a running JBoss server, but the replystring with host/port was '0.0.0.0:110'. (line 1095 myServer = new String (reply).trim();)

      Then, it tries to create a socket for this remote-address, and throws Bind exception, since remote-address is invalid.
      The result is the same, whether the datagram came from server1 or server2


      I've also tried to run the server on a specific address
      by running --host=10.10.10.242, but then the replystring is '10.10.10.', so dropping the final part.


      javax.naming.CommunicationException: Failed to connect to server 0.0.0.0:110. Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 0.0.0.0:110. Root exception is java.net.BindException: Cannot assign requested address: connect
      at java.net.PlainSocketImpl.socketConnect(Native Method)
      at java.net.PlainSocketImpl.doConnect(Unknown Source)
      at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
      at java.net.PlainSocketImpl.connect(Unknown Source)
      at java.net.Socket.(Unknown Source)
      at java.net.Socket.(Unknown Source)
      at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69)
      at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62)
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:186)