Out of Memory Error (AsyncAppender)

235 views
Skip to first unread message

David Harrigan

unread,
Apr 3, 2014, 3:45:52 AM4/3/14
to reactor-...@googlegroups.com
Hi,

Java 1.8 b132
Reactor 1.1.0-BUILD-SNAPSHOT

This morning, I've started to hit this issue:

Failed to instantiate [ch.qos.logback.classic.LoggerContext]
Reported exception:
java.lang.OutOfMemoryError: GC overhead limit exceeded
at reactor.logback.AsyncAppender$3.get(AsyncAppender.java:98)
at reactor.logback.AsyncAppender$3.get(AsyncAppender.java:95)
at reactor.core.processor.Processor$1.newInstance(Processor.java:90)
at reactor.core.processor.Processor$1.newInstance(Processor.java:86)
at com.lmax.disruptor.RingBuffer.fill(RingBuffer.java:1180)
at com.lmax.disruptor.RingBuffer.<init>(RingBuffer.java:60)
at com.lmax.disruptor.RingBuffer.createMultiProducer(RingBuffer.java:78)
at com.lmax.disruptor.RingBuffer.create(RingBuffer.java:144)
at com.lmax.disruptor.dsl.Disruptor.<init>(Disruptor.java:87)
at reactor.core.processor.Processor.<init>(Processor.java:85)
at reactor.core.processor.spec.ProcessorSpec.get(ProcessorSpec.java:165)
at reactor.logback.AsyncAppender.start(AsyncAppender.java:115)
at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:317)
at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:196)
at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:182)
at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62)
at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:149)
at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:135)
at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:99)
at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:49)
at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75)
at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
at org.slf4j.LoggerFactory.bind(LoggerFactory.java:129)
at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:108)
at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:302)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:276)
at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:156)
at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:132)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:274)

Nothing has changed apart from a new update from the BUILD-SNAPSHOT.

-=david=-

David Harrigan

unread,
Apr 3, 2014, 5:13:50 AM4/3/14
to reactor-...@googlegroups.com
Hi,

It was my issue, as part of some testing I reduced the -Xmx to 200MB and forgot that I had done this! :-)

My -Xmx is now 4096 and all is well :-)

-=david=-
Reply all
Reply to author
Forward
0 new messages