IBM Support

PI75485: ISSUE MESSAGE EXPLANING FROM WHERE SESSION TIMEOUT IS PICKED UP

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • There are 4 levels where http session timeout can be set.
    Which one will be picked will depend on the on configuration.
    Many times a session is expiring earlier (or stays alive
    longer) than expected. Users may just look at the server
    level setting while they mistakenly overwrite the setting at
    the ear or war level. A session trace has to be run to
    determine from where the session timeout is picked up.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Trace messages from session management  *
    *                      configuration by level requires more    *
    *                      detailed information.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Session manager can set up different configurations
    individually for specific applications and Web modules that
    vary from the Web container default. Trace messages during
    application start up don't provide detailed information where
    the session management configurations are picked up from. That
    is,  Web container level, applications level or Web modules
    level.
    

Problem conclusion

  • Trace messages from session management configuration by level
    were modified to include additional details such as overridden
    configuration at either application level or Web modules level.
    
    The fix for this APAR is currently targeted for inclusion in
    WebSphere Application Server fix packs 7.0.0.43, 8.0.0.14,
    8.5.5.12 and 9.0.0.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 number

    PI75485

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-26

  • Closed date

    2017-03-23

  • Last modified date

    2017-03-23

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP

  • R900 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PI75485

Modified date: 23 March 2017