The behavior you see on Win2k is to be expected assuming that the JVM was
started from the location "G:\jakarta-tomcat-5.0.16". If you provide a
relative path for the log file, the path will be relative to wherever the
JVM started. If you want the file to go somewhere specific on your system
Quoting Emma Gabriela Guevara <[EMAIL PROTECTED]>:
> We are trying to use Log4J in our Struts app (we are using JDK 1.3).
> But we keep getting errors.
> Can anyone help us?
>
Not until you tell us what the errors are.
Jake
-
You need to do a LogManager.shutdown() upon application shutdown. That will
solve problems with Log4j keeping handles on files. Use a Servlet Context
Listener for this.
Jake
Quoting Antony Paul <[EMAIL PROTECTED]>:
> Hi all,
> I am using Tomcat 4.1.27 + log4j 1.2.8+Win2k sp4. I have some
First, you should use instead of . Second, the is
just a special kind of , the root one. What you want to do is set
a separate (of which, BTW, will inherit from so it will use
's appender). Something like this...
Also, normally, I set the logger to a higher threshold
Something like this should work. Notice the elements (copied from
some earlier post on the user list)
You have a 3 choices...
1. Don't provide log4j.jar and log4j.properties for each
application. Instead, use the single server-provided instance of Log4j
along with a single log4j config file (again, at the server level). You
would initialize Log4j once on server startup, not for each applicat
>I don't remember receiving this error with the previous version of log4j.
>Do I need to do something different?
Maybe you should try an earlier version of Log4j and verify this
statement. I'm guessing you'll get the same behavior. Try adding
debug="true" to your below. Also, you probably
sh
mail.jar shouldn't be in WEB-INF/lib as it is an endorsed library (anything
java.* javax.*, org.xml.*, org.w3c.dom.*). Put it in
CATALINA_HOME/common/lib or endorsed. This allows Tomcat to use the mail
api as well as your apps and will avoid troubles when/if the JDK actually
includes the mail
At 11:09 AM 11/29/2003 +1100, you wrote:
It should have created 3 jar files, one with chainsaw in it's name. Ant may
be ignoring chainsaw's build phase because you are missing some dependant
jars.
Have you edited the build.properties.sample? (I've found that you have to
make sure there is not BOTH
You keep insisting on using non-url syntax for your setup even when you
reference the correct URL syntax. Do this...
java -Dlog4j.configuration=file:/c:/jarfiles/log4j.properties
org.pdfbox.searchengine.lucene.LucenePDFDocument C:\\pdf\h6603lab4.pdf
Also, why are you saying...
c:\\jarfiles\log4j
At 04:02 PM 11/23/2003 -0500, you wrote:
Hi,
I don't know whether anyone has answered this already (I could not
find). I am using Websphere application server 5.0 (EJB Container). I am
using log4j for the logging in my ejb's. I have created a start up bean
(special case of a stateless session
No, his statement is incorrect. You can utilize a repository selector to
separate logging using a single instance of log4j.jar. Read here...
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/AppContainerLogging
In fact, if you use Tomcat, even without using a repository selector,
Have you tried "
Jake
At 04:47 PM 11/21/2003 +0100, you wrote:
Hi everyone,
I have a problem with adding double quotes in a conversion pattern for
PatternLayout specified in an XML configuration.
Let's see the XML configuration fragment :
Does JRun not load from the WebappClassLoader first? Tomcat does this, and
I believe the servlet spec defines this behavior (but don't quote me on
that). Sounds like the same thing JBoss does by default. The way Tomcat
works makes things much easier to work with since libraries in the server
At 01:16 PM 11/17/2003 +0100, you wrote:
I'm NOT stupid...
I hope.
I'm sure, not.
The reason I joined this mailing list was because I had a
auto-configuration problem, but it "went away"... BUT now it's back. Oh joy.
- I have Tomcat 4.1.12 with 1 context (my application).
you should upgrade. 4
This functionality exists in log4j sandbox as an appender+servlet context
listener. It sends app logging info to the same log file which is
configured for your servlet context. Here is what the config looks like...
in log4j.xml...
in web.xml.
Threshold parameter?
see above.
Thank you,
Otis
Jake
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
---- On Fri, 07 Nov 2003, Jacob Kjome ([EMAIL PROTECTED]) wrote:
>
> 1. You sho
look at configureAndWatch() in the configurators.
However, I wouldn't use this in a container as the thread will run until
the JVM is shut down. There is no manual way to stop it.
Look for Mark Womack's watchdogs in the next version of Log4j for a better
solution. Here's an old message with s
1. You should use , not
2. If you don't want to inherit logging from the logger, you should
add additivity="false" to the UserTracker
3. You might want to set the 's you prefer as well
Jake
At 12:06 PM 11/7/2003 -0500, you wrote:
Hello,
I am using log4j 1.2.8 (under JBoss). I'm having a
getting resources from WEB-INF is specific to a servlet application. If
you need to get the config file from both places, then put your config file
back into WEB-INF/classes/config. At that point, the code below will work
and you can change your path in the servlet example to this...
context.
It would help if you actually obtained your servlet context. Right now, it
is null.
ServletContext context = this.getServletContext()
Jake
At 10:47 AM 11/7/2003 +1100, you wrote:
Jake,
Thank you for your time. I have made the changes to the code as you
have suggested. It compiled without prob
You need to look at my code closer. "context" is a ServletContext. You
can use it to access stuff anywhere in the webapp.
URL url = context.getResource("/WEB-INF/config/log4j.properties");
PropertyConfigurator.configure(url);
And, of course, you can also use the InputStream way if you want, but
At 05:39 PM 11/6/2003 +0100, you wrote:
>You never answered my question about how your repository selector
>distinguishes between logger repositories.
What do you mean by this? Should I do something special in your solution
ContextClassLoaderSelector that you put in the sandbox?
There is both a C
istener to do
this. Otherwise, you can set something up in the container to set the
repository selector before any webapps get deployed.
Try all that and let me know how things work.
Jake
-Original Message-----
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: November 6, 2003 12:50 AM
I tried implementing a custom repository selector (taken
from the sandbox by Jacob Kjome) in my webapp so that both hierarchies
worked at the same time without any conflicts. Even though it's supposed to
fix the problem, the webapp logging overwrites the server appenders. I have
this warning:
At 11:29 AM 11/5/2003 +1100, you wrote:
I am using the Log Tag Library 1.0 from Jakarta Project.
In the Installation document, it suggest that in order to initialize
Log4j automatically, the log4j.properties file will have to be placed in
/WEB-INF/classes.
How could I put the log4j.properties file
So, you are getting no logging from your app or you are getting some, but
not in the format you set? And with the hibernate logging, is it logging
to your specified format or some other similar format? What I'm getting at
is whether Hibernate might be including a log4j.properties or log4j.xml
Use two separate file appenders, each pointing to its own file
(eg application.log and junit.log). Then, I recommend that you define
stuff in the logger that you'd want for your most common logging
activities; probably the stuff going to application.log. After that,
define a logger for
You said that the jars are in a directory that is in the
classpath. However for the app to actually work, you must have had the
jars themselves in the classpath. Are you sure that you have the directory
that contains the log4j.properties in the classpath? If not, that is the
problem. I know
At 01:31 PM 10/29/2003 +0100, you wrote:
I could reproduce the problem: it happened right after I reload the apps
using the Manager app, using the URL:
https://myserver/manager/reload?path=/webapp
I could do this several times. After a Tomcat start/stop, the logging and
rotating works. After a r
At 04:25 PM 10/24/2003 +0200, you wrote:
Some people may disagree but we have take the approach of using the
commons-logging API.
commons-logging has never been anything but a pain in the butt in every
case I've seen it used. The classloader issues are never-ending.
We have configured it to use
At 10:23 AM 10/21/2003 -0400, you wrote:
It's best not to get offended by Hani - if you go back and read the
archives, you'll find that every entry has the same kind of attitude, so
it's really a bit of a joke. It is called "The Bileblog", after all.
I think it isn't so much that he is being offen
Thanks,
It was nice of you to put that comparison together. However, did you have
a particular point you were trying to make? There have been lots of
discussions on the list about how many/few levels are appropriate. Have
you perused those already? Do you have an opinion in regard to what l
don't play
with JBoss much, so I have never tested the above statement. Maybe someone
can try it out and report back to the list?
Jake
At 12:40 AM 10/17/2003, Jacob Kjome wrote:
Try reading this and see if it helps out:
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JP
here noone
responded on).
What is very useful is setting the log4j debugging on
(-Dlog4j.debug=on). And if you search for "using" you might find that
log4j is using multiple configuration files. Currently I'm trying to
figure out if that is the case with my problem.
Tom
Jacob Kjome wr
Try reading this and see if it helps out:
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/AppContainerLogging
I'm not sure exactly the problem under JBoss, but they do seem to have the
concept of a single classloader, which seems to cause grief for people who
want to deploy their p
Add log4.jar to common/lib of the Tomcat part of the bundle. Not sure why
it would work on one server, but not on another, though.
Jake
At 01:44 PM 10/13/2003 +0200, you wrote:
Hi!
I am trying to move the jboss-3.2.1_tomcat-4.1.24 container from one
server to another. On the old server every
At 06:56 AM 10/7/2003 -0700, you wrote:
log4j.appender.DISSLog.File=diss.log
That's the culprit. Notice that you simply specified the log file
name. This is written out, as you've discovered, to a location relative to
the directory where the JVM started. Try using something like...
log4j.appe
That is where the JVM is started from and, hence, the location to which
relatively specified files will be written. What does your config file
look like? Have you specified a directory for output of your FileAppender?
Jake
At 04:40 AM 10/7/2003 -0700, you wrote:
Hi
I'm using log4j in my web
At 11:18 AM 10/6/2003 +, you wrote:
Hi,
I have a jar that contains some EJBs where I'm logging some
informations. In the present implementation I'm initializing and
shutting down log4j via a ServletContextListener. This approach
requires the deployment of a webapp (I had to declare the
list
At 03:43 PM 10/3/2003 +, you wrote:
I am having problems getting log4j to configure from an XML file.
When I use the xml file shown below, i get the following warning in
java (1.4.1_02). Note: When I use a non-XML properties file it works
just fine.
log4j:WARN No appenders could be found for lo
At 04:03 AM 10/3/2003 -0500, you wrote:
What is NDC?
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/NDCvsMDC
Jake
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat uses commons-logging as well. Try doing this. Put a copy of
log4j.jar in CATALINA_HOME/common/lib. Also put a copy of log4j.jar in
WEB-INF/lib of your webapp. commons-logging uses some class loader
trickery that flubs up much of the time. I don't even want to know why it
does this,
At 04:06 PM 9/16/2003 +0300, you wrote:
Now, what in the world does "Cause: java.lang.IllegalArgumentException:
Attempted to reset the LoggerFactory without possessing the guard." mean?
The "guard" is a simple object that protects against re-setting of the
LoggerFactory by anyone but the one who
docs since much of Log4j
functionality is documented there.
Jake
Marc
Jacob Kjome wrote:
At 03:19 PM 9/15/2003 +0200, you wrote:
I am starting to use log4j since some weeks now and I am very pleased
with it.
The worsed thing about it is documentation I guess.
I beg to differ...
https://www.q
At 07:28 PM 9/15/2003 +0300, you wrote:
Fortunately, I can use listeners, actually, I already have a context
listener. But I'm not really sure how I can shut down log4j.
LogManager.shutdown();
Jake
-
To unsubscribe, e-mail: [EM
At 03:19 PM 9/15/2003 +0200, you wrote:
I am starting to use log4j since some weeks now and I am very pleased
with it.
The worsed thing about it is documentation I guess.
I beg to differ...
https://www.qos.ch/shop/products/clm_t.jsp
Jake
I'm still unable to comprehend why you have jboss-specific jars in Tomcat???
Also, the only thing that needs to go in the common/endorsed directory is
the XML parser. "endorsed" means that it overrides existing libraries in
the JDK. Only the xerces jar needs to go in common/endorsed because it
You can't put endorsed libraries under WEB-INF/lib. This includes both JDK
endorsed libraries (such as javax.xml.*, org.w3c.dom.*, org.xml.*) and
libraries which Tomcat treats specially such as the servlet API and xml
parsers (Xerces). Why do you need the j2ee jar there anyway? Tomcat
provid
See recent posts on the LevelRangeFilter. I think it should do what you
require.
Jake
At 07:15 PM 9/8/2003 +0100, you wrote:
Hi,
Is there a way for me to add a conditional second appender? I want to log
my data to another log, in addition to the regular log, only when a
certain condition is tr
t seem to like it, I keep gettin the URL as null.
Jacob Kjome <[EMAIL PROTECTED]> wrote:
Try this...
String configFileName = "/com/common/logger.xml";
Always use forward slashes when dealing with class loader paths. These are
Java packages, not system directories (even though they loo
Try this...
String configFileName = "/com/common/logger.xml";
Always use forward slashes when dealing with class loader paths. These are
Java packages, not system directories (even though they look similar).
One other thing. Where is the class you are using to load the logger.xml
file? Is i
Use a custom repository selector. There are two available in the
log4j-sandbox project. Read about them here:
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/AppContainerLogging
Note that here, you might need to install a repository selector at app or
server startup. Not entire
It doesn't sound like it does at
this point. That is where the InitContextListener from logj4-sandbox
comes in. It attempts to install a repository selector if one is provided
in the 's used by InitContextListener.
Hmm... I need to learn more about logging in JBoss.
Jake
At 02:05 AM 8/28
At 01:08 PM 8/29/2003 -0700, you wrote:
Hi
I've just started using Log4J and had a couple of doubts about how to set
it up for a web-based application that uses Webwork.
1. Since Webwork configures log4j to use Configure, is there any way that
can be changed to ConfigureAndWatch, without going
s where the InitContextListener from logj4-sandbox comes
in. It attempts to install a repository selector if one is provided in the
's used by InitContextListener.
Hmm... I need to learn more about logging in JBoss.
Jake
At 02:05 AM 8/28/2003 -0500, Jacob Kjome wrote:
Well, if yo
At 06:16 PM 8/28/2003 +0200, you wrote:
Two short comments.
1) My name is Ceki not Ciki.
Sorry Ceki, typo.
2) You can use LogManager.resetConfiguration() to reset or clear the
existing config before you read the new config file.
Ah, yes. Never bothered with that since the configuration I do is
Unfortunately, I don't have much to say here. I only ever added
loggers. A better approach is to use a runtime logger configurator. There
is one in the sandbox, but that only works on existing loggers. There are
other runtime configurators out there that can add/remove loggers and
appenders
J Users List
>Subject: RE: Log file location
>
>
>
>We should have a look at the jboss mailing lists. JBoss' class loader
>is called UnifiedClassLoader. The last time I look at
>UnifiedClassLoaders about a year ago, it seemed very smart. I'd have to
>look at the
. The last time I look at UnifiedClassLoaders
about a year ago, it seemed very smart. I'd have to look at the details again.
At 02:05 AM 8/28/2003 -0500, Jacob Kjome wrote:
>Well, if you your app is seeing jboss/lib/log4j.jar in preference to
>WEB-INF/lib/log4j.jar, then there is a bug i
even my application class loader takes the classes from log4j.jar
located in jboss/lib?
If I remove log4j.jar in jboss/lib, then I think I will not get server log
of JBoss.
How to solve this issue? Please inform.
Sriram
-Original Message-----
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent:
Hi Sriram,
Do you have log4j.jar in WEB-INF/lib? If not, I'd expect default
initialization not to work. Remember that the webapp class loader can see
parent class loaders, but the parents cannot see the webapp class loader,
hence your log4j.properties will definitely not be found. If you are
Oh, and I forgot to mention setting the -Dlog4j.configuration system
property which you can poll to find where log4j.xml exists.
Jake
At 06:09 PM 8/27/2003 -0500, you wrote:
I used to use the configureAndWatch() method in my webapps, but I advise
against it now. The watchdog classes currently
I used to use the configureAndWatch() method in my webapps, but I advise
against it now. The watchdog classes currently have no lifecycle
control. LogManager.shutdown() will *not* end the thread that the watchdog
uses. If you try to reload your servlet context, the thread will continue
to re
Hi Rishi,
Notice that you didn't get a ClassNotFoundException, but a
NoClassDefFoundError. They are very different. The former means that it
couldn't be found on the classpath where the latter means that at least one
was found, but not the version it expected. This is usually caused by
diff
At 09:00 PM 8/23/2003 -0400, you wrote:
>>Hi all, I'm trying to work with JBoss and Log4J, and have run
>>into a question that I can't seem to find the answer to. In the
>>course of trying to figure out how to specify "per-application"
>>Log4J configuration for web-apps running under JBoss,
>>I fo
There doesn't appear to be anything wrong with your log4j.xml (except that
you should use rather than , but that isn't the issue here).
Note that the error you've mentioned in previous emails is not an issue here...
"Log4j: WARN No appenders could be found for logger
(org.apache.commons.digest
machine however, I only run one at a time
depending on what I am working on.
My app does not use struts or anything else requiring commons-logging.
Jake,
Enjoy your vacation! And thanks again.
-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Friday, August 08, 200
Remove Log4j.jar and you won't see that
erroror, I suppose, you could add log4j.xml or log4j.properties to
common/classes and all would be well.
Jake
-----Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Monday, August 11, 2003 2:05 AM
To: Log4J Users List
anks again.
Tim
-Original Message-----
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Monday, August 11, 2003 10:45 AM
To: Log4J Users List
At 09:25 AM 8/11/2003 -0400, you wrote:
>Jake,
>
>Having done as you said I am now getting a log file generated
Glad you got things going. Wh
Just use default initialization or use the InitContextListener that I
created in the log4j-sandbox project..
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/AppContainerLogging
Jake
At 03:48 PM 8/12/2003 +0100, you wrote:
yeah, I'm using ant but I dont like the fact that it is ha
Not sure what the issue is, but why did you upgrade to 1.2.7? 1.2.8 is the
latest and recommeded release.
Jake
At 11:04 AM 8/14/2003 -0700, you wrote:
Hi All
I was able to run log4j 1.1.3 version in my environment without any
problems. Now when I updated my log4j to ver 1.2.7
and I boot my web
03:20 PM 8/7/2003 -0400, you wrote:
Sorry about that.
Here you go.
Thanks again.
-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 3:17 PM
To: Log4J Users List
If you want to attach something to the list, put it in a zip file first and
attach
What exactly is the current problem you are having? Just add log4j.jar to
WEB-INF/lib and log4j.properties or log4j.xml to WEB-INF/classes and you
are ready to go. There are a couple of other options that are more
advanced, but this should get you going for now.
Jake
At 06:39 PM 8/6/2003 +01
Jake
Let me know if you have any additional thoughts.
Sincerely,
Tim
-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 11:38 AM
To: Log4J Users List
I see that error in Tomcat5 as well. I assume you have log4j.jar in
CATALINA_HOME/comm
.
I did mean that my log4j.jar file is in the WEB_INF/lib directory.
Everything is where is belongs.
Thanks again.
-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 12:50 PM
To: Log4J Users List
At 12:24 PM 8/7/2003 -0400, you wrote:
>J
Well, actually, under Tomcat, I wrote an InitContextListener which
automagically figures out where the current webapp exists and sets a system
property which is referenced in log4j.xml and, viola!, the log files are
placed in WEB-INF/logs of the current application no matter where it exists
an
the same
JVM. Sorry, just haven't explored logging in these cases as much as with
servlet apps.
Jake
Yoav Shapira
Millennium ChemInformatics
>-----Original Message-
>From: Jacob Kjome [mailto:[EMAIL PROTECTED]
>Sent: Monday, August 11, 2003 1:53 AM
>To: Log4J Users List
hat I noticed was that there was log4j path information in my
classpath, so I took that out. I rebooted the machine and tried to start
Tomcat again. I got the same appender messages.
-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Monday, August 11, 2003 2:49 PM
To: L
This should be possible using separate logger repositories
per/webapp. Please see:
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/AppContainerLogging
I've added a link to this in the wiki FAQ as well:
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/FrequentlyAskedQ
om4j.jar;
E:\Tomcat 4.1\common\lib\servlet.jar;
E:\Tomcat 4.1\bin\bootstrap.jar;
E:\Sandbox\build\classes;
C:\j2sdk1.4.1_01\bin;
E:\Ant1.5.3\apache-ant-1.5.3-1\lib\ant.jar;
E:\Ant1.5.3\apache-ant-1.5.3-1\lib\optional.jar
Thanks for hanging in there.
Sincerely,
Tim
-----Original Message-
Fr
ers. Does anyone know what may be
causing this error.
Thanks.
Tim
-Original Message-----
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 06, 2003 2:58 PM
To: Log4J Users List
What exactly is the current problem you are having? Just add log4j.jar to
WEB-I
At 07:50 AM 8/4/2003 -0500, you wrote:
You pretty much have two options...
1) Seek out all libraries using either log4j/commons-logging and moving them
from the server class-path to the appropriate app-specific directory.
2) Place your log4j.properties file also in the system/server class-path.
The
Put log4j.properties in WEB-INF/classes of your webapp.
Jake
At 08:52 AM 7/25/2003 -0500, you wrote:
I just started using Tomcat 4.1 (moving from another server). My apps
were all coded to use the Log4j logger (1.2.8). Here's my problem.
When starting up, Tomcat apparently uses commons-logging.ja
At 01:44 PM 7/14/2003 -0700, you wrote:
On Fri, 11 Jul 2003, Jacob Kjome wrote:
> I'm in almost total agreement with what you've just said. Logging
> configuration should be set by the application, not its libraries.
> Libraries shouldn't be adding a log4j.properties or l
Hi Mike,
I'm in almost total agreement with what you've just said. Logging
configuration should be set by the application, not its
libraries. Libraries shouldn't be adding a log4j.properties or log4j.xml
file to their classpath, thus triggering automatic log4j
configuration. However, the ap
You need to tell javac to compile with debug flags, otherwise the line
numbers will not be provided.
Jake
At 07:26 PM 7/10/2003 +0200, you wrote:
Dear Steven and all
Thanks for the reply.
I tried and follow the examples in the mailing list.
Now I have a strange problem.
If have two web applicat
You seem to be making two contradicting statements...
1. "I want to use the Default Initialization ..."
2. "Which filename do I have to specify in the DOMconfigurator ..."
Basically, if you want #1, then you don't perform #2 yourself. That is
done automatically by Log4j. Additionally, don't
At 12:51 PM 6/26/2003 +, you wrote:
Hi. I have problem in using the common-logging with struts and
Log4j. I am basically lost. I have short questions, I appreciate if
anyone can help me little bit. these are the questions with examples:
First, if you are using commons-logging, then that is a q
Log4j, by default, uses a single logger repository. So, unless you log
within the context of your own custom logger repository, the last entity to
configure log4j will have configured log4j for every app using the default
logger repository. This is not usually a concern in a standalone app, bu
NoClassDefFoundError means that you probably have conflicting versions of
Log4j in your classpath. Try to set it up where you only have one copy of
log4j.jar in your classpath and see if that fixes things.
Jake
At 03:25 AM 6/14/2003 -0700, you wrote:
I am trying to get log4j working with a ver
Can I ask why you didn't migrate to the latest version of Tomcat which is
well past 4.1.18 by now? 4.1.24 is the latest release:
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.24/
I have heard lots of complaints about 4.1.18. I would first try to upgrade
Tomcat and see if tha
Hi Christian,
Search the archives for discussions on custom loggers using wrappers vs
inheritance. Actually, this was just discussed rather recently. The
wrapper the recommended way to go.
Jake
At 01:04 PM 6/12/2003 -0600, you wrote:
Hi folks,
Supposing I had a need to create and use a cust
enough for you.
Jake
At 12:51 PM 6/12/2003 -0400, you wrote:
Thanks... But, can you give some example please??
I'm newbie with log4j and I don't know how to do it.
Thank you!
Atte,
Carlos Yaconi Hitschfeld
Anexo: 8-4619
Teléfono: 388-4619
-Mensaje original-
De: Jacob Kjome [ma
If you load the properties file with a file name, it will look for the file
in the location where the java process was started unless you provide an
absolute path to the file. The better way to do this is load it off the
classloader and then provide it as an inputstream or URL to the configure
I think you want a console appender or something that isn't so
permanent. Overwriting the file each time you log to it really defeats the
purpose of logging to file.
Jake
At 10:01 AM 6/5/2003 -0600, you wrote:
I've just discovered this group, so my apologies if this has been posted
before. I l
Hi Lukas,
I have tested these context listeners with multiple contexts and they work
fine. However, I'd only tested on Tomcat-4.1.xx, not 4.0.xx. Not sure if
that makes a difference? Try doing the following...
1. copy log4j-1.2.8.jar (or latest CVS, I guess) to
CATALINA_HOME/common/lib (or
Log4j-1.2.8 introduced a better entity resolving mechanism and should clear
up the problem. There were bugs in previous versions. The change
shouldn't do much other than fix your issue. Test first, of course.
Jake
At 04:07 PM 5/28/2003 +0200, you wrote:
we use log4j in a production environme
If you are looking for advice about using commons-logging, the only answer
you will get on this list is to dump it and use log4j directly. Ask
yourself what you are gaining by using this wrapper and read..
http://www.qos.ch/logging/thinkAgain.html
Jake
At 12:16 PM 4/12/2003 -0700, you wrote:
If you make them class static variables, it is the same as marking them as
transient. The recommended way to define a logger is probably
private static final Logger logger = Logger.getLogger(MyClass.class.getName());
This will not be serialized. If you don't make it static, then do...
pri
1 - 100 of 181 matches
Mail list logo