GlassFish v3 Error Message Reference
\

SGMT

This page lists error messages with the SGMT prefix.

See How to Contribute for more information about adding to and enhancing the information on this page.

----SGMT0005 Self Management Service on Shutdown

Cause

TBD

Solution

TBD

----SGMT0006 Self Management Service on Termination

Cause

TBD

Solution

TBD

----SGMT0008 Self Management Service not configured

Cause

TBD

Solution

TBD

----SGMT0013 Error in registering action : {1} in Rule : {0}. Possible error with action, try redeploying the application

Cause

TBD

Solution

TBD

----SGMT0017 Error creating and configuring the rule : {0} due to IlegalArguments specified for its event type : {1}. Create the rule with correct arguments for the configured event.

Cause

TBD

Solution

TBD

----SGMT0018 Configured action name={1} for Rule name={0} is disabled. The action would not be executed till it is enabled.

Cause

TBD

Solution

TBD

----SGMT0019 Could not delete rule. No configured rule exists with name={0}

Cause

TBD

Solution

TBD

----SGMT0020 Error encountered while trying to delete rule={0}. Reason - {1}

Cause

TBD

Solution

TBD

----SGMT0021 Successfully deleted rule={0}, with description= {1}

Cause

TBD

Solution

TBD

----SGMT0200 Error in sending the alert me2sage for event : {0} due to : {1}

Cause

TBD

Solution

TBD

----SGMT0201 Error in sending the alert for event : {0} as no configured mail recipients

Cause

TBD

Solution

TBD

----SGMT0203 Error in sending the alert for event : {0} due to configured mail resource {1} not found

Cause

TBD

Solution

TBD

---SGMT0210 {0} Cannot check for potential non-responsive requests/threads. This is because internal statistics are not available due HttpService monitoring being switched OFF. Set it to non-OFF value for successful checks to occur.

Cause

TBD

Solution

TBD

---SGMT0211 {0} No http requests received

Cause

TBD

Solution

TBD

---SGMT0212 {0} Could not send mail alert due to invalid ref, {1} ,configured. Please ensure that the configured mail alert application is available.

Cause

TBD

Solution

TBD

---SGMT0213 {0} Error encountered while trying to send mail alert. Would proceed to log the detail.

Cause

TBD

Solution

TBD

---SGMT0214 {0} Potential request/threads found to be non-responsive={1}.

Cause

TBD

Solution

TBD

---SGMT0215 {0} Error encountered while trying to stop/interrupt the potential unresponsive request/thread/

Cause

TBD

Solution

TBD

---SGMT0216 {0} Error encountered while trying to retrieve statistics to determine potential non-responsive requests/threads.

Cause

TBD

Solution

TBD

---SGMT0217 {0} Found non-responsive http request/thread on listener port:{1}, for URI={2}

Cause

TBD

Solution

TBD

---SGMT0218 {0} Stopped non-responsive http request/thread on listener port={1}, for URI={2}

Cause

TBD

Solution

TBD

---SGMT0219 {0} Cannot send mail alert on the check for non-responsive requests/threads, as application ref for mail alert is not provided.

Cause

TBD

Solution

TBD

---SGMT0220 {0} HttpService monitoring switched ON. Statistics for check for non-responsive http request/threads would now be enabled.

Cause

TBD

Solution

TBD

---SGMT0221 {0} HttpService monitoring switched OFF. It would not be possible to check for non-responsive http requests/threads, due to non-availability of internal statistics.

Cause

TBD

Solution

TBD

---SGMT0222 {0} Due ThresholdWaitInMillis:{1} being less than load balancer default timeout value of:{2}; resetting it to load balancer default.

Cause

TBD

Solution

TBD

---SGMT0223 {0} Due ThresholdWaitInMillis:{1} being less than load balancer response timeout:{2}, resetting it to load balancer response timeout.

Cause

TBD

Solution

TBD

----SGMT0224 Instance hang check - Listener: {1} of server :{0} is not responding to the for instance hang check request. The request timeout occurred for the timeout value of={2}.

Cause

TBD

Solution

TBD

----SGMT0225 Instance hang check - Listener: {1} of server: {0} has not responded to the ping request for instance hang check. However it still has scope to receive further http requests, as it has not max'd out on threads. No. of busy http threads={2}.

Cause

TBD

Solution

TBD

----SGMT0226 Instance hang check - Listener: {1} of server: {0} has not responded to instance hang check request. The listener has max'd out on threads. No. of busy http threads={2}.

Cause

TBD

Solution

TBD

----SGMT0227 Instance hang check - Listener: {1} of server: {0} is healthy for the instance hang check carried out.

Cause

TBD

Solution

TBD

----SGMT0228 Instance hang check - Server {0} is healthy.

Cause

TBD

Solution

TBD

----SGMT0229 Instance hang check - Server: {0} is not responding; is unhealthy.

Cause

TBD

Solution

TBD

----SGMT0230 Instance hang check - Invalid name : {0} specified in the check list of the rule. Ignoring this value.

Cause

TBD

Solution

TBD

