WebSphere Application Server - Help with Thread Analyzer

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Application Server > March 2006 > Help with Thread Analyzer





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Help with Thread Analyzer

2006-03-21, 8:34 am

Problem background:
Websphere Application Server process is present after stopping the server. SystemOut.log shows the server as being stopped. It was suggested in this forum that a thread might still be running after the server stops. So I used kill -3 <process ID> to get a
javacore.....txt file.

I then used Thread Analyzer to view the thread dump. The Analyzer says that 37 threads are still present. (The server is stopped) I don't know how to interpret the analysis. I can provide the thread dump file to anyone who can help me with solving this i
ssue.

Thank you.

Environment: WAS ND 5.1.9, AIX 5.2, LDAP, SSL etc.

Kind Regards,
MPro
Ken Hygh

2006-03-21, 8:34 am

mzkhan@btinternet.com wrote:
> Problem background:
> Websphere Application Server process is present after stopping the server. SystemOut.log shows the server as being stopped. It was suggested in this forum that a thread might still be running after the server stops. So I used kill -3 <process ID> to get

a javacore.....txt file.
>
> I then used Thread Analyzer to view the thread dump. The Analyzer says that 37 threads are still present. (The server is stopped) I don't know how to interpret the analysis. I can provide the thread dump file to anyone who can help me with solving this

issue.
>
> Thank you.
>
> Environment: WAS ND 5.1.9, AIX 5.2, LDAP, SSL etc.
>
> Kind Regards,
> MPro


Even if you can identify the TID of the offending thread, that won't
help you resolve the issue. What you need to do is ask your developers
who is creating threads, and have them figure out a way to stop their
thread when the server (or application) is going down.

Ken
Ben_

2006-03-21, 5:57 pm

Review the stacktraces to identify whose code is still running (WebSphere or
your application) and what exactly it is doing.

You can post the javacore to the newsgroup or somewhere on the web.


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com