Re: memory leaks

2012-03-15 Thread Thiago H. de Paula Figueiredo
On Wed, 14 Mar 2012 23:36:42 -0300, dick_hu dickan...@gmail.com wrote: there is trouble always with me, when I change a page or a component ofen cause significant memory leaks and I must restart the server. You'll probably don't use live class reloading in production at all, maybe just

Re: memory leaks

2012-03-15 Thread dick_hu
How can I use live class reloading,Is there any example to me. I can not understand with you. Thank you -- View this message in context: http://tapestry.1045711.n5.nabble.com/memory-leaks-tp5566822p5567806.html Sent from the Tapestry - User mailing list archive at Nabble.com

Re: memory leaks

2012-03-15 Thread Thiago H. de Paula Figueiredo
On Thu, 15 Mar 2012 09:14:25 -0300, dick_hu dickan...@gmail.com wrote: How can I use live class reloading,Is there any example to me. I can not understand with you. 1) There are no memory leaks in Tapestry related to live class reloading. 2) If you don't know what live class reloading is, why

Re: memory leaks

2012-03-15 Thread Nicolas Barrera
Paula Figueiredo thiag...@gmail.com wrote: On Thu, 15 Mar 2012 09:14:25 -0300, dick_hu dickan...@gmail.com wrote: How can I use live class reloading,Is there any example to me. I can not understand with you. 1) There are no memory leaks in Tapestry related to live class reloading. 2

Re: memory leaks

2012-03-15 Thread Thiago H. de Paula Figueiredo
On Thu, 15 Mar 2012 13:13:32 -0300, Nicolas Barrera nbarr...@gmail.com wrote: I 'm having an issue using mvn:jetty (which can reload the context by pressing enter on the console)... after I press enter (reload context) let's say 3 times an outofmemoryerror turns out... This is a

Re: memory leaks

2012-03-15 Thread Nicolas Barrera
Thiago, thanks for the info I don't want to turn off topic but, what jvm would you recommend instead of oracle's? ps: note that while just class reloading OutOfMemoryError takes a while to appear, but when reloading the application context it really blowns fast (2 or 3 reloads as I said). So

memory leaks

2012-03-14 Thread dick_hu
ofen cause significant memory leaks and I must restart the server. Is there any way to solve that. -- View this message in context: http://tapestry.1045711.n5.nabble.com/memory-leaks-tp5566822p5566822.html Sent from the Tapestry - User mailing list archive at Nabble.com

Memory Leaks

2010-02-09 Thread Jim O'Callaghan
Looking at the memory (private working set) used by the java process my Tapestry 5 app is running under, I notice that when running through the same request cycle with PRODUCTION_MODE set to true, I am getting an increase of approx 4K per repeated request. Is this typical or something to be

Re: Memory Leaks

2010-02-09 Thread Thiago H. de Paula Figueiredo
What are your values for the tapestry.page-pool.* symbols? Have you tested making 1k or 10k request and then taking another used memory reading? Some time ago, someone here (sorry, I forgot the name) posted a test like the one I'm suggesting above (a load test). It found out that Tapestry,

RE: Memory Leaks

2010-02-09 Thread Jim O'Callaghan
...@gmail.com] Sent: 09 February 2010 10:57 To: Tapestry users Subject: Re: Memory Leaks What are your values for the tapestry.page-pool.* symbols? Have you tested making 1k or 10k request and then taking another used memory reading? Some time ago, someone here (sorry, I forgot the name) posted a test

Re: Memory Leaks

2010-02-09 Thread Howard Lewis Ship
: Memory Leaks What are your values for the tapestry.page-pool.* symbols? Have you tested making 1k or 10k request and then taking another used memory reading? Some time ago, someone here (sorry, I forgot the name) posted a test like the one I'm suggesting above (a load test). It found out

T4: page pool memory leaks

2008-03-17 Thread Jean-Philippe Bouchard
Boy, am I glad to have figured out that one! I run a pretty busy site using T4 and tomcat had to be restarted every day because it was running out of memory. That problem has plagued me for the past year and it turns out it was caused by the page pool accumulating several version of each page

Re: Memory leaks in Tapestry 4.1

2007-08-10 Thread Chris Chiappone
Betreff: Re: Memory leaks in Tapestry 4.1 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

Re: Memory leaks in Tapestry 4.1

2007-08-10 Thread munich
Datum: Fri, 10 Aug 2007 04:58:18 +0200 Von: Hans Jörg Hessmann [EMAIL PROTECTED] An: Tapestry users users@tapestry.apache.org Betreff: Re: Memory leaks in Tapestry 4.1 There is an excellent tool for post-mortem memory analyzation: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library

Memory leaks in Tapestry 4.1

2007-08-09 Thread munich
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

Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Kristian Marinkovic
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

Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread munich
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

Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread munich
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

Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Jonathan Glanz
Have you tried pulling heap dumps and anaylizing them ? Sent via BlackBerry by ATT -Original Message- From: [EMAIL PROTECTED] Date: Thu, 09 Aug 2007 17:04:21 To:Tapestry users users@tapestry.apache.org Subject: Re: Memory leaks in Tapestry 4.1 Within one day it rises slowly from 100

Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Jesse Kuhnert
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

Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Todd Orr
: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

Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Ben Tomasini
I have used both Tapestry and HiveMind under high production loads and have never found any memory leaks in the frameworks themselves. This includes memory intensive, high volume workflow and image processing applications for large financial institutions. However, nearly every application I have

Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Todd Orr
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

Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Hans Jörg Hessmann
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