Hello. I have been using Wicket for some time now and noticed that my processor activity is always at about 50%. When I start up my application server (Resin 3.1.6) it is still ol but as soon as I call a page in the wicket app it goes up. With JProfiler I see that the most activity is caused by the org.apache.wicket.util.thread.Task$1 class. Anyone any idea what could be causing this problem? It is just a pretty standard wicket app using authentication (using Swarm) but I eliminated that as to be the source of the problem.
If you need more info please let me know. Greetings, Ronald -- View this message in context: http://www.nabble.com/Processor-50--active-all-the-time-tp19251820p19251820.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
