-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Allen,
On 8/9/2009 10:25 PM, Allen Williams wrote:
I looked, and somewhere along the line, I made my Context tag this:
Context path= docBase= swallowOutput=true debug=5
reloadable=true
antiResourceLocking=false
:19:48 -0600
From: devli...@hanik.com
To: users@tomcat.apache.org
Subject: Re: Console Output Not Going Anywhere
what class is Logger.getLogger(), doesn't look like a tomcat class,
so, no, it wont show up in the tomcat configured logs.
Also, System.out/err only show up in the logs if you have
: Sat, 8 Aug 2009 18:19:48 -0600
From: devli...@hanik.com
To: users@tomcat.apache.org
Subject: Re: Console Output Not Going Anywhere
what class is Logger.getLogger(), doesn't look like a tomcat class,
so, no, it wont show up in the tomcat configured logs.
Also, System.out/err only show up
, 8 Aug 2009 18:19:48 -0600
From: devli...@hanik.com
To: users@tomcat.apache.org
Subject: Re: Console Output Not Going Anywhere
what class is Logger.getLogger(), doesn't look like a tomcat class,
so, no, it wont show up in the tomcat configured logs.
Also, System.out/err only show up in the logs
From: Allen Williams [mailto:anw-d...@infoisland.net]
Subject: Re: Console Output Not Going Anywhere
It is the standard internal tomcat logging mechanism contained in the
distribution of tomcat 6, based on java.util.logging.
1) What platform (OS) are you running on?
2) Are you using
0
Caldarale, Charles R wrote:
From: Allen Williams [mailto:anw-d...@infoisland.net]
Subject: Re: Console Output Not Going Anywhere
It is the standard internal tomcat logging mechanism contained in the
distribution of tomcat 6, based on java.util.logging.
1) What platform (OS) are you
From: Allen Williams [mailto:anw-d...@infoisland.net]
Subject: Re: Console Output Not Going Anywhere
Debian 2.6.26, tomcat from the Debian package (apt-get, etc.), starting
it with the init.d script.
Just for grins, try downloading the 6.0.20 tarball from tomcat.apache.org,
install
That sounds like it might be a bit time consuming. I don't mind trying
it, but I'm going to be traveling next week, so I'll have to do it when
I return.
Caldarale, Charles R wrote:
From: Allen Williams [mailto:anw-d...@infoisland.net]
Subject: Re: Console Output Not Going Anywhere
Debian
...@infoisland.net]
Subject: Re: Console Output Not Going Anywhere
Debian 2.6.26, tomcat from the Debian package (apt-get, etc.),
starting
it with the init.d script.
Just for grins, try downloading the 6.0.20 tarball from
tomcat.apache.org, install that along with your webapps, and see if
your
Williams [mailto:anw-d...@infoisland.net]
Subject: Re: Console Output Not Going Anywhere
Debian 2.6.26, tomcat from the Debian package (apt-get, etc.), starting
it with the init.d script.
Just for grins, try downloading the 6.0.20 tarball from
tomcat.apache.org, install that along
Sorry, I should have mentioned that. Yes, I've tried it both ways,
multiple times. BTW, is that something new in Tomcat6? I've never seen
it before now.
Filip Hanik - Dev Lists wrote:
did you set
swallowOutput=true in conf/context.xml?
Filip
On 08/07/2009 07:01 PM, Allen Williams wrote:
Allen Williams wrote:
I've fixed the exceptions that were being thrown and still have this,
despite having this in my code:
===
public class AppInitializer implements ServletContextListener
{
public void
what class is Logger.getLogger(), doesn't look like a tomcat class,
so, no, it wont show up in the tomcat configured logs.
Also, System.out/err only show up in the logs if you have swallowOutput
set AND it happens during a request.
ServletContextListener don't happen during servlet requests
aucune responsabilité
pour le contenu fourni.
Date: Sat, 8 Aug 2009 18:19:48 -0600
From: devli...@hanik.com
To: users@tomcat.apache.org
Subject: Re: Console Output Not Going Anywhere
what class is Logger.getLogger(), doesn't look like a tomcat class,
so, no, it wont show up
did you set
swallowOutput=true in conf/context.xml?
Filip
On 08/07/2009 07:01 PM, Allen Williams wrote:
I'm trying to get Tomcat 6 up and working; didn't have this problem on 5.
The code:
System.err.println
does not print to the log files. With this logging.properties:
15 matches
Mail list logo
