RE: log4j

Depends on what you're asking. If you're asking to use log4j to capture Tomcat logging, then the answer is - you can't but you can use Log4j2 or JULI. If the question is how to use log4j for your apps deployed under Tomcat, then answer can be found easily... From: Cheltenham, Chris

Re: log4j

Also, it may make more sense to code log4j into your app. If you change servers the logging goes with it. Best, J On Fri, May 18, 2018 at 8:06 AM M. Manna wrote: > Hi Chris, > > How r u planning to use Log4j (or log4j2, which solves a lot of performance > issues for

Re: Does Tomcat supports serialize session access?

On 18/05/2018 14:39, Suvendu Sekhar Mondal wrote: Hello Everyone, We recently migrate our apps from Websphere(WAS) to Tomcat. We are using httpd 2.4.10 in front of multiple Tomcat 7.0.55. There is one feature of WAS that I am interested about and I am looking for it everywhere in Tomcat

Re: log4j

Hi Chris, How r u planning to use Log4j (or log4j2, which solves a lot of performance issues for 1.2.x)? Are you bridging with SLF4J or or using directly? All log4j configuration are automatically discovered and configured provided that you have set up your appplication log4j properties file

log4j

Hello, How do I configure Tomcat 8.5.x to use log4j? Is there a good document to follow? I am not very familiar with java but it looks like you configure to logs to accept java logging for Tomcat. === Thank You; Chris Cheltenham Technology Services

Does Tomcat supports serialize session access?

Hello Everyone, We recently migrate our apps from Websphere(WAS) to Tomcat. We are using httpd 2.4.10 in front of multiple Tomcat 7.0.55. There is one feature of WAS that I am interested about and I am looking for it everywhere in Tomcat world but could not found any source. Feature called

Re: Issue with WebResource Caching

> > > > Tomcat uses the same code for static and class loader resources but it > > is meant to distinguish between the two. However, it looks like there is > > a bug in Tomcat's resource handling that hides this resource once the > > static look-up fails. I need to dig into this some more. > >

Re: Issue with WebResource Caching

On 18/05/18 07:23, Mark Thomas wrote: > Tomcat uses the same code for static and class loader resources but it > is meant to distinguish between the two. However, it looks like there is > a bug in Tomcat's resource handling that hides this resource once the > static look-up fails. I need to dig

Re: Issue with WebResource Caching

On 17/05/2018 15:43, Jeremy Collins wrote: At this point we're unsure if this is an actual bug in Tomcat or an incorrect usage of getResourceAsStream(path) on our part so we're looking for advice. I think it is a bit of both. ServletContext.getResourceAsStream(path) won't normally return