Difference between revisions of "Profiling OpenKM"
| Line 1: | Line 1: | ||
You can profiling local and remote Java applications using [http://docs.oracle.com/javase/6/docs/technotes/guides/visualvm/index.html Java VisualVM]. For local application is easy because it detect automatically them and show in the listing. For remote application you need to do a little work. | You can profiling local and remote Java applications using [http://docs.oracle.com/javase/6/docs/technotes/guides/visualvm/index.html Java VisualVM]. For local application is easy because it detect automatically them and show in the listing. For remote application you need to do a little work. | ||
| − | First of all add this line to '''$TOMCAT_HOME/bin/setenv.sh''' (or '''setenv.bat''' if using Windows) | + | First of all add this line to '''$TOMCAT_HOME/bin/setenv.sh''' file (or '''setenv.bat''' if using Windows): |
<source lang="bash"> | <source lang="bash"> | ||
| Line 28: | Line 28: | ||
Java includes HPROF, a profiler which collect application runtime information. HPROF is capable of presenting CPU usage, heap allocation statistics, and monitor contention profiles. | Java includes HPROF, a profiler which collect application runtime information. HPROF is capable of presenting CPU usage, heap allocation statistics, and monitor contention profiles. | ||
| − | For example, can collect CPU usage information by sampling threads. Add this line to '''$TOMCAT_HOME/bin/setenv.sh''' (or '''setenv.bat''' if using Windows) | + | For example, can collect CPU usage information by sampling threads. Add this line to '''$TOMCAT_HOME/bin/setenv.sh''' file (or '''setenv.bat''' if using Windows): |
<source lang="bash"> | <source lang="bash"> | ||
Revision as of 09:37, 20 September 2012
You can profiling local and remote Java applications using Java VisualVM. For local application is easy because it detect automatically them and show in the listing. For remote application you need to do a little work.
First of all add this line to $TOMCAT_HOME/bin/setenv.sh file (or setenv.bat if using Windows):
CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote=true"
CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote.port=9090"
CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote.ssl=false"
CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote.authenticate=false"
CATALINA_OPTS="$CATALINA_OPTS -Djava.rmi.server.hostname=localhost"
 |
The java.rmi.server.hostname should match the IP of the remote server, so replace localhost by the right IP. |
In order to connect to this remote Tomcat instance, go to File > Add JMX Connection... and fill the hostname and port. In this case the port is 9090 but you can set another one using the com.sun.management.jmxremote.port property.
More info:
- Profiling With VisualVM, Part 1
- Profiling With VisualVM, Part 2
- Connecting Visual VM to Tomcat 7
- Remote Profiling of JBoss using VisualVM
- Troubleshooting application performance with VisualVM
- Monitoring of Tomcat with VisualVM and VisualGC
- Using VisualVM to fix live Tomcat and JVM problems
HPROF
Java includes HPROF, a profiler which collect application runtime information. HPROF is capable of presenting CPU usage, heap allocation statistics, and monitor contention profiles.
For example, can collect CPU usage information by sampling threads. Add this line to $TOMCAT_HOME/bin/setenv.sh file (or setenv.bat if using Windows):
CATALINA_OPTS="$CATALINA_OPTS -agentlib:hprof=cpu=samples"
When Tomcat starts you can see a file called java.hprof.txt. The CPU profiling info will be dumped to this file once Tomcat process is stopped.
More info:
