Supposing it's not some kind of memory leak in your application, you could try increasing the JVM's heap size passing the parameter -Xmx 256m
(256 or the size you like) to it.
By default, the JVM limits the heap size to 64M, so if your application needs more than 64M you will get an OutOfMemoryError. In this case, you must supply the JVM with a -Xmx argument.


Vitor


D'Alessandro, Arthur wrote:


We've been getting these every now and then:

Jan 23, 2004 5:03:30 PM org.apache.tomcat.util.net.TcpWorkerThread runIt
SEVERE: Exception in acceptSocket
java.lang.OutOfMemoryError
Jan 23, 2004 5:03:30 PM
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run
SEVERE: Caught exception executing
[EMAIL PROTECTED], terminating thread
java.lang.IllegalStateException: Terminating thread
       at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:53
2)
       at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:619)
       at java.lang.Thread.run(Thread.java:536)



Once this occurrs, I have to stop / start the entire Tomcat container in
order to allow this particular webapp to function again.  It only
effects a particular servlet mapping for a  given webapp.  Does anyone
have any suggestions on how to resolve?  We're running version 4.1.24..
Any leads would be great, thanks.

-Art

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to