Re: [log4perl-devel] Log4perl and catching unhandle exceptions but not using 'easy' mode

2009-05-20 Thread Robert Jacobson
Richard Burton richard-at-atomwide.com |log4perl_sourceforge| wrote: Hi all I am trying to capture unhandled exceptions that are sent to STDERR, e.g. for example the following could would give such an error [snip] I can catch this using stealth as loggers outlined in

Re: [log4perl-devel] subclassed DBI (DBI_Buffer) does not release dbh filehandles on reinit

2009-02-26 Thread Robert Jacobson
Mike Schilli m-at-perlmeister.com |log4perl_sourceforge| wrote: On Tue, 24 Feb 2009, Robert Jacobson wrote: Those are mostly the expected values from the Layout I specified (time, log level, script name, hostname, PID, ?, message). That's peculiar ... what does your layout look like

Re: [log4perl-devel] subclassed DBI (DBI_Buffer) does not release dbh filehandles on reinit

2009-02-24 Thread Robert Jacobson
Robert Jacobson wrote: If I add equivalent code to my existing conditional for the definition of errorappender, i.e.: if ($self-{errorappender}) { # Pass back the appender to be synchronized as a dependency # to the configuration file parser push @{$p

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

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 error without