Skip to main content

Source code revision

svn

summary: Changes to handle GMS config information on the group management service object in the server config for user-managed clusters. GMS can be started now by setting the GMS_DISCOVERY_URI_LIST and GMS_ENABLED properties on the config (along with the needed cluster and instance names). The health history will now be stored on each instance since each one is a clustered DAS.
revision: 48290
author: Bobby Bissett
date: 2011-07-25 18:59:25 UTC (3 years)
message: Changes to handle GMS config information on the group management service object in the server config for user-managed clusters. GMS can be started now by setting the GMS_DISCOVERY_URI_LIST and GMS_ENABLED properties on the config (along with the needed cluster and instance names). The health history will now be stored on each instance since each one is a clustered DAS.

Next steps: change in GMS to treat an empty discovery list as meaning this is the first instance coming up. Also need to register tx recovery handler in the case where the DAS is a core GMS member.

Code reviewed by Joe, pom changes by Jane.

Change Path Actions
M branches/umc/cluster/gms-adapter/src/main/java/org/glassfish/gms/GMSAdapterImpl.java
M branches/umc/cluster/gms-bootstrap/src/main/java/org/glassfish/gms/bootstrap/GMSAdapterService.java
M branches/umc/cluster/gms-bootstrap/src/main/java/org/glassfish/gms/bootstrap/HealthHistory.java
M branches/umc/cluster/gms-bootstrap/src/main/resources/org/glassfish/gms/bootstrap/LogStrings.properties
M branches/umc/packager/resources/pkg_conf.py
M branches/umc/pom.xml
 
 
Close
loading
Please Confirm
Close