Hi Isomorphic,
We are running into this exception in the com.isomorphic.log.RevolvingMemoryAppenderImpl.
v14.1p_2025-04-04
Regards,
Jeremey
Hi Isomorphic,
We are running into this exception in the com.isomorphic.log.RevolvingMemoryAppenderImpl.
v14.1p_2025-04-04
Regards,
Jeremey
There is indeed a theoretical concurrency issue here, which could cause a single log message to be lost. What’s strange is:
we have extensive stress tests to make sure we have no concurrency issues
no one has ever reported this before on our forums or other places (like StackOverflow)
We’ve gone ahead and fixed this for older versions with the narrowest possible synchronized check - available in tomorrow’s builds.
For the latest version (15.0) we’re doing a more elaborate rework to make sure there can’t even be a microsecond of thread wait even with massive logs
If you don’t mind, can you:
confirm that for you, this has been a very rare, intermittent error, or perhaps that it resulted from a monster stress test?
let us know if there’s anything special about your environment - experimental or unusual JVM, log interceptors or DataDog-like system, something like that?
confirm the error disappears after our fix - it would be great if you could follow up once you’ve had this deployed for a while, to let us know this issue is definitely gone
Thank you
If by chance we do find out more, we will let you know.
Hi Isomorphic,
We encountered another issue in com.isomorphic.log.RevolvingMemoryAppenderImpl.append.
‘v14.1p_2025-04-04’
Could you confirm whether the fix also covers this case?
Thank You
ERROR
org.apache.logging.log4j.core.appender.AppenderLoggingException: An exception occurred processing Appender SmartClientLog
Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 10003 out of bounds for length 10000
at org.apache.commons.collections4.queue.CircularFifoQueue.add(CircularFifoQueue.java:246)
at com.isomorphic.log.RevolvingMemoryAppenderImpl.append(RevolvingMemoryAppenderImpl.java:129)
at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:160)
Sorry for the delayed response. We were never able to reproduce the errors you originally reported, even through serious stress tests. However, the changes we made should avoid errors of this kind even if your usage was invalid.
So we believe with high confidence that both types of errors are now impossible, but we have not been able to reproduce either error, so we cannot say definitively.