Tomcat OutOfMemoryError Java heap space Arrays.copyOf

Question

We have an servlet that uploads files from customers and stores them on our server. Every few weeks the servlet fails with the following error:

java.lang.OutOfMemoryError: Java heap space
    at java.util.Arrays.copyOf(Arrays.java:2882)
    at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
    at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390)
    at java.lang.StringBuffer.append(StringBuffer.java:224)
    at java.util.logging.SimpleFormatter.format(SimpleFormatter.java:74)
    at org.apache.juli.FileHandler.publish(FileHandler.java:129)
    at java.util.logging.Logger.log(Logger.java:458)
    at java.util.logging.Logger.doLog(Logger.java:480)
    at java.util.logging.Logger.logp(Logger.java:680)
    at org.apache.juli.logging.DirectJDKLog.log(DirectJDKLog.java:167)
    at org.apache.juli.logging.DirectJDKLog.error(DirectJDKLog.java:135)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
    at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
    at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
    at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
    at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
    at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
    at java.lang.Thread.run(Thread.java:619)

Tomcat is running with -Xmx256M. I'm not sure how to debug this memory leak - could it be something to do with the java.util.logger filling up?

Aaron Digulla · Accepted Answer · 2010-07-26 09:29:30Z

1

There probably isn't a memory leak; my guess is that someone tries to write a huge log message. Check the log settings.

Also check how much memory Tomcat uses on the manager page and how much is free. Depending on your web app, 256MB might not be enough.

One last explanation could be a denial of service attack or an attempt to trigger a Java bug to hack your server.

answered Jul 26, 2010 at 9:29

Aaron Digulla

330k111 gold badges626 silver badges840 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Tarski Over a year ago

Looking at the apache logs I think it might have been a denial of service attack, not to do with tomcat.

Greg Hewgill · Accepted Answer · 2010-07-26 09:24:45Z

1

You've probably got something that holds on to some object references and never lets go. It's not that the logger is filling up memory, but the logger probably runs most frequently and is therefore the first thing to notice if you do fill up your heap.

answered Jul 26, 2010 at 9:24

Greg Hewgill

1.0m192 gold badges1.2k silver badges1.3k bronze badges

3 Comments

Joachim Sauer Over a year ago

This is a possibility, but it could also be an abnormally large value being logged.

Tarski Over a year ago

I have a static instance to an org.apache.Log4j.Logger. Could holiding an instance for the lifetime of the servlet cause an OutOfMemoryError?

Joachim Sauer Over a year ago

@Tarski: unlikely. The problem does not appear to be with memory occupied by the Logger permanently. It's crashing when building a log message, which uses memory that is released quickly.

Collectives™ on Stack Overflow

Tomcat OutOfMemoryError Java heap space Arrays.copyOf

2 Answers 2

1 Comment

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related