IBM Support

PM74725: MONITOR COMPONENT INITIALIZATIONS, REPORT "HUNG THREADS"

Fixes are available

7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
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.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

  • Component initializations normally run under our standard
    thread pool, which monitors threaded actions and issues
    "may be hung" diagnostic warnings if those take an
    exceptionally long time.
    
    However, when a component was started synchronously, we were
    invoking the initialization in-line. Since there was no
    thread, we were unable to monitor it. As a result, a slow/hung
    component initialization could silently hang WebSphere
    Application Server startup.
    
    The new code runs the component init in a monitored thread (so
    we get "may be hung" warnings telling us what's going on), but
    waits for its completion, thus emulating the synchronous-start
    behavior.
    
    In WebSphere Application Server V7.0 through V8.5, we continue
    to default to the inline invocation (no behavior change). To
    enable the new diagnostics, set the property
    -Dcom.ibm.websphere.WsComponentImpl.synch_init_monitored=true
    
    In later versions, we will default to running with the new
    diagnostics turned on. To disable them and switch back to the
    old inline invocation, set
    -Dcom.ibm.websphere.WsComponentImpl..synch_init_monitored=false
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Slow or hung synchronous component      *
    *                      initialization could silently hang      *
    *                      WebSphere Application Server startup.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Slow or hung component initialization could silently hang
    WebSphere Application Server startup.
    

Problem conclusion

  • Component initializations normally run under our standard
    thread pool, which monitors threaded actions and issues
    "may be hung" diagnostic warnings if those take an
    exceptionally long time.
    
    However, when a component was started synchronously, we were
    invoking the initialization in-line. Since there was no
    thread, we were unable to monitor it. As a result, a slow or
    hung component initialization could silently hang WebSphere
    Application Server startup.
    
    The new code runs the component init in a monitored thread (so
    we get "may be hung" warnings telling us what's going on), but
    waits for its completion, thus emulating the synchronous-start
    behavior.
    
    In WebSphere Application Server V7.0 through V8.5, we continue
    to default to the inline invocation (no behavior change). To
    enable the new diagnostics, set the property
    -Dcom.ibm.websphere.WsComponentImpl.synch_init_monitored=true
    
    In later versions, we expect to default to running with the new
    diagnostics turned on. To disable them and switch back to the
    old inline invocation, set
    -Dcom.ibm.websphere.WsComponentImpl.synch_init_monitored=false
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.0.2, 8.0.0.6, and 7.0.0.29.  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

    PM74725

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-10

  • Closed date

    2013-02-14

  • Last modified date

    2013-02-14

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM74725

Modified date: 14 February 2013