PQ58291: CLONES ARE NOT CHECKED QUICKLY ENOUGH AND WHEN FAILOVER OCCURS TO SWITCH TO AN ACTIVE CLONE. | |||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||
APAR status Closed as duplicate of another APAR. Error description When clone Aapp Servers exists and one is being taken down, there is a period from the time the app server start to go down (apparently via " stop" from gui or wscp) then there is a period of time when, instead of being routed to another clone, that the client receives an HTML 404 "Not Found" error rather than being rerouted to one of the App Server clones that is available. . This condition is transient and proper handling does occur shortly (don't know exactly how long). . Need to review the way app servers are being shut down and determine what change(s) need to be made to prevent the problem as described. See defect 111732 for more detail.Local fix Use "Force Stop" as a workaround to prevent any errors seen during the stoppage of a clone. Error is not thrown when this is used.Problem summary Problem conclusion Temporary fix Comments This is a duplicate of PQ56389.
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ58291
IBM Group: Software Group
Modified date: Mar 6, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.