IBM Support

PM60919: DEPLOYMENT MANAGER PROCESS RUNS INTO HIGH CPU INTERMITTENTLY

Fixes are available

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.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.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

  • Intermittently the deployment manager process runs into high
    CPU utilization
    .
    Hang / performance MustGather docs revealed that the threads are
    hung at :
    .
    [2/3/12 22:18:10:389 PST] 00000029 ThreadMonitor W   WSVR0605W:
    Thread "SoapConnectorThreadPool : 527" (00009da4) has been
    active for 706299 milliseconds and may be hung.  There is/are
    1 thread(s) in total in the server that may be hung.
    at java.io.UnixFileSystem.getBooleanAttributes0(Native Method)
    at
    java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:
    258) at java.io.File.isDirectory(File.java:753)
    at
    com.ibm.ws.management.repository.FileRepository.eliminateEmptyFo
    lders(Fi leRepository.java:1846)
    at
    com.ibm.ws.management.repository.FileRepository.eliminateEmptyFo
    lders(Fi leRepository.java:1847)
    at
    com.ibm.ws.management.repository.FileRepository.eliminateEmptyFo
    lders(Fi leRepository.java:1847)
    

Local fix

  • Re-start deployment manager.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All WebSphere Application Server V6.1 and   *
    *                  V7.0 Network Deployment edition customers.  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Deployment Manager process runs into    *
    *                      high cpu intermittenly during           *
    *                      application deployment.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Deployment Manager process runs into high cpu intermittenly
    during application deployment.
    [2/3/12 22:18:10:389 PST] 00000029 ThreadMonitor W WSVR0605W:
    Thread "SoapConnectorThreadPool : 527" (00009da4) has been
    active for 706299 milliseconds and may be hung. There is/are 1
    thread(s) in total in the server that may be hung.
    at java.io.UnixFileSystem.getBooleanAttributes0(Native Method)
    at
    java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:
    258) at java.io.File.isDirectory(File.java:753)
    at
    com.ibm.ws.management.repository.FileRepository.eliminateEmptyFo
    lders(FileRepository.java:1846)
    at
    com.ibm.ws.management.repository.FileRepository.eliminateEmptyFo
    lders(FileRepository.java:1847)
    at
    com.ibm.ws.management.repository.FileRepository.eliminateEmptyFo
    lders(FileRepository.java:1847)
    

Problem conclusion

  • A performance fix that was included in V8.0 is backported to
    address this problem.
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.45 and 7.0.0.25. 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

    PM60919

  • 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

    2012-03-21

  • Closed date

    2012-03-30

  • Last modified date

    2012-10-08

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

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

    PM74557

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM60919

Modified date: 08 October 2012