Jprofiler Monitoring Tomcat_ Application Deployment

Introduced
Jprofiler is a full-featured Java profiling Tool (Profiler) designed to analyze J2SE and EE applications.
Jprofiler is a commercially mandated Java profiling tool developed by EJ Technology Limited for Java EE and Java SE applications. It allows two memory sections to evaluate memory usage and dynamic allocation of leaks and CPU profiling to assess threading conflicts. Jprofiler Intuitive GUI allows you to find performance bottlenecks, capture memory misses (memory leaks), and troubleshoot threads.

Environment: 1, JDK 1.7

2, Jprofiler 9.0.3

3, Tomcat 7

Download Address: http://www.ej-technologies.com/download/jprofiler/files

Remote linux Server configuration decompression:
Tar -ZXVF jprofiler_linux_9_0_3.tar.gz

Copy:
CD jprofiler9/bin/
CP jprofiler/usr/local/

Configure environment variable:
Modify/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 effective: Source/etc/profile

Local Windows installation to run the download directly jprofiler_windows-x64_9_0_ 3.exe
always Next to the place where you enter the registration code, the following is the registration code you can use
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

Install to the end, run Jprofiler.

Generating scripts

To generate the startup_jprofiler.sh script on this computer, follow these steps:

At this point, the startup_jprofiler.sh has been generated and the build location is in the same directory as the startup.sh we chose.

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

Unlike the usual boot tomcat, instead of using startup.sh, we started Tomcat directly using startup_jprofiler.sh.

Here's what you need to say, the default startup_jprofiler.sh the last boot Tomcat is run, we need to modify it to start, we compare the difference between startup.sh and startup_jprofiler.sh:

In fact, the difference is to add 2 lines of configuration, recommended that you copy directly on the server startup.sh as startup_jprofiler.sh, and then add the following two lines can be:

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

If you are using a tool-generated startup_jprofiler.sh, notice that we want to change the last line of the startup_jprofiler.sh run to start, then start Tomcat, and start as shown:

Finally, start Jprofiler monitoring

After clicking OK, we can view the various situations of server Tomcat.