1 Reply Latest reply on Mar 19, 2003 3:03 PM by Sacha Labourey

    ClusterPartition hangs up

    Markus Newbie

      Hi there!

      I've got the following problem: Using JBoss on WinXP worked fine with clustering and farming. Now I've tried to use it on Suse-Linux, but JBoss hangs up after telling me "Connecting to channel". I can't shutdown the server then any more...

      2003-03-18 12:16:12,375 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/usr/local/jboss/jbosstomcat/server/all/deploy/cluster-service.xml
      2003-03-18 12:16:12,375 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, create step: url file:/usr/local/jboss/jbosstomcat/server/all/deploy/cluster-service.xml
      2003-03-18 12:16:12,375 DEBUG [org.jboss.deployment.SARDeployer] Registering service UCL=jmx.loading:UCL=15623809
      2003-03-18 12:16:12,377 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository] UnifiedLoaderRepository skipping duplicate org.jboss.mx.loading.UnifiedClassLoader@ee6681{ url=file:/usr/local/jboss/jbosstomcat/server/all/tmp/deploy/server/all/deploy/cluster-service.xml/52.cluster-service.xml }
      2003-03-18 12:16:12,379 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss:service=DefaultPartition
      2003-03-18 12:16:12,379 DEBUG [org.jboss.system.ServiceCreator] code: org.jboss.ha.framework.server.ClusterPartition
      2003-03-18 12:16:12,425 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss:service=DefaultPartition
      2003-03-18 12:16:12,426 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss:service=HASessionState
      2003-03-18 12:16:12,426 DEBUG [org.jboss.system.ServiceCreator] code: org.jboss.ha.hasessionstate.server.HASessionStateService
      2003-03-18 12:16:12,466 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss:service=HASessionState
      2003-03-18 12:16:12,467 DEBUG [org.jboss.system.ServiceController] recording that jboss:service=HASessionState depends on jboss:service=DefaultPartition
      2003-03-18 12:16:12,467 DEBUG [org.jboss.system.ServiceConfigurator] considering with object name jboss:service=DefaultPartition
      2003-03-18 12:16:12,467 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss:service=HAJNDI
      2003-03-18 12:16:12,467 DEBUG [org.jboss.system.ServiceCreator] code: org.jboss.ha.jndi.HANamingService
      2003-03-18 12:16:12,524 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss:service=HAJNDI
      2003-03-18 12:16:12,525 DEBUG [org.jboss.system.ServiceController] recording that jboss:service=HAJNDI depends on jboss:service=DefaultPartition
      2003-03-18 12:16:12,525 DEBUG [org.jboss.system.ServiceConfigurator] considering with object name jboss:service=DefaultPartition
      2003-03-18 12:16:12,525 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss:service=invoker,type=jrmpha
      2003-03-18 12:16:12,525 DEBUG [org.jboss.system.ServiceCreator] code: org.jboss.invocation.jrmp.server.JRMPInvokerHA
      2003-03-18 12:16:12,576 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss:service=invoker,type=jrmpha
      2003-03-18 12:16:12,577 INFO [org.jboss.ha.framework.server.ClusterPartition] Creating
      2003-03-18 12:16:12,578 DEBUG [org.jboss.ha.framework.server.ClusterPartition] Creating JavaGroups JChannel
      2003-03-18 12:16:13,513 DEBUG [org.jboss.ha.framework.server.ClusterPartition] Creating HAPartition
      2003-03-18 12:16:13,774 DEBUG [org.jboss.ha.framework.server.ClusterPartition] Initing HAPartition: org.jboss.ha.framework.server.HAPartitionImpl@955cd5
      2003-03-18 12:16:13,774 INFO [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] Initializing
      2003-03-18 12:16:13,775 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] setMembershipListener
      2003-03-18 12:16:13,775 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] setMessageListener
      2003-03-18 12:16:13,775 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] create replicant manager
      2003-03-18 12:16:13,792 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] init replicant manager
      2003-03-18 12:16:13,792 DEBUG [DefaultPartition:ReplicantManager] registerRPCHandler
      2003-03-18 12:16:13,792 DEBUG [DefaultPartition:ReplicantManager] registerMembershipListener
      2003-03-18 12:16:13,798 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] bind replicant manager
      2003-03-18 12:16:13,798 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] create distributed state
      2003-03-18 12:16:13,821 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] init distributed state service
      2003-03-18 12:16:13,829 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] bind distributed state service
      2003-03-18 12:16:13,845 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] creating SubcontextHAPartition
      2003-03-18 12:16:13,846 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] done initing.
      2003-03-18 12:16:13,847 DEBUG [org.jboss.ha.framework.server.ClusterPartition] HAPartition initialized
      2003-03-18 12:16:13,847 INFO [org.jboss.ha.framework.server.ClusterPartition] Created
      2003-03-18 12:16:13,850 INFO [org.jboss.ha.hasessionstate.server.HASessionStateService] Creating
      2003-03-18 12:16:13,871 DEBUG [org.jboss.ha.hasessionstate.server.HASessionStateImpl./HASessionState/Default] creating SubcontextHASessionState
      2003-03-18 12:16:13,872 INFO [org.jboss.ha.hasessionstate.server.HASessionStateService] Created
      2003-03-18 12:16:13,874 INFO [org.jboss.ha.jndi.HANamingService] Creating
      2003-03-18 12:16:13,874 DEBUG [org.jboss.ha.jndi.HANamingService] Initializing HAJNDI server
      2003-03-18 12:16:13,875 DEBUG [org.jboss.ha.jndi.HANamingService] jndi lookup of /HAPartition/DefaultPartition
      2003-03-18 12:16:13,875 DEBUG [org.jboss.ha.jndi.HANamingService] Create remote object
      2003-03-18 12:16:13,883 DEBUG [org.jboss.ha.jndi.HANamingService] initialize HAJNDI
      2003-03-18 12:16:13,883 DEBUG [org.jboss.ha.jndi.HAJNDI] subscribeToStateTransferEvents
      2003-03-18 12:16:13,883 DEBUG [org.jboss.ha.jndi.HAJNDI] registerRPCHandler
      2003-03-18 12:16:13,884 INFO [org.jboss.ha.jndi.HANamingService] Created
      2003-03-18 12:16:13,885 INFO [org.jboss.invocation.jrmp.server.JRMPInvokerHA] creating
      2003-03-18 12:16:13,885 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvokerHA] Container Invoker RMI Port='Anonymous'
      2003-03-18 12:16:13,886 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvokerHA] Container Invoker Client SocketFactory='Default'
      2003-03-18 12:16:13,886 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvokerHA] Container Invoker Server SocketFactory='Default'
      2003-03-18 12:16:13,886 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvokerHA] Container Invoker Server SocketAddr='Default'
      2003-03-18 12:16:13,886 INFO [org.jboss.invocation.jrmp.server.JRMPInvokerHA] created
      2003-03-18 12:16:13,886 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying cluster-service.xml
      2003-03-18 12:16:13,886 DEBUG [org.jboss.deployment.MainDeployer] start step for deployment file:/usr/local/jboss/jbosstomcat/server/all/deploy/cluster-service.xml
      2003-03-18 12:16:13,886 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, start step: url file:/usr/local/jboss/jbosstomcat/server/all/deploy/cluster-service.xml
      2003-03-18 12:16:13,887 INFO [org.jboss.ha.framework.server.ClusterPartition] Starting
      2003-03-18 12:16:13,887 DEBUG [org.jboss.ha.framework.server.ClusterPartition] Starting ClusterPartition: DefaultPartition
      2003-03-18 12:16:13,887 INFO [org.jboss.ha.framework.server.ClusterPartition] Connecting to channel

      Can someone help me? I really don't know, why it hangs up...

      Greetings,
      Markus

        • 1. Re: ClusterPartition hangs up
          Sacha Labourey Master

          make sure:
          - a firewall is not started as part of your linux distrib (iptables, etc.)
          - multicast is enabled (and present in your kernel)
          - etc.

          (the doc contains some trick on how to detect if your basic setup is working before trying to launch the full JBoss stack)

          cheers,


          sacha