Foglight for Java EE Technologies 5.9.11

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:

On the Object Tracking tab, click Edit

beside IgnoredAllocations.

In the Settings Editor, click Add.

In the new row that appears, type the name in the Class Name box.

If you want to specify the name as a regular expression, select the Regex check box.

After you have added all the classes necessary, click OK.

Click Save.

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

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 .

Click the Requests tab of the Edit dialog box.

Type a value in the MaxRequestFragmentCacheSize box.

Click Save.

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: