You can try to see if its any page in particular that causes this. Or of its something general... Also you need to watch out for objects that just keep growing in number..
None of our classes has an unexpected high instance count.
It's a little abstract to use a profiler as it will not give you a clear idea as everything originates in class[] int[] etc...
Of course.
Tom
Nino Saturnino Martinez Vazquez Wael wrote:
You can try to see if its any page in particular that causes this. Or of
its something general... Also you need to watch out for objects that
just keep growing in number..
It's a little abstract to use a profiler as it will not give you a clear
idea as everything originates in class[] int[] etc...
regards Nino
Thomas Singer wrote:
Be sure to checkout the wiki for gotchas and tips:
http://cwiki.apache.org/WICKET/wicket-and-jmeter.html
http://cwiki.apache.org/WICKET/wicket-and-jmeter-with-regular-expressions.html
Already done, but what we can get? An OOME in our application with the
heapdump. Well, we already have one and the most used objects appear
to come from Wicket (char[], byte[], String, <class>[], HashMap$Entry,
XMLTag, ValueMap, ComponentTag, RawMarkup, HashMap$EntrySet, int[],
short[] just to name the largest).
--
Best regards,
Thomas Singer
_____________
SyntEvo GmbH
www.syntevo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
