PM38840: DOCUMENTATION: HTTP SESSION COOKIE NAME: JSESSIONID

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • AFFECTED URLs:
    7.0
    http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Configuring_portal
    _behavior_wp7
    6.1
    http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp?to
    pic=/com.ibm.wp.ent.doc_v6101/admin/adptlcfg.html
    6.0
    http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/topic/com.ib
    m.wp.exp.doc/wps/adptlcfg.html
    .
    TEXT SHOULD READ:
    *** new section: HTTP session cookie name: JSESSIONID ***
    
    The Java Servlet API up to version 2.5 states that the session
    identification cookie *MUST* be named 'JSESSIONID'. Although
    WebSphere Application Server offers to modify the cookie name,
    this is not supported with WebSphere Portal.
    
    Right now the majority of use cases for changing the JSESSIONID
    cookie name results from cookie name clashes due to http proxy
    server usage. The general recommendation for such use cases is
    to enable the HttpSessionIdReuse setting in WebSphere
    Application Server. This prevents cookie name clashes by reusing
    the session id values across different servers.
    .
    See section: 'Using the session ID that is sent from a browser
    to preserve session data' in WebSphere Application Server
    infocenter:
    (http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com
    .ibm.websphere.nd.doc/info/ae/ae/rweb_custom_props.html)
    .
    The custom property HttpSessionIdReuse determines whether the
    session manager can use the session ID sent from a browser to
    preserve session data across Web applications that are running
    in an environment that is not configured for session
    persistence. In a multi-JVM environment that is not configured
    for session persistence setting this property to true enables
    the session manager to use the same session information for all
    of a user's requests even if the Web applications that are
    handling these requests are governed by different JVMs. The
    default value for this property is false. To enable the session
    manager to use the session ID sent from a browser to preserve
    session data across Web applications that are running in an
    environment that is not configured for session persistence, use
    the following name-value pair:
    .
    Name:  HttpSessionIdReuse
    Value: true
    

Local fix

  • Refer to the above
    

Problem summary

  • This is planned to be updated in the product documentation.
    

Problem conclusion

  • This is planned to be updated in the product documentation.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM38840

  • Reported component name

    WEBSPHERE PORTA

  • Reported component ID

    5724E7600

  • Reported release

    700

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-11

  • Closed date

    2011-05-23

  • Last modified date

    2011-05-23

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

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

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Portal

Software version:

7.0

Reference #:

PM38840

Modified date:

2011-05-23

Translate my page

Machine Translation

Content navigation