Use: For performance issue in 10.6 and above glowroot must be collected as a part of analysis.
1. If you start application as service, Uncomment below entry in wrapper.conf and restart the application server.
#wrapper.java.additional.42=-javaagent:../glowroot/glowroot.jar
2. If you start application through SDP_HOME/bin/run.bat, Uncomment below entry in run.bat and restart the application server.(You can uncomment by removing rem)
rem set JAVA_OPTS=%JAVA_OPTS% -javaagent:"%SERVER_HOME%\glowroot\glowroot.jar"
3. If you start application through SDP_HOME/bin/run.sh, Uncomment below entry in wrapper.conf and restart the application server.
#JAVA_OPTS="$JAVA_OPTS -javaagent:$SERVER_HOME/glowroot/glowroot.jar"
Glowroot must be enabled for atleast two days, After two days from enabling collect the glowroot folder present under SDP_HOME/.
After collecting glowroot log ask cx to revert the above changes and restart the server to disable glowroot.
For Linux instance, Uncomment the below entry in the file called Run.sh available under SDP_HOME/bin/run.sh
#JAVA_OPTS="$JAVA_OPTS -javaagent:$SERVER_HOME/glowroot/glowroot.jar"
Disable the glowroot, when it is not required or when the application is up & running fine.
How to check if glowroot is enabled correctly:
1. Connect to localhost:4000
If the glowroot is not enabled you will get the error stating the page is not connected:
Note : Please ensure that the application is stopped and started once successfully after enabling glowroot, as sometimes restarting the application will not enable the glowroot properly hence stop the application and then start it once.
2. After enabling the glowroot when you connect to localhost:4000 It will connect and the page will display as the below:
Please make sure the glowroot is enabled successfully so that the performance of the application is monitored.