log4perl-devel — Ongoing log4perl development

[log4perl-devel] wrong day of year in output

[Robert J. <yad...@sn...>]

Hi all,

I think the day of year format has an off-by-one problem.  This is a classic error when using localtime, as the range returned by localtime is not expected -- it is 0..364 (or 0..365 in leap years.) instead of 1-365 (1 - 366 in leap years)

For example, this test script shows that the day of year is off by one:

	use Log::Log4perl::DateFormat;

	my $format = Log::Log4perl::DateFormat->new("yyyy-DDD-HH:mm:ss,SSS");

	# Simple time, resolution in seconds	
	my $time = time();
	print $format->format($time), "\n";

Run on my system:

	# perl log4perl_test.pl
	2006-176-15:45:08,000
	# date "+%Y-%j-%H:%M:%S"
	2006-177-15:45:13


To fix, change DateFormat.pm
	push @{$self->{stack}}, [7, sub { $_[0] }];
to
	push @{$self->{stack}}, [7, sub { $_[0] + 1}];


Patch, (generated with "diff -Naur" against 1.04, but I believe 1.05 is the same as in 1.04)

--- Log-Log4perl-1.04/lib/Log/Log4perl/DateFormat.pm  2005-03-27 07:45:58.000000000 +0000
+++ DateFormat.pm       2006-06-26 20:03:52.000000000 +0000
@@ -191,7 +191,7 @@
 #D - day of the year #
 ######################
     } elsif($first eq "D") {
-        push @{$self->{stack}}, [7, sub { $_[0] }];
+        push @{$self->{stack}}, [7, sub { $_[0] + 1}];
         return "%${len}s";

 ######################

If I've made some sort of dumb error, please let me know (it wouldn't be the first time)! :)

Re: [log4perl-devel] New logging levels possible?

[Mike S. <m...@pe...>]

On Wed, 21 Jun 2006, Workman, Joe wrote:

> I LOVE Log4Perl, you guys rock for developing this!!!!

Thanks! :)

> How difficult would is be to add more legging levels to Log4Perl?

Very easy:

    http://log4perl.sourceforge.net/d/Log/Log4perl.html#d21fb

-- Mike

Mike Schilli
m...@pe...

> Although I do
> wish there were a couple more logging levels above debug. When I develop
> larger applications, it tends to be hard to debug when I have sooo much
> output potentially coming out with just one debug level. If there were a
> couple more levels I could easily throttle back the logging for the
> certain types of things that I am debugging. I have developed a very
> simple logging perl module that has the following levels: DISABLED,
> FATAL, ERROR, WARN, INFO, DEBUG, EXDG (extensive debug), & DUMP (mostly
> used for logging where I use Data::Dumper).
>

[log4perl-devel] New logging levels possible?

[Workman, J. <joe...@gs...>]

I LOVE Log4Perl, you guys rock for developing this!!!! Although I do
wish there were a couple more logging levels above debug. When I develop
larger applications, it tends to be hard to debug when I have sooo much
output potentially coming out with just one debug level. If there were a
couple more levels I could easily throttle back the logging for the
certain types of things that I am debugging. I have developed a very
simple logging perl module that has the following levels: DISABLED,
FATAL, ERROR, WARN, INFO, DEBUG, EXDG (extensive debug), & DUMP (mostly
used for logging where I use Data::Dumper).=20

How difficult would is be to add more legging levels to Log4Perl? Could
it be done through a new sub-class . . . I would be willing to develop
it if someone were to point me in the right direction :o)

Thanks
Joe

Re: [log4perl-devel] log4perl and Log::Dispatch::ApacheLog, debug msgs getting default PatternLayout

[John O. <joh...@o-...>]

Mike Schilli wrote:

>On Tue, 13 Jun 2006, John ORourke wrote:
>  
>
>>"[Tue Jun 13 16:02:21 2006] [debug] ApacheLog.pm(95):
>>Apache2::ScriptSite::authen - entered handler"
>>(looks like a PatternLayout of "%F(%L): %M - %m")
>>    
>>
>Strange. I'm not quite sure if the apache logger does anything to
>the message, but if you use the simple file appender of the
>  
>
Found in the Apache2::Log documentation:

