Node that can not join cluster due to license restriction causes cluster panic

XMLWordPrintable

      It appears that when a node is denied entry to a cluster because it would violate the licensed maximum number of nodes, the node continues to run. It would appear that the cluster safety job continues to function which will cause the valid nodes in the cluster to panic. We need to prevent the unlicensed node from using the database in this situation.

      2008-02-28 03:44:58,065 INFO [main] [confluence.cluster.tangosol.TangosolClusterManager] startCluster Bringing up cluster service
2008-02-28 03:44:58,746 ERROR [main] [atlassian.config.bootstrap.DefaultAtlassianBootstrapManager] init Home is not configured properly: com.atlassian.config.ConfigurationException: Exception bootstrapping cluster:This licence only allows 2 nodes in the cluster. This would be exceeded if this node joined.
2008-02-28 03:44:58,773 FATAL [main] [atlassian.confluence.setup.ConfluenceConfigurationListener] contextInitialized An error was encountered while bootstrapping Confluence (see below): 
Unable to bootstrap application: Exception bootstrapping cluster:This licence only allows 2 nodes in the cluster. This would be exceeded if this node joined.
com.atlassian.config.bootstrap.BootstrapException: Unable to bootstrap application: Exception bootstrapping cluster:This licence only allows 2 nodes in the cluster. This would be exceeded if this node joined.
	at com.atlassian.config.util.BootstrapUtils.init(BootstrapUtils.java:38)
	at com.atlassian.confluence.setup.ConfluenceConfigurationListener.initialiseBootstrapContext(ConfluenceConfigurationListener.java:74)

              Assignee:
              Unassigned
              Reporter:
              Ivan Benko [Atlassian]
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: