Issue Type: Bug Bug
Assignee: Unassigned
Attachments: IBM-SupportAssitant-leak-analyse-ApplicationShutdownHooks.PNG, IBM-SupportAssitant-leak-analyse-duplicated-classes.PNG, IBM-SupportAssitant-leak-analyse-histogram.PNG, IBM-SupportAssitant-leak-analyse-Introspector.PNG, IBM-SupportAssitant-leak-analyse-top-consumers-classes.PNG, IBM-SupportAssitant-leak-analyse-top-consumers.PNG, IBM-SupportAssitant-leak-analyse-WinstoneSession.PNG, IBM-SupportAssitant-leak-analyse.PNG, loaded-classes.PNG
Components: core
Created: 11/Oct/12 4:27 PM
Description:

Jenkins is out of memory after 1 day of use.
I've analysed heapdump with IBM Support Assistant. The results are attached.

Is it normal that these objects take so much space in the heap (see IBM-SupportAssitant-leak-analyse.PNG) ?

Furthermore, I noticed that the number of loaded classes is continuously increasing (see loaded-classes.PNG). Is this normal? or is it related to the monitoring plugin which can not properly handle information of IBM JVM?
It seems that this is related to it because the application crashes when the monitoring graph displays 50k loaded classes.

How can I find the source of the problem?

Thanks in advance,
Michaël Pailloncy

Environment: Jenkins 1.478 - Aix 5.3 - IBM Java 6
Project: Jenkins
Priority: Major Major
Reporter: Pailloncy Michaël
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

Reply via email to