On 2/22/06, Erik Daughtrey <[EMAIL PROTECTED]
> wrote:
Hello,
For this sort of problem, I've found analysis of jvm thread dumps very
effective.
If you're using unix, then "kill -QUIT pid" is usually sufficient to get a
current thread dump. In this case, pid would be the process id of the
running Tomcat process.
If you're using Windows, then the easiest way to get a thread dump is by
running the target process in the foreground and using CTRL+BREAK. The
output will usually go to stderr or stdout so, using output redirection on
the process at startup is recommended.
Where the output goes depends on the jdk in use. It may wind up in the
stderr/stdout, or files like javadumpxxxx may appear in the current directory
of the process being dumped.
Analyzing a threaddump can be tricky, but I suspect that in this case it may
jump from the output. Personally, I'd look for some number of threads having
the same or very similar top of stack. This will indicate the first level of
debug. I suspect that the threads are waiting on some external resource --
at least that's been my experience in cases like these.
Good luck.
On Wednesday 22 February 2006 12:54, Franz Coriand wrote:
> Hi all,
>
> we have the problem, that our webservices become very slow after some
> requests.
> For the first request we need about 10s.
> For the 100th request we need about 2mins - its the same request like
> the first one, with the same result.
>
> We use Tomcat 5.5.12 and Axis 1.3.
>
> We have no clue what's the problem.
> Do you have any ideas?
>
> Thanks, Franz
--
Regards,
Erik
