Bug 36435 - Log4J RollingFileAppender under OpenVMS does not follow RMS rules
Summary: Log4J RollingFileAppender under OpenVMS does not follow RMS rules
Status: NEW
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Appender (show other bugs)
Version: 1.2
Hardware: Other OpenVMS
: P3 enhancement
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-31 11:04 UTC by Nils Hammar
Modified: 2006-11-12 10:34 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nils Hammar 2005-08-31 11:04:44 UTC 
OpenVMS has it's own file versioning, and that versioning is not followed by
Log4J using the RollingFileAppender. Instead of having the highest version as
latest, Log4J has the current logfile as the highest version, but version 1 as
the next latest etc. This will cause inconsistencies when for example a PURGE
/KEEP=4 is executed.

It's not a critical issue, but it's highly annoying when the version behavior
conflicts with the OS expectation.
Comment 1 Kay Abendroth 2006-11-12 10:34:37 UTC 
Marked as enhancement.
Priority lowered from P2 -> P3.