|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
I just saw a unit test fail randomly with the following exception:
{code}
java.lang.NullPointerException: null
at java.util.LinkedHashMap$Entry.remove(LinkedHashMap.java:328) ~[na:1.7.0_05]
at java.util.LinkedHashMap$Entry.recordRemoval(LinkedHashMap.java:358) ~[na:1.7.0_05]
at java.util.HashMap.removeEntryForKey(HashMap.java:577) ~[na:1.7.0_05]
at java.util.LinkedHashMap.addEntry(LinkedHashMap.java:428) ~[na:1.7.0_05]
at java.util.HashMap.put(HashMap.java:402) ~[na:1.7.0_05]
at ch.qos.logback.classic.turbo.LRUMessageCache.getMessageCountAndThenIncrement(LRUMessageCache.java:47) ~[logback-classic-0.9.28.jar:na]
at ch.qos.logback.classic.turbo.DuplicateMessageFilter.decide(DuplicateMessageFilter.java:62) ~[logback-classic-0.9.28.jar:na]
at ch.qos.logback.classic.spi.TurboFilterList.getTurboFilterChainDecision(TurboFilterList.java:51) ~[logback-classic-0.9.28.jar:na]
at ch.qos.logback.classic.LoggerContext.getTurboFilterChainDecision_1(LoggerContext.java:269) ~[logback-classic-0.9.28.jar:na]
at ch.qos.logback.classic.Logger.filterAndLog_1(Logger.java:434) ~[logback-classic-0.9.28.jar:na]
at ch.qos.logback.classic.Logger.trace(Logger.java:481) ~[logback-classic-0.9.28.jar:na]
[...]
{code}
Since the test passed when I relaunched it, I think I encountered the synchronization problem mentioned in this bug. So, thanks for fixing it :)
I'm posting the exception here in case other people encounter the same bug and try to google the exception.