----SGMT0231 Instance hang check - The threshold timeout= {1} specified for cluster: {0} is less than the load balancer health checker configured for it. Raising this timeout to its load balancer health checker value of {2}.

Cause

TBD

Solution

TBD

----SGMT0232 Instance hang check - The threshold timeout= {1} specified for server: {0} is less than the load balancer health checker configured for it. Raising this timeout to its load balancer health checker value of {2}.

Cause

TBD

Solution

TBD

----SGMT0233 Instance hang check - There are no instances specified in the check list to check for instance hang.

Cause

TBD

Solution

TBD

----SGMT0234 Started instance hang check for server: {0} in cluster: {1}

Cause

TBD

Solution

TBD

----SGMT0235 Started instance hang check for server: {0}

Cause

TBD

Solution

TBD

----SGMT0236 Instance hang check - Server: {0} in Cluster {1} is healthy.

Cause

TBD

Solution

TBD

----SGMT0237 Instance hang check - Server: {0} in Cluster {1} is unhealthy.

Cause

TBD

Solution

TBD

----SGMT0239 Instance hang check - Trying to restart non-responsive instance: {0}

Cause

TBD

Solution

TBD

----SGMT0240 Instance hang check - Trying to stop non-responsive instance: {0} in cluster: {1}

Cause

TBD

Solution

TBD

----SGMT0241 Instance hang check - Successfully stopped instance: {0}

Cause

TBD

Solution

TBD

----SGMT0242 Instance hang check - Successfully stopped instance: {0} in cluster: {1}

Cause

TBD

Solution

TBD

----SGMT0243 Instance hang check - Error in stopping non-responsive instance: {0}. Cannot restart this instance.

Cause

TBD

Solution

TBD

----SGMT0244 Instance hang check - Error in stopping non-responsive instance: {0} in cluster: {1}. Cannot restart this instance.

Cause

TBD

Solution

TBD

----SGMT0245 Instance hang check - Trying to restart instance: {0}

Cause

TBD

Solution

TBD

----SGMT0246 Instance hang check - Trying to restart instance: {0} in cluster: {1}

Cause

TBD

Solution

TBD

----SGMT0247 Instance hang check - Successfully restarted instance: {0}

Cause

TBD

Solution

TBD

----SGMT0248 Instance hang check - Successfully restarted instance: {0} in cluster: {1}

Cause

TBD

Solution

TBD

----SGMT0249 Instance hang check - Error in trying to restart non-responsive instance: {0}

Cause

TBD

Solution

TBD

----SGMT0259 Instance hang check - Error in trying to restart non-responsive instance: {0} in cluster: {1}

Cause

TBD

Solution

TBD

----SGMT0260 Instance hang check cycle completed.

Cause

TBD

Solution

TBD

----SGMT0261 This action can only be deployed on a DAS instance.

Cause

TBD

Solution

TBD

----SGMT0262 Could not obtain MBeanServerConnection.

Cause

TBD

Solution

TBD

----SGMT0301 Reconfig notification received for creation

Cause

TBD

Solution

TBD

----SGMT0302 Reconfig notification received for update

Cause

TBD

Solution

TBD

----SGMT0303 Reconfig notification received for deletion

Cause

TBD

Solution

TBD

----SGMT0304 Reconfig notification received for handling rules creation

Cause

TBD

Solution

TBD

----SGMT0305 Reconfig notification received for handling rules update

Cause

TBD

Solution

TBD

----SGMT0306 Reconfig addition for rule - {0}

Cause

TBD

Solution

TBD

----SGMT0307 Reconfig notification received for handling rules deletion

Cause

TBD

Solution

TBD

----SGMT0308 Reconfig deletion for - {0}

Cause

TBD

Solution

TBD

----SGMT0309 Reconfig update on - {0}

Cause

TBD

Solution

TBD

----SGMT0310 Reconfig - Disabling self management service. All enabled rules would be implicitly disabled.

Cause

TBD

Solution

TBD

----SGMT0311 Reconfig - Enabling self management service. All enabled rules would be activated.

Cause

TBD

Solution

TBD

----SGMT0313 Reconfig - Error encountered while deleting rule, name= {0}. Reason for error : {1}.

Cause

TBD

Solution

TBD

----SGMT0314 Reconfig - Successfully deleted management rule, Name= {0}, it's Description= {1}.

Cause

TBD

Solution

TBD

----SGMT0315 Reconfig - Updating management rule attribute={0}. Old value= {1}, new value= {2}

Cause

TBD

Solution

TBD

----SGMT0316 Error encountered while disabling rule, name= {0}. Reason is : {1}.

Cause

TBD

Solution

TBD

----SGMT0317 Error encountered while enabling management rules. Reason is :{0}.

Cause

TBD

Solution

TBD

----SGMT0318 Reconfig - Cannot activate rule, name= {0}, Description= {1} as the management rules is disabled. First enable the management rules to activate this rule.

Cause

TBD

Solution

TBD

----SGMT0319 Reconfig - Cannot disable rule, name= {0}, Description= {1} as it is already not active due to the management rules being disabled.

Cause

TBD

Solution

TBD