"The filename and the line number of the caller are logged only if
Apache2::Const::LOG_DEBUG is used (because that's how Apache 2.0 logging
mechanism works)."

Sorry I didn't see it sooner, thanks anyway!

John

Re: [log4perl-devel] appender initialisation issue

[Mike S. <m...@pe...>]

On Thu, 15 Jun 2006, Roger Day wrote:

> My logging situation is complex - the pseudo-code looks like this:
>
> <initialise main log>
> log to main log
> :                 :
> for 1 to n of builds
>       log to main log
>       :                :
>        <swap for local log for building component>
>       log to local log
>       :               :
>       <swap to main log>
>       log to main log
>       :              :
>
> so I'm swapping appenders every so often, which is why I didn't use
> Log::Log4perl->init. In fact, I destroy the previous local-log appender.

It's not exactly a common thing to do in Log4perl, but you can certainly
do it :). I'd rather use a buffer appender for this purpose, though,
and I would just check the buffer every so often and write its content
to the appropriate file. This way, you put the logic out of Log4perl
and into your application, where it probably belongs in the first place.
But YMMV, of course.

> Or maybe I could us Log::Log4perl->init every time?

init() is usually only called once at the start of the program.

-- Mike

Mike Schilli
m...@pe...

>
> Cheers
> Roger
> At 15/06/2006 07:52:05, Mike Schilli <m...@pe...> wrote:
> >On Wed, 14 Jun 2006, Roger Day wrote:
> >
> >>   my $appender = Log::Log4perl::Appender->new(
> >>                                               "Log::Dispatch::File",
> >>                                               filename =>
> $main_logpath,
> >>                                               mode     => "append",
> >>                                               name
> >> =>$current_appender_name,
> >>                                               level=>$INFO
> >>                                              );
> >>
> >> I'm doing this, but it doesn't seem to change the level of
> initialisation.
> >> Am I doing something wrong?
> >
> >I'd recommend using a Log4perl configuration file and the file
> >appender that comes with Log::Log4perl:
> >
> >use Log::Log4perl qw(:easy);
> >
> >my $conf = q{
> >log4perl.category              = DEBUG, Logfile
> >log4perl.appender.Logfile      = Log::Log4perl::Appender::File
> >log4perl.appender.Logfile.mode = append
> >log4perl.appender.Logfile.filename = /tmp/test.log
> >log4perl.appender.Logfile.layout = Log::Log4perl::Layout::PatternLayout
> >log4perl.appender.Logfile.layout.ConversionPattern = %d %F{1} %L> %m%n
> >};
> >
> >Log::Log4perl->init(\$conf);
> >DEBUG "Hey there!";
> >
> >If you really need to use Log::Dispatch::File and the L4p API, here's
> >what I think you had in mind:
> >
> >use Log::Log4perl qw(get_logger :levels);
> >
> >my $logger = get_logger("");
> >my $appender = Log::Log4perl::Appender->new(
> >"Log::Dispatch::File",
> >filename  =>  "woot.txt",
> >mode      => "append",
> >name      => "quack",
> >min_level => "debug",
> >);
> >$logger->add_appender($appender);
> >
> >$logger->debug("waaa!");
> >
> >-- Mike
> >
> >Mike Schilli
> >m...@pe...
> >
>

Re: [log4perl-devel] log4perl and Log::Dispatch::ApacheLog, debug msgs getting default PatternLayout

[Mike S. <m...@pe...>]

On Tue, 13 Jun 2006, John ORourke wrote:

