IBM Support

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

Fixes are available

9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10

Subscribe

You can track all active APARs for this component.

 

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

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:
06 December 2021