?
- Original Message
From: Dave Greggory davegregg...@yahoo.com
To: Tapestry users users@tapestry.apache.org
Sent: Monday, September 14, 2009 6:44:27 PM
Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak (doesn't
reduce after forced GC)
I created a ComponentLoader component (below
users users@tapestry.apache.org
Sent: Thursday, September 17, 2009 2:58:09 AM
Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak (doesn't reduce
after forced GC)
I've tried it with a ComponentWrapper (or loader) too, but don't got it to work
this way.
Now i use a simple BeanEditForm
Em Thu, 17 Sep 2009 15:28:36 -0300, Dave Greggory davegregg...@yahoo.com
escreveu:
So nobody has still answered my question whether ComponentSource is an
acceptable way to retrieve a component instance you need? The interface
is not internal, so I'd assume so, but the implementation is,
If the interface is NOT in an internal package, than its public API. Despite
my best efforts, there's a lot of that! :-)
On Thu, Sep 17, 2009 at 11:48 AM, Thiago H. de Paula Figueiredo
thiag...@gmail.com wrote:
Em Thu, 17 Sep 2009 15:28:36 -0300, Dave Greggory davegregg...@yahoo.com
escreveu:
of functionality, to use something similar to what I had to
do.
- Original Message
From: Howard Lewis Ship hls...@gmail.com
To: Tapestry users users@tapestry.apache.org
Sent: Thursday, September 17, 2009 2:54:19 PM
Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak (doesn't reduce
a large number of
ComponentPageElements with it. Is that an accurate?
- Original Message
From: Dave Greggory davegregg...@yahoo.com
To: Tapestry users users@tapestry.apache.org
Sent: Monday, September 14, 2009 6:44:27 PM
Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak (doesn't
, Dave Greggory davegregg...@yahoo.comwrote:
NYC.
- Original Message
From: Howard Lewis Ship hls...@gmail.com
To: Tapestry users users@tapestry.apache.org
Sent: Friday, September 11, 2009 3:11:57 PM
Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak (doesn't reduce
after
Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak (doesn't reduce
after forced GC)
Although upgrading is a good idea for many reasons, I don't think it will
solve your problem. You need a little re-architecting of your approach to
get the component instance count back under control
:
NYC.
- Original Message
From: Howard Lewis Ship hls...@gmail.com
To: Tapestry users users@tapestry.apache.org
Sent: Friday, September 11, 2009 3:11:57 PM
Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak (doesn't
reduce
after forced GC)
Although upgrading
Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak
(doesn't
reduce
after forced GC)
Although upgrading is a good idea for many reasons, I don't think
it
will
solve your problem. You need a little re-architecting of your
approach
to
get the component instance count back under control
Em Mon, 14 Sep 2009 10:49:15 -0300, Stefan ste...@wammel.com escreveu:
I think the best, or most common and stable solution would be to extend
the always existing infrastructure to be able to register own
datatypes and their view/edit components.
But is that possible? And how?
Yes. Take a
I created a ComponentLoader component (below) based off of PropertyEditor
component and I got it working for the top most of layer of my
ubercomponent-stack. It uses PropertyEditBlock page and the existing
BeanBlockSource to provide the right Block containing my layouts / components.
Does it
I have T5.0.18 running in Tomcat 5.5 with Java 1.5 32-bit -Xms2048m -Xmx2048m
-XX:PermSize=128m -XX:MaxPermSize=128m.
Configured as:
tapestry.page-pool.active-window = 5 m
tapestry.page-pool.hard-limit = 10
Ran a JMeter Load Test with
10 concurrent users
Ramp-up time of
Em Fri, 11 Sep 2009 12:47:23 -0300, Dave Greggory davegregg...@yahoo.com
escreveu:
I have T5.0.18 running in Tomcat 5.5 with Java 1.5 32-bit -Xms2048m
-Xmx2048m -XX:PermSize=128m -XX:MaxPermSize=128m.
Have you tried 5.1.0.5?
--
Thiago H. de Paula Figueiredo
Independent Java consultant,
I applaud the efforts, but I think you really really have to upgrade
to 5.1.0.5 before you can get this on anybody's radar. There's a good
possibility the same wouldn't happen in it. If you are running with
-server (think it may be automatically chosen if you haven't specified
with that heap max)
Tapestry 5.1.0.5 is more efficient, but that's mostly in terms of reducing
the number of temporary objects created during a single request.
392,000 instances of ComponentPageElementImpl?
How many pages in your application? Say there's 15 distinct pages.
392,000 / (15 district * 10 hard limit) =
From: Howard Lewis Ship hls...@gmail.com
To: Tapestry users users@tapestry.apache.org
Sent: Friday, September 11, 2009 2:36:00 PM
Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak (doesn't reduce
after forced GC)
Tapestry 5.1.0.5 is more efficient, but that's mostly in terms of reducing
we know
whether that's a potential solution to the problem.
- Original Message
From: Thiago H. de Paula Figueiredo thiag...@gmail.com
To: Tapestry users users@tapestry.apache.org
Sent: Friday, September 11, 2009 12:17:38 PM
Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak
NYC.
- Original Message
From: Howard Lewis Ship hls...@gmail.com
To: Tapestry users users@tapestry.apache.org
Sent: Friday, September 11, 2009 3:11:57 PM
Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak (doesn't reduce
after forced GC)
Although upgrading is a good idea
Leak (doesn't reduce
after forced GC)
Em Fri, 11 Sep 2009 12:47:23 -0300, Dave Greggory davegregg...@yahoo.com
escreveu:
I have T5.0.18 running in Tomcat 5.5 with Java 1.5 32-bit -Xms2048m
-Xmx2048m -XX:PermSize=128m -XX:MaxPermSize=128m.
Have you tried 5.1.0.5?
--Thiago H. de Paula
20 matches
Mail list logo