> The problem is, that normal lines come out like this: (note that Apache
> adds the date/time and level)
>
> "[Tue Jun 13 16:02:21 2006] [info] DataSite::Payment::new - successfully
> loaded WorldPay"
> (ie. that is the "%M - %m" layout I've specified)
>
> but debug messages come out like this:
>
> "[Tue Jun 13 16:02:21 2006] [debug] ApacheLog.pm(95):
> Apache2::ScriptSite::authen - entered handler"
> (looks like a PatternLayout of "%F(%L): %M - %m")

Strange. I'm not quite sure if the apache logger does anything to
the message, but if you use the simple file appender of the
Log::Dispatch hierarchy (just for the sake of demonstrating, otherwise
I'd use Log4perl's file appender), as in

  use Log::Log4perl qw(get_logger :levels);

  my $rootlog=get_logger('');
  $rootlog->level($DEBUG);
  my $appender=Log::Log4perl::Appender->new( "Log::Dispatch::File",
      name=>'apache log', min_level=>'debug', filename => "foo.txt",
      mode => "append");
  $appender->layout(Log::Log4perl::Layout::PatternLayout->new('%M - %m%n'));
  $rootlog->add_appender($appender);

  $rootlog->debug("debug message");
  $rootlog->error("error message");

you'll see

    main:: - debug message
    main:: - error message

in the logfile as expected. Note that I've added "%n" to the layout to
include a line break.

Mike Schilli
m...@pe...

Re: [log4perl-devel] appender initialisation issue

[Roger D. <rog...@gl...>]

My logging situation is complex - the pseudo-code looks like this:

<initialise main log>
log to main log
:                 : 
for 1 to n of builds
      log to main log
      :                :
       <swap for local log for building component>
      log to local log
      :               :
      <swap to main log>
      log to main log
      :              :

so I'm swapping appenders every so often, which is why I didn't use 
Log::Log4perl->init. In fact, I destroy the previous local-log appender. 
Or maybe I could us Log::Log4perl->init every time?

Cheers
Roger
At 15/06/2006 07:52:05, Mike Schilli <m...@pe...> wrote:
>On Wed, 14 Jun 2006, Roger Day wrote:
>
>>   my $appender = Log::Log4perl::Appender->new(
>>                                               "Log::Dispatch::File",
>>                                               filename => 
$main_logpath,
>>                                               mode     => "append",
>>                                               name
>> =>$current_appender_name,
>>                                               level=>$INFO
>>                                              );
>>
>> I'm doing this, but it doesn't seem to change the level of 
initialisation.
>> Am I doing something wrong?
>
>I'd recommend using a Log4perl configuration file and the file
>appender that comes with Log::Log4perl:
>
>use Log::Log4perl qw(:easy);
>
>my $conf = q{
>log4perl.category              = DEBUG, Logfile
>log4perl.appender.Logfile      = Log::Log4perl::Appender::File
>log4perl.appender.Logfile.mode = append
>log4perl.appender.Logfile.filename = /tmp/test.log
>log4perl.appender.Logfile.layout = Log::Log4perl::Layout::PatternLayout
>log4perl.appender.Logfile.layout.ConversionPattern = %d %F{1} %L> %m%n
>};
>
>Log::Log4perl->init(\$conf);
>DEBUG "Hey there!";
>
>If you really need to use Log::Dispatch::File and the L4p API, here's
>what I think you had in mind:
>
>use Log::Log4perl qw(get_logger :levels);
>
>my $logger = get_logger("");
>my $appender = Log::Log4perl::Appender->new(
>"Log::Dispatch::File",
>filename  =>  "woot.txt",
>mode      => "append",
>name      => "quack",
>min_level => "debug",
>);
>$logger->add_appender($appender);
>
>$logger->debug("waaa!");
>
>-- Mike
>
>Mike Schilli
>m...@pe...
>

Re: [log4perl-devel] appender initialisation issue

[Roger D. <rog...@gl...>]

cheers - I discovered that $logger->level($INFO) also works as well.

Roger
At 14/06/2006 19:55:25, log...@li... 
wrote:
>Roger Day wrote:
>
>>                                              level=>$INFO
>>
>>
>I believe that should be 'min_level'.
>
>>I'm doing this, but it doesn't seem to change the level of 
initialisation.
>>Am I doing something wrong?
>>
>>
>John
>
>
>
>_______________________________________________
>log4perl-devel mailing list
>log...@li...
>https://lists.sourceforge.net/lists/listinfo/log4perl-devel
>

Re: [log4perl-devel] appender initialisation issue

[Mike S. <m...@pe...>]

On Wed, 14 Jun 2006, Roger Day wrote:

>   my $appender = Log::Log4perl::Appender->new(
>                                               "Log::Dispatch::File",
>                                               filename =>  $main_logpath,
>                                               mode     => "append",
>                                               name
> =>$current_appender_name,
>                                               level=>$INFO
>                                              );
>
> I'm doing this, but it doesn't seem to change the level of initialisation.
> Am I doing something wrong?

I'd recommend using a Log4perl configuration file and the file
appender that comes with Log::Log4perl:

  use Log::Log4perl qw(:easy);

  my $conf = q{
  log4perl.category              = DEBUG, Logfile
  log4perl.appender.Logfile      = Log::Log4perl::Appender::File
  log4perl.appender.Logfile.mode = append
  log4perl.appender.Logfile.filename = /tmp/test.log
  log4perl.appender.Logfile.layout = Log::Log4perl::Layout::PatternLayout
  log4perl.appender.Logfile.layout.ConversionPattern = %d %F{1} %L> %m%n
  };

  Log::Log4perl->init(\$conf);
  DEBUG "Hey there!";

If you really need to use Log::Dispatch::File and the L4p API, here's
what I think you had in mind:

  use Log::Log4perl qw(get_logger :levels);

  my $logger = get_logger("");
  my $appender = Log::Log4perl::Appender->new(
    "Log::Dispatch::File",
    filename  =>  "woot.txt",
    mode      => "append",
    name      => "quack",
    min_level => "debug",
  );
  $logger->add_appender($appender);

  $logger->debug("waaa!");

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] appender initialisation issue

