Sorry if resurrecting the dead is frowned upon here but I thought I would
just add my resolve to this. Honestly, after writing a lot of code
otherwise, logging was probably the most frustrating.
Tomcat 7.0.42, RHEL 6
1. SL4FJ with Logback works beautifully.
2. I have custom error pages in web.xm
Alec: "That seems like a good solution. Are you able to avoid having a
single giant catalina.out file in $CATALINA_HOME/logs?"
No, we find we can live with that but we try to minimise writes to
stdout etc. From Chris's note it seems like the ideal solution for us
would be
1. server log4j isolat
>> Dale wrote:
>> We found issues with trying to have log4j in catalina/lib.
>>
>> That said, it would be nice to use log4j for tomcat, however we found
>> that the two configurations collided in our slf4j setup.
>You can do this if you put log4j.jar into a server-only ClassLoader.
>That's not c
Chris,
"The examples don't meet your needs exactly? Well, I'm sure we're all
terribly sorry about that."
Heh...Sorry, I was responding to Konstantin's comment and mine crossed over
just before your long and helpful reply.
Thanks, as always,
Alec
On Wed, Dec 4, 2013 at 12:39 PM, Christopher Sc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dale,
On 12/3/13, 11:01 PM, Dale Ogilvie wrote:
> Currently we use tomcat configured as out-of-the-box for logging
> (no log4j) and log4j.jar and config in the app war file.
>
> We found issues with trying to have log4j in catalina/lib.
>
> That s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alec,
On 12/4/13, 11:31 AM, Tomcat Random wrote:
> I'd argue that dealing with logging configuration is not newbie
> stuff. This is probably some of the most poorly implemented
> technology in the servlet container.
What about the implementation is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alec,
On 12/3/13, 1:12 PM, Tomcat Random wrote:
> I'm trying to implement log4j as per the instructions here
> (skipping step 5):
> http://tomcat.apache.org/tomcat-7.0-doc/logging.html#Using_Log4j
>
> Since I'm not using the Manager, I've removed
I'd argue that dealing with logging configuration is not newbie stuff. This
is probably some of the most poorly implemented technology in the servlet
container.
On Tue, Dec 3, 2013 at 3:44 PM, Konstantin Kolinko
wrote:
> 2013/12/3 Tomcat Random :
> > Environment is RHEL6, Tomcat 7.0.42. There is
That seems like a good solution. Are you able to avoid having a single
giant catalina.out file in $CATALINA_HOME/logs?
On Tue, Dec 3, 2013 at 11:01 PM, Dale Ogilvie wrote:
> Currently we use tomcat configured as out-of-the-box for logging (no
> log4j) and log4j.jar and config in the app war file
Currently we use tomcat configured as out-of-the-box for logging (no
log4j) and log4j.jar and config in the app war file.
We found issues with trying to have log4j in catalina/lib.
That said, it would be nice to use log4j for tomcat, however we found
that the two configurations collided in our sl
2013/12/3 Tomcat Random :
> Environment is RHEL6, Tomcat 7.0.42. There is only one webapp.
>
> I'm trying to implement log4j as per the instructions here (skipping step
> 5):
> http://tomcat.apache.org/tomcat-7.0-doc/logging.html#Using_Log4j
>
> Since I'm not using the Manager, I've removed the rel
11 matches
Mail list logo
