At that place your request has already been received and its processing starts. That is the entry point from Tomcat connectors and into the Servlet engine.

A good place for a breakpoint is .rvice() method.

This way you will see if there are any changes, any progress.

If you are troubleshooting some process that takes noticeable time, take several (three) thread dumps with some interval between them.

This way you will find out what Tomcat is actually doing. Modern operating systems can use IPv6 addresses for localhost / local network access, while external network is still using IPv4.

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).

If your request is not listed there, then it has not been processed by Tomcat.

Look into Tomcat access log (the log file generated by AccessLogValve).

If you have already looked into Tomcat logs, there are no error messages, and you just want to find out what is going on, you may try the following Java 5 JConsole and Remote Management FAQįrom Java 6 onward a process does not need to have the management agent enabled when it starts, as the Attach API permits the management agent to be activated on demand. NB(2) On Windows, if Tomcat is started using a service wrapper, this will prevent JConsole & VisualVM from using the local JMX connector stub.

NB(1) On Windows, this means that the temporary directory must be located on an NTFS formatted disk. Java processes which are accessible via the local connector will automatically appear in the client. This method relies on being able to create a protected temporary file, accessible only to a user with administrator privileges. When running a JMX client (JConsole, VisualVM) on the same machine as the target JVM process it is possible to connect without pre-configuring a JMX port, using the local connector stub. jcmd - Multitool intended to replace the above JDK tools.

jmap - Dumps heap and shows heap status.

Apache ant ppt