[John O. <joh...@o-...>]

Roger Day wrote:

>                                              level=>$INFO
>  
>
I believe that should be 'min_level'.

>I'm doing this, but it doesn't seem to change the level of initialisation. 
>Am I doing something wrong?
>  
>
John

[log4perl-devel] appender initialisation issue

[Roger D. <rog...@gl...>]

  my $appender = Log::Log4perl::Appender->new(
                                              "Log::Dispatch::File",
                                              filename =>  $main_logpath,
                                              mode     => "append",
                                              name 
=>$current_appender_name,
                                              level=>$INFO
                                             );

I'm doing this, but it doesn't seem to change the level of initialisation. 
Am I doing something wrong?

Roger

[log4perl-devel] log4perl and Log::Dispatch::ApacheLog, debug msgs getting default PatternLayout

[John O. <joh...@o-...>]

Hi folks,

I'm not sure how active this list is (first post) but hopefully someone 
can advise!  I'm seeing messages at 'debug' level getting one 
PatternLayout, but all higher levels get the layout I specify.

In more detail...

(Incidentally I've patched Log::Dispatch::ApacheLog to work with 
mod_perl 2 - sent patch to Dave Rolsky, awaiting response)
I'm seeing problem which looks like it's log4perl related.  I'm doing this:

use Log::Log4perl qw(get_logger :levels);
my $s=Apache2::ServerUtil->server();
my $rootlog=get_logger('');
$rootlog->level($DEBUG);
my $appender=Log::Log4perl::Appender->new( "Log::Dispatch::ApacheLog",
           name=>'apache log', min_level=>'debug', apache=>$s
                                    );
$appender->layout(Log::Log4perl::Layout::PatternLayout->new('%M - %m'));
$rootlog->add_appender($appender);

The problem is, that normal lines come out like this: (note that Apache 
adds the date/time and level)

