Ed,
* Which version of Mach-II are you running? Sort of important for us to
know.
It's probably not a framework issue. Adobe CF tends to point to strange
code if a request times out. Usually it's a red herring.
* First, I'd look at this FAQ:
http://trac.mach-ii.com/machii/wiki/FAQWhySlow
I've seen problems like this when somebody accidentally leaves CF
debugging on (it runs on all requests even if you don't see output if
checked) or has the server monitor on some where.
* What's calling setArgs()?
It could be an bad loop (like <cfloop condition="#something#"> where
something always evaluates to true).
* Are you using scheduled tasks?
If it is coming in bunches, then it could be a scheduled task that is
holding things up. Especially tasks that use <cflocks>
* It could be deadlock issue with locks...
* Are you deploying changes to production and restarting the application
manually?
It could be that requests are piling up as an application gets
restarted. This is especially true if you are using an query string
parameter and calling LoadFramework() manually in your Application.cfc.
Reloading from the Dashboard uses a different technique (or optionally
in 1.9 we are adding a new method to do that called `reloadConfig()`
which uses the same process as the Dashboard).
* You might consider adding an onError() method to your Application.cfc
so you can log more information like the name of the event and incoming
parameters etc. You only about 30ms if the request is timed out to do
stuff, but you can extend the request execution by using an CF admin CFC
method so you can do more like send an email (let me know if need the
code to extend the timeout).
* Check your DB queries. Could be a long running query. Maybe somebody
dropped an index and didn't re-add it or something.
HTH,
.Peter
szwedo...@epamail.epa.gov said the following on 05/05/10 13:12:
Our production server has been slow off and on for the last few days.
Checking the server log showed some requests taking on the order of 300
seconds. Changed a server setting: checked the box that says "Timeout
Requests after (seconds): [tried 60 and 90]. Got a bunch of errors
after changing the setting, saying that the particular thread exceeded
the 60 second warning. The errors all come in bunches, e.g. 10 during
the same minute. Since we changed the administrator setting, the errors
all point to a<CFLOOP> statement in the setArgs function of
Machii/Framework/event.cfc.
I would like to know if the cause is one of our apps or some outside
event. We've been running machii for a few years now. The errors show
up in several of our apps, all pointing to the machii setArgs function.
These are all apps that have been running successfully for years.
How can I find out what is causing the slowdowns? Can anyone recommend
any tools? Any suggestions?
Thanks
______________________________________________________________________
Ed Szwedo
Web Development Team Lead
ECS Team - ITS-EPA II Contractor
109 TW Alexander Drive, Building NCC, Mail Drop N176-05, Research
Triangle Park, NC 27711
Information Technology Infrastructure Solutions | Office: (919)541-3955
| Fax: (919)541-3641 | szwedo...@epa.gov | www.ecs-federal.com
--
You received this message because you are subscribed to Mach-II for CFML list.
To post to this group, send email to mach-ii-for-coldfusion@googlegroups.com
To unsubscribe from this group, send email to
mach-ii-for-coldfusion-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/mach-ii-for-coldfusion?hl=en
***New URLs as of April 29th, 2010***
SVN: http://svn.mach-ii.com/machii/
Wiki / Documentation / Tickets: http://trac.mach-ii.com/machii/
