APAR status
Closed as program error.
Error description
There is a tiny window in which the Admin database has to
be -between- making an update and closing the statement.
At that exact moment, the database must go down completely
causing a locking problem. This can occur even with the
latest CM code. This is why it's not a very big window,
and why we've never seen the problem before.
Local fix
Workaround: You simply have to force the sessions closed in
Oracle, this will cause the locks to be released and the server
to restart.
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users *
* with an admin repository on Oracle. *
****************************************************************
* PROBLEM DESCRIPTION: A problem exists where during an *
* update to the admin repository, *
* if Oracle goes down, locks could *
* be left open. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A small window existed where we could try to close a connection
twice. This would only happen if the code using CM was not
following the programing model and the Oracle DB had to go
down at just the right time.
Problem conclusion
Code was added to verify that destruction only happens once.
Temporary fix Comments
APAR information |
APAR number |
PQ78605 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A2202 |
Reported release |
400 |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Submitted date |
2003-09-17 |
Closed date |
2003-10-01 |
Last modified date |
2003-10-01 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PQ79104
Modules/Macros
SRLS
Applicable component levels |
R400 PSY |
UP |
|