Greetings all, Recently I have been performance testing a Wicket application (1.4.1) and I am running into the dreaded Too Many Files Open issue. I have searched the mailing lists and most of the trouble around this issue seems to come from being in DEVELOPMENT mode so I made sure we were in DEPLOYMENT mode. When I run 'lsof -p xxxx | grep wicket-1.4.1.jar' I see over 1000 entries and it's growing monotonically. This seems really unusual - why would wicket need 1000 copies of this jar open? An additional bit of weirdness came up when our load tests stopped loading the embedded assets (css, js and images) in each page - this seemed to cap the number of lsof entries at 5... This is even weirder because our app serves these static items from httpd without tomcat ever knowing about them. How could our loading of embedded items really affect the number of file handles wicket needs?
For completeness we are running this app on Red Hat Enterprise Linx 5 with Tomcat 6.0.20 and Java 1.6 Adam
