
Configuring the Load Balancer
For optimal performance, use a pool with eight to 16 connections per node. For example, if you have four nodes configured, then the
For the best performance, use the following settings:
■Connection Validation: Required
■Validation Method: metadata
■Transaction Isolation Level:
In addition to the standard attributes, add the two following properties:
■cacheDatabaseMetaData: false
■eliminateRedundantEndTransaction: true
To add a property, click the Add Property button, then specify the property name and value, and click Save.
For more information on configuring the JDBC connection pool, see “Tuning JDBC
Connection Pools” on page 77.
Configuring the Load Balancer
The Enterprise Server provides a load balancer plugin that can balance the load of requests among multiple instances which are part of the cluster.
Note – The following section assumes that the server is tuned effectively to service incoming requests.
Enabling the Health Checker
The load balancer periodically checks all the configured Enterprise Server instances that are marked as unhealthy, based on the values specified in the
The load balancer’s health check mechanism communicates with the application server instance using HTTP. The health checker sends an HTTP request to the URL specified and waits for a response. The status code in the HTTP response header should be between 100 and 500 to consider the instance to be healthy.
To enable the health checker, edit the following properties:
■url: Specifies the listener’s URL that the load balancer checks to determine its state of health.
120 | Sun GlassFish Enterprise Server 2.1 Performance Tuning Guide • January 2009 |