3 Replies Latest reply on Mar 7, 2002 10:16 AM by adrian.brock

    3.0 Beta fails to start

    whitmad

      I have downloaded and unzipped the 3.0 beta. Running on Redhat 7.2 with Sun JDK 1.3.1, when I start jboss with run.sh - exactly as unzipped, no config changes or deployed packages - it hangs after outputting:

      08:44:28,468 INFO [ClusterPartition] Starting
      08:44:28,475 INFO [ClusterPartition] Connecting to channel

      It then won't shutdown or die, except with a kill -9

      I've tried using editing and using the jboss_init_redhat.sh script runing as root with the same result.
      Any ideas?

        • 1. Re: 3.0 Beta fails to start

          You are not connected to a network?

          Remove the cluster-service.xml from the deploy
          directory.

          Regards,
          Adrian

          • 2. Re: 3.0 Beta fails to start
            whitmad

            That seems to do the trick because I am indeed not connected to a network. I'm having a look and play on my laptop, which is generally not connected to a network while I'm commuting to work on the train. I've fooled other software that likes to think it's connected to a network by assigning my hosts IP address to the loopback interface when disconnected. Do you know precisely what jboss is doing at this point that this little con trick doesn't work?

            Thanks

            David

            • 3. Re: 3.0 Beta fails to start

              Well sort of,

              Actually it is JavaGroups that is part of the cluster
              service. It does a UDP broadcast looking for other
              JBoss installations on the network to cluster with.

              Regards,
              Adrian