PM20594: JAX-RPC CLIENTS MAY SLOW DOWN DUE TO OUTBOUND ONE-WAY CONNECTIONS NOT BEING RESET CORRECTLY

Fixes are available

APAR status

Closed as program error.

Error description

Outbound one-way connections are not reset correctly in a
busy environment and such connections could fill up the
connection pool. You may notice the client application slowing
down.

Informational messages from the trace could show below:

[8/12/10 15:50:55:353 CEST] 00000117 OutboundConne 1   Exit:
findGroupAndReturnConnection() - WSWS3595I: Current pool size:
30. Connections-in-use size: 18. Configured pool size: 100

[8/12/10 16:02:02:426 CEST] 0000020c OutboundConne 1   Enter:
WSWS3595I: Current pool size: 18. Connections-in-use size: 18.
Configured pool size: 100

In this case, there was a 5 minutes window that there was no
HTTP activity.  The current pool size was not reduced to 0.

Local fix

No work around noted, candicate to be fixed in next release.

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V6.1 and   *
*                  V7.0 users of JAX-RPC Web services          *
*                  clients.                                    *
****************************************************************
* PROBLEM DESCRIPTION: Outbound one-way connections are not    *
*                      reset correctly in a busy environment.  *
****************************************************************
* RECOMMENDATION:  Install a fix pack containing this APAR.    *
****************************************************************
Outbound one-way connections are not reset correctly in a
busy environment and such connections could fill up the
connection pool. The user may notice the client application
slowing down.

For example, following message shows the connection pool status:

[8/12/10 15:50:55:353 CEST] 00000117 OutboundConne 1   Exit:
findGroupAndReturnConnection() - WSWS3595I: Current pool size:
30. Connections-in-use size: 18. Configured pool size: 100

After 5 minutes without any HTTP and network activity, the
connections should be reset and the current pool size should
be reduced to 0.  However, following messages showed there are
18 connections are still being used.

[8/12/10 16:02:02:426 CEST] 0000020c OutboundConne 1   Enter:
WSWS3595I: Current pool size: 18. Connections-in-use size: 18.
Configured pool size: 100

Problem conclusion

There is a synchronization problem in JAX-RPC connection
management code that causes some one-way connections to not get
reset correctly in a busy environment.  The Web services
runtime code has been changed to fix this problem.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.35 and 7.0.0.15.  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
PM20594
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-08-16
Closed date
2010-09-15
Last modified date
2010-09-15

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

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM20594: JAX-RPC CLIENTS MAY SLOW DOWN DUE TO OUTBOUND ONE-WAY CONNECTIONS NOT BEING RESET CORRECTLY

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?