For more information on conguring the load balancer plug-in, see “Conguring the HTTP
Load Balancer” in Sun GlassFish Enterprise Server 2.1 High Availability Administration Guide
.
HADB timeouts
The sql_client time out value may aect performance.
Operating System Conguration
If the number of semaphores is too low, HADB can fail and display this error message:
No space left on device
This can occur either while starting the database, or during run time.
To correct this error, congure semaphore settings. Additionally, you may need to congure
shared memory settings. Also, adding nodes can aect the required settings for shared memory
and semaphores. For more information, see
“Conguring Shared Memory and Semaphores” in
Sun GlassFish Enterprise Server 2.1 High Availability Administration Guide
.
Tuning the Enterprise Server for High-Availability
This section discusses how you can congure the high availability features of Enterprise Server.
This section discusses the following topics:
■
“Tuning Session Persistence Frequency” on page 117
■
“Session Persistence Scope” on page 118
■
“Session Size” on page 118
■
“Checkpointing Stateful Session Beans” on page 119
■
“Conguring the JDBC Connection Pool” on page 119
■
Descriptor conguration in the web application
To ensure highly available web applications with persistent session data, the high availability
database (HADB) provides a backend store to save HTTP session data. However, there is a
overhead involved in saving and reading the data back from HADB. Understanding the
dierent schemes of session persistence and their impact on performance and availability will
help you make decisions in conguring Enterprise Server for high availability.
In general, maintain twice as many HADB nodes as there are application server instances. Every
application server instance requires two HADB nodes.
TuningtheEnterprise ServerforHigh-Availability
SunGlassFishEnterpriseServer2.1PerformanceTuningGuide • January2009116