PI28603: SERVLETREQUEST.GETREQUESTEDSESSIONID() RETURNS NULL FOR A CLIENT CREATED JSESSIONID.

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

APAR status

• Closed as program error.

Error description

• When a client adds a new session id to a request the new
  session id is not available to the target of the request.
  
  Note: A client created session id is not a valid session id,
  but should be available to an application using the
  ServletRequest.getRequestedSessionId() API.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: ServletRequest.getRequestedSessionId()  *
  *                      returns null for a client created       *
  *                      jsessionId.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a client adds a new session id to a request the new session
  id is not available to the target resource of the request using
  the ServletRequest.getRequestedSessionId()  API.
  

Problem conclusion

• If a client sends a session id to the server it will now be
  available using the ServletRequest.getRequestedSessionId() API
  unless the request is already associated with a valid server
  created session id. However, note that a client created session
  id is not a valid session id.  The fix for this APAR is
  currently targeted for inclusion in fix pack 8.5.5.4.  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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP