Java Filters

Select the Java Filters tab to

• Include or exclude Java filters

• Create new filters

• Delete existing filters

• Restore the default filters

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, ...)

For constructors, method-name is <init>.

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.*"

The last two examples are currently equivalent because the filters are applied only to your custom classes and Identity Manager classes.

If necessary, you can instrument other jars by modifying the following lines in build.xml as appropriate. For example,

<instrument todir="${lighthouse-dir-profiler}/WEB-INF" 
verbose="${instrumentor.verbose}" includeMethods="${profiler.includes}" 
excludeMethods="${profiler.excludes}">
           <fileset dir="${lighthouse-dir}/WEB-INF">
               <include name="lib/idm*.jar"/>
               <include name="classes/**/*.class"/>
           </fileset>
</instrument>

By default, the configuration includes all your custom classes and most Identity Manager classes. A number of Identity Manager classes are forcibly excluded— because enabling them would break the Profiler.

For example, classes from the workflow, forms, and XPRESS engines are excluded or the Profiler would produce an unintelligible snapshot when profiling Java and Identity Manager objects.

Note that Java filters provide much more filtering granularity than IDM Object Filters. Java instrumentation adds significant overhead to the execution time, which can drastically skew the profiling results. Because Identity Manager objects are interpreted rather than compiled, the instrumentation overhead is negligible. So for example, there is basically no reason to exclude workflow A and include workflow B, and so forth.

You cannot modify Java filters while the Profiler is running. You must stop the Profiler before changing Java filters.