-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 10/8/18 14:27, David Filip wrote:
> Dear Tomcat Users,
>
> Apologies if this is more of a log4j question, but I thought that
> I'd start here, in case Tomcat has any easy remedies.
>
> I have a common webapp that I deploy to multiple, di
Dear Dave,
I walk through that years before, too.
Yes - you can't let write different Log4J Appenders to the same file or you get
this garbage.
Yes - you have property resolving here, but there are no properties you need.
We did a solution using an additional servlet called at application ini
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To whom it may concern,
On 6/24/2011 12:18 PM, jjgtx wrote:
> Christopher Schultz-2 wrote:
>> Where did you put your log4j.properties file and what does it contain?
>> Can you just post the whole thing?
>
> [I put log4j.properties in] $CATALINA_HOME/l
Where did you put your log4j.properties file and what does it contain?
Can you just post the whole thing?
$CATALINA_HOME/lib
I hate to post the whole thing, its a bit long would it be better to send
it?
One thing I was curious about is that should be the value of the
$LOGGING_CONFIG propert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To whom it may concern,
On 6/23/2011 5:44 PM, jjgtx wrote:
> Followed the
> instructions at http://tomcat.apache.org/tomcat-6.0-doc/logging.html
> replacing the tomcat-juli.jar file in $CATALINA_HOME/bin with the one from
> extras and placing the log4
> From: Mark H. Wood [mailto:mw...@iupui.edu]
> Subject: Re: Log4j logging doesn't work when a web application is moved
> outside Tomcat/webapps directory
>
> Maybe because the documentation doesn't say it's improper;
The current documentation for states (in bold):
On Wed, May 05, 2010 at 08:31:33AM -0500, Caldarale, Charles R wrote:
> As always, don't put elements in server.xml. The above got you
> double deployment of the foo webapp, once as foo, once as the default.
>
> Why do people invite problems when it's so easy to do things properly?
Maybe becau
Mark, Chuck, Andre, and Charles, You guys rock!
Mark, I followed your recommendations and
1. I copied the virtual host webapps directories outside Tomcat.
c:/hosts/abc.local/webapps
c:/hosts/xyz.local/webapps
2. Copied the manager.xml to Tomcat/conf/Catalina/abc.local and
Tomcat/conf/Catalina/xyz.
> From: Mark Eggers [mailto:its_toas...@yahoo.com]
> Subject: Re: Log4j logging doesn't work when a web application is moved
> outside Tomcat/webapps directory
>
> I just hacked together a quick example on Windows/XP Professional.
> > That was a nice and concise
> From: Nuno Faria [mailto:nuno.m.fa...@gmail.com]
> Subject: Re: Log4j logging doesn't work when a web application is moved
> outside Tomcat/webapps directory
>
> Following this thread and reading the docs I created virtual hosts
> using the same webapps dir
That'
> From: Mark Eggers [mailto:its_toas...@yahoo.com]
> Subject: Re: Log4j logging doesn't work when a web application is moved
> outside Tomcat/webapps directory
>
> Note that I do not have any non-Tomcat jar in apache-tomcat-6.0.26
> besides JDBC jars at this point.
Wh
I was having a similar problem moving a Tomcat 5.5 configuration to 6.0.
Following this thread and reading the docs I created virtual hosts
using the same webapps dir (it is a development environment with CVS
and I would have to change many things to accomplish one webapp folder
per virtual host).
That was a nice and concise write-up, well-worth of an article in the
Tomcat FAQ/WIKI.
"How to setup Tomcat with 3 virtual hosts, each with its own homepage
and Manager (and other) applications, and its own logfiles".
My only minor remark :
Mark Eggers wrote:
...
Finally for my setup, I adde
org.springframework.web.servlet.DispatcherServlet
2
dispatcher
*.htm
30
redirect.jsp
Sorry for the formatting.
Hope this helps. I hate to say this . . . it works for me.
/mde/
--- On Tue
On 05/05/2010 02:24, Caldarale, Charles R wrote:
>> From: Joe Hansen [mailto:joe.hansen...@gmail.com]
>> Subject: Re: Log4j logging doesn't work when a web application is moved
>> outside Tomcat/webapps directory
>>
>> Scenario 1:
>> log4j.jar is in Tomcat
> From: Joe Hansen [mailto:joe.hansen...@gmail.com]
> Subject: Re: Log4j logging doesn't work when a web application is moved
> outside Tomcat/webapps directory
>
> Scenario 1:
> log4j.jar is in Tomcat/lib directory
> log4j.jar is NOT in WEB-INF/lib directories
Have yo
This thread has grown too long. For anyone following this thread,
here's the summary:
Two web applications, each with a Virtual Host entry in server.xml file.
Tomcat/webapps-abc
Tomcat/webapps-xyz
These two web applications have different log4j.properties files.
These log4j property files log to
Joe Hansen wrote:
Chuck, please note that when commons-logging.jar is present only in
the WEB-INF/lib directory,
I get the following error:
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
So, either I get
a) Invalid class loader hierarchy. You have more than one version of
pps-common-lib-logging/
But that doesn't solve my issue.
Thanks,
Joe
On Tue, May 4, 2010 at 4:58 PM, Caldarale, Charles R
wrote:
>> From: Joe Hansen [mailto:joe.hansen...@gmail.com]
>> Subject: Re: Log4j logging doesn't work when a web application is moved
>> outsi
> From: Joe Hansen [mailto:joe.hansen...@gmail.com]
> Subject: Re: Log4j logging doesn't work when a web application is moved
> outside Tomcat/webapps directory
>
> When commons-logging.jar is present in Tomcat/lib and WEB-INF/lib
> directories, I get the following erro
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: Log4j logging doesn't work when a web application is moved
> outside Tomcat/webapps directory
>
> Oh, I forgot to mention in my other message: you should put log4j.log
> into your webapp&
Thanks for the reply, Charles!
When commons-logging.jar is present in Tomcat/lib and WEB-INF/lib
directories, I get the following error :
Invalid class loader hierarchy. You have more than one version of
'org.apache.commons.logging.Log' visible, which is not allowed.
Here's the complete stack tr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
On 5/4/2010 6:15 PM, Joe Hansen wrote:
> There are common classes in Tomcat/lib/ but they don't attempt to do
> any logging.
Are you sure?
> However, the abc Spring Web application does initialize a
> Quartz object which runs once every hour an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
On 5/4/2010 1:59 PM, Joe Hansen wrote:
> 2. But the web application logging is working wierdly.The log entries
> are written to c:\Tomcat\logs\xyz.log (i.e. the xyz web application's
> log) instead of writing to c:\Tomcat\logs\abc.log. .
>
> He
Chuck,
There are common classes in Tomcat/lib/ but they don't attempt to do
any logging. However, the abc Spring Web application does initialize a
Quartz object which runs once every hour and does some logging. I
don't know if that has any implications.
Thanks,
Joe
Here's the stack trace from ca
> From: Joe Hansen [mailto:joe.hansen...@gmail.com]
> Subject: Re: Log4j logging doesn't work when a web application is moved
> outside Tomcat/webapps directory
>
> Initially I placed log4j-1.2.15.jar in the c:\Tomcat\lib
> directory only. This resulted in abc webapp log
Hansen [mailto:joe.hansen...@gmail.com]
>> Subject: Re: Log4j logging doesn't work when a web application is moved
>> outside Tomcat/webapps directory
>>
>> However, logging is still an issue. One webapp's log4j seems to stomp
>> over other webapp's log fi
> From: Joe Hansen [mailto:joe.hansen...@gmail.com]
> Subject: Re: Log4j logging doesn't work when a web application is moved
> outside Tomcat/webapps directory
>
> However, logging is still an issue. One webapp's log4j seems to stomp
> over other webapp's log f
upIndex=4
And what about the xyz one?
p
> Please advise!
>
> Thank you!
> Joe
>
> On Tue, May 4, 2010 at 11:30 AM, Caldarale, Charles R
> wrote:
>>> From: Joe Hansen [mailto:joe.hansen...@gmail.com]
>>> Subject: RE: Log4j logging doesn't work whe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 5/4/2010 4:08 PM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>> Subject: Re: Log4j logging doesn't work when a web application is moved
>> outside Tomcat/webapps d
Thanks Andre and Chuck.
Andre, I renamed Tomcat/abc/ to Tomcat/webapps-abc/ to keep the naming
consistent. The directory structure that you've advocated is exactly
the same as the one Chuck told me. And I have implemented that.
However, logging is still an issue. One webapp's log4j seems to stomp
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: Log4j logging doesn't work when a web application is moved
> outside Tomcat/webapps directory
>
> You want this:
>
> webapps/abc
> webapps/abc/ROOT <-- this is your "ab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
On 5/4/2010 1:26 PM, Joe Hansen wrote:
> I have written two web applications abc and xyz. I have mapped
> abc.local and xyz.local to my machine's IP Address in my Windows HOST
> file. So when I visit http://abc.local, I would want the abc web
> a
Joe Hansen wrote:
Many Thanks for the link Chuck! Here's what I did.
1. Created a directory named c:\Tomcat\abc\ROOT.
2. Moved the previous contents of c:\Tomcat\webapps\abc to
c:\Tomcat\abc\ROOT directory.
...
Let me throw in my grain of salt.
I like things organised in a logical way, with a
%n
log4j.appender.A2.File=c:/Tomcat6/logs/trestlewood.log
log4j.appender.A2.MaxFileSize=100KB
log4j.appender.A2.MaxBackupIndex=4
Please advise!
Thank you!
Joe
On Tue, May 4, 2010 at 11:30 AM, Caldarale, Charles R
wrote:
>> From: Joe Hansen [mailto:joe.hansen...@gmail.com]
>> Subject
> From: Joe Hansen [mailto:joe.hansen...@gmail.com]
> Subject: RE: Log4j logging doesn't work when a web application is moved
> outside Tomcat/webapps directory
> Looks like I have some reading to do! Will post back after
> I read some Tomcat documentation.
Start here:
http
Thanks for the reply, Mark. You made me understand the mess I have created.
I have written two web applications abc and xyz. I have mapped
abc.local and xyz.local to my machine's IP Address in my Windows HOST
file. So when I visit http://abc.local, I would want the abc web
application to be access
> From: Joe Hansen [mailto:joe.hansen...@gmail.com]
> Subject: Re: Log4j logging doesn't work when a web application is moved
> outside Tomcat/webapps directory
>
>
>
> elements. They
must be distinct.
>
>
On 04/05/2010 17:59, Joe Hansen wrote:
> Mark, Here's the server.xml before moving abc out of the webapps directory:
>
>unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
>
>
Mark, Here's the server.xml before moving abc out of the webapps directory:
On Tue, May 4, 2010 at 10:53 AM, Mark T
On 04/05/2010 17:43, Joe Hansen wrote:
> Thank you for the super quick reply Mark! We are using Java Spring.
> The reason for moving the web application out of the webapps directory
> was that the Spring Context Loader was loading twice. First because
> its in the webapps directory. Secondly, becau
Thank you for the super quick reply Mark! We are using Java Spring.
The reason for moving the web application out of the webapps directory
was that the Spring Context Loader was loading twice. First because
its in the webapps directory. Secondly, because it is being referred
to by the entry in the
On 04/05/2010 17:32, Joe Hansen wrote:
> Hey all,
>
> We are using Tomcat 6 on a Windows XP box. We have a web application
> named abc. It was initially in the c:\Tomcat\webapps directory. I then
> moved the c:\Tomcat\webapps\abc directory to c:\Tomcat\abc. I then
> changed the Tomcat/conf/server.
Hi Denis
What do you mean by the "internal logging works fine in both cases"?
Does the call from the servlet produce an error in the tomcat logs?
Do you call an initializer servlet (load-on-startup) to load the
log4j.properties file?
Tom
On 30/07/2008, at 12:34 AM, Denis Kezerashvili wrote
Does anybody has any idea what might be causing the problem with Log4J? I've
googled for the longest time and there are no leads I found.
Denis
- Original Message
From: Denis Kezerashvili <[EMAIL PROTECTED]>
To: users@tomcat.apache.org
Sent: Tuesday, July 29, 2008 9:49:08 AM
Subject:
It now points to http://tomcat.apache.org/tomcat-4.1-doc/config/logger.html
That's perfect for me.
Thank you very much,
Dave
On Jun 24, 2008, at 3:30 PM, Mark Thomas wrote:
David Fisher wrote:
(3) On the logger FAQ page the Configuration link is dead! http://tomcat.apache.org/tomcat-5.0-doc/c
Walter Thompson wrote:
The same one you claimed to have fixed the 404 error on!
(3) On the logger FAQ page the Configuration link is dead!
http://tomcat.apache.org/tomcat-5.0-doc/config/logger.html gives a
404.
Of course it will give a 404. That URL doesn't exist which is why I updated
the
2008 3:45 PM
To: Tomcat Users List
Subject: Re: Log4j Logging
Walter Thompson wrote:
> OK. It doesn't give 404, how about fixing the page not found on this
> server error too?
I'm not a mind reader. Which link is broken?
Mark
--
Walter Thompson wrote:
OK. It doesn't give 404, how about fixing the page not found on this
server error too?
I'm not a mind reader. Which link is broken?
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsu
OK. It doesn't give 404, how about fixing the page not found on this
server error too?
-Original Message-
From: Mark Thomas [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2008 3:30 PM
To: Tomcat Users List
Subject: Re: Log4j Logging
David Fisher wrote:
> (3) On the logger
David Fisher wrote:
(3) On the logger FAQ page the Configuration link is dead!
http://tomcat.apache.org/tomcat-5.0-doc/config/logger.html gives a 404.
Fixed. Note, the FAQ is now on a wiki so anyone who spots an error can just
fix it.
Mark
---
(This must be national logging questions month :-)
More like International logging month - everyone upgrading to tomcat
5.5 or better is forced to confront this issue, many are under a lot
of pressure, and they don't all read English. The differences are
subtle and lost in translation.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
|> From: Hexsel, Gustavo [mailto:[EMAIL PROTECTED]
|> Subject: Log4j Logging
|
| (This must be national logging questions month :-)
Logging too much is bad for the environment. You should recycle your
telephone boo
per log statement was what drove me
insane in the first place).
[]s Gus
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2008 10:57 AM
To: Tomcat Users List
Subject: RE: Log4j Logging
> From: Hexsel, Gustavo [mailto:[EMAIL PROTEC
> From: Hexsel, Gustavo [mailto:[EMAIL PROTECTED]
> Subject: Log4j Logging
(This must be national logging questions month :-)
> if, according to
> http://tomcat.apache.org/tomcat-6.0-doc/logging.html,
> log4j is the recommended logger
I don't see anything on that page that implies log4j is recom
When starting a new thread (ie sending a message to the list about a
new topic) please do not reply to an existing message and change the
subject line. To many of the list archiving services and mail clients
used by list subscribers this makes your new message appear as part
of the old thread. Thi
WARN: ambiguous subject line
TODO: make meaningful subject
LOG: That should help get the answers you are looking for
--
Alex
--
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
Fo
57 matches
Mail list logo