APAR status |
Closed as program error.
| Error description
Configuration: WASv3.5.4/NT4/DB2, some Servlets connect to Oracl
v8.1.7 for transaction of user data.
Problem description:
Exception occurred in program but cannot find correspondin
i.) 20011030-mss_stdout.txt: 500 error DESTROYED occured
5:30pm to 6pm.
[01.10.28 15:08:15:937 CST] 7cfff386 ServletInstan X Uncau
service() exception thrown by servlet {0}: {1}
"JSP 1.1 Processor"
javax.servlet.ServletException: Illegal ConnectO state:Problem description:Exception occurred in program but cannot find correspondini.) 20011030-mss_stdout.txt: 500 error DESTROYED occured5:30pm to 6pm.[01.10.28 15:08:15:937 CST], 7cfff386 ServletInstan X Uncauservice() exception thrown by servlet {0}: {1}"JSP 1.1 Processor"
DESTORYED
After our investigation, we suggest customer to apply efix
last night in production environment.
But, this exception still appears.
[01.11.02 16:47:28:531 CST] 86458fba ServletInstan X Uncau
service() exception root cause {0}: {1}
"JSP 1.1 Processor"
java.lang.Exception: Illegal ConnectO state: DESTROYED
.
This is the same as WAS 3.0 APAR PQ54739. javax.servlet.ServletException: Illegal ConnectO state:DESTORYEDAfter our investigation, we suggest customer to apply efixlast night in production environment.But, this exception still appears.[01.11.02 16:47:28:531 CST], 86458fba ServletInstan X Uncauservice() exception root cause {0}: {1}"JSP 1.1 Processor"java.lang.Exception: Illegal ConnectO state: DESTROYED., This is the same as WAS 3.0 APARPQ54739. Local fix
This is fixed in WAS 4.0 base (this is true for all WAS 4.0
component IDs, 5630a220x and 5630a230x).
.
There is no workaround for WAS 3.5.x other than applying a
eFix for this APAR. Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who rely *
* on StaleConnectionException to clean up the *
* connection pool *
****************************************************************
* PROBLEM DESCRIPTION: StaleConnection was being caught by *
* WebSphere code and another exception *
* was thrown *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The Exception: Illegal ConnectO State was being thrown, and
WebSphere was not clearing the connection pool Problem conclusion
Modified the code where the StaleConnectionException was not
being re-thrown. Temporary fixComments
APAR information | APAR number | PQ54471 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-11-09 | Closed date | 2002-01-17 | Last modified date | 2003-11-17 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|