PI12707: An IllegalStateException exception is caused by multiple invalidation calls.

APAR status

• Closed as program error.

Error description

• When MaxInactiveInterval is set to 0 during an explicit
  invalidation call and the session.invalidate() method is called,
  the session is invalidated twice. See the following example
  exception:
  
  com.ibm.ws.webcontainer.servlet.ServletWrapper service
  SRVE0014E:
  Uncaught service() exception root cause action:
  javax.servlet.ServletException: java.lang.IllegalStateException
  Caused by: java.lang.IllegalStateException
  at
  com.ibm.ws.xs.sessionmanager.WXSSessionImpl.invalidate(WXSSessio
  nImpl.ja
  va:1113)
  

Local fix

• Only call session.invalidate()
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of WebSphere eXtreme Scale HTTP       *
  *                  session replication with the splicer        *
  *                  property, listenerMode, set to false in a   *
  *                  Servlet3.0 specification runtime            *
  *                  environment.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: If listenerMode=false in a Servlet3.0   *
  *                      runtime, and the application sets       *
  *                      maxInactiveInterval to 0, the session   *
  *                      times out.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The meaning of setting maxInactiveInterval to 0 has changed in
  the Servlet3.0 specification. Previously, it meant to time out
  the session immediately. In the Servlet3.0 specification, it
  means to never timeout. The WebSphere eXtreme Scale Client
  timed out the session immediately, regardless of the servlet
  specification level.
  

Problem conclusion

• The WebSphere eXtreme Scale Client HTTP session component has
  been updated to properly time out or never time out the session
  when maxInactiveInterval has been set to 0, depending on the
  servlet specification level of the runtime.
  

Temporary fix

Comments

APAR Information

• 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

  WS EXTREME SCAL

• Fixed component ID

  5724X6702

Applicable component levels

• R850 PSY

     UP

• R860 PSY

     UP