Hi, K.P.

Sure, we assumed that was the cause and change it some time ago (in March, if my memory serves me). Currently we use the next configuration in our jenkins.xml config file:

<executable>%BASE%\jre\bin\java</executable>
  <arguments>-Xrs -XX:PermSize=100m -Xmx768m -Dhudson.slaves.WorkspaceList="_" -Djava.rmi.server.hostname=10.0.100.90 -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=6666 -Dcom.sun.management.jmxremote.local._only_=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -jar "%BASE%\jenkins.war" --httpPort=80 -Xloggc:D:\Jenkins\loggcjenkins.txt</arguments>

For four weeks we also add parameters for monitoring Jenkins with jconsole. Assuming that these parameters are correct, we have never seen that used memory exceeds 200 MB of occupation. And PermGem has never exceeded 66 MB of occupation.

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/d/optout.

Reply via email to