: OutOfMemoryError - 100 thread limit?
the default Perm is 64M. If LeeAnn's webapp have a large number of
classes, maybe there's too many; therefore forcing the VM to resize
the perm.
IIRC (haven't looked at core HotSpot code in detail since 1.4.1 days),
the virtual address boundary between perm
should
also solve this problem.
--
Virtually,
Andre Van Klaveren
Architect III, SCP
Enterprise Transformation Services
Unisys Corporation
On 4/21/05, Caldarale, Charles R [EMAIL PROTECTED] wrote:
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 20, 2005 8:35 PM
To: Tomcat Users List
Subject: Re: OutOfMemoryError - 100 thread limit?
ok, I just tried starting tomcat with the default heap size and 18
instances of my webapp and it got OOME just as you see
From: J. Ryan Earl [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
So let me get this straight, LeeAnn is specifying a maximum
heap size of 512MB and a minimum size of 128MB. It looks
like the heap doesn't get adjusted up when the servlets are
initializing
] wrote:
From: J. Ryan Earl [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
So let me get this straight, LeeAnn is specifying a maximum
heap size of 512MB and a minimum size of 128MB. It looks
like the heap doesn't get adjusted up when the servlets
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 21, 2005 9:19 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: J. Ryan Earl [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
So let me get
Subject: RE: OutOfMemoryError - 100 thread limit?
From: J. Ryan Earl [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
So let me get this straight, LeeAnn is specifying a maximum
heap size of 512MB and a minimum size of 128MB. It looks
like the heap doesn't
From: J. Ryan Earl [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
Peter Lin reproduced and fixed the problem LeeAnn is seeing,
and said If I set my heap to -Xms256m -Xmx512m I'm able to
load the 18 webapps just fine. the total memory used after
all
to work.
peter
On 4/21/05, Caldarale, Charles R [EMAIL PROTECTED] wrote:
From: J. Ryan Earl [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
Peter Lin reproduced and fixed the problem LeeAnn is seeing,
and said If I set my heap to -Xms256m -Xmx512m I'm able
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
if it doesn't work, then back to square one :)
It would be even better to get some real data with the
-XX:+PrintGCDetails, so we can stop speculating...
- Chuck
THIS COMMUNICATION MAY CONTAIN
I, for one, am awaiting LeeAnn's response with abated breath. =)
-ryan
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 21, 2005 9:53 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: Peter Lin [mailto:[EMAIL
. =)
-ryan
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 21, 2005 9:53 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit
LeeAnn's response with abated breath. =)
-ryan
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 21, 2005 9:53 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re
. =)
-ryan
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 21, 2005 9:53 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100
silly question, does this webapp have like thousands of JSP and
servlets and preload the JSP's?
peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Not a silly question :)
We have 1 servlet that is the main entry point, everything else is done
with standard java classes. We have no jsp's.
At 09:13 AM 4/21/2005, you wrote:
silly question, does this webapp have like thousands of JSP and
servlets and preload the JSP's?
peter
Possible success!
I went back to my weblogic installation which I was successfully able to
open up 25 sites to see what it was doing when starting up.
It had -XX:MaxPermSize=128m in the process description.
I added that to my catalina_opts and I got past the 18 site limitation of
just firing
glad I was wrong and you found a solution.
http://java.sun.com/docs/hotspot/VMOptions.html
I'm just guessing here, but by forcing the maxPermSize to 128, it
leaves more space for the eden and prevents classes from getting
promoted to perm. Atleast that's logical explanation I can think of.
21, 2005 11:21 AM
To: Tomcat Users List
Subject: Re: OutOfMemoryError - 100 thread limit?
Not a silly question :)
We have 1 servlet that is the main entry point, everything else is done
with standard java classes. We have no jsp's.
At 09:13 AM 4/21/2005, you wrote:
silly question, does
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
It had -XX:MaxPermSize=128m in the process description.
Ahah, as they say.
Can anyone give me any information on what this does? Is
this the perm gen that Chuck mentioned before?
Yes
-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 21, 2005 11:52 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
It had -XX:MaxPermSize=128m
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
I'm just guessing here, but by forcing the maxPermSize to 128, it
leaves more space for the eden and prevents classes from getting
promoted to perm.
I think you're confusing tenured with perm
:52 AM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
It had -XX:MaxPermSize=128m in the process description.
Ahah, as they say.
Can anyone give me any
:
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
I'm just guessing here, but by forcing the maxPermSize to 128, it
leaves more space for the eden and prevents classes from getting
promoted to perm.
I think you're confusing tenured with perm
:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
I'm just guessing here, but by forcing the maxPermSize to 128, it
leaves more space for the eden and prevents classes from getting
promoted to perm.
I think you're confusing tenured with perm. Nothing is ever promoted
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
so it would appear by setting the PermSize, the jvm is pushing all
java.lang.Class instances to Perm rather than loading them in eden and
then promoting them to tenured.
Instances
On 4/21/05, Caldarale, Charles R [EMAIL PROTECTED] wrote:
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
so it would appear by setting the PermSize, the jvm is pushing all
java.lang.Class instances to Perm rather than loading them in eden
From: Peter Lin [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
the default Perm is 64M. If LeeAnn's webapp have a large number of
classes, maybe there's too many; therefore forcing the VM to resize
the perm.
IIRC (haven't looked at core HotSpot code in detail
There are no limits in tomcat.
http://jakarta.apache.org/tomcat/faq/memory.html
-Tim
LeeAnn Pultz wrote:
I have a tomcat server with multiple copies of our web application
running. We are running into what seems to be a hard-coded limit on the
number of threads available to the Tomcat
I'm able to go up to 647 threads and 500 concurrent connections with
5.5.4 without any problems. chances are, it's a memory leak in the
webapp. only way to know for sure is to profile the application.
peter lin
On 4/20/05, Tim Funk [EMAIL PROTECTED] wrote:
There are no limits in tomcat.
This is not a memory leak in the application - we have hooked up a profiler
to the application and watched the actual memory usage when causing this
issue to happen. We have lots of memory available, are nowhere near the
Xmx limit, and the machine has lots of memory available over and above
that sounds very odd. so if I understand correctly. this happens when
you hit the login page. I assume this don't happen with a static html
page? by any chance are you using jsp tags or some web framework?
peter
On 4/20/05, LeeAnn Pultz [EMAIL PROTECTED] wrote:
This is not a memory leak in
On 4/20/05, LeeAnn Pultz [EMAIL PROTECTED] wrote:
This is not a memory leak in the application - we have hooked up a profiler
to the application and watched the actual memory usage when causing this
issue to happen. We have lots of memory available, are nowhere near the
Xmx limit, and the
We have no jsps in the application. The index.html page loads our servlet
class, and I've put logging of active number of threads at the beginning of
the servlet ini() and the very end of the service() methods in that servlet
class. The application initializes, but we aren't doing any of the
No, unfortunately, changing those options doesn't seem to make any
difference either.
On tomcat 3, I even tried manipulating the thread pool settings (since in 4
and 5 those are handled inside tomcat).
But I'm seeing the same problems on 3, 4 and 5.0
In fact, I can cause the error to happen
that is some really odd behavior coming from Tomcat. I've probably run
over 1K benchmarks on Tomcat over the last 3 years and I've yet to see
that kind of behavior. Here are some random ideas to try, which I've
used in the past. They may not help, but I figure it wouldn't hurt to
suggest them.
We did run some code that just makes threads, on the machine and it had no
effect - I'll incorporate that code inside a servlet, so we can do this
test against tomcat and see if it makes a difference.
We just tried the same test against tomcat 5.0 using port 8080 and not
using any of the
Perhaps this will trigger some ideas? The stack trace we get when we get
the OutOfMemoryError is :
2005-04-20 09:55:33 StandardWrapperValve[ExtraView]: Allocate exception for
servlet ExtraView
javax.servlet.ServletException: Error allocating a servlet instance
at
that looks really bizzare to me. From the exception, it looks like
tomcat can't create a new thread to process the request. It makes me
think the previous threads that are done are being held by something
for some odd reason. Normally the threads should be available again.
What is the ramp up time
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
Perhaps this will trigger some ideas? The stack trace we get
when we get the OutOfMemoryError is :
- Root Cause -
java.lang.OutOfMemoryError
It's what comes after this spot
This was first reported when we had multiple web applications running on
one tomcat, and a user would be logged into the site and be using the
application fine, and then if another user started working in a new site,
they would get the OutOfMemory error when the first tried to load the page
of
At 10:43 AM 4/20/2005, you wrote:
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
Perhaps this will trigger some ideas? The stack trace we get
when we get the OutOfMemoryError is :
- Root Cause -
java.lang.OutOfMemoryError
It's what
Might want to turn on -verbose:gc just to see.
I turned on verbose:gc and ran the test again:
INFO: Server startup in 14608 ms
Start Init Method.
The CONFIG_FILE from web.xml is :
WEB-INF/configuration/Configuration.properties
Using Configuration FILE:
On 4/20/05, LeeAnn Pultz [EMAIL PROTECTED] wrote:
This was first reported when we had multiple web applications running on
one tomcat, and a user would be logged into the site and be using the
application fine, and then if another user started working in a new site,
they would get the
the number of threads seems odd. unless your webapp creates a bunch of
threads using ServletContextListener, the total thread count should be
between 10-15. I have a webapp which creates 10 threads on startup.
When tomcat is done and my webapp is loaded, I have a total of 38.
if your webapp is
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: RE: OutOfMemoryError - 100 thread limit?
I turned on verbose:gc and ran the test again:
[Full GC 48357K-47096K(129792K), 0.6358540 secs]
This shows you've given the JVM only 128 MB to work with; looks like you
really are out of heap
We tried a new test :)
We added code that spins up 8 threads inside just a plain servlet that
doesn't do anything else. When I fire up 10 different instances of that
servlet, I get hundreds of threads printing out as being active - and no
out of memory errors.
So we added the same code to our
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
[Full GC 47271K-47262K(129792K), 0.7056980 secs]
If anyone has any suggestions on other things that I could
check for ?
It still looks like your heap size is too small - 128MB isn't much
Thanks - I'll try that -
we do have CATALINA_OPTS set in catalina.sh of -Xms128m and -Xmx512m.
At 02:12 PM 4/20/2005, you wrote:
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
[Full GC 47271K-47262K(129792K), 0.7056980 secs]
If anyone has any
-
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 20, 2005 4:35 PM
To: Tomcat Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
Thanks - I'll try that -
we do have CATALINA_OPTS set in catalina.sh of -Xms128m and -Xmx512m.
At 02:12 PM 4/20/2005, you wrote:
From
Users List
Subject: RE: OutOfMemoryError - 100 thread limit?
Thanks - I'll try that -
we do have CATALINA_OPTS set in catalina.sh of -Xms128m and -Xmx512m.
At 02:12 PM 4/20/2005, you wrote:
From: LeeAnn Pultz [mailto:[EMAIL PROTECTED]
Subject: Re: OutOfMemoryError - 100 thread limit?
[Full GC
if your application is thread heavy, I would recommend changing it so
that one thread can manage several processes. creating 800+ threads is
going to hit a scalability and reliability wall very quickly. In
general, you want to make sure the number of threads remain constant
under constant load.
I think we've gotten things a bit confused :)
The application itself is not thread intensive - our original tests show
that each separate copy of the web application started up 3 active threads.
Further testing, when we added in debugging code that would spin up dozens
of threads just to see if
ahh ok. .. my confusion.
back to the problem you see. I've tested tomcat with 30-40 threads
without any problems in the past. Even with heavy weight JSTL tags in
JSP's, I'm able to go up to 50 threads with tomcat4.1.
I'll try hitting tomcat's status servlet with 50 threads tonight and
see what
when you say 50 threads, do you mean 50 separate web applications?
My concern right now is that we seem to be limited to 17-18 copies of our
web app on a particular installation of tomcat. And that
is just hitting the login page - not doing any work. Practically, for
applications with many
I'll try loading up 18 version of my webapp and see if tomcat blows
up. should know in a hour or so
peter
On 4/20/05, LeeAnn Pultz [EMAIL PROTECTED] wrote:
when you say 50 threads, do you mean 50 separate web applications?
My concern right now is that we seem to be limited to 17-18 copies
ok, I just tried starting tomcat with the default heap size and 18
instances of my webapp and it got OOME just as you see. If I set my
heap to -Xms256m -Xmx512m I'm able to load the 18 webapps just fine.
the total memory used after all the webapps are loaded is 152Megs.
the total number of
57 matches
Mail list logo
