Hi,
When using clusters GMS takes care of notifying the participating
cluster instances of membership changes.
The DAS also seems to participate in this as spectator, but as the
processing to join in happens at start up time (see stacktrace below),
you have to restart the DAS first.
I'm not sure yet why the DAS needs to be notified of its clusters'
membership changes, but for each cluster the DAS seems to create like 10
threads so with multiple clusters running the restart of the DAS makes
it sluggish and consume a lot of resources.
Am I looking at a potential bug or is this per design?
at com.sun.enterprise.jxtamgmt.HealthMonitor.start(HealthMonitor.java:381)
at com.sun.enterprise.jxtamgmt.ClusterManager.start(ClusterManager.java:339)
at
com.sun.enterprise.ee.cms.impl.jxta.GroupCommunicationProviderImpl.join(GroupCommunicationProviderImpl.java:142)
at com.sun.enterprise.ee.cms.impl.jxta.GMSContext.join(GMSContext.java:124)
at
com.sun.enterprise.ee.cms.impl.common.GroupManagementServiceImpl.join(GroupManagementServiceImpl.java:309)
at
com.sun.enterprise.ee.cms.lifecycle.GMSLifecycleImpl.initializeGMSForThisInstance(GMSLifecycleImpl.java:217)
at
com.sun.enterprise.ee.cms.lifecycle.GMSLifecycleImpl.onInitialization(GMSLifecycleImpl.java:102)
at
com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:284)
at
com.sun.enterprise.server.ondemand.OnDemandServer.onInitialization(OnDemandServer.java:101)
Thanks,
Dies