Douglas Ferguson <douglas <at> douglasferguson.us> writes:
>
> We are experiencing some hard to trace performance issues (CPU pegged by
JAVA). so we want to implement some
> logging in order to Audit the code.
>
> Any suggestions on wicket state that we can easily print out? I.E. size of
page map? Etc?
>
> D/
Hi,
I'm having similar problems, my setup is: Java 1.6.10, Wicket 1.3.5 and
Tomcat 6 on Windows XP. Tomcat seems to need 50% CPU from time to time, and
often for a very long time.
Will try Jeremy's suggestion, mind to share your findings ?
Cheers,
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
