YourKit and Jprofile with Alfresco

1. We can run jprofiler and YKit from the remote machine.

Basically these tools will be putting the configurations in the server, startup.bat file and we can start alfresco using alf_start.bat normally.

Jprofiler :

1. Install Jprofiler in the client machine and server machine.

2. In the client machine run the wizard by selecting option an application server locally or remotely

in the wizard provide jprofile installation directory, location of startup.bat file,ip of the machine and the type of tomcat

port number for jprofile to run. When we Finish the wizard it updates

startup.bat file and makes below entry

rem The following lines have been added by the rem application server integration wizard of JProfiler

set CATALINA_OPTS=-agentpath:C:\jprofiler7\bin\windows-x64\jprofilerti.dll=port=8849 %CATALINA_OPTS%

rem end of modifications

3. Now from client Go to Start Center - and select the previously configured Ip

Your Kit

1. Install Your Kit in client and server 2. Through the command prompt execute below caoomnds C:\yourkit\lib>java -jar yjp.jar -integrate

follow the steps,

C:\yourkit\lib>java -jar yjp.jar -integrate Choose server to integrate with:

1) Geronimo

2) GlassFish / Sun Application Server

3) JBoss

4) Jetty HTTP Server 5.x

5) JRun 4

6) Resin 2.x/3.x

7) Tomcat 3/4/5/6/7

8) WebLogic 9 and newer

9) WebSphere Application Server 7

10) Generic server (use if your server is not on the list) Enter number which corresponds to your server (0 to exit) and press Enter:

>7

Please specify whether the server runs on a 32-bit JVM or a 64-bit JVM.

Hint: If you are not sure what to choose, choose "32-bit JVM". If with this choi ce the server does not start with profiling, re-run the integration and choose "

64-bit Java" option.

1) 32-bit JVM

2) 64-bit JVM

>2

Location of Tomcat startup script (\bin\startup.bat or tomcat5.exe or tomcat6.exe or tomcat7.exe):

>C:\alfresco-server-bmi335\tomcat\bin\startup.bat

Startup options configuration: step 1 of 5 Should option 'disablestacktelemetry' be specified?

1) Yes (recommended to minimize profiling overhead in production)

2) No

>2

Startup options configuration: step 2 of 5 Should option 'disableexceptiontelemetry' be specified?

1) Yes (recommended to minimize profiling overhead in production)

2) No

>2

Startup options configuration: step 3 of 5 Should option 'builtinprobes=none' be specified?

1) Yes (recommended to minimize profiling overhead in production)

2) No

>2

Startup options configuration: step 4 of 5 Should option 'delay=10000' be specified?

1) Yes (recommended)

2) No

>2

Startup options configuration: step 5 of 5 Please specify comma-separated list of additional startup options, or press Ente r for no additional options:

>

It changes the file start_up.bat. later we can start alfresco with alf_start.bat Startup script to be used for profiling has been successfully created:

set JAVA_OPTS=-agentpath:C:\yourkit\bin\win64\yjpagent.dll=sessionname=Tomcat %JAVA_OPTS%

When we start server, we should be able to connect to it by seeing the logs from remote profiling of YKIT

Make sure The path of installation of Jprofile and YKit is not having spaces and special characters,else server will not start

Info i got from

http://www.yourkit.com/docs/80/help/profiling_j2ee_remote.jsp