Technical data

13 Installing and Configuring the Netscape Enterprise Server Plug-In (NSAPI)
13-12 Administration Guide
Connection Errors and Clustering
Failover
When the Netscape Enterprise Server Plug-In attempts to connect to WebLogic Server,
the plug-in uses several configuration parameters to determine how long to wait for
connections to the WebLogic Server host and, after a connection is established, how
long the plug-in waits for a response. If the plug-in cannot connect or does not receive
a response, the plug-in will attempt to connect and send the request to other WebLogic
Servers in the cluster. If the connection fails or there is no response from any
WebLogic Server in the cluster, an error message is sent.
Figure 13-1 “Connection Failover” on page 13-14 demonstrates how the plug-in
handles failover.
Connection Failures
Failure of the host to respond to a connection request could indicate possible problems
with the host machine, networking problems, or other server failures.
Failure of WebLogic Server to respond, could indicate that WebLogic Server is not
running or is unavailable, a hung server, a database problem, or other application
failure.
Failover with a Single, Non-Clustered WebLogic
Server
If you are running only a single WebLogic Server the same logic described here
applies, except that the plug-in only attempts to connect to the server defined with the
WebLogicHost parameter. If the attempt fails, an HTTP 503 error message is returned.
The plug-in continues trying to connect to WebLogic Server until
ConnectTimeoutSecs is exceeded.