"[Tue Jun 13 16:02:21 2006] [info] DataSite::Payment::new - successfully 
loaded WorldPay"
(ie. that is the "%M - %m" layout I've specified)

but debug messages come out like this:

"[Tue Jun 13 16:02:21 2006] [debug] ApacheLog.pm(95): 
Apache2::ScriptSite::authen - entered handler"
(looks like a PatternLayout of "%F(%L): %M - %m")

I have no idea where that layout is coming from!  Apache doesn't do 
anything special I believe.

any help appreciated,
John

[log4perl-devel] Log::Log4perl 1.05 released

[Mike S. <m...@pe...>]

Hi all,

just released Log::Log4perl 1.05 to Sourceforge, here's what's new
in this release:

1.05 2006/06/10

*   (ms) Added recreate signal handler to L4p::Appender::File for
         newsyslog support. Two new FAQ entries on dealing with
         newsyslog and log files being removed by external apps.
*   (ms) L4p::Config::Watch no longer sets the global $SIGNAL_CAUGHT by
         default but uses an instance variable instead to prevent
         clobbering L4p's config and watch mechanism.
*   (ms) die() on undefined configuration (rt 18103 by jus...@wa...)
*   (ms) Hugh Esco submitted a FAQ on where to put logfiles
*   (ms) Applied patch provided by Chia-liang Kao to suppress an error
         message and skip tests in the suite when DBI is missing.

You can download it at

    http://log4perl.sourceforge.net

If all goes well, it's going to CPAN in a couple of days. Let me know
if you find any issues!

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] Log-Log4perl-1.04 released

[Lars T. <la...@th...>]

Kevin M. Goess wrote:
> Sorry for the delay.  I just upgraded XML::DOM to 1.44 on my ancient
> perl 5.6.1 instance, and the tests run without a problem.
> 
> This is log4perl v. 1.05, not 1.04 like you mentioned before.  Maybe
> that's the problem?  I don't know what else to suggest right now.  I can

Is 1.05 available anywhere? I notice it's not (yet) on neither
SourceForge nor CPAN. I'd like to try out whether this fixes the issue.

Otherwise, the only remaining thing to try is the 5.6.1/5.6.2 perl version.

/Lars

Re: [log4perl-devel] Log-Log4perl-1.04 released

[Kevin M. G. <kn...@go...>]

On May 29, 2006, at 7:13 AM, Lars Thegler wrote:

> Lars Thegler wrote:
>> Kevin M. Goess wrote:
>>> Lars Thegler wrote:
>>>> Running the test suite under perl 5.6.2, I get 3 of the cases  
>>>> failing
>>>> with this:
>>>>
>>>> --cut--
>>>> Can't locate object method "SWASHNEW" via package  
>>>> "utf8" (perhaps you
>>>> forgot to load "utf8"?) at
>>>> blib/lib/Log/Log4perl/Config/DOMConfigurator.pm line 270.
>>>> --cut--
>>>>
>>>> I can make this go away by adding "use utf8;" just before the  
>>>> offending
>>>> line, but I'm sure there is a better way.
>>>>
>>>> And why these tests passes on 5.005_03 and 5.8.8, but fails on  
>>>> 5.6.2, I
>>>> have no idea.
>>>
>>> No problems for me on perl 5.6.1.  It sounds like it could be a
>>> problem in XML::DOM, which version of that are you using? (I used  
>>> 1.29).
>>
>> Ah, good point. I'm using the current version on CPAN, which is 1.44.
>> 1.29 is ancient, released sometime back in 2001. Maybe that is why  
>> your
>> tests are passing?
>
> Is there any chance that I could get you to check up on your XML::DOM
> version, and rerun the tests with the latest XML::DOM?

Sorry for the delay.  I just upgraded XML::DOM to 1.44 on my ancient  
perl 5.6.1 instance, and the tests run without a problem.

This is log4perl v. 1.05, not 1.04 like you mentioned before.  Maybe  
that's the problem?  I don't know what else to suggest right now.  I  
can try installing perl 5.6.2, but not right now, I have to go to  
sleeeeeeeppp......zzzzzzz

--
Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217

Re: [log4perl-devel] Log-Log4perl-1.04 released

[Lars T. <la...@th...>]

Lars Thegler wrote:
> Kevin M. Goess wrote:
>> Lars Thegler wrote:
>>> Running the test suite under perl 5.6.2, I get 3 of the cases failing
>>> with this:
>>>
>>> --cut--
>>> Can't locate object method "SWASHNEW" via package "utf8" (perhaps you
>>> forgot to load "utf8"?) at
>>> blib/lib/Log/Log4perl/Config/DOMConfigurator.pm line 270.
>>> --cut--
>>>
>>> I can make this go away by adding "use utf8;" just before the offending
>>> line, but I'm sure there is a better way.
>>>
>>> And why these tests passes on 5.005_03 and 5.8.8, but fails on 5.6.2, I
>>> have no idea.
>>
>> No problems for me on perl 5.6.1.  It sounds like it could be a
>> problem in XML::DOM, which version of that are you using? (I used 1.29).
> 
> Ah, good point. I'm using the current version on CPAN, which is 1.44.
> 1.29 is ancient, released sometime back in 2001. Maybe that is why your
> tests are passing?

