Difference between revisions of "Debugging remote JBoss server"

Revision as of 09:45, 11 September 2012

If you got problems on production environment this configuration is specially useful.

OpenKM 6.x - Tomcat

Add the following options when the JVM is started:

-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n

If you are using shell scripts to start Tomcat, start it with the following command:

$ $TOMCAT_HOME/bin/catalina.sh jpda start

It will start Tomcat so that a remote debugger can be connected to port 8000.

OpenKM 5.1 - JBoss

Add this line at the top of $JBOSS_HOME/bin/run.sh script:

JAVA_OPTS="-Xmx2000m -Djava.awt.headless=true -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000"

Select the project and the host. Include in source your OpenKM java project. You can debug normally, setting breakpoints etc...

There are some other interesting tools for debugging and profiling a Java application:

@@ Line 40: / Line 40: @@
 ** [https://blogs.oracle.com/nbprofiler/entry/profiling_with_visualvm_part_1 Profiling With VisualVM, Part 1]
 ** [https://blogs.oracle.com/nbprofiler/entry/profiling_with_visualvm_part_2 Profiling With VisualVM, Part 2]
+** [http://hillert.blogspot.com.es/2010/01/remote-profiling-of-jboss-using.html Remote Profiling of JBoss using VisualVM]
 * [http://java.sun.com/developer/technicalArticles/Programming/HPROF.html HPROF: A Heap/CPU Profiling Tool in J2SE 5.0]
 * [https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=HPJMETER HPjmeter]
 [[Category:Developer Guide]]