IBM Support

PI14544: BLUEPRINT APPLICATION STARTUP DEADLOCKS WHEN USING A BEAN FOR A REFERENCE-LISTENERS AND THE BEAN USES THE REFERENCE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Blueprint application startup deadlocks when using
    reference-listeners that refer to a bean that uses the
    reference, and where another bundle uses the service for that
    bean.
    
    
    Java core dumps of the hang will show two or more threads with
    the name containing: "Blueprint Extender:", and the top of the
    stack similar to:
    
    at sun/misc/Unsafe.park(Native Method)
    at
    java/util/concurrent/locks/LockSupport.park(LockSupport.java:182
    )
    at
    java/util/concurrent/locks/AbstractQueuedSynchronizer.parkAnd
    CheckInterrupt(AbstractQueuedSynchronizer.java:822)
    at
    java/util/concurrent/locks/AbstractQueuedSynchronizer.doAcquireS
    haredInterruptibly(AbstractQueuedSynchronizer.java:980)
    at
    java/util/concurrent/locks/AbstractQueuedSynchronizer.acquireSha
    redInterruptibly(AbstractQueuedSynchronizer.java:1292)
    at
    java/util/concurrent/FutureTask$Sync.innerGet(FutureTask.java:22
    9)
    at java/util/concurrent/FutureTask.get(FutureTask.java:94)
    at
    org/apache/aries/blueprint/di/AbstractRecipe.create(AbstractReci
    pe.java: 93)
    

Local fix

  • Currently our workaround is to remove the reference-listener in
    the datasource-management reference.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using Blueprint                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: A deadlock can occur during blueprint   *
    *                      application start.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Blueprint applications can dead lock when starting if the
    application is configured such that a reference-listener
    references a bean that also uses the reference containing the
    reference, as well as another service that uses the same bean.
    During start, multiple threads are used to start the
    application, and a deadlock can occur as two threads are
    waiting for the blueprint startup to complete on the other
    thread.
    

Problem conclusion

  • The blueprint startup sequence has been altered so that
    services are not registered before they are ready for use.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.3.  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

    PI14544

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-26

  • Closed date

    2014-06-06

  • Last modified date

    2014-06-06

  • 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

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

Document Information

Modified date:
28 April 2022