PM76903: WLM OUTBOUND PROXY CONNECTION USES WRONG IP ADDRESS

Fixes are available

APAR status

Closed as program error.

Error description

There exists code in the WebSphere Proxy server that is invoked
when a failed request happens to try and determine the health
of the target the request was sent to.  This is accomplished by
sending a simple HEAD / request to the same target host/port as
the request.  However, the health monitor code uses the default
outbound IP address for the machine, which means if the machine
is configured with a different outbound IP address than the
default for that physical machine, the customized IP address
will not be used when the HealthMonitor attempts to connect to
the remote target.

This APAR addresses the issue by putting the Health Monitor
code in line with the rest of the Proxy routing code to make
use of the configured IP address versus the default IP address
for the outbound local connection.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: The Workload Management(WLM) health     *
*                      monitor in the proxy uses the           *
*                      machine's default outbound IP address   *
*                      rather than the outbound IP address     *
*                      configured in the proxy.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In the WebSphere Proxy server, after a failed request the
proxy server tries to determine the health of the target of
the request.  This is accomplished by sending a HEAD request
to the same target host/port as the request.  However the WLM
health monitor code in the proxy uses the default outbound IP
address for the machine rather than the outbound IP address
configured in the proxy server.  So if the proxy server is
configured with a different outbound IP address than the
default for that physical machine, the proxy server's
configured outbound IP address will not be used by the WLM
health monitor.

Problem conclusion

This APAR addresses the issue by putting the Health Monitor
code in line with the rest of the Proxy routing code to make
use of the configured IP address versus the default IP address
for the outbound connection.

APAR PM76903 is currently targeted for inclusion in Fix Packs
7.0.0.28, 8.0.0.8, and 8.5.5.2 of WebSphere Application
Server. Please refer to the Recommended Updates page for
delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM76903
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-12
Closed date
2013-07-25
Last modified date
2014-03-20

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

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PM76903: WLM OUTBOUND PROXY CONNECTION USES WRONG IP ADDRESS

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?