From: Mike S. <m...@pe...> - 2006-04-17 06:15:14
|
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 > |