Scott,
Is it possible that the Jakarta libraries are reconfiguring log4j on you after your
configuration has run? I ran into this with the open source Joram JMS implemnetation.
As soon as I started using the Joram classes, some static Joram code would
reconfigure log4j and blow away my
Jeff,
Log4j uses org.apache.log4j.config.PropertySetter to set the properties specified in
the param tag. PropertySetter can only set properties that are assignable from the
following types: String, Integer, Long, Boolean, and Priority. In order to set the
ResourceBundle property on a logger
Hi,
Unfortunately, I am not using JBoss so I am not sure why that is happening to you.
Here is the javadoc from LogManger.setRepositorySelector()
/**
Sets codeLoggerFactory/code but only if the correct
emguard/em is passed as parameter.
pInitally the guard is null. If the
Kevin,
I am not sure I understand what you are trying to do. There is no reason to create
all loggers at startup. They will automatically be created and cached by the
Hierarchy (the default LoggerRepository) when they are first used. You do not need
your own Logger Factory for that. I am
Stefan,
I cannot seem to find your stack trace so I am not sure exactly what the nature of
your problem is. I suspect that you have your version of the Logger class in the
system classpath of the JBoss app server. That would require you to restart JBoss.
If your log classes are deployed
Stefan,
Log4j caches instances of loggers that have already been created (as indicated in the
link you provided). Are you creating the loggers you are accessing in your
configuration file or are they being created for the first time when you execute
OurLogger.getLogger(XXX.class.getName())?
Stefan,
The only logger created in that file is org.eupki.ca. I think you will need
categoryFactory class=yourcategoryfactoryclass/ in your XML config file. If you
use a RepositorySelector that returns a LoggerRepository impl that always uses your
factory then you should avoid the
Hi,
The bug that you are referring to has not been resolved. You can try the work-around
that I posted in http://marc.theaimsgroup.com/?l=log4j-userm=106312777504479w=2.
That worked for me and now the loggers returned by Logger.getLogger(class) are my
Logger subclasses.
Here is the basic
Wolfram,
I cannot seem to find your source code and DTD. However, from what I understand of
your code you are using the LoggerFactory declared in the xml file to load Logger and
Category instances that are defined in the config file to be consistent with the
behavior of PropertyConfigurator
Yes,
Under the distribution package look in ../src/java/org/apache/log4j/xml/examples
-Mark
-Original Message-
From: Digambar, Shaligram (Consultant)
[mailto:[EMAIL PROTECTED]
Sent: Thursday, September 04, 2003 11:09 AM
To: 'Log4J Users List'
Subject: log4j.xml file
Are there any
Ceki,
Thank you - that fixed my problem! The characters 0xEFBBBF are the UTF-8 Byte Order
Mark that is part if the unicode standard. Apparently, Crimson can't handle UTF-8
while Xerces can.
On another topic, do you if there any is interest in the patch I contributed to fix
the LoggerFactory
Ceki,
I am using log4j 1.2.8. I am using the JRun application server which packages up
Crimson version 1.1.
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 03, 2003 11:43 AM
To: Log4J Users List
Subject: Re: Problem with Crimson parser
Mark,
Ceki,
I tried initializing with a sample xml config file from the distribution and it works
fine with Crimson. I tried playing around with DOCTYPE and other preamable elements
in my document but I could not get it to work. I have attached my config file to this
email in case you can figure
Hi,
I am having trouble parsing my config file with DOMConfigurator using Crimson. I have
no problems with Xerces but when I use crimson I get the exception at the end of this
message.
Somehow, Crimson is not able to find the dtd using the SYSTEM identifier log4j.dtd. I
noticed there was a
Hi,
I am interested in internationalizing my logging messages and I see that I can use the
l7dlog() methods on Logger to accomplish this. I am interested only in l7d at the
source rather than at the destination so these methods are perfect (i.e. I don't need
to do l7d in the appenders). Like
15 matches
Mail list logo
