![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
wolfs
|
|
Attachments:
|
jenkins_permgen_leak.jpg |
|
Components:
|
all-changes |
|
Created:
|
30/Jan/13 7:08 AM
|
|
Description:
|
I migrate from Hudson #1376 to Jenkins #1498.
I upgrade the plugins and clean the config files as proposed by the message views on "Manage Jenkins".
I monitor our JVM servers 24/7 and I see clearly the impact on the migration on the PermGen area. Same settings than Hudson, same plugins, same jobs and a huge difference in PermGen. (see the attached graph)
I upgrade Jenkins to #1500, the plugins, checked the configurations (and reboot Tomcat). No changes.
It's a critical problem since Hudson asked nearly nothing in maintenance.
|
|
Environment:
|
Windows Server 2003R2 SP2
Tomcat 6.0.16
Java 1.6.0_05-b13
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
christophe dontaine
|
|
|
|
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.
