Changes for page Troubleshooting Frozen Deployed Instances
Last modified by David Avendasora on 2010/11/30 06:43
From version 7.1
edited by Jonathan 'Wolf' Rentzsch
on 2009/02/03 16:54
on 2009/02/03 16:54
Change comment:
There is no comment for this version
To version 8.1
edited by Kieran Kelleher
on 2008/02/04 06:35
on 2008/02/04 06:35
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. rentzsch1 +XWiki.kieran - Content
-
... ... @@ -94,20 +94,6 @@ 94 94 95 95 = What to Look For = 96 96 97 -##jdb##'s ##watch all## command will give you a stack trace for all threads in your app. But your process needs first to be suspended in order to get a coherent stack trace. Use it like so: 98 - 99 -{{noformat}} 100 - 101 -> suspend 102 -All threads suspended. 103 -> where all 104 -... 105 -> suspend 106 -All threads suspended. 107 -> 108 - 109 -{{/noformat}} 110 - 111 111 An example of a stack trace is shown below. You'll notice the java class name and source-code line number at the end of a particular entry in the stack. Here we can see that the thread called "WorkerThread103" has stuck trying to get a session from the session store. In this situation another thread will most likely have the session store locked and is not releasing the lock. 112 112 113 113 {{noformat}}