Well, I was using a release from the previous days and that is why it wasn't
swallowing the Exception (I have since verified that I am using the latest
SNAPSHOT from source, not wicketstuff repo).  But I still experience HUGE
delays when it goes wrong (I just can't see why now, which is actually worse
than before because at least I could see why that app ground to a halt)

I had one bog down for 59 seconds today.  My average seems to be between
20-30 seconds.  

I guess maybe the question might be will
http://issues.apache.org/jira/browse/WICKET-278 potentially solve the
problem by eliminating the Exceptions or is their another issue that causes
the slowdown and #278 is just one way to repeatedly cause the problem?

Chuck


Eelco Hillenius wrote:
> 
> On 2/9/07, ChuckDeal <[EMAIL PROTECTED]> wrote:
>>
>> Wicket 1.3 (revision 505283)
>>
>> The following is a stack trace that I have experienced quite a few times
>> recently.  This new behavior started in the past couple of weeks.  My
>> real
>> concern (besides all of the crap that is spewed into my log, obscuring
>> the
>> real exception) is the time it takes to do this: from the timestamps you
>> can
>> see that this takes roughly 21 seconds!  I guess my argument would be
>> that
>> if I received the first exception then of course something is screwed up,
>> so
>> why bother continueing whatever processing that is going on that causes
>>         at wicket.util.lang.Objects.sizeof(Objects.java:1281)
>>         at wicket.Component.getSizeInBytes(Component.java:1107)
>>         at
>> wicket.markup.html.debug.PageView$3.component(PageView.java:140)
>> to be called.  It looks like some attempt to serialize but, if I got the
>> first exception, what cause would there be to serialize anything?  Is
>> this a
>> work in progress type of thing or unexpected behavior?
> 
> The NotSerializableExceptions gets swallowed silently in that function
> since yesterday (which is in line with how it was implemented for
> 2.0). Why it takes so long? I have no idea unless you are working with
> huge components. Even then 21 seconds sounds like something
> definitively being wrong.
> 
> Eelco
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier.
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
> 
> 

-- 
View this message in context: 
http://www.nabble.com/tons-of-%22size-of-failed%22-exceptions-tf3200578.html#a8974021
Sent from the Wicket - User mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to