Is there any chance that I could get you to check up on your XML::DOM
version, and rerun the tests with the latest XML::DOM?


/Lars

Re: [log4perl-devel] problems installing...

[Kevin M. G. <kn...@go...>]

 > Error: Failed to download URL
 > ___http://log4perl.sourceforge.net/ppm/Log-Log4perl.p_
 > pd: 500 Can't connect to log4perl.sourceforge.net:80 (connect: Unknown
 > error)

Well, can you get to http://log4perl.sourceforge.net from that computer? 
  If you click on that link in a browser, does it come up?  If not, 
you're having local network problems.

If it does come up, then try the install again now.  There was probably 
a temporary problem on the internet somewhere between you and sourceforge.

[log4perl-devel] problems installing...

[<Ste...@no...>]

Hello,

I just tried to install log4perl on my laptop which is running perl,
v5.8.7 built for MSWin32-x86-multi-thread.
Below is the output of "perl --version":

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\novakovi>perl --version

This is perl, v5.8.7 built for MSWin32-x86-multi-thread
(with 7 registered patches, see perl -V for more detail)

Copyright 1987-2005, Larry Wall

Binary build 813 [148120] provided by ActiveState
http://www.ActiveState.com
ActiveState is a division of Sophos.
Built Jun  6 2005 13:36:37

Perl may be copied only under the terms of either the Artistic License
or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using `man perl' or `perldoc perl'.  If you have access to
the
Internet, point your browser at http://www.perl.org/, the Perl Home
Page.

I tried following the "Install on ActiveState 5.8.*" instructions on the
web page:

http://log4perl.sourceforge.net/releases/Log-Log4perl/docs/html/Log/Log4
perl/FAQ.html#f7dc3

I got the error message (after running ppm> install Log-Log4perl
command) saying that it could not contact

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\novakovi>ppm
PPM - Programmer's Package Manager version 3.2.
Copyright (c) 2001 ActiveState Corp. All Rights Reserved.
ActiveState is a division of Sophos.

Entering interactive shell. Using Term::ReadLine::Perl as readline
library.

Type 'help' to get started.

ppm> install Log-Log4perl
Error: Failed to download URL
http://log4perl.sourceforge.net/ppm/Log-Log4perl.p
pd: 500 Can't connect to log4perl.sourceforge.net:80 (connect: Unknown
error)

Sincerely,

Steven Novakovich
Nokia Networks
Consulting & Integration (C&I)

6000 Connection Drive 4E-3-325
Irving Texas 75039
972.374.1217 office
469.877.6609 mobile
972.374.0200 fax

Re: [log4perl-devel] Log-Log4perl-1.04 released

[Lars T. <la...@th...>]

Kevin M. Goess wrote:
> Lars Thegler wrote:
>> Running the test suite under perl 5.6.2, I get 3 of the cases failing
>> with this:
>>
>> --cut--
>> Can't locate object method "SWASHNEW" via package "utf8" (perhaps you
>> forgot to load "utf8"?) at
>> blib/lib/Log/Log4perl/Config/DOMConfigurator.pm line 270.
>> --cut--
>>
>> I can make this go away by adding "use utf8;" just before the offending
>> line, but I'm sure there is a better way.
>>
>> And why these tests passes on 5.005_03 and 5.8.8, but fails on 5.6.2, I
>> have no idea.
> 
> No problems for me on perl 5.6.1.  It sounds like it could be a problem 
> in XML::DOM, which version of that are you using? (I used 1.29).

Ah, good point. I'm using the current version on CPAN, which is 1.44. 
1.29 is ancient, released sometime back in 2001. Maybe that is why your 
tests are passing?

