Re: Can we increase the logging in localhost_access.log
On 25/03/2014 07:59, Utkarsh Dave wrote: Hi, We are using Tomcat 7.0.41. One of my customer faces 404 error while accessing the web application. This continues for some time and goes away automatically without giving us time to debug. We dont have any other clue. Everything else works fine. all services are running great. No issue with Tomcat server also. It seems customer also verified the network settings and firewall. We see 404 error in localhost_access so this the place from where we can dig into. Is there any way we can enhance the logging/information in localhost_access_log. Or then how can debug what happens between user requests and 404 response,? You are only ever going to get one entry per request/response. Control of that entry is by configuring the AccessLogValve. http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html#Access_Log_Valve Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Can we increase the logging in localhost_access.log
We see 404 error in localhost_access so this the place from where we can dig into. Is there any way we can enhance the logging/information in localhost_access_log. Or then how can debug what happens between user requests and 404 response,? Outside of performance monitoring tools, you might try a custom 404 error that points to a servlet. Within that servlet you can capture information and log to a separate 404 log file (say, using LogBack). There are a few pages on the web that describe this process. Here's one: http://www.journaldev.com/1973/servlet-exception-and-error-handling-example-tutorial Best, John
Re: Can we increase the logging in localhost_access.log
On Mar 25, 2014, at 10:58 AM, John Smith tomcat.ran...@gmail.com wrote: We see 404 error in localhost_access so this the place from where we can dig into. Is there any way we can enhance the logging/information in localhost_access_log. Or then how can debug what happens between user requests and 404 response,? Outside of performance monitoring tools, you might try a custom 404 error that points to a servlet. Within that servlet you can capture information and log to a separate 404 log file (say, using LogBack). There are a few pages on the web that describe this process. Here's one: http://www.journaldev.com/1973/servlet-exception-and-error-handling-example-tutorial Best, John Or if possible, connect with a debugger. http://wiki.apache.org/tomcat/FAQ/Developing#Debugging Add some break points in your code and walk through till you find what is generating the 404. Dan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
