You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2003/11/03 17:58:16 UTC
DO NOT REPLY [Bug 24358] New: -
A new z/OS (OS/390) Specific Rolling File Appender.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24358>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24358
A new z/OS (OS/390) Specific Rolling File Appender.
Summary: A new z/OS (OS/390) Specific Rolling File Appender.
Product: Log4j
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: Appender
AssignedTo: log4j-dev@jakarta.apache.org
ReportedBy: mike_nitso@hotmail.com
Typically, we do not have the ability to create dynamic file names for output
in the log4j.properties file. Quality of service dictates that the z/OS
environment will create and destroy servant regions in order to balance load.
Since each of these servant regions will read a single log4j.properties file,
they each will be logging to the same output file, as specified in the
log4j.properties file. Having multiple servant regions log to the same file
will result in lost log statements (only on z/OS), and file contention
(creating reduced performance for a particular servant region). Hence, this
appender will generate a unique file name to log to per servant region. This
appender also supports the PropertyConfigurator.configureAndWatch() method
since the dynamic file name is created the same way each time. Therefore, any
updates made to the log4j.properties file will be realized, and the dynamic
file name will not be changed.
See attached for source code contained within cvs diff output.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org