/Lars

Re: [log4perl-devel] Log-Log4perl-1.04 released

[Kevin M. G. <ke...@go...>]

Lars Thegler wrote:
> Running the test suite under perl 5.6.2, I get 3 of the cases failing
> with this:
> 
> --cut--
> Can't locate object method "SWASHNEW" via package "utf8" (perhaps you
> forgot to load "utf8"?) at
> blib/lib/Log/Log4perl/Config/DOMConfigurator.pm line 270.
> --cut--
> 
> I can make this go away by adding "use utf8;" just before the offending
> line, but I'm sure there is a better way.
> 
> And why these tests passes on 5.005_03 and 5.8.8, but fails on 5.6.2, I
> have no idea.

No problems for me on perl 5.6.1.  It sounds like it could be a problem 
in XML::DOM, which version of that are you using? (I used 1.29).

Re: [log4perl-devel] perl5.8/POE/Log4perl interaction bug

[Mike S. <m...@pe...>]

On Sun, 23 Apr 2006, Mike Schilli wrote:

> Looks like there's an interaction bug between perl5.8/POE/Log4perl,
> could be related to what we've seen on the l4p mailing list
> earlier ...

... or not:

  From: gil...@po...
  To: po...@pe...
  Subject: glibc detected *** double free or corruption (fasttop): 0x09511d40
  Date: Sun, 23 Apr 2006 19:11:09 -0700

  I am not getting this error anymore. I read through the manual and
  discovered that I had made a cardinal sin in POE. My team had built
  several components that refer back to _start.

  We've recoded and now we never go back to the _start state and the SV
  Scalar error and double free error is gone :-)

  Thanks for all your input.

  Gil...@po...
  Position Research

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] perl5.8/POE/Log4perl interaction bug

[Mike S. <m...@pe...>]

Looks like there's an interaction bug between perl5.8/POE/Log4perl,
could be related to what we've seen on the l4p mailing list
earlier ...

-- Mike

Mike Schilli
m...@pe...

---------- Forwarded message ----------
From: sungo <su...@po...>
To: Steve Peters <st...@fi...>
Cc: Gil Vidals <gil...@po...>, po...@pe...,
     'Justin Tang' <jus...@po...>,
     'Robert Gavina' <rob...@po...>
Subject: Re: glibc detected *** double free or corruption (fasttop):
    0x09511d40
Date: Sun, 23 Apr 2006 12:34:36 -0400

Steve Peters wrote:

> The code would also be useful to the Perl core and, I assume, to POE as
> test cases to ensure that this bug does not resurface.

I've seen this bug at my day job The "offending" perl code, in general,
provides very little clue as to the cause of the problem. We're looking
at a complex interaction of perl5.8, poe, and log4perl deep under the
covers. We cleared our first run in with the bug at work by removing a
goto of all things.

POE has a very long history and exposing fun and psychotic bugs in the
perl core. We push perl in odd places and that's why people like Andreas
run POE's test suite when testing new perls. modperl, PPI, and several
other modules are used in a similar fashion.

 From what I've read and seen of the bug, I think the only "test" that's
going to help our users is a documentation note discussing the
interaction of these factors on perl5.8.7. It is possible that p5p will
come up with some crazy fix we can use the stop the problem (ie the
CRIMSON_HACK) but I think that's probably a longshot with this bug.

> Agreed.  Better still a perl built with the Configure option
> -Doptimize="-g" would be helpful to produce a coredump with debugging
> symbols to see where the errors are occurring.

More importantly, add -O0.

sungo.

Re: [log4perl-devel] Log-Log4perl-1.04 released

[Lars T. <la...@th...>]

Mike Schilli wrote:
> just submitted the 1.04 maintenance release to log4perl.sf.net, with
> the following changes:

Running the test suite under perl 5.6.2, I get 3 of the cases failing
with this:

--cut--
Can't locate object method "SWASHNEW" via package "utf8" (perhaps you
forgot to load "utf8"?) at
blib/lib/Log/Log4perl/Config/DOMConfigurator.pm line 270.
--cut--

