The components page (http://wicketstuff.org/wicket13/compref/) is also giving
this OutOfMemoryError.
igor.vaynberg wrote:
johan, can you bump up the permgen memory some more? we have too many
damn things running on that tomcat instance...
-igor
On Jan 31, 2008 4:55 PM, Brad Fritz
done. upped it 40MB more
i am curious what constantly really hangs around. Is it for example
something we in wicket can do if you constantly redeploy our examples?
Should we cleanup some more?
johan
On Feb 1, 2008 2:21 AM, Igor Vaynberg [EMAIL PROTECTED] wrote:
johan, can you bump up the
hm, i thought we already went through and removed all references to
Class with a weakref, so im not sure there is something else. everyone
has this problem if they redeploy a webapp a lot, and we do our
examples quiet often no?
-igor
On Feb 1, 2008 3:41 AM, Johan Compagner [EMAIL PROTECTED]
We dont do it that often, maybe we cant do anything about it, just
wondering if it could be something.
On 2/1/08, Igor Vaynberg [EMAIL PROTECTED] wrote:
hm, i thought we already went through and removed all references to
Class with a weakref, so im not sure there is something else. everyone
Apologies if this isn't the right place to report it, but the Wicket
Stuff examples JVM is currently throwing OutOfMemoryErrors. For
example from http://wicketstuff.org/wicket13/helloworld/ :
[..]
description The server encountered an internal error () that prevented it
from fulfilling
johan, can you bump up the permgen memory some more? we have too many
damn things running on that tomcat instance...
-igor
On Jan 31, 2008 4:55 PM, Brad Fritz [EMAIL PROTECTED] wrote:
Apologies if this isn't the right place to report it, but the Wicket
Stuff examples JVM is currently
