PI88017: JMS CONNECTIONS FROM WEBSPHERE APPLICATION SERVER (WAS) ARE NOT DESTROYED AFTER UPGRADING WAS TO FIX PACK V8.5.5.12

Fixes are available

APAR status

Closed as program error.

Error description

After applying WAS Fix Pack v8.5.5.12, JMS connections from WAS
to not destroyed.  This is causing JMS connections to build
up, leading to the connection pool running with more connection

This issue can be observed in the Tivoli Performance Viewer.
The CloseCount value will remain at zero.  The CloseCount is
the number of connection which have been destroyed.

This problem does not occur on WAS Fix Pack v8.5.5.11

To work around the build-up of connections, WebSphere
Application Server MBean, purgePoolContents, may be called via
the wsadmin console to purge the connection pool.
See Technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21220832

Local fix

```
Use WAS Fix Pack v8.5.5.11
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server traditional                          *
****************************************************************
* PROBLEM DESCRIPTION: After applying WebSphere Application    *
*                      Server traditional                      *
*                      Fix                                     *
*                      Pack                                    *
*                      v8.5.5.12                               *
*                      JMS connections from WAS are            *
*                      not destroyed.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
JMS connections are not destroyed after upgrading to WebSphere
Application
Server traditional Fix
Pack v8.5.5.12. This can lead to unnecessary connections in
the connection pool.

Problem conclusion

JMS connections are now correctly being destroyed at the
appropriate time.

The fix for this APAR is currently targeted for inclusion in
fix pack 9.0.0.6 and 8.5.5.13.  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
PI88017
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-09-27
Closed date
2017-10-25
Last modified date
2017-12-19

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

R850 PSY
UP
R900 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":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI88017: JMS CONNECTIONS FROM WEBSPHERE APPLICATION SERVER (WAS) ARE NOT DESTROYED AFTER UPGRADING WAS TO FIX PACK V8.5.5.12

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

R850 PSY

R900 PSY

Document Information

Share your feedback

Need support?