[logback-user] Memory consumption problem with LRUMessageCache class
francois.petitit at gmail.com
Tue Apr 12 18:05:41 CEST 2011
thanks a lot for your quick answer.
I just created http://jira.qos.ch/browse/LBCLASSIC-262 , please ask me for
Because we use a very old version of IBM JVM, I looked at the IBM JVM fixes,
searching something about LinkedHashMap, but didn't find anything.
Do you have already planned a new release of Logback (0.9.29), including the
patch for LBCLASSIC-255?
2011/4/12 Ceki Gulcu <ceki at qos.ch>
> On 12.04.2011 11:45, François Petitit wrote:
>> we have problems of excessive memory consumption, due to the object
>> LRUMessageCache that grows constantly, until it exceeds 100MB.
>> Then we restart the JVM to avoid crashes.
>> Could the anomaly http://jira.qos.ch/browse/LBCLASSIC-255regarding the
>> fact that the class LRUMessageCache is not multithread-safe explain the
>> Thank you in advance.
> Hello Francois,
> What you describe sounds like a serious bug. Could you please enter a bug
> report so that the bug is not fotgotten?
> Interestingly enough, LRUMessageCache is based for the most part on the
> JDK's LinkedHashMap. If the bug is located in LRUMessageCache in the code
> extending LinkedHashMap then we will fix LRUMessageCache. If however, the
> bug is in LinkedHashMap, which is a distinct possibility, then we can revert
> to the original LRUMessageCache which implemented the functionality from the
> ground up, without relying on LinkedHashMap.
> In any case, please enter a bug report indicating your version of logback
> and JDK.
> QOS.ch, main sponsor of cal10n, logback and slf4j open source projects, is
> looking to hire talented software engineers. For further details, see
> Logback-user mailing list
> Logback-user at qos.ch
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Logback-user