You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Jack Park <ja...@thinkalong.com> on 2005/05/16 01:07:37 UTC
Tomcat 5.0.30 OutOfMemory error
I've done a lot of google surfing on this issue. It would seem this is a
known issue. Some people say to raise the heap. In the manager panel, I
did that: min=256mb, max=512mp and I gave it 512k stack size (not sure
if that's even close enough, in fact, I have no idea what that means).
I'm running stress tests on localhost:8080. I'm using the apache
HttpClient to rapidly access every known URL in the site I'm exercising:
390 distinct URLs. The database is inmemory (a Hashtable) and HTML is
painted by way of Velocity. It's a simple site: no large graphics, etc.
When HttpClient fails, I log that a URL was missed.
When I fire up 1, 2, 4, 8, or 16 threads, nothing unhappy is noted. When
I jump to 32 threads, each running simultaneously, I start to get missed
URLS. While it's running, I try to access a page from a browser and get
the 500 error and out of memory.
The java process is calling up 66,500k of heap so it strikes me that the
OutOfMemory issue isn't related to the heap.
If I try to place
set CATALINA_OPTS= "-Xms256m -Xmx512m -Xss512k"
in catalina.bat, Tomcat won't start at all.
I confess, I'm really confused. It strikes me that 32 threads banging
away on Tomcat 5 on a 2.5 ghz Athalon box just on localhost shouldn't be
all that much stress.
I'll greatly appreciate any concrete suggestions available.
Thanks
Jack
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org