|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I may have resolved this myself. Initially I set my memory limits to extremely high levels:
... -Xms8192m -Xmx8192m -XX:MaxPermSize=16384m ...
This allowed me to gain some stability.
Upon further examination, I found I had one plugin that was misconfigured, was throwing errors, and was probably not being used, the LDAP Email Plugin. I removed that, consolidated redundant environment variables on the JVM call, and ceased using the "-XX:NewSize=128m" parameter. Those were the only substantive changes.
I attempted to trigger a dump by calling the FindBugs Warnings chart, and found I could still obtain the report with memory requests much smaller. The following is now working for me, as I have gone five days without a crash for the first time in weeks.
<jenkins@build-machine-2:~> java -Xms1024m -Xmx1024m \
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/Users/jenkins/dumps \
-XX:MaxPermSize=1024m -jar jenkins.war --httpPort=8070 &
I would feel better knowing which of the changes above resolved the problem, though I am happy enough right now not to have to watch for Jenkins failures every 10 minutes.