PK73705: MAKE SOAP CONNECTOR USE KEEPALIVE/HTTP1.1 SO THAT IT CAN REUSE PORTS DURING ADMIN CLIENT CALLS.

Fixes are available

APAR status

Closed as program error.

Error description

SOAP connector uses a new socket to talk to the server for each
call made via admin client as it uses http 1.0 and does not use
keepAlive.  As a result you can see lots of sockets in
TIME_WAIT state and eventually the system may run out of open
sockets.  To fix this, SOAP connector needs to use http1.1 with
keepAlive so that ports can be reused. This feature is not
turned on by default. You have to pass an additional property
during AdminClient creation.  The property is
"com.ibm.ws.management.connector.soap.keepAlive" and the value
is  "true" (string not boolean).

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
****************************************************************
* PROBLEM DESCRIPTION: SOAP Connector uses too many ports      *
*                      in TIME_WAIT state when called from     *
*                      Rational Application Developer          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Rational Application Developer uses Application Server SOAP
connector to make administrative connections to the application
server.  A large number of administrative calls made from
Rational Application Developer to Application Server in a short
time leaves a lot of ports in TIME_WAIT state on the Rational
Application Developer machine. This happens due to SOAP
connector used by Rational Application Developer opening a new
socket for each SOAP call and the underlying operating system
not closing the socket completly after SOAP Connector
(actually java) closing the socket.   This APAR is to ensure
that SOAP connector used by RAD keeps the socket alive between
successive Application Server calls and hence does not leave
ports in TIME_WAIT state on Rational Application Developer
machine.  Without this fix the client machine running Rational
Application Developer may run out of ports.

Problem conclusion

The problem was fixed by making SOAP connector used by
Rational Application Developer reuse existing socket
connections for successive WebSphere Application Server
calls.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.1.  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
PK73705
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
2008-10-13
Closed date
2008-11-18
Last modified date
2008-11-18

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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:
23 October 2021

Tips

PK73705: MAKE SOAP CONNECTOR USE KEEPALIVE/HTTP1.1 SO THAT IT CAN REUSE PORTS DURING ADMIN CLIENT CALLS.

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

Document Information

Share your feedback

Need support?