IBM Support

PI37874: A WEB SERVICE THREAD HOLDING A SYNCHRONIZATION LOCK MAY HANG DUR ING APPLICATION DEPLOYMENT

Fixes are available

8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During web service application deployment some threads might
    hang because the web service cache file is inconsistent
    unexpectedly. The Java callstack of the hanging thread might
    be as follows:
    3XMTHREADINFO3           Java callstack:
    4XESTACKTRACE                at sun/misc/Unsafe.park(Native
    Method)
    4XESTACKTRACE                at
    java/util/concurrent/locks/LockSupport.park(LockSupport.java:182
    (Compiled Code))
    4XESTACKTRACE                at
    java/util/concurrent/locks/AbstractQueuedSynchronizer.parkAndChe
    ckInterrupt(AbstractQueuedSynchronizer.java:822(Compiled Code))
    4XESTACKTRACE                at
    java/util/concurrent/locks/AbstractQueuedSynchronizer.acquireQue
    ued(AbstractQueuedSynchronizer.java:853(Compiled Code))
    4XESTACKTRACE                at
    java/util/concurrent/locks/AbstractQueuedSynchronizer.acquire(Ab
    stractQueuedSynchronizer.java:1189(Compiled Code))
    4XESTACKTRACE                at
    java/util/concurrent/locks/ReentrantReadWriteLock$WriteLock.lock
    (ReentrantReadWriteLock.java:907(Compiled Code))
    4XESTACKTRACE                at
    com/ibm/ws/webservices/shared/cache/WebServicesModuleCacheImpl.s
    ave(WebServicesModuleCacheImpl.java:420)
    4XESTACKTRACE                at
    com/ibm/ws/websvcs/deploy/WSCacheWriter.writeModuleCache(WSCache
    Writer.java:592)
    5XESTACKTRACE                   (entered
    lock:java/lang/String@0x00000007044A2138, entry count: 1)
    4XESTACKTRACE                at
    com/ibm/ws/websvcs/deploy/WSCacheWriter.writeApplicationCache(WS
    CacheWriter.java:242(Compiled Code))
    4XESTACKTRACE                at
    com/ibm/ws/websvcs/deploy/WSCacheWriter.writeApplicationCache(WS
    CacheWriter.java:167)
    4XESTACKTRACE                at
    com/ibm/ws/websvcs/deploy/PersistentStorageInstallSaveTask.perfo
    rmTask(PersistentStorageInstallSaveTask.java:196)
    4XESTACKTRACE                at
    com/ibm/ws/management/application/sync/AppBinaryProcessor$Expand
    App.expand(AppBinaryProcessor.java:1709(Compiled Code))
    4XESTACKTRACE                at
    com/ibm/ws/management/application/sync/AppBinaryProcessor$AppBin
    Thread.run(AppBinaryProcessor.java:1214(Compiled Code))
    4XESTACKTRACE                at
    java/lang/Thread.run(Thread.java:784(Compiled Code))
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  JAX-WS web service applications             *
    ****************************************************************
    * PROBLEM DESCRIPTION: There might be a few threads hanging    *
    *                      after deploying some JAX-WS web         *
    *                      service applications.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There is a web service cache file storing the information of
    all installed web service applications. When mutiple threads
    operate on the same web service cache file, the
    synchronization mechanism might lead to cache file
    inconsistency, which finally results in the threads hanging.
    

Problem conclusion

  • The synchronization mechanism is changed so as to be
    recoverable even if the cache file is unexpectedly
    inconsistent.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.39, 8.0.0.11 and 8.5.5.6.  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

    PI37874

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-27

  • Closed date

    2015-05-12

  • Last modified date

    2015-05-12

  • 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

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022