|
Problem(Abstract) |
There are items to consider when using the server up or
server down scripts. |
|
|
|
Resolving the
problem |
- If you define the manager cycle to be less than 25% of the advisor
time, you get false reports of servers up and down. By default, the
manager runs every two seconds, but the advisor runs every seven seconds.
Therefore, the manager expects new advisor information within four cycles.
Removing this restriction significantly decreases performance because
multiple advisors can advise on a single server.
- When a server goes down, the server down script executes. However, if
you issue a server up command, it is assumed that the server is up until
the manager obtains new information from the advisor cycle. If the server
is still down, the server down script executes again.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
WebSphere Edge Server |
Load Balancer |
Multi-Platform |
Edge Server 2.0 GA, Edge Server 2.0 NLV, Edge Server 2.0.x |
|
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|