System information

Using the Profiler to Troubleshoot Performance Problems

Page 156 Identity Manager 7.1 Update 1 • Release Notes

Java filters are given in terms of method patterns, and they are expressed in patterns that include or

exclude based on canonical method name. Where a canonical method name is:

fully-qualified-class-name.method-name

(

parameter-type-1, parameter-type-2, ...

)

Here are a few examples:

• To exclude all constructors, enable the Exclude box and add the following filter:

*.<init>(*)

• To exclude all constructors with a single

org.w3c.dom.Element

parameter, enable the

Exclude box and add the following filter:

*.<init>(org.w3c.dom.Element)

• To exclude all Identity Manager classes, enable the Exclude box and add the following

filters:

"com.waveset.*"

"com.sun.idm.*"

• To instrument your custom code only, disable the Exclude box, remove the initial

include

filter, and then add the following filter:

"com.yourcompany.*"

If necessary, you can instrument other JARs by modifying the following lines in

build.xml

appropriate. For example,

NOTE For constructors, method-name is

<init>

NOTE The last two examples are currently equivalent because the filters are

applied only to your custom classes and Identity Manager classes.

<instrument todir="${lighthouse-dir-profiler}/WEB-INF"

verbose="${instrumentor.verbose}" includeMethods="${profiler.includes}"

excludeMethods="${profiler.excludes}">

</fileset>

</instrument>