IBM Support

PH43383: WAS START FAILED BY DEADLOCK BETWEEN THE SERVER.STARTUP THREAD

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The deadlock occurs in the Equinox OSGi layer.
    It is shipped as part of the LongRunningScheduler.ear, which is
    a systemApp.
    
    Equinox bug for this deadlocking issue:
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=479396
    
    
    LongRunningScheduler.ear system application fixed for the
    aforementioned the deadlock bug.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  Java Batch                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: A deadlock can occur during startup of  *
    *                      the LongRunningScheduler system app:    *
    *                      3XMTHREADINFO      "server.startup : 0" *
    *                      J9VMThread:0x00000000321FE100,          *
    *                      omrthread_t:0x0000010025DE8968,         *
    *                      java/lang/Thread:0x000000028258D6C8,    *
    *                      state:B, prio=5                         *
    *                      3XMJAVALTHREAD                          *
    *                      (java/lang/Thread getId:0x9A,           *
    *                      isDaemon:true)                          *
    *                      3XMTHREADINFO1            (native       *
    *                      thread ID:0x649014F, native             *
    *                      priority:0x5, native policy:UNKNOWN,    *
    *                      vmstate:B, vm thread flags:0x00000281)  *
    *                      3XMCPUTIME               CPU usage      *
    *                      total: 2.767175000 secs, user:          *
    *                      2.176358000 secs, system: 0.590817000   *
    *                      secs, current category="Application"    *
    *                      3XMTHREADBLOCK     Blocked on:          *
    *                      org/osgi/util/tracker/ServiceTracker$Tr *
    *                      acked@0x0000000281397838 Owned by:      *
    *                      "server.startup : 1"                    *
    *                      (J9VMThread:0x0000000032200500,         *
    *                      java/lang/Thread:0x000000028258D770)    *
    *                      3XMHEAPALLOC             Heap bytes     *
    *                      allocated since last GC cycle=0 (0x0)   *
    *                      3XMTHREADINFO3           Java           *
    *                      callstack:                              *
    *                      4XESTACKTRACE                at         *
    *                      org/osgi/util/tracker/ServiceTracker.ge *
    *                      tServiceReferences(ServiceTracker.java: *
    *                      555)                                    *
    *                      4XESTACKTRACE                at         *
    *                      org/osgi/util/tracker/ServiceTracker.ge *
    *                      tServiceReference(ServiceTracker.java:5 *
    *                      98)                                     *
    *                      4XESTACKTRACE                at         *
    *                      org/osgi/util/tracker/ServiceTracker.ge *
    *                      tService(ServiceTracker.java:719)       *
    *                      ...                                     *
    *                      4XESTACKTRACE                at         *
    *                      org/eclipse/equinox/servletbridge/Frame *
    *                      workLauncher.start(FrameworkLauncher.ja *
    *                      va:387)                                 *
    *                      5XESTACKTRACE                           *
    *                      (entered lock:                          *
    *                      org/eclipse/equinox/servletbridge/Frame *
    *                      workLauncher@0x0000000283ACA018, entry  *
    *                      count: 1)                               *
    *                      4XESTACKTRACE                at         *
    *                      org/eclipse/equinox/servletbridge/Bridg *
    *                      eServlet.init(BridgeServlet.java:65)    *
    *                      4XESTACKTRACE                at         *
    *                      javax/servlet/GenericServlet.init(Gener *
    *                      icServlet.java:244)                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The deadlock occurs in the Equinox OSGi layer. The
    LongRunningScheduler.ear system app makes use of
    org.eclipse.equinox.servletbridge and there is an Equinox bug
    for this deadlocking issue:
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=479396
    If the org.eclipse.equinox.servletbridge prereq level that is
    packaged with WebSphere can be updated, this fix can be
    incorporated.
    

Problem conclusion

  • The Eclipse servlet bridge prereq level used for this system app
    was updated to a level which contains the deadlock fix mentioned
    in the Problem Summary.
    
    The fix for this APAR is targeted for inclusion in fix pack
    9.0.5.12 and 8.5.5.22. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH43383

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-01-16

  • Closed date

    2022-03-29

  • Last modified date

    2022-03-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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0"}]

Document Information

Modified date:
30 March 2022