Issue is with pipe and filter approach the only info you get in the log is Index.cfm to 72 seconds to run.
Which doesn't tell you what circuit/fuse was causing the issue. Anyone got a work around? g -----Original Message----- From: Sean Corfield [mailto:[EMAIL PROTECTED] Sent: Friday, November 11, 2005 9:03 PM To: Fusebox Subject: Re: Debugging On 11/11/05, Mark Kecko <[EMAIL PROTECTED]> wrote: > I wrote a FB4.1 app that has worked fine for about 6 months. Recently > something was introduced or something changed that's causing jrun > errors on the site. Something happens that causes the FB runtime file > to start taking a long time, 500ms or so, then requests start queueing > up, then jrun error. I'd start by enabling all the verbose GC options on jvm.args and enabling monitoring in the JRun logs so you can get a sense of what the memory / session usage is when the problem manifests. I'd also enable the log slow pages option in the CF Admin (log everything taking over 1 second perhaps). That might at least give you a little bit more information about patterns of usage around the time of failure. -- Sean A Corfield -- http://corfield.org/ Got frameworks? "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:12:6854 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/12 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:12 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.12 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
