> Use this tool. http://www.seefusion.com/seestack/seestack.cfm I will - thank you!
> Are you maxed out at 12, meaning there are normally threads > in the que waiting to be processed? No. Normally there is rarely more than 1 thread running at a time. Except when a crash happens -- then it immediately becomes maxed out (because all threads become hung) with 12 threads. I look forward to another crash so I can use the SeeStack tool :-] On Tue, Dec 2, 2008 at 10:38 PM, Wil Genovese <[EMAIL PROTECTED]> wrote: > You don't have to worry too much about trying to read the stack trace. > Use this tool. http://www.seefusion.com/seestack/seestack.cfm > > It's called see stack. Dump your stack traces into the seestack tool > and it will do the work for you and give you some meaningful > information. Usually the things your looking for are threads that are > present from trace to trace to trace. Those are usually the hung up > or slow running threads. At that point the details of the thread > should give you a clue as to what actions was being taken at the time. > > Also, you mentioned that no more than 12 requests at a time are > allowed. Are you maxed out at 12, meaning there are normally threads > in the que waiting to be processed? > > > > 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 12:31 AM, Philip Kaplan wrote: > > >> When jrun is doing the 100% thing, look at the currently running > >> requests > > > in fusion-reactor > > > > Usually when Jrun is doing its 100% thing, FusionReactor won't load. I > > suppose the server is hogged. > > > > But there are never more than 12 requests running at a time (that's > > the max > > I set). > > > >> How long have they been running? > > > > Whatever requests are running during the 100% thing, will continue > > to run > > forever until the server (or process) is restarted. > > > >> What are they doing? (stack trace) > > > > I admit I don't really know how to effectively read a stack trace. > > There's > > a ton of stuff in there. Would it be useful or annoying if I pasted > > one to > > cf-talk, next time it happens? > > > > Philip > > > > On Tue, Dec 2, 2008 at 10:19 PM, Brad Wood <[EMAIL PROTECTED]> wrote: > > > >> When jrun is doing the 100% thing, look at the currently running > >> requests > >> in > >> fusion-reactor. > >> How many are there? > >> How long have they been running? > >> What are they doing? (stack trace) > >> > >> I'm more familiar with seefusion than reactor, but the stack trace > >> has the > >> stuff you are the most about on the top. It should give you the cf > >> file > >> being executed and the line number. > >> It sounds like you might have an endless loop or something. > >> > >> ~Brad > >> > >> ----- Original Message ----- > >> From: "Philip Kaplan" <[EMAIL PROTECTED]> > >> To: "cf-talk" <cf-talk@houseoffusion.com> > >> Sent: Wednesday, December 03, 2008 12:07 AM > >> Subject: Why is my CF8 server constantly hanging? > >> > >> > >>> Hi, > >>> I give up. > >>> > >> > >> > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:316148 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
