PQ56665: AFTER PQ58003 MAPPING MERANT SEQUELINK'S VENDOR CODE "227" AND SQLSTATE 23000 TO STALECONNECTIONEXCEPTION

 A fix is available

4.0.2-4.0.7: Component cumulative Connection Manager fix



APAR status
Closed as program error.

Error description
Using MERANT SequeLink JDBC Driver 5.1 with WebSphere
Application Server 4.0.1, the error:
  [MERANT][SequeLink JDBC Driver][SQL Server]Violation
  of PRIMARY KEY constraint 'PK__LOCK_TABLE__76CBA758'.
  Cannot insert duplicate key in object 'LOCK_TABLE'.
.
The JDBC's Vendor Code and the SQL State for the above error are
2627 and 23000 respectively.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 4.0 users who   *
*                 use Merant Sequelink driver to connect to    *
*                 databases.                                   *
****************************************************************
* PROBLEM DESCRIPTION: The backend mappings for Merant         *
*                      layers end up being ignored, so         *
*                      exceptions may not get mapped           *
*                      properly.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Fixpak 4.0.2 introduced a regression into the error mapping
where the backend mappings for Merant layers end up being
ignored.
Problem conclusion
Since 4.0.2 contained a fix for another error mapping problem,
the solution to this defect will involve partially rewriting
the error mapping mechanism.  The ErrorMap class will no longer
hold all of the mappings, as this information is insufficient
to cover cases like Merant and IDB, where the actual translation
involves some logic in addition to the usual mapping mechanism.
The ErrorMap class will now hold only the custom mappings and
will contain a reference to the singleton portability layer,
which contains the default mappings and any necessary logic.
  When a request to map an exception is made to the ErrorMap,
it will now delegate to it's corresponding portability layer,
passing in the special custom mappings.   A new
translateException method is provided on the base portability
layer implementation to handle the custom mappings.
  Precedence is now enforced within the translateException
method of the base layer instead of being done in the hashtable.
As before, custom mappings to exception message text are not
supported.
Temporary fix Comments
APAR information
APAR number PQ56665
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-01-14
Closed date 2002-02-19
Last modified date 2002-02-19

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
JDBC          

SRLS

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ56665
IBM Group: Software Group
Modified date: Feb 19, 2002