|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-14596) Upgrade to J... [email protected] (JIRA)
- [JIRA] (JENKINS-14596) Upgrade... [email protected] (JIRA)
- [JIRA] (JENKINS-14596) Upgrade... [email protected] (JIRA)
- [JIRA] (JENKINS-14596) Upgrade... [email protected] (JIRA)
- [JIRA] (JENKINS-14596) Upgrade... [email protected] (JIRA)
- [JIRA] (JENKINS-14596) Upgrade... [email protected] (JIRA)
- [JIRA] (JENKINS-14596) Upgrade... [email protected] (JIRA)
- [JIRA] (JENKINS-14596) Upgrade... [email protected] (JIRA)
- [JIRA] (JENKINS-14596) Upgrade... [email protected] (JIRA)
- [JIRA] (JENKINS-14596) Upgrade... [email protected] (JIRA)

I think it is some kind of problem caused by these new versions.
Anyway, the situation for us was resolved when we edited /etc/sysconfig/Jenkins:
JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true -XX:MaxPermSize=512M"