Re: OutOfMemoryError - 100 thread limit?

[LeeAnn Pultz]

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 their site.  The first user would then start getting exceptions once the 
OutOfMemory error happened.

When we reproduce the error, it doesn't seem to make a difference whether 
we simply click through a list of links, opening each site in a new window 
quickly, or whether we pause a few seconds in between opening new sites.

So it doesn't necessarily *seem* to be dependent on multiple people firing 
up their sites at the same time, or over the course of several hours as 
different people use the system.

We've identified that each instance of our application starts up with 3 
active threads - we have a monitoring thread, the application thread and 
the user's current thread. When I start up tomcat, and hit the first site, 
I see about 44 active threads to start with - this seems to be affected by 
whether we have the Http10 connector commented out, whether the management 
port is set up etc.  If I run the application through Jbuilder + tomcat, 
the active count doesn't count the "tomcat' threads, and I start with 3 
threads and increase by 3 threads for each new application I open in my 
browser, the first time.


At 10:38 AM 4/20/2005, you wrote:
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 for your tests?
in other words, are you throwing 100 concurrent requests at it
simultaneously, or ramping it up over a few seconds?
peter
On 4/20/05, LeeAnn Pultz <[EMAIL PROTECTED]> wrote:
> 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
> org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:691)
>          at
> 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:144)
>          at
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>          at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>          at
> 
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
>          at
> 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
>          at
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>          at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>          at
> 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
>          at
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>          at
> 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
>          at
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
>          at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>          at
> 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>          at
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>          at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>          at
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
>          at
> org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
>          at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
>          at
> 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
>          at
> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
>          at
> 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
>          at java.lang.Thread.run(Thread.java:536)
> ----- Root Cause -----
> java.lang.OutOfMemoryError
>
> LeeAnn Pultz
> ExtraView Corporation
> [EMAIL PROTECTED]
> 831-461-7100 x115
>
> ---------------------------------------------------------------------
> 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]
LeeAnn Pultz
ExtraView Corporation
[EMAIL PROTECTED]
831-461-7100 x115 


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