Tell me more ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
up vote 0 down vote favorite

I have a WebSphere application server running on two nodes in a cluster.

At a given time, only one node remains up and the other one in hung JVM thread.

If I stop the running one, the other one is able to come up but then the second one gets hung.

We have an application that is having its configuration files on shared NAS drive, accessible by both the nodes. We have checked for exclusive read locks on those files in NAS , which could be causing this, but this is not the case.

Can anyone point me to possible causes of this odd behavior ?

share|improve this question
1  
kill -3 on the process IDs and look at the resulting javacore files. Analyze the stack traces of each listed thread and see if you can pinpoint exactly where the thread(s) is(are) hung. If that doesn't resolve the problem for you, I suggest posting the stack traces here into the question. – dbreaux Dec 25 '12 at 0:58

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.