GMSAD

GMSAD016 complete failure recovery callback for component: {0} failed member: {1}

Description: TBD

GMSAD1001 no clustername to lookup

Cause: Required information was not passed into method.

Solution: File issue with all relevant information.

GMSAD1002 Multiple gms-adapter service for cluster {0}

Cause: GMs module is being initialized more than once for the same cluster.

Solution: File issue with all relevant information.

GMSAD1003 GMS cannot initialize with unknown cluster

Cause: No cluster was found with this name in the domain configuration.

Solution: Check that domain exists in domain.xml.

GMSAD1004 Started GMS for instance {0} in group {1}

Description: TBD

GMSAD1005 Member {0} joined group {1}

Description: TBD

GMSAD1006 aliveAndReady monitoring: joinedAndReady memberState is UNKNOWN for core members: {0}

Description: TBD

GMSAD1007 AliveAndReady for signal: {0} for member: {1} of group: {2} current:[{3}] previous:[{4}]

Description: TBD

GMSAD1008 GMSAdapter for member: {0} group: {1} received GlassfishEventType: {2}

Cause: An unexpected exception occurred in the GMS implementation.

Solution: Check the server log file for more information from Shoal-GMS.

GMSAD1009 An exception occurred while creating the HealthHistory object: {0}

Cause: An unexpected exception occurred.

Solution: See server log for more details.

GMSAD1010 An exception occurred while processing GMS configuration properties: {0}

Cause: An unexpected exception occurred.

Solution: See server log for more details.

GMSAD1011 Ignoring group-management-service property {0} with value of {1} due to {2}

Cause: An illegal argument was passed into the Shoal GMS implementation.

Solution: Check the server log file for more information from Shoal-GMS.

GMSAD1012 Error processing cluster property:{0} value:{1} due to exception {2}

Cause: An unexpected exception occurred.

Solution: Check the server log file for more information from Shoal-GMS.

GMSAD1013 Exception in getting GMS module for group {0}: {1}

Cause: There was a problem withing the GMS implementation.

Solution: Check the server log file for more information from Shoal-GMS.

GMSAD1014 An exception occurred while updating the instance health history table: {0}

Cause: An unexpected exception occurred.

Solution: Check the log for Shoal-GMS exceptions.

GMSAD1015 start failure recovery callback for component: {0} failed member: {1}

Description: TBD

GMSAD1017 GMS failed to start. See stack trace for additional information.

Description: TBD

GMSAD1018 GMS failed to start due to a runtime exception. See stack trace for additional information.

Description: TBD

GMSAD1019 GMS bind interface address {0} is invalid. Will use default value instead.

Cause: The specified bind interface address is not an active local address, so it cannot be used on this node.

Solution: Check that you have specified the proper address. See server log for more details from GMS subsystem.

GMSAD3001 GMSAnnounceAfterStartClusterCommand: exitCode:{0} members {1} clusterMembers:{2}

Description: TBD

GMSAD3002 An exception occurred while announcing GMS group startup: {0}

Cause: An unexpected exception occurred in the GMS implementation.

Solution: Check the server log file for more information from Shoal-GMS.

GMSAD3003 An exception occurred while announcing GMS group shutdown: {0}

Cause: An unexpected exception occurred in the GMS implementation.

Solution: Check the server log file for more information from Shoal-GMS.

GMSAD3004 An exception occurred while announcing GMS group startup: {0}

Cause: An unexpected exception occurred in the GMS implementation.

Solution: Check the server log file for more information from Shoal-GMS.

GMSAD3005 An exception occurred while announcing GMS group shutdown: {0}

Cause: An unexpected exception occurred in the GMS implementation.

Solution: Check the server log file for more information from Shoal-GMS.