Hi Chuck, sorry for late answer. The Tomcat Level is 5.5.15.
>How many ThreadWithAttributes objects are you seeing? In one of the HeapDumps i see 25 ThreadWithAttributes Objects. ( http://img518.imageshack.us/img518/4395/incomingreferences.png ~110kb ) Only 1 Object becomes that large. If i analyse the Object by outgoing Refrerences, i see that this Object hast round 515mb of kind "Object" stored. ( http://img10.imageshack.us/img10/4555/outgoingrefrences.png ~100kb) Dont know where these 515MB "Object" Objects are coming from...the reason why iam writing here is, to know why they are there. I dont guess, that this are Object which are not collected my GC, because of a still remaining reference. If it would be something like this, it would be possible to calculate, when memory runs out: The Testfile is round 3MB, doing some operations on it, the memory amount growth to X MB. MaxMemory / X MB = Rounds of Testing till out of Memory. But sometimes it crashes after 20 Testcases(5-6 Hours), then it works for days(without allocating virtual Memory), doing the same Test over and over again. This is why iam interested, in how ThreadWithAttributes is created and handled. Maybe iam totally wrong, searching for the Error on ThreadWithAttribute but dont know where to search.. And nealy all the time all the MemoryAnalyser`s say, that ThreadWithAttribute is the Reason for OOM. And doing a long-term Profining i can not say something like "after every testcase there is a 2% memory increasment". Can not see something like that. But when it runs out of Memory, it doesnt take more then 2-5 mins..then you see the memory increasment in the curve chart(jconsole). Patrick -----Original Message----- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Tuesday, March 10, 2009 8:55 PM To: Tomcat Users List Subject: RE: MemoryLeak Problem with ThreadWithAttributes > From: Hennig, Patrick [mailto:phen...@l1id.com] > Subject: RE: MemoryLeak Problem with ThreadWithAttributes > > (Dont`t know exactly, what you mean by "Tomcat Level") 5.5.?? Fill in the question marks. > <Connector port="8009" enableLookups="false" > redirectPort="8443" protocol="AJP/1.3"></Connector> <Connector > port="8081" maxHttpHeaderSize="8192" > maxThreads="150" minSpareThreads="25" maxSpareThreads="75" > enableLookups="false" redirectPort="8443" acceptCount="100" > connectionTimeout="20000" disableUploadTimeout="true"></Connector> If I understand the code correctly, this will limit the number of threads Tomcat uses to 350 (the default 200 for AJP plus 150 for HTTP). Consequently, you should see no more than that number of ThreadWithAttributes objects. > Iam focused on ThreadWithAttributes, because i see it everytime i > review a ErrorHeapDump. How many ThreadWithAttributes objects are you seeing? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
