IBM Support

PM22584: WEBSPHERE SERVICE INTEGRATION BUS: WSVR0605W WARNINGS WRITTEN TO JVM LOG WHEN ATTEMPTS ARE MADE TO ACCESS MESSAGE STORE.

Fixes are available

7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In the SystemOut file there are a log of messages WSVR0605W
    reporting threads in hang:
    
    [9/8/10 14:24:58:507 BRT] 0000000d ThreadMonitor W   WSVR0605W:
    Thread "Default : 11613" (00003c73) has been active for 628933
    milliseconds and may be hung.  There is/are 1 thread(s) in total
    in the server that may
    be hung.
    
    Prior to the above exception the SystemOut file reports many
    transaction timeouts preceded by a FFDC file as follows:
    [9/8/10 14:14:28:900 BRT] 00003c5e ServiceLogger I
    com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream
    FFDC0010I: FFDC closed incident stream file
    <FILENAME>
    [9/8/10 14:17:22:052 BRT] 0000000f TimeoutManage I   WTRN0006W:
    Transaction <TXNID> has timed out after 120 seconds.
    
    The said FFDC file reports a NullPointerexception exception as
    follows:
    
    Exception = java.lang.NullPointerException
    Source =
    com.ibm.ws.sib.msgstore.transactions.XidParticipant.commit
    probeid = 1:638:1.57.1.12
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server Version    *
    *                  6.1 or Version 7.0, using a file store      *
    ****************************************************************
    * PROBLEM DESCRIPTION: NullPointerException logged in          *
    *                      FFDC with probeid 1:638:1.57.1.12,      *
    *                      followed by a hang                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The occurrence of this issue is very timing sensitive.
    There is code within the file store that restores messages
    swapped out of memory from the store, and when called
    concurrently on multiple threads, on a busy system, it is
    possible for one of the threads to be returned a null
    reference to the restored object.
    The null reference results in a NullPointerException while
    attempting to commit a transaction, which in turn leads to a
    thread failing to release its lock, and other threads
    deadlocking as a result.
    

Problem conclusion

  • The fix for this APAR corrects the code that restores messages
    from the file store, to prevent it from allowing a null
    reference to be returned in the problem scenario.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack7.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

    PM22584

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620600101

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-09-15

  • Closed date

    2010-10-29

  • Last modified date

    2010-10-29

  • 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

    PLAT MSG COM

  • Fixed component ID

    620600101

Applicable component levels

  • R200 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