Jprofiler 9.2

Jprofiler Introduction

Jprofiler is a full-featured Java profiling tool (Profiler) designed to analyze J2SE and EE applications. It combines the analysis of CPU, thread, and memory in a powerful application. Jprofiler can provide many IDE consolidation and application server consolidation purposes. Jprofiler Intuitive GUI allows you to find performance bottlenecks, capture memory misses (memory leaks), and troubleshoot threads. It gives you the root analysis of Heap Walker as a resource collector, and can easily identify memory overflows; heap snapshot (snapshot) mode lets an object that is not referenced (reference), a slightly referenced object, or at the end (Finalizati On) The object of the queue is removed, and the wizard is integrated to dissect the browser's Java plug-in functionality. Download Address

http://www.ej-technologies.com/index.html Installation Environment Server

CentOS Release 6.7 Linux 2.6.32-573.8.1.el6.x86_64
JDK 1.7.0_80
Tomcat 7.0.65

Client

Win7
Jprofiler 9.2 Client

Installation Method ServerDownload the script file and upload it to the server jprofiler_linux_9_2.sh install
Chmod+x jprofiler_linux_9_2.sh
./jprofiler_linux_9_2.sh-c
Installation process slightly ... Almost enter the end (also can be installed in the graphical interface without the-C option, for graphics installation)
Default installation to/opt/jprofiler9
Setting environment variables
Add in Etc/profile
Export jprofiler_home=/opt/jprofiler9/bin/linux-x64
Export Ld_library_path= LDLIBRARYPATH:LD_LIBRARY_PATH:JPROFILER_HOME
Set Variable effective source profile Client

Direct Run Jprofiler_windows-x64_9_2.exe
Registration code:
l-larry_lau@163.com#23874-hrwpdp1sh1wrn#0620
l-larry_lau@163.com#36573-fdkscp15axjj6#25257
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 monitoring generation monitoring script

To generate a script in Jprofiler client, 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 the thing to say is that the default startup_jprofiler.sh finally starts Tomcat for run, we need to modify it, change it to start, let's compare startup.sh and startup_jprofiler.sh The difference :

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. Tomcat Configuration Modify catalina.sh file
Add in catalina.sh
java_opts= "$JAVA _opts-agentlib:jprofilerti=port=8849-xbootclasspath/a:/opt/jprofiler9/bin/agent.jar" startup script to start listening
startup_jprofiler.sh Client Monitoring

Reference articles
Http://www.cnblogs.com/langtianya/archive/2013/07/04/3172180.html