Re: [JBoss-user] Disabling hot deployment to limit open file handles
On (2003/09/02 18:10), Sheldon Hearn wrote: attribute name=ScanEnabledfalse/attribute Nope, ScanEnabled=false doesn't change the behaviour; the JAVA.EXE process maintains an open handle on every single file in lib, server/default/lib and server/default/deploy and server/default/tmp. On my FreeBSD workstation, fstat(1) shows JBoss has only 35 open file descriptors. I'm starting to get the feeling I'm the only idiot in the world to ever have done anything serious with JBoss on a Wintendo box. :-) Hi Adrian, Just a datapoint. I've had private mail from someone who's seeing this with jobss-3.2.1-tomcat-4.1.24 on both Windows XP and RedHat Linux. The person who sent me the mail says that, on his Linux box, each dedeploy increases the number of file descriptors used, until eventually he gets too many open files in system! So, this Jboss distribution seems to exhibit the problem on Windows 2000 Server, Windows XP and RedHat Linux. I'm stumped. :-) Ciao, Sheldon. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Disabling hot deployment to limit open file handles
On (2003/08/31 23:10), Adrian Brock wrote: attribute name=ScanEnabledfalse/attribute Nope, ScanEnabled=false doesn't change the behaviour; the JAVA.EXE process maintains an open handle on every single file in lib, server/default/lib and server/default/deploy and server/default/tmp. I've checked that TASKMGR.EXE agrees with ProcessExplorer, and it does; both say the JBoss process has about 1,400 open handles at the best of times. On my FreeBSD workstation, fstat(1) shows JBoss has only 35 open file descriptors. I'm starting to get the feeling I'm the only idiot in the world to ever have done anything serious with JBoss on a Wintendo box. :-) Ciao, Sheldon. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Disabling hot deployment to limit open file handles
On (2003/08/31 23:10), Adrian Brock wrote: attribute name=ScanEnabledfalse/attribute Thanks! That's not in the Jboss-3.2.1 book, so your response is much appreciated. Setting the period to 0 will just cause it to spin in a cpu loop. Suitable punishment for a server that's given me nothing but grief for 4 days. I finally got everything working, and now the hardware's failed (mobo, according to the colo guys). Some people get all the luck. :-) Are you sure the file handles aren't jasper checking for changed jsps? Dead sure, although that'll be true for _some_ of them. Every jar and xml file deployed by JBoss (even with jbossweb-tomcat.sar disabled) consumes an open NT File Handle for the lifetime of the JBoss process. I'll try ScanEnabled=false and see if that changes the behaviour. If not, this is probably worth looking into, as it seems incredibly wasteful to hold onto those references. Perhaps the Wintendo equivalent of stat() is too expensive or doesn't exist, in which case JBoss's behaviour makes sense. Have you turned off development mode for jasper in jbossweb-tomcat.sar/META-INF/web.xml? Yes. :-) I got around the problem by starting Jboss as an NT service with the Java Service Wrapper. This gets around the hard limit on the number of open file handles for programs run from a CMD.EXE prompt, and around the 22MB heap limit for the desktop when Terminal Server is enabled. Later in the week, I intend to post my notes on getting JBoss to work on high-end PC hardware that's been encumbered with a Wintendo operating system. Probably not useful to serious Microsoft cluebats, but I hope it'll help folks like me who've never had to administer Wintendo systems before. Ciao, Sheldon. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Disabling hot deployment to limit open file handles
On (2003/09/01 14:29), Adrian Brock wrote: Dead sure, although that'll be true for _some_ of them. Every jar and xml file deployed by JBoss (even with jbossweb-tomcat.sar disabled) consumes an open NT File Handle for the lifetime of the JBoss process. I'll try ScanEnabled=false and see if that changes the behaviour. Report back, sounds like something not closing something and leaving it to the gc? Which JBoss version are you using? jboss-3.2.1_tomcat-4.1.24 jdk-1.4.2_01 Windows 2000 Server SP4 I'm using ProcessExporer (http://www.sysinternals.com/) to inspect the handles. It's possible that ProcessExplorer is just plain wrong. Can't try ScanEnabled until the mobo swapout happens, and it's a national holiday for the colo guys. All the luck, I tell you. :-) Ciao, Sheldon. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Disabling hot deployment to limit open file handles
Today's lesson... never colo with a company that has different national holidays (and hence, different time priorities) to you! :-) -- Danny Yates -Original Message- From: Sheldon Hearn [mailto:[EMAIL PROTECTED] Sent: 01 September 2003 15:20 To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Disabling hot deployment to limit open file handles On (2003/09/01 14:29), Adrian Brock wrote: Dead sure, although that'll be true for _some_ of them. Every jar and xml file deployed by JBoss (even with jbossweb-tomcat.sar disabled) consumes an open NT File Handle for the lifetime of the JBoss process. I'll try ScanEnabled=false and see if that changes the behaviour. Report back, sounds like something not closing something and leaving it to the gc? Which JBoss version are you using? jboss-3.2.1_tomcat-4.1.24 jdk-1.4.2_01 Windows 2000 Server SP4 I'm using ProcessExporer (http://www.sysinternals.com/) to inspect the handles. It's possible that ProcessExplorer is just plain wrong. Can't try ScanEnabled until the mobo swapout happens, and it's a national holiday for the colo guys. All the luck, I tell you. :-) Ciao, Sheldon. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user _ Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch, Banc of America Securities Limited and Banc of America Futures Incorporated are regulated by the Financial Services Authority. _ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
