IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Using dump agents > Advanced control of dump agents
filter option
Some JVM events occur thousands of times during the lifetime of an application. Dump agents can use filters and ranges to avoid excessive dumps being produced.
Wildcards
You can use a wildcard in your exception event filter by placing an asterisk only at the beginning or end of the filter. The following command does not work because the second asterisk is not at the end:
-Xdump:java:events=vmstop,filter=*InvalidArgumentException#*.myVirtualMethodIn order to make this filter work, it must be changed to:
-Xdump:java:events=vmstop,filter=*InvalidArgumentException#MyApplication.*
Class loading and exception events
You can filter class loading (load) and exception (throw, catch, uncaught, systhrow) events by Java™ class name:
-Xdump:java:events=throw,filter=java/lang/OutOfMem* -Xdump:java:events=throw,filter=*MemoryError -Xdump:java:events=throw,filter=*Memory*
You can filter throw, uncaught, and systhrow exception events by Java method name:
-Xdump:java:events=throw,filter=ExceptionClassName[#ThrowingClassName. throwingMethodName[#stackFrameOffset]]Optional portions are shown in brackets.
You can filter the catch exception events by Java method name:
-Xdump:java:events=catch,filter=ExceptionClassName[#CatchingClassName. catchingMethodName]Optional portions are shown in brackets.
vmstop event
You can filter the JVM shut down event by using one or more exit codes:
-Xdump:java:events=vmstop,filter=#129..192#-42#255
slow event
You can filter the slow event to change the time threshold from the default of 50 ms:
-Xdump:java:events=slow,filter=#300msYou cannot set the filter to a time that is less than the default time.
allocation event
You must filter the allocation event to specify the size of objects that cause a trigger. You can set the filter size from zero up to the maximum value of a 32 bit pointer on 32 bit platforms, or the maximum value of a 64 bit pointer on 64 bit platforms. Setting the lower filter value to zero triggers a dump on all allocations.
For example, to trigger dumps on allocations greater than 5 Mb in size, use:
-Xdump:stack:events=allocation,filter=#5mTo trigger dumps on allocations between 256Kb and 512Kb in size, use:-Xdump:stack:events=allocation,filter=#256k..512k
Other events
If you apply a filter to an event that does not support filtering, the filter is ignored.
Parent: Advanced control of dump agents
Error 404 - Not Found Error 404 - Not Found
The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.