A Wicket app that is not written correctly can suck up resources. Wicket keeps track of pages a user has been on by serializing them, "back button support". If a page has references to other objects, it serializes them and so on and so on. It can get real ugly real quick.
Wicket has many built-in ways to keep this from happening, but it is still easy for a beginner to write an app that can cause problems. Thanks, Warren Bell On 5/16/12 12:49 PM, Mikolaj Rydzewski wrote: > On 05/16/2012 05:35 PM, Christian Kaufhold wrote: >> its not intentional but the myfaces App runs on the server for years now >> and should not cause the problem >> I recently deployed a wicket app and now >> the server is slowing down when we have about 10 users or so. >> > > So there are two different applications? Myfaces (which used to work for > a long time) and wicket (which takes server down)? > I'd separate them first to have clear environment for investigation. > Then enable GC logging, attach jvisualvm, deploy psi probe > (http://code.google.com/p/psi-probe/), etc. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
