Changes between Version 25 and Version 26 of miniGlobalNotes

Timestamp:

2013-12-16T10:20:45-05:00 (12 years ago)

Author:

warb

Comment:

--

miniGlobalNotes

@@ -33 +33 @@
 ||Chris  Continisio   || (609) 485-5869 || Christopher.CTR.Continisio@faa.gov || NIEC Support
 
-
+=== Java Debugging ===
+{{{
+Step 2: Request a Thread Dump from the JVM
+jstack
+
+If installed/available, we recommend using the jstack tool. It prints thread dumps to the command line console.
+
+To obtain a thread dump using jstack, run the following command:
+jstack <pid>
+
+You can output consecutive thread dumps to a file by using the console output redirect/append directive:
+jstack <pid> >> threaddumps.log
+}}}
+
+Remote Debugging: Client Side: http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Ftasks%2Ftask-remotejava_launch_config.htm 
+
+http://javarevisited.blogspot.com/2011/02/how-to-setup-remote-debugging-in.html
+{{{
+ In order to remote debug a Java application from Eclipse, that application must be started with following JVM debug options:
+
+java -Xdebug -Xrunjdwp:transport=dt_socket,address=8001,server=y,suspend=n -jar stockTradingGUI.jar
+
+This will start java application stockTradingGUI into debug mode using Java Debug Wire Protocol (jdwp) protocol and it will listen on port 8001 suspend=y will ensure that that application will not start running until Eclipse connect it on speicified debug port.It also important to note that application must be start before Eclipse tries to connect it other wise Eclipse will throw error "Failed to connect to remote VM. Connection refused" or "Connection refused: connect" 
+
+Read more: http://javarevisited.blogspot.com/2011/02/how-to-setup-remote-debugging-in.html#ixzz2neS6aaZg
+
+
+{{{
 === SGET ===