I can make this go away by adding "use utf8;" just before the offending
line, but I'm sure there is a better way.

And why these tests passes on 5.005_03 and 5.8.8, but fails on 5.6.2, I
have no idea.

Can anybody shed more light on this?

/Lars

Re: [log4perl-devel] SV (Scalar Variable) error in log4perl

[Mike S. <m...@pe...>]

On Sun, 16 Apr 2006, Kevin M. Goess wrote:

> On Apr 13, 2006, at 11:49 AM, Gil Vidals wrote:
> > Kevin, We're using log4perl in the Perl Object Environment (POE)
>
> I haven't worked with POE at all yet, although I used your question
> as an excuse to take a look at it this weekend for the first time.
> After a superficial browsing of the POE docs, I don't see any reason
> why the Log4perl and POE shouldn't be able to play well together, and
> on Google I see at least one reference to "I have used POE with
> Log4perl before and it was a dream."

I have used POE and Log::Log4perl many times and I'm not aware
of any interaction problems.

> > I'm updating all
> > calls to logger to use the standard init and avoid the
> > "init_and_watch".
> > ...
> > Perhaps the state machine doesn't play well with the dynamic
> > component of
> > init_and_watch, which obviously has to check to see if a file has
> > changed
> > every so often. In a sense "init_and_watch" is kind of a state
> > machine that
> > is triggered by a file change. Since POE is a state machine too,
> > there could
> > be a clash?

There's nothing magical about POE or Log::Log4perl, and their 'states'
are truly orthogonal and they're not sharing any 'state machine code'.
But of course there could be a bug in either of them.

Is there a short snippet of code you could provide that reproduces
the problem? If it's not-so-short, no problem, it's just easier to
track down a problem with actual code in hand.

-- Mike

Mike Schilli
m...@pe...

>
> It's not inconcievable.  Do the problems happen after the timestamp
> on your log4perl.conf file is changed?  The init_and_watch stuff
> shouldn't make any difference to anything if the conf file never
> changes because it would never get called.
>
> So taking out init_and_watch in favor of init sounds like a good
> thing to try--did that help?  If it did, can you forward  a tiny
> sample of code that shows the way you're using POE and Log4perl and
> we could take a look at it.
>
> Hopefully this doesn't sound like ducking the issue, but did you try
> posing the question to the POE folks?  A look at Google suggests POE
> users have seen this error before when not using log4perl. I suspect
> it's something about the magical POE enviroment, so they might have
> something useful to say about it.
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel
>

Re: [log4perl-devel] SV (Scalar Variable) error in log4perl

[Kevin M. G. <cp...@go...>]

On Apr 13, 2006, at 11:49 AM, Gil Vidals wrote:
> Kevin, We're using log4perl in the Perl Object Environment (POE)

I haven't worked with POE at all yet, although I used your question  
as an excuse to take a look at it this weekend for the first time.   
After a superficial browsing of the POE docs, I don't see any reason  
why the Log4perl and POE shouldn't be able to play well together, and  
on Google I see at least one reference to "I have used POE with  
Log4perl before and it was a dream."

> I'm updating all
> calls to logger to use the standard init and avoid the  
> "init_and_watch".
> ...
> Perhaps the state machine doesn't play well with the dynamic  
> component of
> init_and_watch, which obviously has to check to see if a file has  
> changed
> every so often. In a sense "init_and_watch" is kind of a state  
> machine that
> is triggered by a file change. Since POE is a state machine too,  
> there could
> be a clash?

It's not inconcievable.  Do the problems happen after the timestamp  
on your log4perl.conf file is changed?  The init_and_watch stuff  
shouldn't make any difference to anything if the conf file never  
changes because it would never get called.

So taking out init_and_watch in favor of init sounds like a good  
thing to try--did that help?  If it did, can you forward  a tiny  
sample of code that shows the way you're using POE and Log4perl and  
we could take a look at it.

Hopefully this doesn't sound like ducking the issue, but did you try  
posing the question to the POE folks?  A look at Google suggests POE  
users have seen this error before when not using log4perl. I suspect  
it's something about the magical POE enviroment, so they might have  
something useful to say about it.