IBM Support

PK66322: PRETEST CONNECTION LOGIC SHOULD NOT WORK WHEN PURGE POLICY IS ENTIRE POOL, BUT SHOULD WHEN IT IS FAILED CONNECTION ONLY.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Connections should be PreTested in the case of using 'Failed
    Connection Only' and NOT PreTested in the case of using 'Entire
    Pool' for Purge Policies.  This is the behavior to be fixed
    whereby Entire Pool policy does NOT PreTest.  Now there are also
    configurable PreTest New or Existing pool connection properties
    at the DataSource, but these are not used in conjunction with
    the purge policy.  PreTest logic for failed connection does use
    the same PreTest SQL String as shown by Default DataSource
    properties previously mentioned, which is
    which is "SELECT 1 FROM SYSIBM.SYSDUMMY1".  If this value is
    left Blank, then it will revert to "SELECT 1 FROM DUAL".
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of Relational Resource Adapter    *
    *                  (RRA) on IBM WebSphere Application Server   *
    *                  V6.1.                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: After a fatal or stale connection       *
    *                      exception, the new connections are      *
    *                      pre-tested before use.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a connection fails with a fatal error or stale
    connection exception, the new connections for the same
    connection pool are pre-tested before being given to the
    application.
    The following trace point may appear in such cases in the
    WAS.j2c=all traces:
    
    [4/14/08 14:01:11:467 CEST] 00000040 WSRdbManagedC 3
    preTestConnection
    WSRdbManagedConnectionImpl@7e0e7e0e
    preTestSQLString: "SELECT 1 FROM SYSIBM.SYSDUMMY1"
    
    This happens regardless of a value of the Pretest New
    Connections property and is correct. However, this should not
    happen when the pool Purge Policy is EntirePool and this APAR
    corrects that.
    

Problem conclusion

  • After a fatal or stale connection exception, the new
    connections are pre-tested before use only if the pool Purge
    Policy is FailingConnectionOnly.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.19. 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

    PK66322

  • Reported component name

    WEBSPH APP SERV

  • Reported component ID

    5724J0800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-05-20

  • Closed date

    2008-06-10

  • Last modified date

    2008-06-10

  • 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

    WEBSPH APP SERV

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021