4 Replies Latest reply on Mar 21, 2005 10:47 PM by matthew.quinlan

    ChannelException: java.net.SocketException: bad argument for

    lretief

      I am running JBoss 3.2.3 on Suse 9.1. Using a brand new out the box installation of JBoss, I start the all server (run.sh -c all) and get the following exception:

      10:15:24,447 ERROR [ClusterPartition] Starting failed
      ChannelException: java.net.SocketException: bad argument for IP_MULTICAST_IF: address not bound to any interface
      at org.jgroups.JChannel.connect(JChannel.java:224)
      at org.jboss.ha.framework.server.ClusterPartition.startService(ClusterPartition.java:291)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)


      Later on on the log, I get these dependency errors:

      11:37:32,162 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer:

      Incompletely deployed packages:

      MBeans waiting for classes:

      MBeans waiting for other MBeans:
      [ObjectName: jboss.mq:service=HAILSharedState
      state: CREATED
      I Depend On: jboss:service=DefaultPartition

      Depends On Me: jboss.mq:service=InvocationLayer,type=HAIL
      , ObjectName: jboss.mq:service=InvocationLayer,type=HAIL
      state: CREATED
      I Depend On: jboss.mq:service=InvocationLayer,type=UIL2
      jboss.mq:service=HAILSharedState

      Depends On Me: jboss.mq:service=HAILSingletonController
      , ObjectName: jboss.mq:service=HAILSingletonController
      state: CONFIGURED
      I Depend On: jboss:service=DefaultPartition
      jboss.mq:service=InvocationLayer,type=HAIL

      Depends On Me: , ObjectName: jboss.j2ee:jndiName=clustering/HTTPSession,service=EJB
      state: CREATED
      I Depend On: jboss:service=DefaultPartition
      jboss:service=invoker,type=jrmp

      Depends On Me: jboss:service=ClusteredHttpSession
      , ObjectName: jboss:service=ClusteredHttpSession
      state: CREATED
      I Depend On: jboss.j2ee:jndiName=clustering/HTTPSession,service=EJB

      Depends On Me: , ObjectName: jboss:service=DefaultPartition
      state: FAILED
      I Depend On:
      Depends On Me: jboss.mq:service=HAILSharedState
      jboss.mq:service=HAILSingletonController
      jboss.j2ee:jndiName=clustering/HTTPSession,service=EJB
      jboss:service=HASessionState
      jboss:service=HAJNDI
      jboss.cache:service=InvalidationBridge,type=JavaGroups
      jboss:service=FarmMember,partition=DefaultPartition
      ChannelException: java.net.SocketException: bad argument for IP_MULTICAST_IF: address not bound to any interface, ObjectName: jboss:service=HASessionState
      state: CREATED
      I Depend On: jboss:service=DefaultPartition

      Depends On Me: , ObjectName: jboss:service=HAJNDI
      state: CREATED
      I Depend On: jboss:service=DefaultPartition

      Depends On Me: , ObjectName: jboss.cache:service=InvalidationBridge,type=JavaGroups
      state: CONFIGURED
      I Depend On: jboss:service=DefaultPartition
      jboss.cache:service=InvalidationManager

      Depends On Me: , ObjectName: jboss:service=FarmMember,partition=DefaultPartition
      state: CONFIGURED
      I Depend On: jboss:service=DefaultPartition
      jboss.web:service=WebServer
      jboss.system:service=MainDeployer

      Depends On Me: ]

      A colleague get exactly the same problem - same OS and Jboss version. Please help.

      Thanks,
      Lisa

        • 1. Re: ChannelException: java.net.SocketException: bad argument
          jonlee

          The "all" server is configured for a clustered environment and the cluster binding is not configured correctly I guess or the network configuration on the Linux boxen is wrong. For single server operation, you are probably safer using the default configuration - you will still need to get the Linux network configuration correct - /etc/hosts properly set for your machine and so on.

          Hope that is of use.

          • 2. Re: ChannelException: java.net.SocketException: bad argument
            lretief

            Actually, the fix is to change the following lines in /etc/modules.conf:

            alias net-pf-10 ipv6
            #alias net-pf-10 off

            to:

            #alias net-pf-10 ipv6
            alias net-pf-10 off

            Apparently it is a Suse problem that causes applications to IPV6 for DNS resolution and then lock up there. Once I made the change it all starts beautifully.

            • 3. Re: ChannelException: java.net.SocketException: bad argument
              bbbear

              Hi, i have the same problem, but when I do what you suggested, the problem still the same. I wonder if I've missed anything else?? I have the same OS config as you did.

              Thanks.

              • 4. Re: ChannelException: java.net.SocketException: bad argument


                FYI: For those of you using Novell's Suse desktop version you need to modify /etc/modprobe.conf instead of etc/modules.conf.



                "lretief" wrote:
                Actually, the fix is to change the following lines in /etc/modules.conf:

                alias net-pf-10 ipv6
                #alias net-pf-10 off

                to:

                #alias net-pf-10 ipv6
                alias net-pf-10 off

                Apparently it is a Suse problem that causes applications to IPV6 for DNS resolution and then lock up there. Once I made the change it all starts beautifully.