PM45175: Program statements to get client hostname and port may be slow if the network is not performing entirely normally

Fixes are available

APAR status

Closed as program error.

Error description

After upgrading to WebSphere Application Server V6.1.0.35 (or a
later Fix Pack) or V7.0.0.13 (or a later Fix Pack), a delay of
about 16 seconds for incoming SOAP administration calls from
remote hosts might be seen under certain network conditions.
This delay is not seen when the SOAP call originates from the
local system.  The problem can affect both node agents and the
deployment manager.  The problem is due to an error with the fix
for APAR PM14986.

When the problem occurs, the remote host and port associated
with the current SOAP connection, which are only useful for
debugging purposes, are always retrieved, even when no debugging
is enabled.  This could cause slow performance when certain
network configurations combined with possible issues in the Java
SDK make these calls very slow.  The remote host and port should
only be retrieved when debugging is enabled.

To verify that your system is susceptible to this problem, run
the nslookup command on the SOAP client's IP address on the
system on which WebSphere Application Server is running.  If
there is a delay in this command completing, WebSphere
Application Server is susceptible to the problem addressed by
this APAR.  Contact your network administrator to determine why
there is a delay in the nslookup command completing.

Local fix

```
None at this time
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0                        *
****************************************************************
* PROBLEM DESCRIPTION: Program statements to get client        *
*                      hostname and port may be slow if        *
*                      the network is not functioning          *
*                      entirely normally                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Program statements to get client hostname and port may be slow
if the network is not functioning quite normally (for example,
a slow DNS). The root solution is to correct the networking
problems. However, the program statements in question are only
useful for debugging purpose. They need not be called when not
in debugging mode.

Problem conclusion

The code is restructured so that the statements in question
will only be called if debugging is enabled.

The same issue has been fixed in base v8.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.43 and 7.0.0.21.  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
PM45175
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-08-05
Closed date
2011-08-31
Last modified date
2012-02-28

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

PM60344

Fix information

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

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 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":"610","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM45175: Program statements to get client hostname and port may be slow if the network is not performing entirely normally

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?