Description
The following log message [1] occurred a million/billion times in the log files. As a result the log files exploded to 36Gb. After restarting the affected cms node everything works as expected.
Comment from Unico on this:
Looks like a bug in JcrValueList#size. When the session is closed during its evaluation it should probably throw a runtime exception or something. Otherwise, when you are iterating through it, you have an infinite loop on your hand. Can you create an issue?
[1] The log message
Sep 24 15:56:47 cms1 2015-09-24 15:56:47,361 ERROR [http-bio-8080-exec-12847] org.hippoecm.frontend.model.map.JcrValueList - This session has been closed. See the chained exception for a trace of where the session was closed.
Sep 24 15:56:47 cms1 2015-09-24 15:56:47,361 ERROR [http-bio-8080-exec-12847] org.hippoecm.frontend.model.map.JcrValueList - This session has been closed. See the chained exception for a trace of where the session was closed.
Sep 24 15:56:47 cms1 2015-09-24 15:56:47,376 ERROR [http-bio-8080-exec-12847] org.hippoecm.frontend.model.map.JcrValueList - This session has been closed. See the chained exception for a trace of where the session was closed.
Sep 24 15:56:47 cms1 2015-09-24 15:56:47,376 ERROR [http-bio-8080-exec-12847] org.hippoecm.frontend.model.map.JcrValueList - This session has been closed. See the chained exception for a trace of where the session was closed.
... this goes on and on