JProfiler monitoring Tomcat

JProfiler monitoring Tomcat
Introduction
JProfiler is a full-featured Java profiling tool (profiler) dedicated to analyzing J2SE and J2EE applications.
JProfiler is a commercial-authorized Java profiling tool developed for Java EE and Java SE applications by J Technology Co., Ltd. It allows two memory profiles to evaluate memory usage and Dynamic Allocation leaks and CPU profiling to evaluate thread conflicts. JProfiler's intuitive GUI allows you to find performance bottlenecks, capture memory leaks (memory leaks), and solve execution thread problems.

Environment: 1. jdk 1.7

2. jprofiler 9.0.3

3. Tomcat 7

: Http://www.ej-technologies.com/download/jprofiler/files

Unzipping remote Linux Server Configuration:
Tar-zxvf jprofiler_linux_9_0_3.tar.gz

Copy:
Cd jprofiler9/bin/
Cp jprofiler/usr/local/

Configure environment variables:
Modify the/etc/profile system configuration file:
JPROFILER_HOME =/opt/shanhy/jprofiler9/bin/linux-x64
Export LD_LIBRARY_PATH = $ LD_LIBRARY_PATH: $ JPROFILER_HOME
Make the configuration file take effect: source/etc/profile

Local Windows installation run the downloaded jprofiler_windows-x64_9_0_3.exe directly
Until Next to enter the registration code, the following is the available registration code
L-Larry_Lau@163.com #36573-fdkscp15axjj6 #25257 (PRO test available)
L-Larry_Lau@163.com #5481-ucjn4a16rvd98 #6038
L-Larry_Lau@163.com # 99016-hli5ay1ylizjj #27215
L-Larry_Lau@163.com #40775-3wle0g1uin5c1 #0674
L-Larry_Lau@163.com # 7009-14frku31ynzpfr #20176
L-Larry_Lau@163.com #49604-1jfe58we9gyb6 #5814
L-Larry_Lau@163.com # 25531-1qcev4yintqkj #23927
L-Larry_Lau@163.com # 96496-1qsu1lb1jz7g8w #23479
L-Larry_Lau@163.com # 20948-11amlvg181cw0p #171159

Run jProfiler at the end of installation.

 

Generate scripts

Generate the startup_jprofiler.sh script on the local machine. The steps are as follows:

 

So far, startup_jprofiler.sh has been generated, and the generated location is in the same directory as startup. sh we selected.

Upload startup_jprofiler.sh to the Tomcat/bin directory of the remote Linux server.

Unlike starting Tomcat normally, instead of using startup. sh, we directly use startup_jprofiler.sh to start Tomcat.

Here we need to talk about the difference between startup_jprofiler.sh and startup_jprofiler.sh when starting Tomcat by default. We need to modify it to start. Next we will compare the differences between startup. sh and startup_jprofiler.sh:

 

In fact, the difference is that two lines of configuration are added. We recommend that you directly copy startup. sh on the server as startup_jprofiler.sh, and then add the following two lines:

CATALINA_OPTS = "-agentpath:/opt/jprofiler9/bin/linux-x64/libjprofilerti. so = port = 8849, nowait $ CATALINA_OPTS"
Export CATALINA_OPTS

 

If you are using the startup_jprofiler.sh generated by the tool, note that we should change the run of the last line of the generated startup_jprofiler.sh to start, then start Tomcat and start:

 

Finally, start jProfiler monitoring

 

Click OK to view the various Tomcat server situations.