https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1820
Quoting Werner Punz <werner.p...@gmail.com>:
Stan can you give us some info what the issue in Mojarra was?
It might help us to track our problem down.
My personal guess we that it might the our class instantiation code in
shared, but I am guessing here as well.
Werner
Am 15.10.10 14:04, schrieb ssilv...@redhat.com:
I'm pretty sure 2.0.1 has a memory leak on undeploy. Mojarra had an
undeploy leak and it took a long time to track it down. The same test I
was using on Mojarra also failed on MyFaces but I haven't had time to
track down the leak in MyFaces.
Maybe this is fixed in 2.0.2? If not maybe someone can go ahead and take
a look? The mem leak keeps MyFaces from passing TCK on JBoss AS. To
test, all you need to do is create a small exploaded JSF app. Then have
a script that touches web.xml every 10 seconds. That will cause the app
to redeploy. You will get a PermGen error in about an hour.
Stan
Quoting Matthias Wessendorf <mat...@apache.org>:
On Fri, Oct 15, 2010 at 10:15 AM, Werner Punz <werner.p...@gmail.com>
wrote:
Am 15.10.10 09:26, schrieb Matthias Wessendorf:
Right now it has MyFaces 2.0.1, but I'm soon planning to do the full
integration of 2.0.2 as per Leonardo's changes. That will make
MyFaces a
little more efficient on JBoss AS.
+1 you really want 2.0.2 ;)
Hehe I guess Myfaces 2.0.2 performance also will be better due to the
performance work which went in between 2.0.1 and 2.0.2.
that's why ;)
Werner
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
