APAR status |
Closed as program error.
| Error description
WAS hang status by temporary application DB down was
solved by PQ46910. But side-effect might be occur.
The e-fix ignore IHS timeout directive.
---
We applied PQ46910 for the subject prob.
But the result, PQ46910 ignore IHS timeout
directive for the session dispatched to IBM OSE LINK.
This is side effect of PQ46910.
If back end process have trouble etc,,, session
and thread couldn't released by IHS timeout.
So there is no timeout logic at server side.
Session can be removed by client termination,
however thread can't be released.
We need support session timeout and release
thread logic at inlet of the servlet engine.
.
This APAR has been superceded by PQ57425. Local fixProblem summary
as a change to make the plugins handle certain types of failures
more gracefully. In most cases, this fix allows the webserver
to continue to serve static pages when the appserver is not
handling requests. This fix will _not_ actually free up the
AppServer worker threads that are hanging up the appserver.
It will free up webserver threads for more work. Problem conclusion
serving static pages in most cases. About 4 customers have
applied it and found it satisfactory so far. Temporary fixComments
APAR information | APAR number | PQ51372 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-08-14 | Closed date | 2002-01-30 | Last modified date | 2003-01-02 |
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 |
|