IBM Support

PI74454: INFINITE LOOP RESTORING SESSION CONTEXT FROM FAILOVER

Fixes are available

8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The thread goes into an infinite loop when restoring session
context from failover.

The thread stack looks like this:

 at
com/ibm/ws/session/store/db/DatabaseHashMap.getConnection(Databa
seHashMap.java:1174(Compiled Code))
 at
com/ibm/ws/session/store/db/DatabaseHashMap.getValue(DatabaseHas
hMap.java:1417(Compiled Code))
 at
com/ibm/ws/session/store/db/DatabaseSession.getSingleRowAppData(
DatabaseSession.java:160(Compiled Code))
 at
com/ibm/ws/session/store/db/DatabaseSession.getSwappableListener
s(DatabaseSession.java:116(Compiled Code))
 at
com/ibm/ws/session/store/common/BackedHashMap.retrieveSession(Ba
ckedHashMap.java:382(Compiled Code))
    (entered lock:
com/ibm/ws/session/store/db/DatabaseSession@0x00000000ED8230E0,
entry count: 1)
 at
com/ibm/ws/session/store/common/BackedHashMap.getSession(BackedH
ashMap.java:243(Compiled Code))
 at
com/ibm/ws/session/store/common/BackedHashMap.getSession(BackedH
ashMap.java:109(Compiled Code))
 at
com/ibm/ws/session/store/common/BackedStore.getSession(BackedSto
re.java:71(Compiled Code))
 at
com/ibm/ws/session/store/memory/MemoryStore.getSession(MemorySto
re.java:717(Compiled Code))
 at
com/ibm/ws/session/SessionManager.getSessionFromStore(SessionMan
ager.java:497(Compiled Code))
 at
com/ibm/ws/session/SessionManager.getSession(SessionManager.java
:476(Compiled Code))
 at
com/ibm/ws/session/SessionManager.getSession(SessionManager.java
:462(Compiled Code))
 at
com/ibm/ws/session/SessionManager.getSession(SessionManager.java
:693(Compiled Code))
 at
com/ibm/ws/session/SessionContext.getIHttpSession(SessionContext
.java:473(Compiled Code))
 at
com/ibm/ws/session/SessionContext.getIHttpSession(SessionContext
.java:426(Compiled Code))
 at
com/ibm/ws/webcontainer/srt/SRTRequestContext.getSession(SRTRequ
estContext.java:113(Compiled Code))
 at
com/ibm/ws/webcontainer/srt/SRTServletRequest.getSession(SRTServ
letRequest.java:2168(Compiled Code))
 at
com/ibm/ws/webcontainer/srt/SRTServletRequest.getSession(SRTServ
letRequest.java:2152(Compiled Code))
 at
org/apache/webbeans/web/context/WebContextsService.lazyStartSess
ionContext(WebContextsService.java:1016(Compiled Code))
 at
org/apache/webbeans/web/context/WebContextsService.getSessionCon
text(WebContextsService.java:963(Compiled Code))
 at
org/apache/webbeans/web/context/WebContextsService.getCurrentCon
text(WebContextsService.java:306(Compiled Code))
 at
org/apache/webbeans/context/AbstractContextsService.activateCont
ext(AbstractContextsService.java:73(Compiled Code))
 at
org/apache/webbeans/web/failover/FailOverBag.restore(FailOverBag
.java:94(Compiled Code))
 at
org/apache/webbeans/web/failover/FailOverBagWrapper.restore(Fail
OverBagWrapper.java:104(Compiled Code))
 at
org/apache/webbeans/web/failover/DefaultOwbFailOverService.resto
reBeans(DefaultOwbFailOverService.java:223(Compiled Code))
 at
org/apache/webbeans/web/failover/FailOverBagWrapper.sessionDidAc
tivate(FailOverBagWrapper.java:142(Compiled Code))
 at
com/ibm/ws/session/http/HttpSessionObserver.sessionDidActivate(H
ttpSessionObserver.java:253(Compiled Code))
 at
com/ibm/ws/session/SessionEventDispatcher.sessionDidActivate(Ses
sionEventDispatcher.java:213(Compiled Code))
 at
com/ibm/ws/session/StoreCallback.sessionDidActivate(StoreCallbac
k.java:106(Compiled Code))
 at
com/ibm/ws/session/store/common/BackedHashMap.retrieveSession(Ba
ckedHashMap.java:385(Compiled Code))
    (entered lock:
com/ibm/ws/session/store/db/DatabaseSession@0x00000000ED8232E8,
entry count: 1)
 at
com/ibm/ws/session/store/common/BackedHashMap.getSession(BackedH
ashMap.java:243(Compiled Code))
 at
com/ibm/ws/session/store/common/BackedHashMap.getSession(BackedH
ashMap.java:109(Compiled Code))

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Restoring session contexts from         *
*                      failover could result in an infinite    *
*                      loop                                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When Contexts and Dependency Injection (CDI) restored session
contexts it also activated them. In doing so it triggered an
infinite loop.

    



Problem conclusion


    

  • CDI no longer activates session contexts as part of restoring
from failover.

The fix for this APAR is currently targeted for inclusion in
fix packs 8.5.5.12 and 8.0.0.13.  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
    PI74454
    • 

  • Reported component name
    WEBS APP SERV N
    • 

  • Reported component ID
    5724H8800
    • 

  • Reported release
    850
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2017-01-05
    • 

  • Closed date
    2017-02-02
    • 

  • Last modified date
    2017-02-02
    • 





    

  • 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


    

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

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            27 April 2022
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback