|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
For information, and since you are already using the monitoring plugin, you may be able to view the number of instances per class, without taking a heap dump, but with the "Heap histogram" link in the monitoring reports. See an example in the javamelody demo (click on "Details" on the right to see more classes):
http://demo.javamelody.cloudbees.net/monitoring?part=heaphisto
or http://demo.javamelody.cloudbees.net/monitoring?part=heaphisto&format=json
You can also kill a session with a simple button in the monitoring plugin. Example in the demo (sessions may be empty in the demo at the moment):
http://demo.javamelody.cloudbees.net/monitoring?part=sessions
Note that I am not sure if the mega-size of the leaking session may cause a problem to display this sessions page in your server.