On Tuesday 08 October 2013 14:11:01 Christoph Kutzinski wrote: > Caan you open a JIRA issue against the plugin?
while this could be fixed by changes in plugin (probably by fixing backward compatibility), the root cause seems to be Old data monitor which keeps all old data in memory, which can quite easily cause OOM. Even worse, it *may* happen that Old data monitor automatically turn on even if it was manually turned off before. I observed it on one of our Jenkins instance where OOM happened quite often because of Old data monitor, but haven't had enough time to investigate it yet. @Ohad - quick fix could be disable Old data monitor and turn it on once plugin is fixed. You can also check if it turn back on itself to confirm/disapprove my observation above
signature.asc
Description: This is a digitally signed message part.
