2 Replies Latest reply on Apr 17, 2002 5:23 AM by Jason Uithol

    Slow startup !!! HAJNDI Automatic Discovery

    Jason Uithol Newbie

      Why does the HAJNDI Automatic Discovery wait a whole minute listening for queries before allowing Jboss to get on with starting up ?

      Can I stop this ? I've included a ( relatively ) small fragment of log to illustrate.





      (extract of log)

      002-04-16 13:21:52,756 INFO [org.jboss.ha.framework.server.ClusterPartition] Starting
      2002-04-16 13:21:52,762 DEBUG [org.jboss.ha.framework.server.ClusterPartition] Starting ClusterPartition: DefaultPartition
      2002-04-16 13:21:52,762 INFO [org.jboss.ha.framework.server.ClusterPartition] Connecting to channel
      2002-04-16 13:21:52,796 INFO [STDOUT]
      -------------------------------------------------------
      GMS: address is <secret name>:<secret port>
      -------------------------------------------------------
      2002-04-16 13:21:54,861 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] new view accepted: 0 ([<secret name>:<secret port>]
      )
      2002-04-16 13:21:54,862 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] ViewAccepted: initial members set
      2002-04-16 13:21:54,893 INFO [org.jboss.ha.framework.server.ClusterPartition] Starting channel
      2002-04-16 13:21:54,893 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] get nodeName
      2002-04-16 13:21:54,893 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] Get current members
      2002-04-16 13:21:54,894 INFO [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] Number of cluster members: 1
      2002-04-16 13:21:54,899 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] setState called
      2002-04-16 13:21:54,899 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] state is null
      2002-04-16 13:21:54,899 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] State could not be retrieved, (must b
      e first member of group)
      2002-04-16 13:21:54,900 INFO [DefaultPartition:ReplicantManager] mergemembers
      2002-04-16 13:21:54,900 DEBUG [DefaultPartition:ReplicantManager] start MergeMembers
      2002-04-16 13:21:55,070 INFO [org.jboss.ha.framework.server.ClusterPartition] Started ClusterPartition: DefaultPartition
      2002-04-16 13:21:55,071 INFO [org.jboss.ha.framework.server.ClusterPartition] Started
      2002-04-16 13:21:55,071 INFO [org.jboss.ha.hasessionstate.server.HASessionStateService] Starting
      2002-04-16 13:21:55,071 DEBUG [org.jboss.ha.hasessionstate.server.HASessionStateImpl./HASessionState/Default] HASessionState node na
      me : <secret name>:<secret port>
      2002-04-16 13:21:55,072 INFO [org.jboss.ha.hasessionstate.server.HASessionStateService] Started
      2002-04-16 13:21:55,072 INFO [org.jboss.ha.jndi.HANamingService] Starting
      2002-04-16 13:21:55,072 DEBUG [org.jboss.ha.jndi.HANamingService] Create HARMIServer proxy
      2002-04-16 13:21:55,314 DEBUG [DefaultPartition:ReplicantManager] notifyKeyListeners
      2002-04-16 13:21:55,316 DEBUG [DefaultPartition:ReplicantManager] notifying 1 listeners for key change: HAJNDI
      2002-04-16 13:21:55,317 DEBUG [org.jboss.ha.framework.server.HATarget] replicantsChanged 'HAJNDI' to 1 (intra-view id: -<secret id>)
      2002-04-16 13:21:55,389 DEBUG [org.jboss.ha.jndi.HANamingService] Starting listener
      2002-04-16 13:21:55,391 INFO [org.jboss.ha.jndi.HANamingService] Listening on <secret IP2>:<secret port2>

      (Note the 1:05 gap in the log)

      2002-04-16 13:23:00,531 INFO [org.jboss.ha.jndi.HANamingService$AutomaticDiscovery] Listening on <secret IP3>:<secret port3>

      (etc)