This plugin serves two primary purposes:
Copy threaddump.jar into the plugins directory of your Openfire installation. The plugin will then be automatically deployed. To upgrade to a new version, copy the new threaddump.jar file over the existing file.
Once loaded, the plugin will add a page to the Openfire Admin Console, under Server > Server Manager > Thread Dumps. This page can be used to configure the plugin.
Alternatively, the plugin can be configured by using properties, as defined below:
|threaddump.task.enable||Enables a task that periodically determines if a thread dump must be created.|
|threaddump.task.delay||The delay for starting the evaluation task that is observed after applying configuration changes or restarting the plugin.|
|threaddump.task.interval||The frequency at which to check what evaluators are ready to be executed.|
|threaddump.task.backoff||After a thread dump is generated, wait this period before allowing a new one to be generated.|
|threaddump.task.evaluators||A comma-separated list of class names of all evaluators to be used.|
The following evaluator classes are available:
An evaluator that periodically checks the activity in the thread pools that power most network-related activity.
|threaddump.evaluator.threadpools.interval||The frequency (in milliseconds) of core network thread pool evaluation.|
|threaddump.evaluator.threadpools.busy-percentage-max||The percentage of threads in a pool that can be running at the same time that is considered 'busy'.|
|threaddump.evaluator.threadpools.successive-hits||How many successive evaluations must have detected excessive thread pool usage, for a thread dump to be created.|
An evaluator that periodically checks if a thread deadlock has occurred.
|threaddump.evaluator.deadlock.interval||The frequence of deadlock detection evaluator.|
An evaluator that periodically checks the thread pool that is used by Openfire's internal Task Engine.
|threaddump.evaluator.taskengine.interval||The frequency (in milliseconds) of task engine thread pool evaluation.|
|threaddump.evaluator.taskengine.successive-hits||How many successive evaluations must have detected excessive thread pool usage, for a thread dump to be created.|
|threaddump.evaluator.taskengine.max-threads||The minimum amount of active threads in the pool to trigger a thread dump.|
|threaddump.evaluator.taskengine.max-poolsize||The minimum size of the thread pool (including active and inactive threads) to trigger a thread dump.|
Icons made by Vectors Market from www.flaticon.com is licensed by CC 3.0 BY