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

Object Tracking settings

The Object Tracking instrumentation settings for a Java EE agent determine how the agent tracks objects that are not reclaimed by the garbage collector. Changing any of these settings can have performance implications. Review the provided information before changing any settings.
•
Tracking object classes
•
Ignoring specific objects

Tracking object classes

Use the ObjectTrackerClasses setting to watch for objects that are never reclaimed by the garbage collector. You can specify groups of classes with allocated object instances that are tracked during a sampled request.
Object tracking impacts performance overhead if the number of tracked instances is too high. The simplest way to reduce imposed overhead is to track a smaller number of classes. Recording should be delayed until the application has reached a steady state (that is, after start-up work is complete and permanent objects have been created). Use the IgnoredAllocations setting to indicate which objects should not be tracked, even if those allocations are performed by classes in this tracked class list. For more information, see Ignoring specific objects.
* 
NOTE: The ObjectTrackerClasses settings only take effect when object tracking is enabled. Object Tracking can be enabled and disabled on a per request basis, by setting the Enable Object Tracking option found in the Application Servers Monitor > Server JVM view. For more information, see the Foglight for Application Servers User Guide. The pre-instrumentor script must be run on all agent machines after changing either the ObjectTrackerClasses or IgnoredAllocations properties.
For example, the following procedure shows how to configure this object tracking:
•
Track all classes in the com.globex.plan package.
•
Do not track any other classes with globex in the name.
•
Track the com.acme.Widget class.
•
Track the listed collection classes.
To specify object classes for tracking:
* 
TIP: To review how to access the instrumentation settings editor, see Editing agent instrumentation configurations .
1
Click the Object Tracking tab of the Edit dialog box.
2
To add tracked object classes, click Edit beside ObjectTrackerClasses.
3
In the Settings Editor, you can add, remove, or change the order of tracked object classes.
Click Add multiple to define several classes at once.
4
In the dialog box that opens, type the names of the classes, separated by commas or new lines.
5
Click Add.
The new object classes appear at the bottom of the list.
6
Click OK.
7
In the Edit dialog box, click Save.
8
Restart your application servers.
You may also want to ignore specific objects. For more information, see Ignoring specific objects.
Manual configuration — ObjectTrackerClasses
If you manually edit the instrumentation.config file, use the following syntax to specify the object tracking instrumentation.
ObjectTrackerClasses = ClassList(
include "com.globex.plan.",
exclude /(\.|^)globex\./
include "com.acme.Widget",
include "java.util.Stack",
include "java.util.Vector",
);
This example tracks all classes in the com.globex.plan package, but it does not track any other classes with globex in the name. It also tracks the com.acme.Widget class, as well as the listed collection classes.

Ignoring specific objects

Even with object tracking enabled, some object allocations may be considered uninteresting. For example, the StringBuffer class is allocated as a temporary object by boilerplate code and is automatically generated by Java compilers. As a result of string manipulation, these objects are generated but should not cause memory issues. Use the IgnoredAllocations property to indicate objects that should not be tracked, even if those allocations are performed by classes in the tracked class list. For more information about tracking object classes, see Tracking object classes .
By default, java.lang.StringBuffer and java.lang.StringBuilder are ignored.
To ignore specific objects:
1
On the Object Tracking tab, click Edit beside IgnoredAllocations.
2
In the Settings Editor, click Add.
3
In the new row that appears, type the name in the Class Name box.
4
If you want to specify the name as a regular expression, select the Regex check box.
5
After you have added all the classes necessary, click OK.
6
Click Save.
7
Restart your application servers.
Manual configuration — IgnoredAllocations
If you manually edit the instrumentation.config file, use the following syntax to specify the ignored allocations.
IgnoredAllocations = ClassList();

Requests settings

The Requests instrumentation settings for a Java EE agent determine how the agent splits requests based on methods. Changing any of these settings can have performance implications. Review the provided information before changing any settings.
•
Setting the Maximum Request Fragment cache size
•
Setting the Request Recursion Limit
•
Setting the Request Remote Invocation Limit
•
Allowing non-component root nodes
•
Separating requests by parent method
•
Splitting requests during single tracing
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione