What could cause an ajax request (using cfajaxproxy) to hang?

I'm having really inconsistent results with cfajaxproxy, whereby it seems to sometimes hang and ultimately crash the browser. Below is an example template function, so that you can see what the remote functions i'm writing look like, although this does work in 99% of the cases i have one instance inwhich it just hangs indefinately. It is completely bizarre since the log output just before "when it should return" is written out (and so the code block's contents are irrelevant), but yet the browser does not seem to recognise or i suspect receive an end-of-transmission message from the browser. The contents of the code-block does however influence whether or not the function returns, even tho the log outputs IN ALL CASES the final log message WITHOUT then returning!?

My question is has anyone found this hanging problem, i know it's not related to the code being executed hanging since the final log messages are outputed, and it's not due to an error being thrown within the code block since any error should be caught and returned as a message response. The javascript is alerting() all response text in all cases.

Has anyone seen this, and can anyone suggest any reason for this apparent hanging?

BTW. Using firebug it tells me that the javascript is not responding, or waiting for a response, and points me to inside the loop in figure b) in the attached code. Is this not indicating that it's waiting for a response from the server? .. any why does it not receive it??

This problem has been driving me nuts so any help much appreciated!
a)
 
<CFFUNCTION name="performThis" access="remote" returnFormat="plain">
	<CFARGUMENT name="requestData" type="string">
	// code here
 
         <CFSET SESSION.log.debug("I am here")>
 
	<CFRETURN "OK">	
	<CFCATCH type="any">
                  <CFSET SESSION.log.debug("Some error")>
		<CFRETURN "Error-#cfcatch.message#">
	</CFCATCH>
	</CFTRY>
</CFFUNCTION>
 
b)
[CFIDE/scripts/ajax/package/cfajax.js -CF8]
 
$X.processResponse=function(req,_270){
	var _271=true;
	for(var i=0;i<req.responseText.length;i++){
		var c=req.responseText.charAt(i);
		_271=(c==" "||c=="\n"||c=="\t"||c=="\r");
		if(!_271){
			break;
		}
	}
... etc

Open in new window

LVL 1
paddycobbettAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

azadisaryevCommented:
really hard to say what may be wrong from just the code you posted...
but to rule out some possible issues:

1) after all <cfargument ..> tags in your function, add this:
<cfset var fResult = "OK">
1.1) make sure all variables you create in your function are properly var'd to rule out any variable substitution
2) get rid of <CFRETURN "OK"> line
3) change your <CFRETURN "Error-#cfcatch.message#"> line to:
<CFSET fResult = "Error-" & cfcatch.message>
4) add <cfreturn fResult> as the last line in your function, after your </CFTRY>

the 'hanging' of an ajax request is usually due to some code error, so it is likely that 1% of the time some condition is met that causes an error in your code to surface...

you can also try adding ?cfdebug to the url to enable ajax debugger - it may give you some info as to what is the problem...

if you care to post more of your code, including your code that calls your function, it may help us help you further.

hth
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
paddycobbettAuthor Commented:
Sure enough it did turn out to be related to application logic. It was that each ajax call as a side effect wrote out a large text file. What threw me off was that i wrote out a time stamp before and after the writing of the large text file, and the time difference was less than a second, and sure enough it was pretty instant the updating of the file since (having a text editor with the file opened) it notifyed me of a change to the file (that it had open) almost instantly. It appears to just hang after having written the file out (for up to 20 seconds!), although when i remove the writing out of the file sure enough the response time was verging instant. I thought that perhaps the now() function wasn't accurate, but surely it would update itself atleast after each few seconds!? Any ideas as to the cause of this bizarre inconsistency?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ColdFusion Language

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.