Sun Java System Application Server Enterprise Edition 8.1 2005Q2 High Availability Administration Guide

- Previous: Enabling Load Balancer Logging
- Next: Chapter 5 Using Application Server Clusters

## Understanding Monitoring Messages

The format of the load balancer 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.sun.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.sun.com/Webapps-simple/servlet/Example1 http://austen:2222 18`

  Note –

  In the RequestExit message, <response-time> indicates the total request turn-around time in milliseconds, from the perspective of the load balancer 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.sun.com/Apps/servlet/SessionTest 16dfdac3c7e80a40 http://austen:4044 http://austen:4045`

- Previous: Enabling Load Balancer Logging
- Next: Chapter 5 Using Application Server Clusters

- © 2010, Oracle Corporation and/or its affiliates