![jprofiler tutorial jprofiler tutorial](https://wiki.onap.org/download/attachments/25440364/image2018-3-12_14-8-31.png)
When the plan finishes executing, click on /sample/i002 which is a shortcut to the agent view page. Select the plan and execute it: it first stops the jetty server uninstalls it entirely and reinstall and restart the new one. Note that since there is only 1 entry, choosing SEQUENTIAL or PARALLEL will have the same effect. Click on the 'Plans' subtab.Ĭhoose 'Deploy / SEQUENTIAL'. It is graphically represented as a different color.Ĭlick on '/sample/i002' which sets a filter on the model: it excludes all the entries except the one where 'mountPoint' is equal to '/sample/i002'. There is a delta: the system in the console is not matching with what is currently deployed. If you click on the status you can view an explanation of the delta (in this case the context path is different). Note that the second row is now yellow and the status says 'DELTA'. In the second entry (look for "port": 9001, around the bottom of the text area), change the contextPath value to /cp3. The format is an array of entries representing each entry in the model (as explained previously). You should now see the json document that you loaded previously.
![jprofiler tutorial jprofiler tutorial](https://wiki.onap.org/download/attachments/25440364/image2018-3-12_14-7-50.png)
# su - tomcat -c 'nohup java -Dserver.port=8080 -server -Xms256M -Xmx512M -Xmn128M -XX:MetaspaceSize=128M -XX:MaxMetaspaceSize=256M -Xss512k -XX:+DisableExplicitGC -XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=10 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSParallelRemarkEnabled -XX:+CMSClassUnloadingEnabled -XX:LargePageSizeInBytes=128M-XX:+UseFastAccessorMethods -XX:CMSInitiatingOccupancyFraction=70 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/server/application/xw-web/logs/ -Djava.io.tmpdir=/server/application/xw-web/temp =perf -jar /server/application/xw-web/ef9c483.jar>/server/application/xw-web/logs/catalina.out -agentlib:jprofilerti=port=8849 -Xbootclasspath/a:/opt/jprofiler11/bin/agent.You should see a table with 2 entries which shows you the model that you loaded previously (the one highlighted) as well as the empty model (default one when creating a fabric)Ĭlick on the first id. # kill -s 9 19205 //Enter the project package storage directory and execute the startup command # ps -ef | grep /server /application /xw -web |grep -v grep |grep tomcat |awk '' 19205
![jprofiler tutorial jprofiler tutorial](https://examples.javacodegeeks.com/wp-content/uploads/2015/12/telemetries_new.jpg)
First query the project startup process and kill it
![jprofiler tutorial jprofiler tutorial](https://www.ej-technologies.com/blog/wp-content/uploads/2014/06/K0e45veXZpwdoF63FLu67H5hx4ltpEpA3uW3G1eCuhX.png)
Offline mode (use config file to set profiling settings ) 1 Please select the profiling mode : GUI mode (attach with JProfiler GUI ) First select mode: 1, then enter the connection port number: 8849: # sudo -u tomcat /opt /jprofiler11 /bin /jpenableĬonnecting to /server /application /xw -web /ef9c48. # Uncomment the following line to add additional VM parametersĮxecution again, success. INSTALL4J_JAVA_HOME_OVERRIDE = /server /jdk1. The modification is as follows: # Uncomment the following line to override the JVM search sequence You need to modify the jpenable file and execute: vim jpenable edits the file. Please define INSTALL4J_JAVA_HOME to point to a suitable JVM. The version of the JVM must be at least 1.6 and at most 11. If the following error occurs: No suitable Java Virtual Machine could be found on your system. # sudo -u tomcat /opt /jprofiler11 /bin /jpenable