PK77273: ADD ADDITIONAL DEBUG TRACE CODE TO THE OUTBOUNDCONNECTIONCACHE ALGORITHM

Fixes are available

APAR status

Closed as program error.

Error description

A build-up of threads waiting on a HashMap in the Web services
engine OutboundConnectionCache can occur if a thread requests a
connection and creating the connection will cause the number of
connections in the OutboundConnectionCache to exceed the maximum
connection's limit.  This is expected behavior in high load
situations, but unfortunately these same symptoms could
indicate a problem in the outbound connection pool.

Adding monitoring code to the OutboundConnectionCache will
diagnose these kinds of problems.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application               *
*                  Server users of JAX-WS or JAX-RPC           *
*                  web services with debug trace enabled       *
****************************************************************
* PROBLEM DESCRIPTION: Extra debug trace settings are          *
*                      needed to view the status of the        *
*                      outbound connection cache pool.         *
****************************************************************
* RECOMMENDATION:  Install a FixPack containing this APAR      *
****************************************************************
The web service runtime maintains a pool of outbound
connections.  The pool contains connections that are currently
in-use, connections that have recently been used, and
connections that are no longer in use.
If a web service application needs to establish a new
connection and the web service pool is full, the web service
application is forced to wait until a connection is
available from the pool.  This is the correct behavior and
allows the web service engine to execute in temporary high load
situations.  High load is defined as connections having to
wait due to a lack of space in the pool.
However, when these high load scenarios occur we currently do
not have sufficient debug trace to examine the status of the
connection pool or examine the wait times.  In addition,
customers who experience these high loads don't want to turn
on extensive debug trace because gathering trace may degrade
performance.
As a result, several customers have asked for a trace
setting that can be used to capture connection pool and wait
time information without significantly impacting performance.
This APAR introduces new JAX-RPC and JAX-WS settings that can
be used to gather connection pool information.
The new setting for JAX-RPC is:
com.ibm.ws.webservices.engine.transport.channel.Monitor=all=enab
led
The new setting for JAX-WS is:
com.ibm.ws.websvcs.transport.channel.Monitor=all=enabled

Problem conclusion

New classes,
com.ibm.ws.webservices.engine.transport.channel.Monitor and
com.ibm.ws.websvcs.engine.transport.channel.Monitor are added
to the web service runtime.  These Monitor classes are only
activated if debug trace is enabled and the outbound
connection pool is under high load.  The Monitor classes are
designed to capture and write information about the health of
the connection pool and the wait times.  The Monitor classes
are designed so that they have a minimal impact on
performance; thus they can be used in a customer's production
environment.

These new classes and trace settings will make it easier for
the IBM support teams to diagnose outbound connection cache
issues reported by customers.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.37, 6.1.0.27, and 7.0.0.5.  Please refer to
the Recommended Updatespage for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK77273
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
2008-12-10
Closed date
2009-04-20
Last modified date
2012-02-24

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

PK84036

Fix information

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

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK77273: ADD ADDITIONAL DEBUG TRACE CODE TO THE OUTBOUNDCONNECTIONCACHE ALGORITHM

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?