Chatta subito con l'assistenza
Chat con il supporto

Foglight for Java EE Technologies 5.9.9 - Installation Guide

Install and Configure Foglight for Java EE Technologies Integrate with JBoss Integrate with Apache Tomcat Integrate with WebLogic Domain Startup Scripts Integrate with WebSphere Integrate with Oracle AS Create a Generic Installation for Manual Java EE Agent Integration Manage Java EE Agent Installations, Integrations, and Configurations Managing Java EE Agent Configurations Java EE Installation Management Java EE Integration Configuration FAQ and Troubleshooting Manual Application Server Integrations AppendixB: Managing Permissions for the Java EE Integration Agent Appendix A: Java EE Application Methods

Setting the Maximum Request Fragment cache size

In the period between requests, the Java EE agent caches the data structures used to collect the data for request fragments. The MaxRequestFragmentCacheSize setting determines the maximum number of request fragments that are stored in the cache. The default value is 50. Set the value to zero (0) to disable the cache.
* 
NOTE: This setting is only valid for FullDetail, ComponentDetail and BasicDetail Instrumentation Levels. Changing its value has no effect if the Instrumentation Level is NoDetail. For more information about setting instrumentation levels, see Configuring instrumented simple method settings .
To set the maximum request fragment cache size:
* 
TIP: To review how to access the instrumentation settings editor, see Editing agent instrumentation configurations .
1
Click the Requests tab of the Edit dialog box.
2
Type a value in the MaxRequestFragmentCacheSize box.
3
Click Save.
4
Restart your application server.
Manual configuration — MaxRequestFragmentCacheSize
If you manually edit the instrumentation.config file, use the following syntax to specify the maximum request fragment cache size.
MaxRequestFragmentCacheSize = 50;

Setting the Request Recursion Limit

The RecursionLimit configuration setting adjusts the number of recursive calls for which the Java EE agent collects detailed performance information. Beyond this number, the Java EE agent collects and aggregates timing information for the entire recursive sequence.
If you need to see more detail for each method call in a recursive sequence, you can increase this value. Set the value to zero (0) to see only the first method call, but none of the recursive calls. The default value is 5.
* 
NOTE: This setting is only valid for FullDetail, ComponentDetail and BasicDetail Instrumentation Levels. Changing its value has no effect if the Instrumentation Level is NoDetail. For more information about setting instrumentation levels, see Configuring instrumented simple method settings .
To set the request recursion limit:
* 
TIP: To review how to access the instrumentation settings editor, see Editing agent instrumentation configurations .
1
Click the Requests tab of the Edit dialog box.
2
Type a value in the RecursionLimit box.
3
Click Save.
4
Restart your application server.
Manual configuration — RecursionLimit
If you manually edit the instrumentation.config file, use the following syntax to specify the recursion limit.
RecursionLimit = 5;

Setting the Request Remote Invocation Limit

The RemoteInvocationLimit determines the maximum number of calls that the Java EE agent follows from a single method to a remote system. Beyond this number, the Java EE agent only collects and aggregates overall performance information for the remote system invocations. This is done for two reasons:
•
A large number calls to remote systems from a single method is highly likely to produce a performance problem.
•
It is expensive for the Nexus to process Tag and Follow™ information for a large number of remote invocations on a single request.
The default value is 10. If this limit is exceeded, the Java EE agent logs a WARN message that identifies the method where the remote invocations are taking place.
If you are receiving WARN log messages and you require more detail on the remote invocations, you can increase this setting.
* 
IMPORTANT: Increasing this value also increases the amount of CPU and memory that the Nexus uses.
Decrease this value if you are receiving the WARN log messages, but the Nexus is exhibiting symptoms of excessive memory use.
* 
NOTE: This setting is only valid for FullDetail, ComponentDetail and BasicDetail Instrumentation Levels. Changing its value has no effect if the Instrumentation Level is NoDetail. For more information about setting instrumentation levels, see Configuring instrumented simple method settings .
To set the request remote invocation limit:
* 
TIP: To review how to access the instrumentation settings editor, see Editing agent instrumentation configurations .
1
Click the Requests tab of the Edit dialog box.
2
Type a value in the RemoteInvocationLimit box.
3
Click Save.
4
Restart your application server.
Manual configuration — RemoteInvocationLimit
If you manually edit the instrumentation.config file, use the following syntax to specify the remote invocation limit.
RemoteInvocationLimit = 50;

Allowing non-component root nodes

By default, the Java EE agent collects requests that start at a defined component technology (such as HTTP, JMS, RMI, EJB, or Servlet) or a custom component. Enable the AllowNonComponentRootNodes setting to allow the Java EE agent to collect information on requests that start at any method. This may be useful when using the X-Agent or the StopCurrentRequestInMethods configuration setting. For more information, see Separating requests by parent method.
By default, this setting is disabled.
* 
NOTE: This setting is only valid for the FullDetail instrumentation level. Changing the value has no effect if the instrumentation level is set to ComponentDetail, BasicDetail, or NoDetail. For more information about setting instrumentation levels, see Configuring instrumented simple method settings .
To enable non-component root nodes:
* 
TIP: To review how to access the instrumentation settings editor, see Editing agent instrumentation configurations .
1
Click the Requests tab of the Edit dialog box.
2
Select the check box for AllowNonComponentRootNodes.
3
Click Save.
4
Restart your application server.
Manual configuration — AllowNonComponentRootNodes
If you manually edit the instrumentation.config file, use the following syntax to enable non-component root nodes.
AllowNonComponentRootNodes = true;
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione