Socket descriptor leak in SyslogAppender?

Hi, I am using log4j 1.2.8 with the SyslogAppender and my application calls the following code periodically to pick up any configuration changes: Properties prop = ... LogManager.resetConfiguration(); PropertyConfigurator.configure(prop); Each time this code is called, the applicati

RE: Attempted to append to closed appender

Our problems (besides this one) w/ log4j and 8.1 have a little more serious, unfortunately. As I mentioned before, something is definitely different with threading. We are getting hundreds of FileWatchdog threads from configureAndWatch. They keep accumulating and eventually crash the app serv

RE: Stable version of Chainsaw?

Hi Rob, Have you configured a socketappender and a fileappender (where fileappender's patternlayout includes patterns for displaying the line/method or file name? If so, make sure socketappender is first in the list of appenders - the class that provides location info is in a different package

RE: Attempted to append to closed appender

Ceki's note jogged my memory on my problem, which is likely similar to yours. I'm guessing something during your WebLogic upgrade now attempts to use Log4j before your configuration takes affect and in Log4j's initialization attempts it finds another configuration file which creates an appender

RE: Attempted to append to closed appender

They are documented in the javadocs. cheers kaufman -Original Message- From: Rob Byrom [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 26, 2004 11:44 AM To: Log4J Users List Subject: RE: Attempted to append to closed appender I figured this out via trial and error. It would be nice if

RE: Attempted to append to closed appender

I figured this out via trial and error. It would be nice if they were documented :) Rob On Tue, 2004-10-26 at 15:51, Rob Byrom wrote: > hi, > > appologies if this is a rehashed question. > > Can anyone give me a list of all the properties the ConversionPattern > takes? > > I've looked through

RE: Attempted to append to closed appender

Maybe it wasn't using 1.2.8 that's caused this to become visible. We also recently upgraded from WebLogic 6.1 on 1.3.1 to 8.1 on 1.4.2. 6.1 and 8.1 certainly seem to have some differences in their threading behavior. Maybe this is related. We've been using configureAndWatch pretty much since

RE: Attempted to append to closed appender

At 05:12 PM 10/26/2004, you wrote: Is a setup like this more appropriate? log4j.rootLogger=INFO, debug log4j.category.org=ERROR log4j.category.jsp_servlet=INFO, toolkit log4j.category.com.fedex.cc.messaging=INFO log4j.category.com.fedex.cc.domainlib=WARN log4j.category.com.fedex.cc.commons.web.tagl

RE: Attempted to append to closed appender

Eric, If you are sure that no existing settings should be kept, you can wipe the entire existing configuration out with the command: LogManager.resetConfiguration(); This will cause all open appenders to be closed. I previously made a request that there be an option to close all appenders as

RE: Attempted to append to closed appender

hi, Does anyone know which log4j class provides the parsing for the ConversionPattern ? thanks, Rob On Tue, 2004-10-26 at 15:51, Rob Byrom wrote: > hi, > > appologies if this is a rehashed question. > > Can anyone give me a list of all the properties the ConversionPattern > takes? > > I've l

RE: Attempted to append to closed appender

Is a setup like this more appropriate? log4j.rootLogger=INFO, debug log4j.category.org=ERROR log4j.category.jsp_servlet=INFO, toolkit log4j.category.com.fedex.cc.messaging=INFO log4j.category.com.fedex.cc.domainlib=WARN log4j.category.com.fedex.cc.commons.web.taglibs=WARN log4j.category.com.fedex.

RE: Attempted to append to closed appender

I've read that a couple times before and just read it again. I don't understand what you are trying to get me to see in there. -Original Message- From: Ceki Gülcü [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 26, 2004 10:54 AM To: Log4J Users List Subject: RE: Attempted to append to c

RE: Attempted to append to closed appender

At 04:43 PM 10/26/2004, you wrote: So that all logging is performed to the same file. It is a pain to jump from one file to another when tracing a complex app. I suggest that you have a look at the log4j short manual http://logging.apache.org/log4j/docs/manual.html and especially the section on

RE: Attempted to append to closed appender

hi, appologies if this is a rehashed question. Can anyone give me a list of all the properties the ConversionPattern takes? I've looked through the manual but can't find the table I need :) thanks! Rob On Tue, 2004-10-26 at 15:40, Ceki GÃlcà wrote: > Is there any particular reason you are att

Re: Stable version of Chainsaw?

hi I just followed the tutorial available when you run the chainsaw. I'm not sure where else its stored or available. Rob On Tue, 2004-10-26 at 15:39, Vineet Bhatia wrote: > Hi Rob, > > I have also been trying to get chainsaw to work for some time. > > Can you send the link of the page (tutori

RE: Attempted to append to closed appender

So that all logging is performed to the same file. It is a pain to jump from one file to another when tracing a complex app. -Original Message- From: Ceki Gülcü [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 26, 2004 10:41 AM To: Log4J Users List Subject: RE: Attempted to append to clo

RE: Attempted to append to closed appender

Is there any particular reason you are attaching the same appender to multiple loggers? At 04:33 PM 10/26/2004, you wrote: After a little googling I found this. log4j.additivity.default=false I'm still seeing the error, however. Will this change be picked up with configureAndWatch, or do I need

Re: Stable version of Chainsaw?

Hi Rob, I have also been trying to get chainsaw to work for some time. Can you send the link of the page (tutorial)? - vineet On 26 Oct 2004 15:18:39 +0100, Rob Byrom <[EMAIL PROTECTED]> wrote: > hi, > > Are the more stable versions of chainsaw available rather than using V2? > I've tried the

RE: Attempted to append to closed appender

After a little googling I found this. log4j.additivity.default=false I'm still seeing the error, however. Will this change be picked up with configureAndWatch, or do I need to undeploy/redeploy my applications to pickup the new setting? -Original Message- From: Fenderbosch, Eric Sent

RE: Attempted to append to closed appender

Is there a way to turn off additivity in the configuration instead of in code via Category.setAdditivity(false)? -Original Message- From: Ceki Gülcü [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 26, 2004 10:11 AM To: Log4J Users List Subject: Re: Attempted to append to closed appender

Stable version of Chainsaw?

hi, Are the more stable versions of chainsaw available rather than using V2? I've tried the latest cvs version (using the ant script on the log4j website) but haven't had much success with getting it to work well (ie the tutorial works ok but thats as far as I get with it). Rob ---

Re: Attempted to append to closed appender

At 03:57 PM 10/26/2004, you wrote: I searched and found a couple threads on this @ Mail Archive, but those configurations were via XML and we are using log4j.properties. Same problem as other people, once we change/add a level on the fly, our app server log starts filling up with log4j:ERROR Atte

Attempted to append to closed appender

I searched and found a couple threads on this @ Mail Archive, but those configurations were via XML and we are using log4j.properties. Same problem as other people, once we change/add a level on the fly, our app server log starts filling up with log4j:ERROR Attempted to append to closed appender