1 Reply Latest reply on Jan 12, 2006 6:47 AM by Rajesh Chande

    UDP.start(): The requested address is not valid in its conte

    Joe Reger Newbie

      Hi! I downloaded and installed jboss 4.03 SP1 via the installer, choosing the "all" configuration. I then executed "run -c all" and the server beganstartup. However, it hit the following exception:


      22:52:22,564 INFO [TreeCache] setting cluster properties from xml to: UDP(ip_mcast=true;ip_ttl=8;loopback=false;mcast_addr=230.1.2.7;mcast_port=45577;mcast_recv_buf_size=80000;mca
      st_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;m
      in_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,2
      400,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=tru
      e;up_thread=true)
      22:52:22,580 INFO [TreeCache] interceptor chain is:
      class org.jboss.cache.interceptors.CallInterceptor
      class org.jboss.cache.interceptors.LockInterceptor
      class org.jboss.cache.interceptors.UnlockInterceptor
      class org.jboss.cache.interceptors.ReplicationInterceptor
      22:52:22,580 INFO [TreeCache] cache mode is REPL_ASYNC
      22:52:22,658 ERROR [JChannel] exception: java.lang.Exception: exception caused by UDP.start(): java.net.SocketException: The requested address is not valid in its context
      22:52:22,658 WARN [ServiceController] Problem starting service jboss.cache:service=TomcatClusteringCache
      ChannelException: java.lang.Exception: exception caused by UDP.start(): java.net.SocketException: The requested address is not valid in its context
      at org.jgroups.JChannel.connect(JChannel.java:328)
      at org.jboss.cache.TreeCache.startService(TreeCache.java:1119)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)



      I get a similar error a number of times when various loaders attempt to run JCjannel.java line 328. I'm told "Problem starting service" for each of these:

      jboss.cache:service=EJB3SFSBClusteredCache
      jboss:service=DefaultPartition
      jboss.cache:service=EJB3EntityTreeCache
      jboss.cache:service=TomcatClusteringCache


      When I watch the port bindings on the server with "netstat -a" I see that prior to starting jboss port 45577 is available. Shortly thereafter, ports 43333, 45551, 45566 and 45577 are not available.

      At first I assumed that the errors I was seeing were not a problem... just not caught. But near the bottom of the startup process I see:

      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.cache:service=EJB3SFSBClusteredCache
      State: FAILED
      Reason: ChannelException: java.lang.Exception: exception caused by UDP.start(): java.net.SocketException: The requested address is not valid in its context

      ObjectName: jboss.cache:service=EJB3EntityTreeCache
      State: FAILED
      Reason: ChannelException: java.lang.Exception: exception caused by UDP.start(): java.net.SocketException: The requested address is not valid in its context
      I Depend On:
      jboss:service=Naming
      jboss:service=TransactionManager

      ObjectName: jboss.cache:service=TomcatClusteringCache
      State: FAILED
      Reason: ChannelException: java.lang.Exception: exception caused by UDP.start(): java.net.SocketException: The requested address is not valid in its context
      I Depend On:
      jboss:service=Naming
      jboss:service=TransactionManager

      ObjectName: jboss:service=DefaultPartition
      State: FAILED
      Reason: ChannelException: java.lang.Exception: exception caused by UDP.start(): java.net.SocketException: The requested address is not valid in its context
      I Depend On:
      jboss:service=Naming
      Depends On Me:
      jboss:service=HASessionState
      jboss:service=HAJNDI
      jboss.cache:service=InvalidationBridge,type=JavaGroups


      This makes me think that some services are not properly up and running. Is anybody else seeing this? Is it a problem? Is there an easy way to test, for example, the TomcatClusteringCache?

      Thanks,

      Joe

        • 1. Re: UDP.start(): The requested address is not valid in its c
          Rajesh Chande Newbie

          Hello,

          I have also setup and am running 4.0.3 sp1 "all" instance. Everything is OK for me. But I have the following error on the console:

          ###############################

          16:43:53,950 INFO [Server] JBoss (MX MicroKernel) [4.0.3SP1 (build: CVSTag=JBos
          s_4_0_3_SP1 date=200510231054)] Started in 24s:537ms
          16:44:00,680 WARN [UDP] packet from /3.209.120.38:3018 has different version (0
          224) from ours (0227). This may cause problems
          16:44:14,831 WARN [UDP] packet from /3.209.120.38:3018 has different version (0
          224) from ours (0227). This may cause problems
          16:44:14,831 ERROR [UDP] exception=java.io.InvalidClassException: org.jgroups.st
          ack.IpAddress; local class incompatible: stream classdesc serialVersionUID = -19
          99612243427863834, local class serialVersionUID = -8753594169997651306
          at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:463)
          at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:152
          1)
          at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1435)
          at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1
          626)
          at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
          at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:18
          45)
          at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)

          at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1
          646)
          at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
          at org.jgroups.protocols.PingHeader.readExternal(PingHeader.java:55)
          at org.jgroups.util.Marshaller.read(Marshaller.java:77)
          at org.jgroups.Message.readExternal(Message.java:491)
          at org.jgroups.protocols.UDP.handleIncomingUdpPacket(UDP.java:686)
          at org.jgroups.protocols.UDP$UcastReceiver.run(UDP.java:1294)
          at java.lang.Thread.run(Thread.java:534)

          16:44:21,501 WARN [UDP] packet from /3.209.120.38:3018 has different version (0
          224) from ours (0227). This may cause problems


          ###############################

          I deployed one web application in cluster, the application was running fine.

          Any idea, what is the error for?