This section contains the following topics:
The Precise FocalPoint agent stores installation packages files in the following folder:
<i3_root>/products/i3fp/distribution_source
The distribution source folder contains a great quantity of files, and consumes a lot of disk space. If you have difficulties in allocating disk space on the Precise FocalPoint file system, you can specify an alternative folder as the distribution source folder. This alternative folder can be on the same machine or on a network share.
To define an alternative distribution source folder
<i3_root>/products/i3fp/distribution_source
<i3_root>/products/i3fp/registry/products/infrastructure/setup/settings.xml
Change:
<distribution-source-location>products/i3fp/distribution_source</distribution-source-location> to the new location of the distribution source folder (the one you've copied the files to)
Use the forward slash (/) in this entry for UNIX and Windows systems. |
If you have placed the folder on a network share, you should:
For more details about running Precise with a different user, see appendix D in the Installation Guide.
Do not share the same distribution_source folder amongst several Precise installations. |
In case of a federation installation, only the main Precise FocalPoint holds the distribution source folder, and all operations mentioned in this section are relevant only to the main Precise FocalPoint server. |
Over-instrumentation protection should be implemented when in non-production mode only. |
Over-instrumentation protection monitors the overhead that instrumentation introduces and turns off instrumentation when the contribution to the overhead from instrumentation exceeds the thresholds that were user-defined or set by adaptive instrumentation relative to the current overhead budget. Over-instrumentation protection estimates the average percentage that instrumentation contributes to the response time of a method or method invocation. If that time exceeds the threshold, instrumentation on that method or method invocation is disabled and messages are written to the application system error stream and to the over-instrumentation protection log file.
Over-instrumentation protection is enabled by default because the OverInstrumentationProtection.xml file is included in the InstrumenterConfigList.xml file, which is located in the <i3_root>/products/j2ee/config/JVMID
directory.
Over-instrumentation protection uses the following tunable parameters that are contained in the system.properties file located in each JVM’s configuration directory:
Threshold. The threshold specifies the maximum percentage of overhead that instrumentation may contribute to the average response time of a method or method invocation. Adaptive instrumentation sets this value. When adaptive instrumentation modifies the threshold, the previous value is commented in place and the new threshold is appended. Default: 50%.
This default does not mean that the application runs 50% slower, nor does it directly correlate with the actual performance of the application. |
To disable over-instrumentation protection
To change the parameters of over-instrumentation protection
<i3_root>/products/j2ee/config/JVMID
and add the following lines: When over-instrumentation protection disables instrumentation, it issues the following log messages to the application system error stream and to the Over-instrumentation protection log files:
<i3_root>/logs/j2ee.JVMID.oip.log
<i3_root>/logs/j2ee.JVMID.oip.trc
When over-instrumentation protection disables instrumentation on a method, an error message containing text such as the following is created:
disabled_logging:
[classname, methodname, signature, invocation-count, response-time, ]
data-collection-count, data-collection-time, threshold]
<OverInstrumentationProtectionHandler>
When over-instrumentation protection disables instrumentation on a method invocation, an error message containing text such as the following is created:
disabled_logging:
[classname, methodname, signature, classname-called,
methodname-called, signature-called, invocation-count,
response-time, data-collection-count, data-collection-time, threshold]
<OverInstrumentationProtectionHandler>
where
| | | | | | | |