[CONF] Apache Tomcat > Troubleshooting and Diagnostics

[Felix Schumacher (Confluence)]

Title: Message Title

There's 2 new edits on this page

Troubleshooting and Diagnostics Felix Schumacher edited this page Here's the version comments Felix Schumacher edited at 10:25 AM Correct Typo Felix Schumacher edited at 10:24 AM Updated Links to FAQs for Memory and Developing Here's what changed: ... How To: Capture a thread dump How To: Capture a heap dump How To: Examine a Stacktrace How To: Configure Tomcat for debugging FAQ: Developing FAQ: Memory Tomcat Memory Leak Protection Sun Technical Article: Monitoring and Managing Java SE 6 Platform Applications Notes on using JMX clients ... Look into Tomcat access log (the log file generated by AccessLogValve). If your request is not listed there, then it has not been processed by Tomcat. You need to look elsewhere (e.g. at your firewall). You will see what IP address your client is using, and whether it is using an IPv4 (127.0.0.1) or IPv6 address (0:0:0:0:0:0:0:1). Modern operating systems can use IPv6 addresses for localhost / local network access, while external network is still using IPv4. 2. Take a thread dump. This way you will find out what Tomcat is actually doing. If you are troubleshooting some process that takes noticeable time, take several (three) thread dumps with some interval between them. This way you will see if there are any changes, any progress. 3. Try debugging. A good place for a breakpoint is org.apache.catalina.connector.CoyoteAdapter.service() method. That is the entry point from Tomcat connectors and into the Servlet engine. At that place your request has already been received and its processing starts. ... You can also search the archives of the Tomcat users' mailing lists for previous discussions mentioning the RECYCLE_FACADES flag. 2. Read about Java ImageIO issue. Accessing response objects after their lifetime can lead to security issues in your application, such as sending responses to wrong clients, mixing up responses. If you can reproduce the issue and the above diagnostic does not show your own bug, but a bug in Apache Tomcat, ... Go to page history View page

Stop watching space • Manage notifications This message was sent by Atlassian Confluence 6.15.2