Re: [log4perl-devel] Intermittent problems when using signal to reread log configuration

2009-02-23 Thread Mike Schilli
On Mon, 23 Feb 2009, Robert Jacobson wrote: > Apparently my appender is not closing its dbh filehandles. I'm going > to start a separate thread, since the problem is something totally > different (in my code, probably). I apologize for my inadequate > testing :( No problem at all, glad we've fou

Re: [log4perl-devel] Intermittent problems when using signal to reread log configuration

2009-02-23 Thread Robert Jacobson
Ah, apparently I *had* left some appenders using DBI_Buffer (DBI appender subclass) in my config. I retested a bunch of things today and I could not reproduce the error unless I had my DBI_Buffer appender in the config. Further investigation showed that the mysql server was reaching its maximum

Re: [log4perl-devel] Intermittent problems when using signal to reread log configuration

2009-02-22 Thread Mike Schilli
On Sat, 21 Feb 2009, Robert Jacobson wrote: > I am using ActiveState perl on CentOS 4.2 and RHEL4; they both exhibit > the problem. I haven't tried Windows; does SIGHUP even exist there? > (nvm, doesn't matter :) ) Never mind, I was assuming you were using Windows because I've never used Active

Re: [log4perl-devel] Intermittent problems when using signal to reread log configuration

2009-02-21 Thread Robert Jacobson
Mike Schilli m-at-perlmeister.com |log4perl_sourceforge| wrote: > On Fri, 20 Feb 2009, Robert Jacobson wrote: >>> I wonder what kind of config change would cause >>> this. Are you removing an appender by any chance? >> >> Nope, usually I'm only changing the log level. >> >> But I can reproduce the

Re: [log4perl-devel] Intermittent problems when using signal to reread log configuration

2009-02-21 Thread Mike Schilli
On Fri, 20 Feb 2009, Robert Jacobson wrote: >> I wonder what kind of config change would cause >> this. Are you removing an appender by any chance? > > Nope, usually I'm only changing the log level. > > But I can reproduce the error without changing anything in the config, too. Interesting ... is

Re: [log4perl-devel] Intermittent problems when using signal to reread log configuration

2009-02-20 Thread Robert Jacobson
Mike Schilli m-at-perlmeister.com |log4perl_sourceforge| wrote: > Hmm, that's peculiar. I wonder what kind of config change would cause > this. Are you removing an appender by any chance? Nope, usually I'm only changing the log level. But I can reproduce the error without changing anything in the

Re: [log4perl-devel] Intermittent problems when using signal to reread log configuration

2009-02-19 Thread Mike Schilli
On Wed, 18 Feb 2009, Robert Jacobson wrote: > Most of the time (I'd guess ~80%), this works fine. When it doesn't > work, I get the following error on STDERR (even though I've wrapped > STDERR with a "Trapper" as described in the FAQ): > > Can't call method "log" on an undefined value at /o

[log4perl-devel] Intermittent problems when using signal to reread log configuration

2009-02-18 Thread Robert Jacobson
I have been using Log4perl for quite some time in a large project of mine. There are about 20 perl programs, all of which should always be running. I'm using init_and_watch to allow users to update the configuration file; i.e: # Init Log4perl Log::Log4perl->init_and_watch("../ANSlog.