IBM Support

PM79327: Thread deadlock in CriteriaBuilder.

Fixes are available

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The CriteriaBuilder blocks when multiple threads work on
constructing predicate expressions.

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V8.0.0 and V8.5.0 who make           *
*                  use of CriteriaBuilder.                     *
****************************************************************
* PROBLEM DESCRIPTION: CriteriaBuilder predicate               *
*                      construction deadlocks in multi-core    *
*                      VM due to a static initializer.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The CriteriaBuilder blocks when multiple threads work on
constructing predicate expressions.  The following
deadlocked/hung threads are flagged in system
logs implicating CriteriaBuilder code:
WTRN0124I: When the timeout occurred the thread with which the
transaction is, or was most recently, associated was
Thread[WebContainer : 2,5,
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:167)
java.lang.J9VMInternals.initialize(J9VMInternals.java:265)
org.apache.openjpa.persistence.criteria.
CriteriaBuilderImpl.conjunction(CriteriaBuilderImpl.java:186)
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:167)
java.lang.J9VMInternals.initialize(J9VMInternals.java:265)
java.lang.J9VMInternals.initialize(J9VMInternals.java:195)
java.lang.J9VMInternals.initialize(J9VMInternals.java:195)
org.apache.openjpa.persistence.criteria.
CriteriaBuilderImpl.lessThan(CriteriaBuilderImpl.java:367)
WTRN0124I: When the timeout occurred the thread with which the
transaction is, or was most recently, associated was
Thread[DefaultWorkManager.Alarm Pool :
0,5,DefaultWorkManager: WAS
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:167)
java.lang.J9VMInternals.initialize(J9VMInternals.java:265)
java.lang.J9VMInternals.initialize(J9VMInternals.java:195)
org.apache.openjpa.persistence.criteria.
PredicateImpl.<clinit>(PredicateImpl.java:49)
java.lang.J9VMInternals.initializeImpl(Native Method)
java.lang.J9VMInternals.initialize(J9VMInternals.java:228)
java.lang.J9VMInternals.initialize(J9VMInternals.java:195)
org.apache.openjpa.persistence.criteria.
CriteriaBuilderImpl.conjunction(CriteriaBuilderImpl.java:186)
This can occur when many threads are attempting to use
CriteriaBuilder at the same time.  The threads hang due to the
use of static initialization in the construction of classes
used by CriteriaBuilder.

    



Problem conclusion


    

  • With this fix, code has been added to OpenJPA to add proper
sychronization when constructing CriteriaBuilder predicates.

The fix for this APAR is currently targeted for
inclusion in Service Levels (Fix Packs) 8.0.0.6 and
8.5.0.2 of WebSphere Application Server versions 8.0.0 and
8.5.0.

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
    PM79327
    • 

  • Reported component name
    WEBSPHERE APP S
    • 

  • Reported component ID
    5724J0800
    • 

  • Reported release
    800
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2012-12-17
    • 

  • Closed date
    2013-01-24
    • 

  • Last modified date
    2013-01-24
    • 





    

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

    • 

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

    
PM80453
    

    • 



Fix information


    

  • Fixed component name
    WEBSPHERE APP S
    • 

  • Fixed component ID
    5724J0800
    • 



Applicable component levels


    

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

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            29 October 2021
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback