6 Replies Latest reply on Jun 22, 2010 4:53 PM by pdizon

    help : WARN  [UDP] failed to join /224.0.0.75:7500

    j-root

      Dearz ,

      i'm facing a problem when i startup jboss 4.2.2 over RHEL , i'm getting this warnings :

      11:34:24,351 INFO [Server] Starting JBoss (MX MicroKernel)...
      11:34:24,352 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)
      11:34:24,354 INFO [Server] Home Dir: /JB/jboss-4.2.2
      11:34:24,354 INFO [Server] Home URL: file:/JB/jboss-4.2.2/
      11:34:24,355 INFO [Server] Patch URL: null
      11:34:24,355 INFO [Server] Server Name: all
      11:34:24,355 INFO [Server] Server Home Dir: /JB/jboss-4.2.2/server/all
      11:34:24,356 INFO [Server] Server Home URL: file:/JB/jboss-4.2.2/server/all/
      11:34:24,356 INFO [Server] Server Log Dir: /JB/jboss-4.2.2/server/all/log
      11:34:24,356 INFO [Server] Server Temp Dir: /JB/jboss-4.2.2/server/all/tmp
      11:34:24,357 INFO [Server] Root Deployment Filename: jboss-service.xml
      11:34:24,742 INFO [ServerInfo] Java version: 1.6.0_06,Sun Microsystems Inc.
      11:34:24,743 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 10.0-b22,Sun Microsystems Inc.
      11:34:24,743 INFO [ServerInfo] OS-System: Linux 2.6.9-5.ELsmp,i386
      11:34:25,354 INFO [Server] Core system initialized
      11:34:28,624 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
      11:34:28,627 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
      11:34:29,227 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
      11:34:29,227 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
      11:34:29,496 INFO [TransactionManagerService] Starting recovery manager
      11:34:29,605 INFO [TransactionManagerService] Recovery manager started
      11:34:29,605 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
      11:34:33,278 INFO [EJB3Deployer] Starting java:comp multiplexer
      11:34:34,435 WARN [UDP] failed to join /224.0.0.75:7500 on eth0: java.net.SocketException: Address already in use
      11:34:34,436 WARN [UDP] failed to join /224.0.0.75:7500 on bond0: java.net.SocketException: Address already in use


      FYI , configured network bonding on the nw interfaces
      i googled but no solution :-( .
      ur help is appreciated .

      j .

        • 1. Re: help : WARN  [UDP] failed to join /224.0.0.75:7500
          peterj

          Do you need clustering? If not, run the 'default' config instead of the 'all' config. Apparently something about your network doesn't like the udp broadcasts that the clustering code uses to communicate with other jbossas instances.

          • 2. Re: help : WARN  [UDP] failed to join /224.0.0.75:7500
            j-root

            thx 4 reply PeterJ , actually i need the 'all' configuration for clustering .
            in prior jboss versions like 4.0.4 , i didn't faced this issue .
            for my network , all the jbossas instance in the segment and there is nothing blocking the traffic .


            • 3. Re: help : WARN  [UDP] failed to join /224.0.0.75:7500
              peterj

              Did you check to see if anything else was using port 7500?

              • 4. Re: help : WARN  [UDP] failed to join /224.0.0.75:7500
                j-root

                no , noting blocking .

                you know something , 2day i executed the run.sh script with the switch -b 'interface IP" and it worked fine .

                in the prior version of jbossas , like <= 4.0.4 , i just execute the the run.sh script and it's listing on all my NW interfaces , even with network bonding .
                but now as i mentioned , i should execute the shell script with the switch -b .

                many thx PerterJ for helping and for following up , appreciated .

                J .

                • 5. Re: help : WARN  [UDP] failed to join /224.0.0.75:7500
                  peterj

                  It is amazing. 4.2.0, which changed to binding to localhost by default (earlier releases bound to 0.0.0.0, which encompasses all ip address owned by the host), came out over a year ago. Despite that there is a FAQ that mentions this, and there is text in the readme file that points this out, and the numerous forums posts about this, I am still seeing about a half-dozen posts per week on this same issue.

                  But I'm glad you are back up and running.

                  • 6. Re: help : WARN  [UDP] failed to join /224.0.0.75:7500
                    pdizon

                    Hi,

                     

                    The same error occurs multiple times on 4.2.3GA ran with -c all -b IP -g Partition switches

                     

                    When I do a netstat, it seems to be listening on udp/7500

                     

                    udp        0      0 0.0.0.0:7500                0.0.0.0:*                               -
                    udp        0      0 0.0.0.0:7500                0.0.0.0:*                               -
                    udp        0      0 0.0.0.0:7500                0.0.0.0:*                               -
                    udp        0      0 0.0.0.0:7500                0.0.0.0:*                               -