Bugs item #801111, was opened at 2003-09-05 14:10 Message generated for change (Comment added) made by wesgere You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=801111&group_id=22866
Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Bill Burke (patriot1burke) Assigned to: Nobody/Anonymous (nobody) Summary: open file handles from deployernet/effects netboot too Initial Comment: I think the following problem manifests in netboot as well as the servlet container can run out of threads quite easily with netboot. Hi folks, Now that I've managed to configure Wintendo 2000 Server to service a high number of threads (up to about 7,000 although I'm using fewer than that), I'm running into an open handle problem. :-) Since I can't figure out how to bump the OS handle limit, I'm trying to limit the number of handles used by JBoss-tomcat. Using ProcessExplorer[1], I see that a large number of handles (about 1,500) are open for files deployed by UrlDeploymentScanner (jar and xml files). I have the JBoss-3.2.1 book, and have checked the documentation in the section "Hot Deployment of Components, the UrlDeploymentScanner". I've tried setting ScanPeriod to 0 (not documented to behave the way I guessed it might) and the equivalent of 6 hours, and I can't seem to get JBoss to release those file handles. Is there a way to use UrlDeploymentScanner for initial container boot, but to never rescan for deployment updates? I'm assuming it's the need to rescan that causes JBoss to hold these file handles open. We don't need the ability to hot deploy or redeploy after container boot, and can't anyway because we haven't specified dependencies. I realize that an easier solution would be to bump the OS handle limit, but my Wintendo Fu is lacking. Thanks, Sheldon. ---------------------------------------------------------------------- Comment By: Wes Gere (wesgere) Date: 2004-03-24 17:15 Message: Logged In: YES user_id=690357 Unfortunately, I don't think there's anything you can do in JBoss to fix this. It's a limitation of the java vm. All java processes behave this way - any jar files used by the java program stay open during the life of the process. You can see this by looking at any java instance in Process Explorer. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=801111&group_id=22866 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
