Yea - sorry, I meant to explain that it was CFMX 7.0 (with updater and hot fix) running on Win2K3 in IIS 6.0 with all the patches.
Dave ----- Original Message ----- From: "Robertson-Ravo, Neil (RX)" <[EMAIL PROTECTED]> To: "CF-Server" <[email protected]> Sent: Monday, November 21, 2005 2:10 PM Subject: Re: JRun4 100% - server down > Is this on IIS by any chance? > > > > > > "This e-mail is from Reed Exhibitions (Oriel House, 26 The Quadrant, > Richmond, Surrey, TW9 1DL, United Kingdom), a division of Reed Business, > Registered in England, Number 678540. It contains information which is > confidential and may also be privileged. It is for the exclusive use of > the > intended recipient(s). If you are not the intended recipient(s) please > note > that any form of distribution, copying or use of this communication or the > information in it is strictly prohibited and may be unlawful. If you have > received this communication in error please return it to the sender or > call > our switchboard on +44 (0) 20 89107910. The opinions expressed within > this > communication are not necessarily those expressed by Reed Exhibitions." > Visit our website at http://www.reedexpo.com > > -----Original Message----- > From: David Hannum <[EMAIL PROTECTED]> > To: CF-Server <[email protected]> > Sent: Mon Nov 21 18:17:51 2005 > Subject: JRun4 100% - server down > > Last week we started up a new CF7 server (on Win2K3) with 2 processors and > 2GB RAM. This is a high traffic server running the CommonSpot CMS. Over > the past week, we've watched the RAM creap up from 715MB to 1GB and above. > Today, the JRun went to 100% and the site quit responding. We restarted > the > > JRun service, but it immediately went to 100% and is staying there with no > response. RAM is currently at 750MB +/-. > > When we started this new box, we studied the JVM.CONFIG very much, and put > what we thought would be good values in. But the constant RAM creep has > been in the back of our minds, and it seems to have come to a head today. > Our critical JVM.CONFIG settings are: > -Xmx1024m -Xmx512m -Dsun.io.useCanonCaches=false -XX:MaxPermSize=128m > -XX:PermSize=64m > -XX:+UseConcMarkSweepGC -XX:NewSize=64m > > We believed that with the GC set to "UseConcMarkSweepGC" we'd avoid the > big > garbage collection issues, but now we're not sure. > > Any suggestions what our problem may be? > > Thanks, > Dave > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Purchase Contribute 3 from House of Fusion, a Macromedia Authorized Affiliate and support the CF community. http://www.houseoffusion.com/banners/view.cfm?bannerid=53 Message: http://www.houseoffusion.com/lists.cfm/link=i:10:5678 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/10 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:10 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.10 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
