PQ61926: AFTER PQ60039, REMOTE OSE PLUGIN FAILOVER DOES NOT TAKEN

Fixes are available
PQ71589: Incorrect response code is logged in IIS access log
PQ67072; 3.5.4: Invalid error number reported in plug-in traces
PQ67072; 3.5.4: Invalid error number reported in plug-in traces
PQ60039: Connect timeout enablement for OSE remote with WebSphere 3.5.x
PQ61926, 3.5.x: Connect timeout enablement for OSE remote
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)
PQ60991, 3.5.4, 3.5.6: Connection handshake enablement for OSE remote
PQ57425: Timeout enablement on the Apache/IHS webserver with plug-ins.
PQ76785: Cumulative plug-in fix for WebSphere Application Server V 3.5.4-3.5.7

APAR

APAR status
Closed as program error.

Error description
After applying PQ60039. remote ose plugin failover will fail if
node is up and running but WebSphere Application server clone
have not yet started. ( WAS clone has not LISTEN plugin port )
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users on    *
*                 AIX who use the ose.connect.timeout          *
*                 directive.                                   *
****************************************************************
* PROBLEM DESCRIPTION: Failover was not on occuring on AIX     *
*                      when the all of the following           *
*                      conditions were met:                    *
*                       - ose.connect.timeout directive was    *
*                         set in the bootstrap.properties      *
*                         file                                 *
*                       - ose remote configuration             *
*                       - remote appserver was not started     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
On AIX when using nonblocking connect, the return codes that
were being checked gave the appearance that the connection
was successful when in fact the connect had failed.  OSE
needed to add an additional error checking for nonblocking
connects.
Problem conclusion
Added additional error checks for the nonblocking connect
feature.
Temporary fix
pq61926_355_AIX.tar
Comments
APAR information
APAR numberPQ61926
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-06-07
Closed date2002-06-27
Last modified date2002-08-29

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
PLUGIN
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ61926
IBM Group: Software Group
Modified date: 2002-08-29