|
From: Leif M. <le...@ta...> - 2003-01-29 07:13:35
|
Ashish Gawarikar wrote: > Its not very easy to reproduce. I ran tomcat with 100 users for 100 > iterations to do all the application > stuff, and sometimes in a blue moon this happens. > Our QA team is having a problem in reproducing this. Try setting the max memory to 32 or 48MB rather than the default 64MB. Should make it happen more easily. Another idea is to create a class EatMemory.doIt() that simply creates a LinkedList and goes into an infinite loop of creating double arrays of length 100000 and adding them to the list. You should get an OutOfMemoryError pretty quickly. Question is whether or not it happens in the right place to cause Tomcat to stop responding. > This does sound like a very very good option. If something like this > is present, it will > help us a lot :) Ok, I posted a feature request to track this feature: http://sourceforge.net/tracker/index.php?func=detail&aid=676599&group_id=39428&atid=425190 Read it over and post any comments if you would like to see things done any differently. Cheers, Leif |