JinsightLive for IBM System z
A tool that provides a dynamic, lightweight Java profiler and visualizer for Linux on System z and z/OS.
Date Posted: February 5, 2008
|
|
 |
|
|
|
It could be you haven't specified the right class name. Another possibility is that your complete CLASSPATH string contains spaces. For example, it might have the string Program Files... in it. If it does, test_jinsight_trace will treat the remainder of your CLASSPATH string as the program name you are trying to trace, and it will fail. | | |
|
The trace is probably incomplete because the application or the tracing activity did not end normally. The visualizer is unable to read the final incomplete event(s). This problem affects only the end of the trace; the trace up to that point can still be viewed.
This problem will likely be accompanied by the Workspace Window failing to show the total number of events. A properly completed trace normally records the total number of events. The Workspace Window uses this information to show progress as it loads the trace:
If the number of events is not available because, for example, tracing ended abruptly, the Workspace Window shows only the number of events read so far:
In order to ensure a complete trace, terminate your trace by, for example, Stop Burst. | | |
|
No views are visible initially. You must open each view by choosing it in the Workspace Window's Views menu (for example, choose Views > Execution for the Execution view). | | |
|
This is OK. It may appear that the burst command is not working. But the additional delay should be due merely to buffering of the trace data before transmission to the visualizer. | | |
|
We have refined the overhead compensation calculations in JinsightLive tracing to account more accurately for overhead time due to JVM (Java™ Virtual Machine) tracing. As part of these improved calculations, the JinsightLive Timetest.class (inside file jinsightServer.jar) is used at tracing start-up to do some timing calibrations. The message indicates that the JinsightLive profiling agent could not find Timetest.class, so timings reported will be less accurate. You should fix this by placing JINSIGHT_HOME/jinsightServer.jar on the class path.
Please refer to the installation guide for instructions on updating the JVM's classpath. A restart of the JVM is required in order to pick up changes to the class path setting. | | |
|
You're probably not using a visualizer with the same build number as the tracing profiling agent. Check the visualizer build number by clicking on Help > About, and check the tracing profiling agent build number that appears on stderr when you start running the program to be traced. The visualizer should be able to read any traces produced by any earlier build of any version of Jinsight, but it is best to use a pair matched by build date. | | |
|
This is OK. The pause is probably due to the overhead compensation calculations that the profiling agent is performing during initialization. These calculations will account more accurately for overhead time due to JVM tracing. | | |
|
The visualizer is running out of memory. You can use two settings on the Java invocation of the visualizer in order to affect the amount of memory. For example:
- -Xmx205M
- -DJINSIGHT_MAXHEAP=300M
The JINSIGHT_MAXHEAP setting alerts the visualizer to put out error messages such as the one above because memory gets tight while reading a large amount of trace data. See the example in the command file named jinsightLive.bat. In that command file, you can adjust the environment variable JINSIGHT_HEAP to be about 80% of your actual memory on the machine running the visualizer. | | |
|
There are several keys that control the execution view. They include the following:
- The up, down, left, and right arrow keys move the view of the view up, down, left, and right in the frame, as would be expected.
- The comma "," and period "." keys compress and expand the time index, respectively.
- The plus "+" and minus "-" keys zoom in and zoom out on the view, respectively.
- CTL + first mouse button allows you to drag the current execution view across the screen.
- Dragging the mouse over a rectangular area lets you zoom in on the view and fills the screen with this area.
- The HOME key will reset the view as originally displayed. The same effect is achieved with the menu entry Zoom > Home.
| | |
|
Please email Louis Wilen for support.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
| |
|
|
|
|
 View screenshots:
 |
| |
View screenshots:
