The problem with snapshots is that it makes it that much harder to figure out if this is a bug that's been fixed, or something new.
On Fri, May 9, 2008 at 5:39 PM, Martin Grotzke <[EMAIL PROTECTED]> wrote: > Hi, > > yesterday we deployed our application upgraded from T5.0.5 to 5.0.10 > (SNAPSHOT 2008-02-11) on the production system, now it hangs from time > to time with several thread blocked at > PerThreadServiceCreator.createObject. > > We started with default settings for thetapestry.page-pool.hard-limit > and soft-limit (20, 5). With this we got a page pool exausted error on > one tomcat after some time, while others were fine with this. > > Then we increased the soft-limit to 20 and the hard-limit to 100, which > also produced this error, but not always. Even without the pool exausted > error the application hung and did not respond for some minutes (about 3 > minutes). > > Now we have the hard-limit set to 150, which does not produce any pool > exausted errors, but still the application hangs. > > All thread dumps that are created when the application is not responding > show blocked threads at PerThreadServiceCreator.createObject, and I > cannot see anything else that might cause this behaviour. > Looking at jconsole when the app is not responding shows an increasing > number of threads, and an increasing amount of used memory (e.g. from > 500M to 800M), CPU is very low all the time. > > I have uploaded a complete threaddump at http://senduit.com/a7afc7, an > aggregated version of this can be found at http://senduit.com/0d3f16. > > We're running java-1.6.0_02, T5.0.10-SNAPSHOT and Tomcat 6. > > Has anybody an idea what might be the reason for this behavior? > > Thanx a lot for your help, > cheers, > Martin > > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
