Monitoring the GlassFish Loadbalancer Plug-In

• Configuring Log Messages

• Types of Log Messages

• Enabling HTTP Load Balancer Logging

• Understanding Monitoring Messages

• Configuring Log Messages

• Types of Log Messages

• Enabling HTTP Load Balancer Logging

• Understanding Monitoring Messages

Configuring Log Messages

The Loadbalancer Plug-In uses the web server’s logging mechanism to write log messages. The default log level is set to the default logging level on Sun Java System Web Server (INFO), Apache Web Server (WARN) and Microsoft IIS (INFO). The log levels, FINE, FINER, and FINEST, map to the DEBUG level on the web server.

These log messages are written to the web server log files, and are in the form of raw data that can be parsed using scripts, or imported into spreadsheets to calculate required metrics.

Types of Log Messages

The Loadbalancer Plug-In generates the following types of log messages:

• Load Balancer Configurator Log Messages

• Request Dispatch and Runtime Log Messages

• Configurator Error Messages

Load Balancer Configurator Log Messages

These messages will be logged when you are using idempotent URLs and error page settings.

An output for idempotent URL pattern configuration contains the following information:

• When the log level is set to FINE:

  CONFxxxx: IdempotentUrlPattern configured <url-pattern> <no-of-retries> for web-module : <web-module>

• When the log level is set to SEVERE:

  CONFxxxx: Duplicate entry of Idempotent URL element <url-pattern> for webModule <web-module> in loadbalancer.xml."

• When the log level is set to WARN:

  CONFxxxx: Invalid IdempotentUrlPatternData <url-pattern> for web-module <web-module>

  An output for error page URL configuration contains the following information (log level set to WARN):

  CONFxxxx: Invalid error-url for web-module <web-module>

Request Dispatch and Runtime Log Messages

These log messages are generated while a request is being load balanced and dispatched.

• An output for standard logging for each method start contains the following information (log level set to FINE):

  ROUTxxxx: Executing Router method <method_name>

• An output for router logs for each method start contains the following information (log level set to INFO):

  ROUTxxxx: Successfully Selected another ServerInstance for idempotent request <Request-URL>

• An output for runtime logs contains the following information (log level set to INFO):

  RNTMxxxx: Retrying Idempotent <GET/POST/HEAD> Request <Request-URL>

Configurator Error Messages

These errors appear if there are configuration problems, for example, if the custom error page referenced is missing.

• Log level set to INFO:

  ROUTxxxx: Non Idempotent Request Request-URL cannot be retried

  For example:

  ROUTxxxx: Non Idempotent Request http://oracle.com/addToDB?x=11&abc=2 \
  cannot be retried

• Log level set to FINE:

  RNTMxxxx: Invalid / Missing Custom error-url / page: error-url for web-module: web-module

  For example:

  RNTMxxxx: Invalid / Missing Custom error-url / page: myerror1xyz \
  for web-module: test

Enabling HTTP Load Balancer Logging

The Loadbalancer Plug-In logs the following information:

• Request start/stop information for every request.

• Failed-over request information when the request fails over from an unhealthy instance to a healthy instance.

• List of unhealthy instances at the end of every health check cycle.

To Turn on HTTP Load Balancer Logging

1. Set the logging options in the web server. The procedure depends on the web server:
   • With Oracle iPlanet Web Server

     In the server’s Admin console, go to the Magnus Editor tab and set the Log Verbose option to On.

   • For Apache Web Server, set the log level to DEBUG.
   • For Microsoft IIS, set the log level to FINE in the sun-passthrough.properties file.
2. Set the load balancer configuration’s monitor option to true.

   Use the asadmin create-http-lb-config subcommand to set monitoring to true when you initially create the load balancer configuration, or use the asadmin set command to set it to true later. Monitoring is disabled by default.

Understanding Monitoring Messages

The format of the Loadbalancer Plug-In log messages is as follows.

• The start of an HTTP request contains the following information:

  RequestStart Sticky(New) <req-id> <time-stamp> <URL>

  The timestamp value is the number of milliseconds from January 1, 1970. For example:

  RequestStart New 123456 602983 \
  http://austen.oracle.com/Webapps-simple/servlet/Example1

• The end of an HTTP request contains the RequestExit message, as follows:

  RequestExit Sticky(New) req-id time-stamp URL listener-id response-time Failure-reason for error(incase of a failure)

  For example:

  RequestExit New 123456 603001 \
  http://austen.oracle.com/Webapps-simple/servlet/Example1 http://austen:2222 18

  ---

  Note - In the RequestExit message, response-time indicates the total request turnaround time in milliseconds, from the perspective of the Loadbalancer Plug-In.

  ---

• The list of unhealthy instances, as follows:

  UnhealthyInstances cluster-id time-stamp listener-id, listener-id...

  For example:

  UnhealthyInstances cluster1 701923 http://austen:2210, http://austen:3010

• A list of failed-over requests, as follows:

  FailedoverRequest req-id time-stamp URL session-id failed-over-listener-id unhealthy-listener-id

  For example:

  FailedoverRequest 239496 705623 http://austen.oracle.com/Apps/servlet/SessionTest \
  16dfdac3c7e80a40 http://austen:4044 http://austen:4045