Bug 36435

Summary: Log4J RollingFileAppender under OpenVMS does not follow RMS rules
Product: Log4j - Now in Jira Reporter: Nils Hammar <u36674300>
Component: AppenderAssignee: log4j-dev <log4j-dev>
Status: NEW ---    
Severity: enhancement CC: kay.abendroth
Priority: P3    
Version: 1.2   
Target Milestone: ---   
Hardware: Other   
OS: OpenVMS   

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.