PM74718: EARLY START-UP OF SESSION INVALIDATION CAN CAUSE DEADLOCK WITH APPLICATION START-UP THREAD IN VERY RARE SITUATIONS

8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.14: WebSphere Application Server V8.5.5 Fix Pack 14

APAR status

• Closed as program error.

Error description

• If the following conditions are true,
  
  - application implements http session listeners
  - application listener code and application initialization code
  both passing to same synchronized resource and can get in
  deadlock.
  - application is running on clustered environment with
  distributed sessions turned on.
  
  
  In this very rare situation, application startup thread and
  session invalidation thread can get in deadlock situation.
  

Local fix

• Use scheduled invalidation
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Version    *
  *                  7, 8, and 8.5 users.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: The session invalidation alarm for an   *
  *                      application starts firing before an     *
  *                      application finishes starting.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During server startup, the invalidation alarm associated with
  each web module will start and begin to look for invalid
  sessions. For applications that process session information on
  startup, it may be desirable to delay the start of the
  invalidation alarm.
  

Problem conclusion

• A session manager custom property
  DelayInvalidationAlarmDuringServerStartup was introduced. Set
  this property to the desired numerical value (in seconds) to
  delay the start of the invalidation alarm on server startup.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.27, 8.0.0.6 and 8.5.0.2.  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 is sysrouted FROM one or more of the following:

  PM63475

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

Fix information

• Fixed component name

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP