Changes for page Troubleshooting Frozen Deployed Instances
Last modified by David Avendasora on 2010/11/30 06:43
From version 9.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
To version 12.1
edited by Pascal Robert
on 2007/09/03 22:05
on 2007/09/03 22:05
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. kieran1 +XWiki.probert - Content
-
... ... @@ -56,14 +56,6 @@ 56 56 57 57 Now restart your instances. 58 58 59 -Note that some JVM's on other platforms expect the "jdwp" to be specified as follows; 60 - 61 -{{noformat}} 62 - 63 --agentlib:jdwp=transport=dt_socket,address=8121,server=y,suspend 64 - 65 -{{/noformat}} 66 - 67 67 = When Something Goes Wrong... = 68 68 69 69 The instances are listed in the JavaMonitor. A screenshot is shown below with the instance number circled in red. You need to first identify which instance has frozen. ... ... @@ -128,7 +128,3 @@ 128 128 = Conclusion = 129 129 130 130 Despite the simplicity of this approach, it provides for a means by which you can find out what is going on inside frozen instances rather than playing laborious guessing games. 131 - 132 -= Alternative Approaches = 133 - 134 -[[http://www.gvcsitemaker.com/gvc.webobjects/faq&mode=single&recordID=41413]]