I just removed /usr/java/j2sdk1.4.1_02/jre/lib/ext/log4j-1.2.8.jar and
now it works!!!
Thanks.
Dean
Dean A. Hoover wrote:
Ceki Gülcü wrote:
Do you have a copy of the log4j.jar file other than the WEB_INF/lib
directory of your web-app?
I did a find on *log*.jar and found the following:
/usr
At 10:03 PM 7/3/2003 -0400, you wrote:
Ceki Gülcü wrote:
Do you have a copy of the log4j.jar file other than the WEB_INF/lib
directory of your web-app?
I did a find on *log*.jar and found the following:
/usr/java/j2sdk1.4.1_02/jre/lib/ext/log4j-1.2.8.jar
Bingo.
/usr/java/jakarta-tomcat-4.1.24/s
Ceki Gülcü wrote:
Do you have a copy of the log4j.jar file other than the WEB_INF/lib
directory of your web-app?
I did a find on *log*.jar and found the following:
/usr/java/j2sdk1.4.1_02/jre/lib/ext/log4j-1.2.8.jar
/usr/java/jakarta-tomcat-4.1.24/server/lib/commons-logging.jar
/usr/java/jakart
Ceki Gülcü wrote:
At 08:40 AM 7/4/2003 +1000, you wrote:
Mmmm, for some reason it is using all the right class loaders to
attempt to
find the log4j.xml file, but it only uses 1 different methods to try
to find
log4j.properties. That is odd. Is this a Tomcat 4.1 specific class
loader
issue?
Do you have a copy of the log4j.jar file other than the WEB_INF/lib
directory of your web-app?
Do you have it in the classpath? In the JVM extensions directory?
By the way, tomcat is not starting properly which means that your web-app
will also not start but you get log4j messages which mean th
At 08:40 AM 7/4/2003 +1000, you wrote:
Mmmm, for some reason it is using all the right class loaders to attempt to
find the log4j.xml file, but it only uses 1 different methods to try to find
log4j.properties. That is odd. Is this a Tomcat 4.1 specific class loader
issue?
That's probably a cut-n-
J Users List
> Subject: Re: tomcat and log4j, again
>
>
> Ceki Gülcü wrote:
>
> >
> > My suggestion would be to start tomcat and set the log4j.debug
> > property to true.
>
> OK, did it:
>
> log4j.debug=true
> log4j.logger.fermataintl.migrasponder
Ceki Gülcü wrote:
My suggestion would be to start tomcat and set the log4j.debug
property to true.
OK, did it:
log4j.debug=true
log4j.logger.fermataintl.migrasponder=DEBUG, l1
log4j.appender.l1=org.apache.log4j.FileAppender
log4j.appender.l1.File=/tmp/migrasponder
log4j.appender.l1.layout=org.a
My suggestion would be to start tomcat and set the log4j.debug property to
true.
The extra command line argument is -Dlog4j.debug=true
This should show which configuration file log4j load if it loads one at
all. If your config file is found, you should also see log4j parsing it.
BTW, your co
Sorry about that. It turns out that I had
some tags in the web.xml file in the wrong
place. I didn't realize that the order of
those tags was important. Anyway. I fixed
that, but the file logging is still not
working. Here is the catalina.out file:
0 [main] INFO modeler.Registry - Loading registry
At 12:54 PM 7/3/2003 -0400, Dean A. Hoover wrote:
PS. I looked for the commercial manual (on the website) at 2 local
bookstores and on amazon.com. Nobody has it. I hesitate to order from
Switzerland, as I am in the US. How long would that take...
You can "The complete log4j manual" in the US from
Following the discussion on this topic. I am working on using the log4j
taglib for the presentation layer( jsps)
I also am not seeing anything in caltalina.out nor am not seeing a file
being created. Any suggestions?
# Sample properties to initialise log4j^M
log4j.debug=true^M
#log4j.rootCa
Howdy,
>OK, here goes. I shutdown tomcat, removed catalina.out, and restarted.
>Here it is:
>4932 [main] ERROR digester.Digester - Parse Error at line 37 column
11:
>The content of element type "web-app" must match
>"(icon?,display-name?,description?,distributable?,context-
>param*,filter*,filt
Shapira, Yoav wrote:
Howdy,
This is what I changed log4.properties to:
log4j.logger.fermataintl.migrasponder=DEBUG, l1
log4j.appender.l1=org.apache.log4j.FileAppender
log4j.appender.l1.File=/tmp/migrasponder
log4j.appender.l1.layout=org.apache.log4j.PatternLayout
log4j.appender.l1.layout.Conv
Howdy,
>This is what I changed log4.properties to:
>
>log4j.logger.fermataintl.migrasponder=DEBUG, l1
>log4j.appender.l1=org.apache.log4j.FileAppender
>log4j.appender.l1.File=/tmp/migrasponder
>log4j.appender.l1.layout=org.apache.log4j.PatternLayout
>log4j.appender.l1.layout.ConversionPattern=%d
Shapira, Yoav wrote:
Howdy,
I am not explicitly initializing log4j. A class that I am using
in my app invokes logging as follows:
package fermataintl.migrasponder.common;
import java.sql.*;
import org.apache.log4j.*;
public class Vendor
{
...
logger.warn("attempt to authenticate '" + id + "
PS. WRAX press' Tomcat book has a section on Log4J. Pretty simple, 20 pages
tops, but it will get you started. If you can get a handle of that, of course.
At 12:54 PM 7/3/2003, you wrote:
OK, with my current configuration, I *am* seeing
output in catalina.out. However, its not formatted
the way I
Howdy,
>I am not explicitly initializing log4j. A class that I am using
>in my app invokes logging as follows:
>
>package fermataintl.migrasponder.common;
>import java.sql.*;
>import org.apache.log4j.*;
>
>public class Vendor
>{
>...
> logger.warn("attempt to authenticate '" + id + "' failed"
1. look into using fileappenders, or even better rolling file appenders.
2. in the log4j api find patternlayout. it has very good documentation.
d Used to output the date of the logging event. The date conversion
specifier may be followed by a date format specifier enclosed between
braces. For ex
19 matches
Mail list logo
