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 (slightly more complex) application servlet, and did the same thing. Now the reported number of threads is much higher, but I still get an OutOfMemory error at the same number of new instances fired up (between 17-18 sites started up).
Active Threads : WHEN STARTING INIT() 617 [GC 57193K->46096K(129792K), 0.0353880 secs] [GC 57936K->47554K(129792K), 0.0238210 secs] [Full GC 49312K->47441K(129792K), 0.6546550 secs] [Full GC 47732K->47129K(129792K), 0.7706500 secs] [Full GC 48310K->47256K(129792K), 0.6425030 secs] [Full GC 47276K->47263K(129792K), 0.6445770 secs] [Full GC 47263K->47263K(129792K), 0.6368020 secs] [Full GC 47263K->47241K(129792K), 0.7775600 secs] java.lang.OutOfMemoryError [Full GC 47295K->47242K(129792K), 0.6301470 secs] [Full GC 47248K->47245K(129792K), 0.6451800 secs] [Full GC 47257K->47250K(129792K), 0.6454320 secs] [Full GC 47271K->47262K(129792K), 0.7056980 secs] java.lang.OutOfMemoryError java.lang.OutOfMemoryError
So it looks like it isn't just a thread issue.
If I fire up the simple servlet 18 times, I don't get the error. In fact, I can then go on to fire up our main servlet another 17-18 times before we get the OutOfMemory error - this time at 844 threads before it dies.
There must be something else going on within our application that is consuming something that the simple servlet doesn't.
If anyone has any suggestions on other things that I could check for ? Someone said OOM errors can mean out of file descriptors as well?
thanks for all your help so far - I'm really hoping we can figure this out!
At 11:20 AM 4/20/2005, you wrote:
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 creating threads at start, what are they doing?
peter lin
> Threads Active : 94 > Threads Active : 94 > [Full GC 48357K->47096K(129792K), 0.6358540 secs] > > > 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]
