APAR status |
Closed as program error.
| Error description
After fixpack 5 is installed on WAS3.5 ,
Sevlet Instance logs are traced twice in the stdout.log file.
Also confirmed that Servlet Instances are not getting loaded twi
Only the message is getting printed twice in the log file. Local fixProblem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server 3.5.5 *
* users of servlets. *
****************************************************************
* PROBLEM DESCRIPTION: In WAS 355, the message "Servlet *
* available for Service" is logged *
* twice in stdout.log and adminconsole. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In WAS355, "Servlet Available for service" message gets
logged twice Problem conclusion
This problem was corrected by modifying the file
WebAppServletmanager.java to not log the message twice. Temporary fix
I have placed the tentative fix under
wasdoc0\apars\v355\PQ55130.jar
Awaiting customer's feedback
.
Thanks,
Jegan Comments
APAR information | APAR number | PQ55130 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-11-26 | Closed date | 2001-12-13 | Last modified date | 2001-12-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
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 | APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels | R350 PSY | UP |
|