1. I increased the Java heap to 512k. 2. I lowered the number of allowed concurrent requests from 12 to 8 3. I added the TIMEOUT param to all my <cfhttp> and <cfpop> tags... I realized some of them were hanging. In the future I won't consider that param optional. 4. I configured CF8 Enterprise's auto self-healing stuff
So far so good...! On Wed, Dec 3, 2008 at 10:39 PM, Wil Genovese <[EMAIL PROTECTED]> wrote: > Philip, > > Glad to hear things are getting better. Please do tell us what changes > you made that worked. And if something didn't work let us know that > also. > > Wil Genovese > > One man with courage makes a majority. > -Andrew Jackson > > A fine is a tax for doing wrong. A tax is a fine for doing well. > > On Dec 3, 2008, at 4:17 PM, Philip Kaplan wrote: > > > You are all awesome. Took many of your suggestions, haven't had a > > crash yet > > today. I'm crossing my fingers. > > > > On Wed, Dec 3, 2008 at 2:05 PM, Jochem van Dieten > > <[EMAIL PROTECTED]> wrote: > > > >> On Wed, Dec 3, 2008 at 7:33 AM, Philip Kaplan wrote: > >>> At risk of sounding like an idiot, is there a way to just figure > >>> out WHAT > >>> Jrun is working on when it's spiked to 100%? Assume CF Monitor and > >>> FusionReactor are unavailable, but I can usually get into the > >>> Windows box > >>> and mess around. > >> > >> Try jstack to get a stack trace: > >> > >> > http://jochem.vandieten.net/2008/12/03/using-jdk-tools-to-analyze-coldfusion-hangs/ > >> > >> Jochem > >> > >> > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:316370 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
