PQ62196: CLONE FAILOVER DOES FOR WAS 4.0 FP3 DOES NOT WORK ON SOLARIS | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description In a cloned Solaris environment: . When a clone is shut down: The Plugin detects that the clone is down but does not flag the clone internally as being unavailable. . Reloading the request from the current browser sessions does not failover to another clone. A new browser session will direct the request to another clone.Local fix No Local Fix or WorkAroundProblem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0.3 users * * of the iPlanet webserver plugin with * * multiple clones. * **************************************************************** * PROBLEM DESCRIPTION: An unexpected return code from connect * * was causing the plugin to think the * * connection had succeeded when in fact * * it had failed. This caused problems * * in the failover logic. * **************************************************************** * RECOMMENDATION: * **************************************************************** The plugin would think that a connect() had been successful when in fact it had failed. This would cause failover to not work as expected.Problem conclusion Modify the error checking on the connect to see when the connect fails and allow failover to work properly.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ62196
IBM Group: Software Group
Modified date: Jul 23, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.