1 Reply Latest reply on Mar 6, 2005 11:06 AM by belaban

    HAJNDI: Service unavailable

    nferreira
    nferreira Mar 6, 2005 10:13 AM

      Hi All,

      I am using the HA JNDI feature in my application. Nevertheless, I am just able to use it when I start the JBoss server with:

      ./run.sh --host=192.168.190.1 -c all


      If I start the service without the --host flag the following error occurs and the services gets unavailable. 

      11:48:22,693 INFO [TreeCache] setting cluster properties from xml to: UDP(ip_mcast=true;ip_ttl=64;loopback=false;mcast_addr=230.1.2.3;mcast_port=45577;mcast_recv_buf_size=80000;mcast_send_buf_size=150000;ucast_recv_buf_size=80000;ucast_send_buf_size=150000):PING(down_thread=false;num_initial_members=3;timeout=2000;up_thread=false):MERGE2(max_interval=20000;min_interval=10000):FD_SOCK:VERIFY_SUSPECT(down_thread=false;timeout=1500;up_thread=false):pbcast.NAKACK(down_thread=false;gc_lag=50;max_xmit_size=8192;retransmit_timeout=600,1200,2400,4800;up_thread=false):UNICAST(down_thread=false;min_threshold=10;timeout=600,1200,2400;window_size=100):pbcast.STABLE(desired_avg_gossip=20000;down_thread=false;up_thread=false):FRAG(down_thread=false;frag_size=8192;up_thread=false):pbcast.GMS(join_retry_timeout=2000;join_timeout=5000;print_local_addr=true;shun=true):pbcast.STATE_TRANSFER(down_thread=true;up_thread=true)
11:48:22,864 INFO [TreeCache] interceptor chain is:
class org.jboss.cache.interceptors.CallInterceptor
class org.jboss.cache.interceptors.LockInterceptor
class org.jboss.cache.interceptors.CreateIfNotExistsInterceptor
class org.jboss.cache.interceptors.ReplicationInterceptor
11:48:22,865 INFO [TreeCache] cache mode is REPL_ASYNC
11:48:23,039 INFO [UDP] unicast sockets will use interface 127.0.0.2

11:48:23,042 ERROR [JChannel] exception: java.lang.Exception: exception caused by UDP.start(): java.net.SocketException: bad argument for IP_MULTICAST_IF:address not bound to any interface


      I checked in the source code and notice that the JChannel error was related with the bind.address property used by JGroup. Therefore, I set the bind.address option in the run.conf file. The error is not occuring any more. Nevertheless, the service is still UNAVAILABLE.

      Do you guys have any suggestion?

      • 3435 Views
      • Tags: