ut in JAVA_OPTS or in CATALINA_OPTS?
> Thanks.
> --
> View this message in context:
> http://www.nabble.com/commons-logging-problem-tp21736872p25816008.html
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
Hi,
Can you just tell me, please, if the option
-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES
should be put in JAVA_OPTS or in CATALINA_OPTS?
Thanks.
--
View this message in context:
http://www.nabble.com/commons-logging-problem-tp21736872p25816008.html
Sent from the
Certainly putting commons-logging and log4j in the container's
common/lib directory is the documented configuration. However this does
not allow application-level logging for libraries used by the
application like digester or spring that themselves use commons logging.
The application log messa
On Fri, Jan 30, 2009 at 8:33 PM, Rusty Wright wrote:
> Does that work reliably now? I was under the impression that it caused
> problems, but that may have been with a previous version of tomcat. That's
> why I asked my "where else" question; I was wondering if that's what he was
> thinking of.
Does that work reliably now? I was under the impression that it caused problems, but
that may have been with a previous version of tomcat. That's why I asked my "where
else" question; I was wondering if that's what he was thinking of.
Gregor Schneider wrote:
On Fri, Jan 30, 2009 at 7:45 PM,
On Fri, Jan 30, 2009 at 7:45 PM, Rusty Wright wrote:
> John Holman wrote:
>>
>> Also is it a supported configuration to use commons-logging and log4j in
>> WEB-INF/lib?
>
> Where else would you put them?
>
i.e. ${CATALINA_HOME}/common/lib
Saves the hazzle to put them into each webapp.
Rgds
Gre
John Holman wrote:
Also is it a supported configuration to use commons-logging and log4j in
WEB-INF/lib?
Where else would you put them?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-m
> From: John Holman [mailto:j.g.hol...@qmul.ac.uk]
> Subject: Re: commons-logging problem
>
> Doing this does make me a bit nervous though, as we've had
> problems with PermGen memory exhaustion in the past.
I think your nervousness is quite justified.
> is it worth
uk]
Subject: commons-logging problem
When packaged as a war file this combination reliably produces the
exception shown below in the Tomcat console under the following
circumstances:
This is likely the result of a fix to prevent PermGen from filling up after
some number of webapp redeplo
> From: John Holman [mailto:j.g.hol...@qmul.ac.uk]
> Subject: commons-logging problem
>
> When packaged as a war file this combination reliably produces the
> exception shown below in the Tomcat console under the following
> circumstances:
This is likely the result of a fix
I have a web application running in Tomcat 5.5.27 with JDK 1.5.0_16-b02
on Windows XP SP3. log4j-1.2.15.jar and commons-logging-1.1.1.jar are
installed in WEB-INF/lib and there is a context.xml file in META-INF.
When packaged as a war file this combination reliably produces the
exception shown be
Lists [mailto:[EMAIL PROTECTED] Sent: 22
August 2007 21:19
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6
Ashley Hollands wrote:
There wasn't any trace at all - I added my own logging to tell me
that one server had sent the message, but on the other server there
was
do you have an
alternative place you would like it sent?
Regards
Ashley
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 22 August 2007 21:19
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6
Ashley Hollands wrote:
There wasn
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 22 August 2007 21:19
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6
Ashley Hollands wrote:
> There wasn't any trace at all - I added my own logging to tell me that
> one s
that
if the rootCategory is set to ERROR in my web app log4j.properties then
it should be logging all exceptions in the web app log?
Ashley
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 22 August 2007 21:19
To: Tomcat Users List
Subject: Re: Logging Problem on
side of the scope of Tribes
classloader, you are better off just sending a byte[] and do the
serialization/deserialization yourself.
Filip
Ashley
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 22 August 2007 20:39
To: Tomcat Users List
Subject: Re
ist
Subject: Re: Logging Problem on Upgrade to Tomcat 6
Ashley Hollands wrote:
> OK - I'll run through the steps from scratch again and see if I have
> more joy this time.
>
let me know how it goes, I can help out more.
> By the way, I have been using Tribes in my application an
20:21
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6
Ashley Hollands wrote:
What is confusing me is that I never had to catch the exception and
log it from within my application in Tomcat 4, 5 or 5.5 - it just
appeared in the web app log automatically.
Is there
Sent: 22 August 2007 20:21
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6
Ashley Hollands wrote:
> What is confusing me is that I never had to catch the exception and
> log it from within my application in Tomcat 4, 5 or 5.5 - it just
> appeared in the web ap
t: Re: Logging Problem on Upgrade to Tomcat 6
it will only log to the webapp.log if your application catches the
exception, then issues a log.error("msg",exception) (tomcat will do the same
assuming it was correctly configured)
if you provide a sample war, I can validate it for you
Filip
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 22 August 2007 19:51
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6
it will only log to the webapp.log if your application catches the
exception, then issues a log.error("msg"
the
web app log.
Ashley
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 22 August 2007 19:12
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6
Ashley Hollands wrote:
Thanks for the reply Filip
if you want a global log4j
web app to the
web app log.
Ashley
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 22 August 2007 19:12
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6
Ashley Hollands wrote:
> Thanks for the reply Filip
>
>
>&
ge-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 22 August 2007 18:03
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6
if you want a global log4j (instead of tomcat's own framework)
http://tomcat.apache.org/tomcat-6.0-doc/logging.html
then you w
OTECTED]
Sent: 22 August 2007 18:03
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6
if you want a global log4j (instead of tomcat's own framework)
http://tomcat.apache.org/tomcat-6.0-doc/logging.html
then you will need to be tomcat-juli.jar and tomcat-juli-adapters.jar a
if you want a global log4j (instead of tomcat's own framework)
http://tomcat.apache.org/tomcat-6.0-doc/logging.html
then you will need to be tomcat-juli.jar and tomcat-juli-adapters.jar
as described in the docs,
let me know if you need more clarification
Filip
Ashley Hollands wrote:
Hi
I have
Hi
I have recently upgraded from Tomcat 5.5 to 6.0 and from Java 1.5
to 6.
I use Log4J for all my web application logging and have discovered
that after the upgrade, any exceptions thrown in the web application
are not logged to my web application log, but to the top-level Tomcat
log.
Does anybo
Hello there,
Am using JDK 1.5 and Tomcat 5.5.9...
I have two init servlets for the following purposes:
1. One is for logging
2. The other is for loading (and parsing) XML based configuration
files using Commons Digester.
When I go to %CATALINA_HOME%/conf/server.xml and inside the
tag, when I
nge over time.
-Original Message-
From: Tejas Dhedia [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 03, 2006 6:00 PM
To: users@tomcat.apache.org
Subject: Tomcat logging problem
Hi,
I am running tomcat 5.5.17 under opensuse 10.1 and my JVM version is
1.5.0_06. I am running my tomca
rtup and shutdown scripts change over time.
-Original Message-
From: Tejas Dhedia [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 03, 2006 6:00 PM
To: users@tomcat.apache.org
Subject: Tomcat logging problem
Hi,
I am running tomcat 5.5.17 under opensuse 10.1 and my JVM version is
1.5.0_0
Hi,
I am running tomcat 5.5.17 under opensuse 10.1 and my JVM version is
1.5.0_06. I am running my tomcat as a seperate tomcat user and starting it
at boot time using the following script in /etc/init.d.
#!/bin/sh
#
# Startup script for Tomcat
JAVA_HOME=/usr/lib/jvm/java
export JAVA_HOME
start_t
Hi Boris,
I have now switched my server to "one-properties-per-webabb" (inside
webapp dir). It's not nice, but it works.
Thanks a lot for your help.
Regards,
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addition
Remy Maucherat wrote:
Very funny.
Funny what?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
> Boris Unckel wrote:
>
> > I have a workaround:
> > You provide a logging.properties in your webapp. All relevant parameters
> are
> > controlled per system -D properties.
>
> A workaround for what? Providing a logging.properties in my webapp is
> exactly what I'm trying to avoid. What's t
On 2/27/06, Andreas Schildbach <[EMAIL PROTECTED]> wrote:
> Boris Unckel wrote:
>
> > I have a workaround:
> > You provide a logging.properties in your webapp. All relevant parameters are
> > controlled per system -D properties.
>
> A workaround for what? Providing a logging.properties in my webapp
Boris Unckel wrote:
I have a workaround:
You provide a logging.properties in your webapp. All relevant parameters are
controlled per system -D properties.
A workaround for what? Providing a logging.properties in my webapp is
exactly what I'm trying to avoid. What's the relevant parameters, an
Hi,
I have a workaround:
You provide a logging.properties in your webapp. All relevant parameters are
controlled per system -D properties. With x4juli this will work for all
webcontainers.
Regards
Boris
-
To unsubscribe, e-mail
Hello,
> Thanks for your explanation about why real per-webapp logging is
> currently not possible with Tomcat 5.5 and Juli/java.util.logging. Is it
> the same with Log4J?
>
Yes, naturally. You would have to place log4j.jar into your WEB-INF/lib and
the configuration into the webapp to get logg
Boris Unckel wrote:
You want to have a _one_ central place for your log configuration _and_ the
correct logging just for that application - currently impossible.
I would not necessarely say that logging has to be configured in one
central place/file, but I think putting logging config _into_
Hello Andreas,
I have read your response to Remy's mail.
> >> Could it be that all libraries I use go to the wrong log?
> >
> > This depends on the common and shared classloader. Please put any JAR
> > which is not delivered by Tomcat and already there in a default
> > installation in your
> >
Boris Unckel wrote:
Could it be that all libraries I use go to the wrong log?
This depends on the common and shared classloader. Please put any JAR
which is not delivered by Tomcat and already there in a default
installation in your
WEB-INF/lib folder. Test again.
I don't understand. The
Remy Maucherat wrote:
Could it be that all libraries I use go to the wrong log?
All your libraries, like Spring, will use their own logger names. All
these loggers are not defined in your configuration, so will all use
the handlers for the root logger (".handlers").
org.apache.catalina.core.Co
On 2/26/06, Andreas Schildbach <[EMAIL PROTECTED]> wrote:
> Could it be that all libraries I use go to the wrong log?
All your libraries, like Spring, will use their own logger names. All
these loggers are not defined in your configuration, so will all use
the handlers for the root logger (".handl
Good Morning Andreas,
Andreas Schildbach wrote:
Hello Boris,
thanks for your answer.
I could not see any error but one:
handlers = 1catalina.org.apache.juli.FileHandler,
2localhost.org.apache.juli.FileHandler,
3app1.org.apache.juli.FileHandler, 4app2.org.apache.juli.FileHandler,
java.util.
Hello Boris,
thanks for your answer.
I could not see any error but one:
handlers = 1catalina.org.apache.juli.FileHandler,
2localhost.org.apache.juli.FileHandler,
3app1.org.apache.juli.FileHandler, 4app2.org.apache.juli.FileHandler,
java.util.logging.ConsoleHandler
as first line (aside from
Hello,
Andreas Schildbach wrote:
My problem is, there is no logging going to any logfile. What am I
doing wrong?
Do I need to have unique numbers as a prefix to app1 and app2? (could
I use 0app1 and 0app2?)
I could not see any error but one:
handlers = 1catalina.org.apache.juli.FileHandler,
Hello everyone,
I despair of configuring per-webapp logging for Tomcat 5.5, something
that was easily possible with swallowOutput on pre-5.5 Tomcats.
I've got 2 hosts (app1.de, app2.de), containing one context each. In
addition, there is also the localhost context from the example server.xml.
I think you haven't defined the root category in your log4j.properties file.
That might be causing the problem.
Adding following lines should fix the problem:
log4j.rootCategory=[priority], appenderName
Regards,
gaurav
On 1/2/06, mukesh <[EMAIL PROTECTED]> wrote:
>
> Hi friends,
>
>
>
>
Hi friends,
I am not able to log the information. Though file gets created
after restarting the tomcat5.5.12 but nothing is being written.
**I have done application specific setting
log4j.properties is on
/usr/local/apache-tomcat-5.5.12/webapps/axis/WE
This is a repost of a message I first posted in June that I got no replies
to.
I have a double-logging problem, by which I mean that
some of my log messages get logged to two logfiles. I have only one
logfile configured using java.util.logging, but in some cases, the
same log message gets
50 matches
Mail list logo
