Hello, We ran into a problem in our production environment where the tapestry page pool was maxed out and new requests for a page were denied. We had set the tapestry.page-pool.hard-limit value to 300, and the worker thread pool for jboss was set to 160. We ended up changing the tapestry.page-pool.hard-limit value to 800 and the jboss worker thread pool also to 800 and now it is not reaching that max and the website is stable again.
Can anyone explain why problem would occur in the first place? Would this problem happen is the tapestry.page-pool.hard-limit is Greater than the worker thread pool as the Tapestry docs suggest now? Any insight into this would be much appreciated. Also, can someone explain how to monitor the actual runtime tapestry.page-pool.hard-limit and tapestry.page-pool.soft-limits in production for Tapestry 5.2? I had found the following IMonitor class that you can provide an MBean for, but this is gone in tapestry 5.2 now. Is there any other way to see current actual number of page instances used in production? Thanks in advance for the help, Hemant http://tapestry.apache.org/tapestry4/tapestry/apidocs/org/apache/tapestry/engine/IMonitor.html -- View this message in context: http://tapestry-users.832.n2.nabble.com/How-to-monitor-Tapestry-page-pool-for-issues-tp5640517p5640517.html Sent from the Tapestry Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
