Jake,
I've looked into the examples you've sent me. Can't make anything out of them.
One of the important tasks to be done before releasing 1.3, is to write unit tests which go through the whole web-app lifecycle to check that log4j releases all resources correctly. I started doing that with jetty but got sidetracked.
Anyway, I'd appreciate small and manageable test cases reproducing the problem. You are a log4j committer, have you considered submitting test cases verifying that resources are correctly handled by log4j?
At 11:06 PM 12/2/2004, Jacob Kjome wrote:
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
-- Ceki G�lc�
The complete log4j manual: http://qos.ch/eclm
Professional log4j support: http://qos.ch/log4jSupport
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
