This page last changed on Aug 16, 2006 by dylan@atlassian.com.

If some of the steps in the Profiling Memory and CPU usage with YourKit page are skipped or not correctly followed you could run into some trouble. Here are some things to look out for:

'Oops - an error has occurred' when viewing manageyourkitprofiling.jsp

If you encounter an error page when trying to view the manageyourkitprofiling.jsp that looks like this:

org.apache.jasper.JasperException: Unable to compile class for JSP Generated servlet error: Only a type can be imported. com.yourkit.api.Controller resolves to a package An error occurred at line: 5 in the jsp file: /secure/admin/manageyourkitprofiling.jsp Generated servlet error: Controller cannot be resolved (or is not a valid type) for the parameter controller of the method stopMemoryRecording An error occurred at line: 5 in the jsp file: /secure/admin/manageyourkitprofiling.jsp Generated servlet error: Controller cannot be resolved (or is not a valid type) for the parameter controller of the method stopCPURecording An error occurred at line: 5 in the jsp file: /secure/admin/manageyourkitprofiling.jsp Generated servlet error: Controller cannot be resolved (or is not a valid type) for the parameter controller of the method dumpMemoryInfo An error occurred at line: 5 in the jsp file: /secure/admin/manageyourkitprofiling.jsp Generated servlet error: Controller cannot be resolved (or is not a valid type) for the parameter controller of the method dumpCPUInfo An error occurred at line: 5 in the jsp file: /secure/admin/manageyourkitprofiling.jsp Generated servlet error: Controller cannot be resolved (or is not a valid type) for the parameter controller of the method startCPURecording An error occurred at line: 5 in the jsp file: /secure/admin/manageyourkitprofiling.jsp Generated servlet error: Controller cannot be resolved (or is not a valid type) for the parameter controller of the method startMemoryRecording An error occurred at line: 109 in the jsp file: /secure/admin/manageyourkitprofiling.jsp Generated servlet error: Controller cannot be resolved or is not a type An error occurred at line: 109 in the jsp file: /secure/admin/manageyourkitprofiling.jsp Generated servlet error: Controller cannot be resolved or is not a type

It is likely that you have not correctly included the yjp-controller-api-redist.jar in your JIRA WEB-INF/lib directory or you have not restarted JIRA since you have placed the jar there. Please verify that the jar is present and that JIRA has been restarted and try again.

HTTP Status 404 - /secure/admin/manageyourkitprofiling.jsp

If you encounter this error when trying to view the manageyourkitprofiling.jsp then the likely cause is that you have not correctly placed the manageyourkitprofiling.jsp into your instance of JIRA. Please verify that the file is present in the correct place and try again.

Error occurred during initialization of VM Could not find -Xrun library: libyjpagent.so

If you encounter this error then it is likely that you have not made the profiler agent library accessible to the Java Virtual Machine correctly while trying to use the -Xrunyjpagent JMV parameter. Please re-read the section on this and ensure that you have set this up correctly and try again.

Error occurred during initialization of VM Could not find agent library on the library path or in the local directory: yjpagent

If you encounter this error then it is likely that you have not made the profiler agent library accessible to the Java Virtual Machine correctly while trying to use the -agentlib:yjpagent JMV parameter. Please re-read the section on this and ensure that you have set this up correctly and try again.

'Error: An unknown error occurred, caused by: To profile application, you should run it with the profiler agent' shown on manageyourkitprofiling.jsp page

If you see this error when viewing the manageyourkitprofiling.jsp page then it is likely that you have not instructed the JVM running JIRA to use the YourKit Agent. Please re-read the section on this and ensure that you have set this up correctly and try again.

Document generated by Confluence on Oct 06, 2009 00:26