APAR status
Closed as program error.
Error description
Problem desc: Customer reported different behavior of the log4j
on
WAS V4 and WAS V5. In WAS V5 log4j looses logging of time
stamps.
Local fix
Local Fix supplied to customer. Customer approved that supplied
fix is working
Problem summary
****************************************************************
* USERS AFFECTED: This affects users who are using log4j as *
* their logging API, as well as other users *
* that write or print to System.out directly. *
****************************************************************
* PROBLEM DESCRIPTION: When printing or writing to System.out *
* and System.err some logging APIs write *
* directly to System.out and System.err *
* with the write methods. In order to *
* more gracefully separate lines written *
* in this manner, this fix adds a new *
* record header (including timestamp, *
* thread id, etc.) at the start of any *
* line following a new line terminated *
* write or print. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The logging code looks for logical places to break System.out
and System.err requests into separate events. The logic
that existed before this fix was that separate events would
only be created in the case where a System.out.println or
System.err.println request was processed. Some logging
infrastructures such as log4j can write to System.out
directly using the write method instead of System.out.println.
Problem conclusion
In order to avoid log4j never getting headers printed, it
was decided that a write with a last character of \n would
also be an indication that a new header should be printed
on the next request. This results in a more reasonable
breaking of System.out.write data in the System.out log.
Temporary fix
Submitted APAR to
pq99999 for customer validation
Comments
APAR information |
APAR number |
PQ89439 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-05-27 |
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
Publications Referenced
Applicable component levels |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|