PM01631: A NEW SESSION CAN GET INVALIDATED

APAR status

• Closed as program error.

Error description

• A new session can get invalidated when added to an existing
  SipApplicationSession by an encoded URI while the latter is
  invalidating.
  
  The issue is revolving the new "invalidate when ready" feature
  (See JSR 289 6.1.2.2.2).
  The container is getting the first request and a session and
  application session are created. When the transaction ends,
  the ApplicationSession gets to the readyToinvalidate state
  (according to the conditions specified in the JSR) and starts
  invalidating. This happens on one of the container threads.
  In the meantime on the stack thread, there is a new incoming
  initial request , that creates a new session, and has this
  ApplicationSession id encoded in its URI. The container then
  relates this new session to the applicationSession.
  The container thread that is in the process of invalidating
  the ApplicationSession and all its sessions, also invaildates
  this new session.
  When its time to process that new request, the container sees
  the session is invalid and returns 481.
  
  This race needs to be fixed in the container. It can also
  happen when SAS was invalidated explicitally by the
  application, and not "when ready"
  Still this indicates a wrong use by the application (it
  shouldn't allow the SAS to invalidate if there are more
  messages expected to come with its Id encoded), so this defect
  priority can be set to low.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server Feature Pack   *
  *                  for Communications Enabled Applications     *
  *                  users of Session Initiation Protocol (SIP)  *
  *                  container.                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Sip container could not handle a sip    *
  *                      message for an encoded URI sip          *
  *                      application session.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If an application encoded SIP application session to a URI and
  the message arrived with proximity to the invalidation of
  that session. Container couldn't process that message because
  the SIP application session was invalidating.
  This can result an IllegalStateException.
  

Problem conclusion

• Code was modified to prevent events like this. Session will
  not be attached to an invalidated sip application session.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 1.0.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:

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

Fix information

• Fixed component name

  CEA FEATUREPACK

• Fixed component ID

  5724J0855

Applicable component levels

• R700 PSY

     UP