Hi Bill This is a very generic error message. I've been caught out by it before. The timeout is probably actually occuring a few line prior to where CF tells you or somewhere else entirely. Charlie Arehart has recently blogged about it here which saves me having to explain how to track down the culprit http://www.carehart.org/blog/client/index.cfm/2010/10/15/Lies_damned_lies_and_CF_timeouts/
Cheers Matthew On Nov 23, 8:29 am, [email protected] wrote: > Thank you for your reply Peter. > Didn't really think it was machii, but I thought I would throw it out > there to see what came back. > > Bill Peddy > Web Developer > ECS Team - ITS-EPA II - > Contractor > voice: (919) 541-1329 > fax: (919) 541-3700 > > |------------> > | From: | > |------------> > > >---------------------------------------------------------------------------------------------------------------------------------------| > |"Peter J. Farrell" <[email protected]> > | > > >---------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | To: | > |------------> > > >---------------------------------------------------------------------------------------------------------------------------------------| > |[email protected] > | > > >---------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | Date: | > |------------> > > >---------------------------------------------------------------------------------------------------------------------------------------| > |11/22/2010 01:16 PM > | > > >---------------------------------------------------------------------------------------------------------------------------------------| > |------------> > | Subject: | > |------------> > > >---------------------------------------------------------------------------------------------------------------------------------------| > |Re: [Mach-II] The request has exceeded the allowable time limit Tag: > CFLOOP | > > >---------------------------------------------------------------------------------------------------------------------------------------| > > [email protected] said the following on 11/22/2010 11:08 AM: > > > Hey guys, > > it has been a while since I have had to post a question/issue. > > We have been battling slow server and request time out issues here as > of > > late. > > I don't think it is related, but we did upgrade to 1.8 maybe four of > > five months back. > > > The issue seems to be occurring in this section of the event.cfc: > > > <cffunction name="setArgs" access="public" > returntype="void" > > output="false" > > hint="Sets a structure of args to the event > object."> > > <cfargument name="args" type="struct" > required="true" > > hint="A structure of args to > set." /> > > <cfset var key = "" /> > > > <cfloop collection="#arguments.args#" > item="key"> > > <cfset setArg(key, > > arguments.args > [key]) /> > > -----------> ******* This is line 180 *************** > > </cfloop> > > </cffunction> > > I hate to be the bring bad news, but request timeout errors are the most > > difficult to track down because the error reporting on ACF usually just > points to a line that doesn't make sense. This is because ACT only > checks of the request timeout is exceeded on certain tags (not all > tags). CFloop is one of them. The error you are seeing is that it > checked the request timeout at the end of the loop. The loop itself is > NOT causing the error. For example, your request timeout may be > something like 30 seconds. At the beginning of the loop, the request > time is 29.99 and therefore hasn't timed out. At the end of the loop, > it has timed out and CF reports the loop as the error. > > What you need to do is look for things that can cause the request to > take too much time: > > * queries > * web services / rest requests > * cfdocument > * cfimage > * cfpdf > * file operations > * cfmail operations > > We all "setArgs()" after you announce an event (internally). More than > likely -- something is causing the request to take a while and then you > are announcing another event. If you know the event name of the > request, you should be able to trace yourself through the code and see > if any of the "big" things I listed could be causing problems. In the > past, the hard I tracked down had to do with a slow SMTP server and > switching to spooling to disk instead of directly to the server fixed > the issue. > > Let us know what you figure out. Sadly, I wish I could say -- oh that's > > an issue with Mach-II, but alas -- there aren't any known issues with > request timeouts with Mach-II. They are almost always one of those > things I listed. > > .pjf > > -- > You received this message because you are subscribed to Mach-II for CFML > list. > To post to this group, send email to > [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group > athttp://groups.google.com/group/mach-ii-for-coldfusion?hl=en > > SVN:http://svn.mach-ii.com/machii/ > Wiki / Documentation / Tickets:http://trac.mach-ii.com/machii/ -- You received this message because you are subscribed to Mach-II for CFML list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en SVN: http://svn.mach-ii.com/machii/ Wiki / Documentation / Tickets: http://trac.mach-ii.com/machii/
