Hi All, This is a tricky question one since I do realize there are several possibilities to explain the problem, not all of which are Tapestry related. We have battled to understand what is going on in production for the past year or so, and have tried to pinpoint where the problem lies and come up short. If anyone has experienced anything similar *please share.
Our environment is: Ubuntu Server Tapestry 5.1 JDK 6 Tomcat 6 Apache in front (reverse proxy) We are deploying our Tapestry apps to Tomcat 6, and they do run great even with load, and it remains very stable as the session count increases; this is when a server restart is done after a deployment. The problem appears to be specific to 'Tapestry applications' and hot deployment. We run several apps, both small and large and they all react the same way... If we stop then undeploy any of these Tapestry apps, and afterwards do a hot deploy with a newer version (without the restart), the CPU usage shoots to 100% and stays there. JSP based apps pure Servlets don't appear to react in the same way. Has anybody experienced something similar? Kind regards, Peter --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
