APAR status
Closed as program error.
Error description
After getting the connection, the database goes down. If the
application calls any method (e.g. executeQuery, executeBatch)
on the connection:
- Oracle 9i JDBC driver will throw ORA-17002 every time
- Oracle 10g JDBC driver will throw ORA-17002 the first time
and then ORA-17430 on the subsequent call
.
ORA-17002: Io exception (General JDBC Message)
ORA-17430: Must be logged on to server (TTC - Two-Task Common
Message)
This APAR maps ORA-17430 to WebSphere's StaleConnectionException
For some reason if the ORA-17002 was missed to capture
as StaleConnectionException, then ORA-17430 will be captured
as StaleConnectionException to allow the application to
recover from these "stale" connections successfully.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users *
* of connection management and Oracle. *
****************************************************************
* PROBLEM DESCRIPTION: With Oracle 10G, a different *
* exception is issued when a connection *
* is stale, in the past it was 17002, *
* and now it may issue 17430. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
We needed to add ORA-17430 to the StaleConnectionException map.
Problem conclusion
We added 17430 to the SCE map.
Temporary fix Comments
APAR information |
APAR number |
PQ90201 |
Reported component name |
WEBSPHERE AE NT |
Reported component ID |
5630A2201 |
Reported release |
400 |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Submitted date |
2004-06-15 |
Closed date |
2004-06-29 |
Last modified date |
2004-06-29 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
SRLS
Applicable component levels |
R400 PSY |
UP |
|