: Tuesday, October 18, 2005 4:03 PM
> To: users@tomcat.apache.org
> Subject: RE: Debugging Tomcat hangs
>
>
> I understand synchronization and deadlocks. I'm just looking
> for some guidance. (1) Based on the problem I've described,
> is an analysis of a JVM thread du
On 10/18/05, David Boyer <[EMAIL PROTECTED]> wrote:
> (2) are there any resources that would be helpful with that analysis (e.g.
> >something that I can use as a tutorial for understanding everything the dump
> >contains).
Take a look at:
http://issues.apache.org/bugzilla/show_bug.cgi?id=36541
I understand synchronization and deadlocks. I'm just looking for some guidance.
(1) Based on the problem I've described, is an analysis of a JVM thread dump a
good next step for diagnosing the hang, or else what would be and (2) are there
any resources that would be helpful with that analysis (e
> If I generate a dump of the JVM using Ctrl-Break while
> running Tomcat as a console app, what's the best resource for
> interpreting this? I suspect the problem is a thread
> deadlock, or something similar.
This tells us that you succeed in getting a JVM thread dump and
you are asking for he
One stupid suggestion is to run the tomcat inside an environment like
eclipse
with an eclipse plugin like sysdeo. Then stress the webapplication.
When, it 'hangs'
issue a 'pause' inside the tomcat jvm, and explore the various threads.
Search for 2 kinds of locks:
- non returning http-thread leadin
can you port your application to linux where kill -quit given you
complete stacktrace? Unfortunately I don't know how to create full
stack trace under windows, but you'd need it definitely.
Have you tried the manager? It could show you the
servlets/actions/whatever which hangs. Probably you have a
