Quoting Ceki G�lc� <[EMAIL PROTECTED]>:
> Jake,
>
> The config file looks good.
>
[cut]
> >Am I missing something in the configuration of the rolling appenders? I'd
> >like to make sure I have everything set properly and avoid the warnings.
>
> The rollover failure is real though. (Fortunately it will not cause data
> loss as was the case in previous versions of log4j.) Something is
> preventing the file from being renamed
>
> One thing which raises suspicions is the missing message (of level DEBUG)
> by the rename method in o.a.l.roling.helper.Util
>
> DEBUG[Thread-1]: org.apache.log4j.rolling.helper.Util 11594 - Renaming
> file [D:\Java\Apache\Jakarta\jakarta-tomcat-5.5.4/logs/localhost.log]
> toFile [D:\Java\Apache\Jakarta\jakarta-tomcat-5.5.4/logs/localhost.log.1]
>
> Why is this log statement is missing? Is the logger named
> "o.a.l.rolling.helper.Util" disabled?
>
I have a logger defined as:
<logger name="org.apache.log4j">
<level value="debug"/>
</logger>
it inherits the console appender from the root logger. Oh, and I have
<log4j:configuration debug="false">
> I'd venture to say that more than one LoggerRepository has a handle to
> "../jakarta-tomcat-5.5.4/logs/localhost.log". Is it possible that more than
> one repository is being automatically configured with the same config file?
> Are you using log4j-1.3alpha3 or CVS head? Have you set a RepositorySelector?
>
I'm using CVS HEAD. At startup, the default selector is used. It is not until
my one app that uses initializtion code starts up that I set the
ContextJNDISelector. I am also using the ServletContextLogAppender from
log4j-sandbox which hooks into the servlet api's servletContext.log() method.
So, in a roundabout way, logging from one repository (my app's repository) is
going to a logger defined in the default repository (although this seems to
work sporadically and I haven't figured out the conditions under which it works
or doesn't work. I've debugged and append() always gets called, but then, many
times, I see no output in the log file defined for my servlet context. If I
put another copy of log4j in my WEB-INF/lib, then it seems to work pretty
consistently, of course then app logging is completely separated from container
logging except through servletContext.log()). I don't think any other
repository is being configured with the same config file since you turned off
autoconfiguration on non-default logger repositories. The only reason it could
happen is if Joran is parsing twice. Wasn't that pointed out in another thread
on the list? Just a shot in the dark.
When I get home, I'll try removing usage of the ServletContextLogAppender and
see if the bad behavior goes away and report my findings.
Jake
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
