|
||||||||
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-14989) NPE in WarningsResu... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-14989) NPE in Warning... rdesgrop...@java.net (JIRA)
- [JIRA] (JENKINS-14989) NPE in Warning... rdesgrop...@java.net (JIRA)
- [JIRA] (JENKINS-14989) NPE in Warning... rdesgrop...@java.net (JIRA)
- [JIRA] (JENKINS-14989) NPE in Warning... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-14989) NPE in Warning... rdesgrop...@java.net (JIRA)
- [JIRA] (JENKINS-14989) NPE in Warning... rdesgrop...@java.net (JIRA)
- [JIRA] (JENKINS-14989) NPE in Warning... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14989) NPE in Warning... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14989) NPE in Warning... scm_issue_l...@java.net (JIRA)
Hallo Ulli,
The server in question has plenty of RAM and the issue may happen right after Jenkins startup, so I guess there's nothing to do with memory management.
BTW, we had to revert to warnings 4.13, as warnings 4.14 have the same problem as 4.15: