PQ74406: DUPLICATE KEY EXCEPTIONS ARE BEING THROWN IN COMPLIANCE MODE WHEN AN EXISTING SESSION IS REQUESTED

 A fix is available

5.0.2: WebSphere Application Server Version 5.0 Fix Pack 2 (Version 5.0.2)



APAR status
Closed as program error.

Error description
Customer is getting the following error on 3.5.5:
com.ibm.ejs.cm.portability.DuplicateKeyException: [IBM][CLI Driv
[DB2/SUN] SQL0803N  One or more values in the INSERT statement,
UPDATE statement, or foreign key update caused by a DELETE
statement are not valid because the primary key, unique constrai
or unique index identified by "2" constrains table "WAS.SESSIONS
rom having duplicate rows for those columns.  SQLSTATE=23505
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.sql.SQLException.<init>(SQLException.java:36)
at com.ibm.ejs.cm.portability.PortableSQLException.<init>
(PortableSQLException.java:22)
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server -- Session      *
*                 Manager Users                                *
****************************************************************
* PROBLEM DESCRIPTION: Duplicate Key Exceptions are being      *
*                      thrown in compliance mode when an       *
*                      existing session is requested.          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In the 2.2 compliance mode the session manager creates one
session object per web module from the same HttpClient. The
session objects share the same session id in the different web
modules.  If multiple requests come in with an existing
session id in a different web module and the session does not
exist, there is a window where multiple threads serving this
different request could end up creating multiple session
objects in the same JVM and try to persist them to the database
resulting in DuplicateKeyExceptions. This multiple request could
be caused by double clicks or a multi frame jsp. This window is
Problem conclusion
This fix causes the session create operation to be synchronized
across multiple threads therefore avoiding multiple session
objects to be created within a web module for the same
HttpClient.
Temporary fix
PQ71645_test.jar
Comments
APAR information
APAR number PQ74406
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-05-21
Closed date 2003-05-21
Last modified date 2003-05-21

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

APAR is sysrouted TO one or more of the following:

Modules/Macros
SESSIONS          

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

Applicable component levels
R00W PSY    UP
R00I PSY    UP
R00H PSY    UP
R00S PSY    UP
R003 PSY    UP
R00A PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ74406
IBM Group: Software Group
Modified date: May 21, 2003