Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error log: The buffer cannot hold more than 500 objects. #2302

Closed
lennartkoopmann opened this issue May 28, 2016 · 1 comment
Closed

Error log: The buffer cannot hold more than 500 objects. #2302

lennartkoopmann opened this issue May 28, 2016 · 1 comment
Assignees
Milestone

Comments

@lennartkoopmann
Copy link
Member

@lennartkoopmann lennartkoopmann commented May 28, 2016

This error appears in my graylog-server (on current 2.0 branch state) log:

2016-05-28 15:28:35,699 Service Thread ERROR An exception occurred processing Appender graylog-internal-logs org.apache.commons.collections.BufferOverflowException: The buffer cannot hold more than 500 objects.
    at org.apache.commons.collections.buffer.BoundedFifoBuffer.add(BoundedFifoBuffer.java:237)
    at org.apache.commons.collections.buffer.CircularFifoBuffer.add(CircularFifoBuffer.java:93)
    at org.graylog2.log4j.MemoryAppender.append(MemoryAppender.java:76)
    at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:152)
    at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:125)
    at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:116)
    at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84)
    at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:390)
    at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:378)
    at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:362)
    at org.apache.logging.log4j.core.config.LoggerConfig.logParent(LoggerConfig.java:384)
    at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:379)
    at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:362)
    at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:352)
    at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:63)
    at org.apache.logging.log4j.core.Logger.logMessage(Logger.java:147)
    at org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:1022)
    at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:980)
    at org.apache.logging.slf4j.Log4jLogger.warn(Log4jLogger.java:253)
    at org.graylog2.periodical.GarbageCollectionWarningThread$1.handleNotification(GarbageCollectionWarningThread.java:130)
    at sun.management.NotificationEmitterSupport.sendNotification(NotificationEmitterSupport.java:156)
    at sun.management.GarbageCollectorImpl.createGCNotification(GarbageCollectorImpl.java:147)

It might be that an upgrade of the apache-commons library caused this exception to be thrown. This did not happen in <2.0 versions.

@lennartkoopmann lennartkoopmann added this to the 2.0.3 milestone May 28, 2016
joschi pushed a commit that referenced this issue May 30, 2016
Jochen Schalanda
Fixes #2302
@joschi joschi self-assigned this May 30, 2016
@kroepke kroepke closed this in #2307 Jun 3, 2016
kroepke added a commit that referenced this issue Jun 3, 2016
* Make MemoryAppender thread-safe
* improve thread safety test to make the original implementation fail much quicker and more reliably

Fixes #2302
kroepke added a commit that referenced this issue Jun 3, 2016
* Make MemoryAppender thread-safe
* improve thread safety test to make the original implementation fail much quicker and more reliably

Fixes #2302
(cherry picked from commit 9d411ef)
@kroepke
Copy link
Member

@kroepke kroepke commented Jun 3, 2016

This has been backported to 2.0.3 but not released yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants