We ran into this issue as well on a production box and it turned out to be the 
CF server monitor, specifically the memory tracker, that was hosing up 
everything!  We stopped it and the timeouts stopped.

 

From: [email protected] 
[mailto:[email protected]] On Behalf Of Peter J. Farrell
Sent: Friday, August 28, 2009 4:46 AM
To: [email protected]
Subject: [Mach-II] Re: The request has exceeded the allowable time limit 
Tag"error

 

FYI,

If you have "Timeout Requests After" on the "Settings" page turned on and set 
too low, CF will kill the request.  The default is 15 seconds I think and for 
some applications that is too low if you have some long requests (usually 
because of DB operations).  I wouldn't uncheck the option because no request 
will timeout ever, but set to something like 60 seconds instead.

The logging code you mentioned Prashant is called VERY frequently throughout 
the request.  So it's not that code that is causing the problem -- it's just 
really likely for CF think it's that place because it killed the request in 
that code block.

.pjf

prashant roy said the following on 08/28/2009 03:11 AM: 

hi, 

I remember, i was having same error at the time of loading mach-ii in DEV 
server. after CF restart, it was good. 
We came across same error again on production, and then we have commented some 
cfloop code in log.cfc and it solved the problem. 
I know that was not so good solution but i remember we have done that at that 
time.  just as a note, it was occurring after mach-ii reload. 

-prashant roy



On 28/08/2009, Peter J. Farrell <[email protected]> wrote: 

You're request timeout is too low when the framework is loading. What is it set 
to in the CFIDE? For dev, you should turn it off on the request settings page.

jarthel said the following on 08/28/2009 01:17 AM: 

Apologies for the short replies.
 
+++++++++++++++
 
the problem can happen at any time.
 
logging to the system. error. If I try again and again, it'll work in
the end.
 
Clicking on a link (retrieves single record from multiple tables), the
 
error will happen. The only workaround is to click on the link again.
 
Here's a screenshot of the exception: http://tinyurl.com/nylpu7
 
 
Thanks again.
 
On Aug 28, 2:40 pm, "Peter J. Farrell"  <mailto:[email protected]> 
<[email protected]> wrote:
  

It's very unclear when this exception is occurring.  Can you elaborate
when / how this is occurring (details)? Your questions tend to be short
with little additional information -- adding more details will
 
definitely give you better answers.
 
jarthel said the following on 08/28/2009 12:26 AM:
 
    

I'm using mach2, coldspring and transfer.
      

Could this be the cause? thanks again :)
      

  






 




-- 
Prashant Roy







__________ Information from ESET NOD32 Antivirus, version of virus signature 
database 4375 (20090827) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


__________ Information from ESET NOD32 Antivirus, version of virus signature 
database 4377 (20090828) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 


--~--~---------~--~----~------------~-------~--~----~
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://greatbiztoolsllc.svn.cvsdude.com/mach-ii/
Wiki / Documentation / Tickets: 
http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/
-~----------~----~----~----~------~----~------~--~---

Reply via email to