|
Problem(Abstract) |
Every so often a need arises that dictates that a
particular cluster member should no longer be part of the Load Balancing /
Fail Over listing. |
|
|
|
Cause |
The cause for this situation could be related to a
back-end application server that is going down, or you might want to bring
an application server down for maintenance. Either situation requires that
requests should no longer be routed to it. |
|
|
Resolving the
problem |
The most effective way to handle this issue is to manually
remove the cluster member name from the primary server list. This takes it
out of the listing of available cluster members and the plug-in will no
longer see it as a viable option.
Before you manually change anything within the plugin-cfg.xml
file, it is recommended that you make a back up copy.
There are 2 ways that you can remove the cluster member form the Primary
Server listing:
- Delete the line in question.
- Comment out the cluster member line. To comment out an XML
line, you need to use the following syntax:
<!-- comment --> |
|
Based on the preceding syntax, your
listing would look like the following: |
|
<PrimaryServers>
<!--<Server Name="cluster_member_1"/>-->
<Server Name="cluster_member_2"/>
</PrimaryServers> |
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|