There is an excellent tool for post-mortem memory analyzation: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0eaafd5-6ffd-2910-019c-9007a92b392f. Just add -XX:+HeapDumpOnOutOfMemoryError to the startup parameters of your JVM. This will produce a memory dump when your JVM dies because of an OutOfMemoryError. With the memory analyzer you can see which objects consumed all the memory and find out the cause for the the garbage collector not collecting them. (See the corresponding documentation and the wiki to find out how to do this.)
Todd Orr wrote: > True enough. I'll get more details from our side. I was merely > pointing in that direction based on experience. > > On 8/9/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > >> Whatever this mysterious "issue" is that you seem to think exists it'd >> be impossible to fix whatever memory leaks you think you have found >> without knowing about them. >> >> There is a map that grows as large as the system using it internally >> to javassist of various cached reflection info - but it doesn't leak >> in any way. >> >> Anyways, vague comments with no specific versions or specific issues >> that you have faced don't really help anyone. >> >> On 8/9/07, Todd Orr <[EMAIL PROTECTED]> wrote: >> >>> We've run into this problem on a production system. It was a not a >>> good situation. One of our developers narrowed down the issue to >>> Hivemind. There is some Map that continually grows and grows (I can >>> speak to our dev to get more detail). After some research into similar >>> posts it became evident that this issue was brought up to HLS, but the >>> bug's existence was denied. We've since dropped Tapestry for mission >>> critical apps. I'm hoping this is no longer an issue in future >>> versions of Tapestry, but time will tell. >>> >>> On 8/9/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: >>> >>>> Tapestry 4.1.2 has no memory leaks. Each and every object created / >>>> managed is accounted for and known. I've done a lot of analysis in >>>> this area lately which is why I'm so sure. >>>> >>>> On 8/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >>>> >>>>> Within one day it rises slowly from 100 MByte to about 1 Gigabyte at >>>>> night when it crashes due to the limt that was set to the virtual >>>>> machine. It could be increased - but only with the effect of having an >>>>> additional day or so before it crashes again.....restarting Tomcat is >>>>> also not a viable solution. >>>>> >>>>> -------- Original-Nachricht -------- >>>>> Datum: Thu, 09 Aug 2007 17:01:19 +0200 >>>>> Von: [EMAIL PROTECTED] >>>>> An: "Tapestry users" <users@tapestry.apache.org> >>>>> Betreff: Re: Memory leaks in Tapestry 4.1 >>>>> >>>>> >>>>>> We have tried both enabling and disabling the cache. The same effect... >>>>>> it is only leaking a little bit slower in the other case. >>>>>> >>>>>> -------- Original-Nachricht -------- >>>>>> Datum: Thu, 9 Aug 2007 15:33:43 +0200 >>>>>> Von: Kristian Marinkovic <[EMAIL PROTECTED]> >>>>>> An: "Tapestry users" <users@tapestry.apache.org> >>>>>> Betreff: Re: Memory leaks in Tapestry 4.1 >>>>>> >>>>>> >>>>>>> do you have Tapestry caching deactivated? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> andyhot <[EMAIL PROTECTED]> >>>>>>> Gesendet von: Andreas Andreou <[EMAIL PROTECTED]> >>>>>>> 09.08.2007 15:28 >>>>>>> Bitte antworten an >>>>>>> "Tapestry users" <users@tapestry.apache.org> >>>>>>> >>>>>>> >>>>>>> An >>>>>>> Tapestry users <users@tapestry.apache.org> >>>>>>> Kopie >>>>>>> >>>>>>> Thema >>>>>>> Re: Memory leaks in Tapestry 4.1 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Well, we did lots of tests with 4.1.2 and >>>>>>> have yet to observe such memory leaks. >>>>>>> >>>>>>> [EMAIL PROTECTED] wrote: >>>>>>> >>>>>>>> Have you ever observed the memory usage for your Tapestry application? >>>>>>>> >>>>>>>> For example, make a simple HelloWorld Application and load the page >>>>>>>> >>>>>>> regularly using HTTP_LOAD. Then watch how the memory consumption grows >>>>>>> >>>>>> and >>>>>> >>>>>>> grows .... especially after an hour. >>>>>>> >>>>>>>> Has anyone got a solution how avoid this leakage? >>>>>>>> >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> 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] >>>>>>> >>>>>>> >>>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> 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] >>>>> >>>>> >>>>> >>>> -- >>>> Jesse Kuhnert >>>> Tapestry/Dojo team member/developer >>>> >>>> Open source based consulting work centered around >>>> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com >>>> >>>> --------------------------------------------------------------------- >>>> 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] >>> >>> >>> >> -- >> Jesse Kuhnert >> Tapestry/Dojo team member/developer >> >> Open source based consulting work centered around >> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com >> >> --------------------------------------------------------------------- >> 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] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
