Uwe Schäfer wrote:
Hi Artur,
I suppose it isn´t the AppendingStringBuffer that is causing your problem.
Did you attach a profiler? http://YourKit.com is just one example of a
good, easy to setuprun profiler.
I did like you said. I turns out that my refreshView consume so much memory
On Sun, 2007-12-30 at 07:46 -0800, Artur W. wrote:
Uwe Schäfer wrote:
Hi Artur,
I suppose it isn´t the AppendingStringBuffer that is causing your problem.
Did you attach a profiler? http://YourKit.com is just one example of a
good, easy to setuprun profiler.
I did like
yeah but South Africa has 3G no idea what thats gonna cost me.
But also internet cafes so i should use those more often..
johan
On Dec 29, 2007 12:09 AM, Sebastiaan van Erk [EMAIL PROTECTED] wrote:
He, I thought you were having vacation :-PPP
Seb*
Johan Compagner wrote:
Nowadays its
the permgen space param = -XX:MaxPermSize=256m
Just in case.
Maurice
On Dec 29, 2007 3:09 PM, Artur W. [EMAIL PROTECTED] wrote:
Eelco Hillenius wrote:
Yes, use a profiler. Everyone who is working on a production system
should regularly use a profiler and load testing tool to ensure
Hello Everybody!
I just got OutOfMemoryError in our production application (wicket 1.3rc2).
Any ideas what was the reason?
Artur
java.lang.OutOfMemoryError: Java heap space at
org.apache.wicket.util.string.AppendingStringBuffer.expandCapacity(AppendingStringBuffer.java:158)
at
Hi Artur,
I suppose it isn´t the AppendingStringBuffer that is causing your problem.
Did you attach a profiler? http://YourKit.com is just one example of a
good, easy to setuprun profiler.
java.lang.OutOfMemoryError: Java heap space at
Did you try starting your app container with extra memory, by default
java does not allocate that much, a common webapp is likely to run out
of memory with the default settings.
Maurice
On Dec 28, 2007 1:20 PM, Uwe Schäfer [EMAIL PROTECTED] wrote:
Hi Artur,
I suppose it isn´t the
Uwe Schäfer wrote:
I suppose it isn´t the AppendingStringBuffer that is causing your problem.
Did you attach a profiler? http://YourKit.com is just one example of a
good, easy to setuprun profiler.
I didn't. It happened in our production server and only once. But this kind
of errors
Artur W. schrieb:
I didn't. It happened in our production server and only once. But this kind
of errors makes me worry so
I wanted to ask about it.
i´d suggest you duplicate your productionserver and attach a profiler
while load-testing with some usual tool like jmeter etc in order to see
Mr Mean wrote:
Did you try starting your app container with extra memory, by default
java does not allocate that much, a common webapp is likely to run out
of memory with the default settings.
I start tomcat with:
-Xms512M -Xmx768M
Should I consider something else?
I start tomcat with:
-Xms512M -Xmx768M
Should I consider something else?
Yes, use a profiler. Everyone who is working on a production system
should regularly use a profiler and load testing tool to ensure there
are no memory leaks etc. In my experience and if you search threads in
this list,
11 matches
Mail list logo
