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.
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.