APAR status
Closed as program error.
Error description
Environment:
WSAS ND v5.0.2.12 with 5 node clusters
AIX 5.1 OS.
DB2 Connect 8 fixpack 9 with UDB type 2 driver.
IBM IHS 2.0.42.1 remotely running on separate boxes.
Problem Description:
The application server is running with session persistence.
Duplicate session row errors occur when sending calls to DB2
7.x zOS remotely.
The problem started after upgrading from WSAS v5.0.2.3 to WSAS
v5.0.2.12.
Logs show the following:
[10/16/05 17:06:56:837 EDT] 1cd24df6 SessionContex E SESN0042E:
BackedHashtable:ejbCreate - database error. If a SQLException
has occurred then refer to the appropriate database
documentation for your environment. Also, ensure that you have
properly configured a datasource for Session Manager.
[10/16/05 17:06:56:838 EDT] 1cd24df6 SessionContex E Session
Object is: Session Object Internals:
id : mi3CCM2ashK6Zk5ifC6cdo7
hashCode : 929713643
create time : Sun Oct 16 17:06:56 EDT 2005
last access : Sun Oct 16 17:06:56 EDT 2005
max inactive interval : 1800
user name : anonymous
valid session : true
new session : true
[10/16/05 17:06:56:840 EDT] 1cd24df6 SessionContex E
Miscellaneous data: Update SQL insert into PRI1E.sessions (id,
propid, appname, listenercnt, lastaccess, creationtime,
maxinactivetime, username, small, medium, large) values (?, ?,
?, ?, ?, ?, ?, ?, NULL, NULL, NULL)
[10/16/05 17:06:56:841 EDT] 1cd24df6 SessionContex E Exception
is:
com.ibm.websphere.ce.cm.DuplicateKeyException: AN INSERTED OR
UPDATED VALUE IS INVALID BECAUSE INDEX IN INDEX SPACE
CONSTRAINS COLUMNS OF THE TABLE SO NO TWO ROWS CAN CONTAIN
DUPLICATE VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X''
---- Begin backtrace for Nested Throwables
com.ibm.db2.jcc.b.SqlException: AN INSERTED OR UPDATED VALUE IS
INVALID BECAUSE INDEX IN INDEX SPACE CONSTRAINS COLUMNS OF THE
TABLE SO NO TWO ROWS CAN CONTAIN DUPLICATE VALUES IN THOSE
COLUMNS. RID OF EXISTING ROW IS X''
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Users who have configured their session *
* manager for database persistence. *
****************************************************************
* PROBLEM DESCRIPTION: When session manager is configured to *
* use database persistence, sometimes a *
* DuplicateKeyException will be thrown. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DuplicateKeyException in session manager under database
persistence
Problem conclusion
Code changes were made in session manager code to handle
this exception. Code changes have been made and will
form part of service packs 5.0.2.17, 5.1.1.11, and
6.0.2.10.
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 |
PK19292 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2006-02-07 |
Closed date |
2006-03-09 |
Last modified date |
2006-09-21 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PK31847
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
Applicable component levels |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|