IBM Support

PK90248: LOB DATA NOT STORED IN SESSION TABLE IN SOME INSTANCES WHEN USING SESSION PERSISTENCE TO DB2

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When fullyMaterializeLobData is set to false in the JDBC driver
    custom properties for the DB2 driver being used, the session
    persistence code fails to write LOB's to the session table.  The
    data is instead stored in memory and thus can be lost when the
    server is recycled.
    

Local fix

  • Keep fullyMaterializeLobData set to true in the driver custom
    properties settings.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere Application Server    *
    *                 V7.0                                         *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Session Manager does not return an      *
    *                      existing session attributes             *
    *                      persisting in session persistence in a  *
    *                      failover application.                   *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a failover application retrieves an existing session
    attributes persisting into the lob data type column defined in
    the session persistence table, session attributes will not be
    retrieved since the lob data is not fully materialized properly.
    

Problem conclusion

  • The session manager data retrieval mechanism is enhanced to
    fully materialize the data from the database in the
    configuration of datasource property fullyMaterializeLobData
    disabled.
    
    APAR PK90248 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.5 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK90248

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-06-30

  • Closed date

    2009-07-08

  • Last modified date

    2009-08-03

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

    PK77100

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

Modules/Macros

  • BBGUBINF BBOUBINF
    

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK48201

       UP09/07/27 P F907

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022