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/01/19 14:53:29 UTC
DO NOT REPLY [Bug 16238] New: -
log4j(1.2.6) - does not terminate if permission is denied to the folder where the log file are created
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=16238>.
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=16238
log4j(1.2.6) - does not terminate if permission is denied to the folder where the log file are created
Summary: log4j(1.2.6) - does not terminate if permission is
denied to the folder where the log file are created
Product: Log4j
Version: 1.2
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: Critical
Priority: Other
Component: Other
AssignedTo: log4j-dev@jakarta.apache.org
ReportedBy: esathya@chn.cognizant.com
CC: esathya@chn.cognizant.com
My application continues to run even if the permission to folder or the log
file inside that folder is denied.
It says " log4j:ERROR setFile(null,true) call failed"
and the following stack trace is printed only to the console(it's not thrown
back as exception).
...................................
java.io.FileNotFoundException: load_reset.log.err.20030119 (Permission denied)
at java.io.FileOutputStream.openAppend(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:100)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:272)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:151)
at org.apache.log4j.config.PropertySetter.activate
(PropertySetter.java:247)
at org.apache.log4j.config.PropertySetter.setProperties
(PropertySetter.java:123)
at org.apache.log4j.config.PropertySetter.setProperties
(PropertySetter.java:87)
at org.apache.log4j.PropertyConfigurator.parseAppender
(PropertyConfigurator.java:645)
at org.apache.log4j.PropertyConfigurator.parseCategory
(PropertyConfigurator.java:603)
at org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers
(PropertyConfigurator.java
:524)
at org.apache.log4j.PropertyConfigurator.doConfigure
(PropertyConfigurator.java:408)
at org.apache.log4j.PropertyConfigurator.configure
(PropertyConfigurator.java:340)
.........................................
But, i need the exception to be thrown back to my calling program to terminate
my application.
Is this a bug or is there any valid reason for this behaviour?
If there's any valid reason for this behaviour, can you suggest what work
around has to be done to handle this problem?
Can you please help me out in this regard?
Thanks,
Sathya.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>