Ben Nadel
On User Experience (UX) Design, JavaScript, ColdFusion, Node.js, Life, and Love.
I am the chief technical officer at InVision App, Inc - a prototyping and collaboration platform for designers, built by designers. I also rock out in JavaScript and ColdFusion 24x7.
Meanwhile on Twitter
Loading latest tweet...
Ben Nadel at the jQuery Conference 2010 (Boston, MA) with:

500 null : Mysterious ColdFusion Error

By Ben Nadel on
Tags: ColdFusion

When I first encountered the 500 null error it took many head-beating sessions to figure out what the hell was going on. The very nature of the 500 null error makes it hard to debug. This occurs (from what I can figure) when an error gets thrown so early in your application that nothing ever gets flushed to the browser. The "null" part of the error probably means that no data was received from the browser.

In order to debug this error put a CFFlush tag right after your application declaration (Application.cfm) or somewhere very early in the code. Once you get the data stream going, you sort of let gravity take over (metaphorically speaking). Now, the 500 null error will be replaced with the CFError that is actually being thrown.

CAUTION: Once done, REMOVE THE CFFLUSH. The CFFlush tag will kill of your CFLocation tags as they work via page headers (which are not settable after data has been sent to the browser).

Tweet This Interesting post by @BenNadel - 500 null : Mysterious ColdFusion Error Thanks my man — you rock the party that rocks the body!


Reader Comments

Hi ben.
Question about 500 error. I have been fighting off hacking attempts from Netlynks technologies. They have been hacking my site installing (gumblers) viral Iframes. They bogged down my old server so bad godaddy changed my servers. Now that I have gotten through that. They have somehow caused this 500 error. I have nailed it down to the Cffile, I cant upoad photos. Any Ideas.

..... What would you charge to review this issue If i cant get it resolved, I dont want to feel like im bugging you with silly problems. but Im getting my butt kicked latley by hacks from netlynks. Do you encounter similar problems with host my site ?

Reply to this Comment

@James,

Maybe you don't have file-write permissions? Or the directory you are writing to doesn't exist. Did you try doing a CFFlush before you do anything else on the page that errors?

Reply to this Comment

I tried the flush cant get it to say anything. The recieving page could just be a simple message like hi with no form processing, just get the error. It's only when my form contains input type file field. And when I send it I get the jrun servlet error 500 on the recieving page. If i remove the input type file field. And send the form it works ? All this stuff worked a couple of days ago. Could this be another virus or attack - thx

Reply to this Comment

Wierd. I can upload the image file through the fcked editor. I dont get it. I cant upload a file with and input field but i can throught the editor........

Reply to this Comment

Back in motion, It wasnt me that was crazy ( at least not to crazy ). It was a problem with the server. They fixed it - I yaaaaaaaaa! !_! !_! !_!
im so smrt smart. Not really but I was begining to look like one of those angry little smilly faces. Thank you Ben ! your site rocks

Reply to this Comment

@James,

Awesome my man. Glad they got it working.

Crazy question, but is the phrase "I yaaaa" a reference to a park ranger on TV by any change?

Reply to this Comment

No but the (" im so smrt smart" ) is from the Simpsons ! the best tv show on the planet. O i might of forgot to say the problem abouve, as to not get of topic to much was related to their file/cffile upload tag. But its all good now !_! till we type again Ben.

Reply to this Comment

Ranger Danger! I thought he was only on my local area television (upstate NY). He's a radio DJ now on Q103 WQBK (103.5/103.9 Albany).

I was watching your jQuery "Intensive Exploration" screencast and saw the comment, couldn't resist.

Reply to this Comment

@Brendon,

Yeah, Rander Danger - that's the one I was referring to. My business partner, Clark Valberg, is from the Albany area (New Amsterdam) and showed me some Ranger Danger videos on YouTube. Since then, "Aiiyaaaaaaa" has become a staple of speech in our office.

Reply to this Comment

Ben,

I am a newbie to coldfusion. I am using <input type="file"> on the page and submitting it to a page where it uploads using cffile. I used "post" method.

Using Coldfusion 8 on IIS and Windows 2003.

On coldfusion server the maximum file size is set to 100MB. If I try to upload a file larger than 100MB,

it throws following error in IE8:
====================
This problem can be caused by a variety of issues, including:

Internet connectivity has been lost.
The website is temporarily unavailable.
The Domain Name Server (DNS) is not reachable.
The Domain Name Server (DNS) does not have a listing for the website's domain.
There might be a typing error in the address.
If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.

For offline users

You can still view subscribed feeds and some recently viewed webpages.
To view subscribed feeds

Click the Favorites Center button , click Feeds, and then click the feed you want to view.

To view recently visited webpages (might not work on all pages)

Click Tools , and then click Work Offline.
Click the Favorites Center button , click History, and then click the page you want to view.
------------------------------------------

In firefox it throws the following error:
=============

The connection was reset

The connection to the server was reset while the page was loading.
* The site could be temporarily unavailable or too busy. Try again in a few
moments.
* If you are unable to load any pages, check your computer's network
connection.
* If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.

---------------------------------------------

In Chrome:
==========
This webpage is not available.

The webpage at http://misredprdsw/includes/support/fpsupport/uploadFile.cfm might be temporarily down or it may have moved permanently to a new web address.

More information on this error
Below is the original error message

Error 103 (net::ERR_CONNECTION_ABORTED): Unknown error.
---------------------------------------------


Please help before they kick me out of here. People here are not so helpful and I tried everything, searched on google etc. No luck.

Thanks,
Nicky Pooh!!!

Reply to this Comment

If your uploading files that large I belive you FTP it not ( http it or file upload it ) !_!. - Can you set the timeout on the http to be Longer ? Your server will timeout if it takes to long to load my is limited at like 20 secounds. asspeacialy if your on a shared server.

Reply to this Comment

Thanks for reply James. No, I am not uploading using FTP. Just by usual form post.

On form page following is the code:
----------------------------------------------
<form action="upload.cfm" method="post" enctype="multipart/form-data">

<input type="file" name="myFile" accept="application/zip" />
<input type="submit" value="Upload file"/>

</form>
----------------------------------------------

On the upload.cfm page, following is the code:

----------------------------------------------
<cfset maxfilesize = 102400000>

<cfif val(cgi.content_length) gt maxfilesize>
<cfthrow detail="File size too large.">
<cfelse>
<cffile action="upload" fileField="file_name" destination="#Upload#" nameconflict="makeunique">
</cfif>
----------------------------------------------

That's it. This is all the code apart from cftry and cfcatch. And it doesn't even capture any error within the cftry cfcatch.

Also, for your information that might help to understand the problem, on coldfusion 8 server settings are:

----------------------------------------------
Maximum size of post data: 100 MB
Request Throttle Threshold: 4 MB
Request Throttle Memory: 400 MB
----------------------------------------------

It works well when I upload a file of size 99MB or less. But as soon as I put 100.5MB or 101MB or more, it crashes. For debugging purpose, I cfdumped form variables and cgi variables on top of upload.cfm. BUT, it doesn't show that dump. It instead throws the errors which I posted in my previous message above.

Please help!!

Thanks,
Nicky

Reply to this Comment

1. Is this on a shared host. They do have limitations. Mine seem to be 20 secs. You might have to chop the file up to send. and as you pointed out your limit is 100 mb -
-
just a guess, but im pretty sure a file that large would have to ftp'd

Reply to this Comment

It's nothing to do with the hosting. Yes the limitation of 100 MB is there because we do not want anyone to upload anything above 100MB through the http which I am using. Anything above 100MB, we give them a temporary FTP username and password. BUT, what I want is, it shouldn't disconnect from the website like it does. It should redirect to a page which is place. It doesn't even do that. It throws this error.

Reply to this Comment

It says your server settings are for 100mb max. Thats it, you can up load 99.5 not 100.1 your maxed out. Change your server settings. If you cause a server error you crash the server no redirect. you just get the error. I dont think it would redirect if you crashed it. What is the error ? 501 ?

Reply to this Comment

Why do I have to change the server settings? I know that 100 MB is max. And that's why I have a check on the top i.e.:

<cfset maxfilesize = 102400000>

<cfif val(cgi.content_length) gt maxfilesize>
<cfthrow detail="File size too large.">

This should trap the file size and throw error "File size too large" if someone tries to upload something larger than 100MB. It's not doing that. I have put the messages that I get on the browsers.

Reply to this Comment

Brendon & Lonnie,

Thanks for your comments which are pretty close and logical to my problem. Unfortunately, none of these helped me so far. This doesn't seem to be the problems that I'm facing or getting.

It's just weird. The process is logically simple. All I want is:

I don't want anyone to upload anything above 100MB. The Coldfusion 8 server has set Maximum size of post data limited to 100MB. And I am also checking on my submitted page (i.e. upload.cfm in my case), if the http.content length is less than 100 MB, upload the file or else throw an error. So logically it should throw an error as it is within cftry - cfcatch. But its not.

Also, the server isn't crashing at all. It's just that as soon as it goes to the submitted page (i.e. upload.cfm in my case), the connection kind of drops or get aborted or may be the server rejects the page. The upload.cfm doesn't get compiled. I put a <cfdump var="#form#"> <cfabort> on top of the upload.cfm. And it didn't show the cfdump results. And this is only when I try to upload anything above 100MB. Anything below 100 MB works PERFECT!!

Unfortunately none of these silly browsers throw a http status code. It just gives those above mentioned messages which doesn't make any sense.

It's stressing me out. What a stupid problem!!

Reply to this Comment

Jody,

Thanks for the link. I'm doing pretty much the same to what is explained on the blog you mentioned above. Ben is doing a little different way.

BUT, today I checked it on IE6 just to see if it works on any other browser. To my surprise it throws a 500 error on IE6 which explains a bit more than other browsers. I already have a Page set on IIS for 500. Unfortunately, this page is not hit at all. It simply throws error.

Following is the ugly IE6 error:

500
ROOT CAUSE:
coldfusion.filter.RequestThrottleFilter$PostSizeLimitExceededException: Post Size exceeds the maximum limit.
at coldfusion.filter.RequestThrottleFilter.invoke(RequestThrottleFilter.java:112)
at coldfusion.CfmServlet.service(CfmServlet.java:175)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)
at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

javax.servlet.ServletException: ROOT CAUSE:
coldfusion.filter.RequestThrottleFilter$PostSizeLimitExceededException: Post Size exceeds the maximum limit.
at coldfusion.filter.RequestThrottleFilter.invoke(RequestThrottleFilter.java:112)
at coldfusion.CfmServlet.service(CfmServlet.java:175)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)
at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:70)
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)
at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

Thanks,
Nicky

Reply to this Comment

Jody,

Thanks for the link. I'm doing pretty much the same to what is explained on the blog you mentioned above. Ben is doing a little different way.

BUT, today I checked it on IE6 just to see if it works on any other browser. To my surprise it throws a 500 error on IE6 which explains a bit more than other browsers. I already have a Page set on IIS for 500. Unfortunately, this page is not hit at all. It simply throws error.

Following is the ugly IE6 error:

500
ROOT CAUSE:
coldfusion.filter.RequestThrottleFilter$PostSizeLimitExceededException: Post Size exceeds the maximum limit.
at coldfusion.filter.RequestThrottleFilter.invoke(RequestThrottleFilter.java:112)
at coldfusion.CfmServlet.service(CfmServlet.java:175)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)
at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

javax.servlet.ServletException: ROOT CAUSE:
coldfusion.filter.RequestThrottleFilter$PostSizeLimitExceededException: Post Size exceeds the maximum limit.
at coldfusion.filter.RequestThrottleFilter.invoke(RequestThrottleFilter.java:112)
at coldfusion.CfmServlet.service(CfmServlet.java:175)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)
at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:70)
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)
at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

Thanks,
Nicky

Reply to this Comment

Just like i said above change your server settings.
---coldfusion.filter.RequestThrottleFilter$PostSizeLimitExceededException: Post Size exceeds the maximum limit.---

change limit. If you are on shared server you cant.

Reply to this Comment

@Nicky,

Yeah, looks like the ColdFusion server is throwing an error because you are exceeding the allowable file size.

I think the crucial point that might not be communicated well is that you can ONLY check the content length *after* the file has already been uploaded, NOT before. I am not sure if there was any confusion on this point (I know I have fallen into that misconception myself before).

As such, even if you do file-size checking on the server, if the file is too big to be allowed by the server, your file checking will not be executed as the exception is thrown farther above in the request processing.

Reply to this Comment

Hi Ben!!

Finally you're here. Good to hear from you.

That's exactly the problem is. My bad, I was unable to explain properly.

As we all know, we cannot check the file size without uploading. I already have a page in place which has graceful message on it. I set this page on IIS for 500 and sub codes of 500. Plus I also set this page in coldfusion server on "Site-wide Error Handler" under "error handlers" so that when a 500 message occurs, it spits out this page.

But NOPE. As soon as I click the submit button, it's giving that crappy browser message and that's freaking out non-technical people (clients) at work.

I am a BAD BAD programmer.

Now we do not want to change the server settings by allowing bigger size because that's not really the solution to this problem. Simply because even if I set it to 500 MB or 5000MB, trying to upload anything above this limit is going to give the same problem. Isn't it?

If you guys find any work around for this same issue, please let me know.

Thanks,
Nicky

Reply to this Comment

@Nicky,

Ha ha, yeah, been a bit behind on my responses.

So, are you saying that the end-user is *not* seeing your "pretty" fail page for large files?

Reply to this Comment

That is correct. It's not showing my graceful "pretty" page. It's showing the ugly 500 message if on IE6 or other messages if on different browsers as said above in my first message.

Although, on the address bar of the browser it does show upload.cfm. I put <cfdump var="#form#"> on the very first line of upload.cfm, but it doesn't show the dump either.

I know that it uploads the file to a temp location/memory and then it gets copied to the location we give in <cffile>.

So I think it's breaking right before compiling the upload.cfm and after posting the form.

Reply to this Comment

@Nicky,

Hmm, it's possible that the file size post is not handled in the context of an application. If it breaks before the Application.cfc is even run, then you might be out of luck.

To test this, you can try putting a CFDump / CFAbort in the very top of the Application.cfc file. Something like:

<cfif structKeyExists( FORM, "your_file_field" )>

<cfsetting requesttimeout="1500" />
... dump / abort

</cfif>

If that fails to run, then I think the error is occurring too high in the request processing.

The CFSetting tag is to make sure that the dump / abort have time to process if the upload is also causing a timeout.

Reply to this Comment

Hey Ben,

Sorry for replying so late. Got tied up with other things at work. I was able to convince at work that this is not my bad programming. It's their bad request ;). In fact, I should be considered as an expert because being a newbie, I was able to find a bug in Coldfusion. haha!

I tried what you mentioned above. Still the same problem. I also tried to put the <cfsetting requesttimeout="2500" /> on top of every page that was associated in the process. Nope, it just likes to crash.

It's definitely a technical bug; either in IIS or Coldfusion server end.

I think it's something on IIS end because it crashed and did not execute the application.cfm. So IIS is totally rejecting the request and not even throwing out a graceful page.

Have you tried it on your setup and see if it works for you?

Thanks for all your help Ben; and also all those who tried to help.

Please let me know if anyone finds a break through for this bugger bug.

Kind Regards,
Nicky

Reply to this Comment

Is there a way to prevent this type of error from appearing on-screen? I've turn off robust debugging but it still appears on-screen.

Reply to this Comment

@John

Well you can create a onError in your Application.cfc like so

<cffunction name="onError" output="yes">
<!--- FUN ERROR CATCHING STUFF GOES HERE --->

I'm sorry, it seems that an error has occurred. But don't worry we have a team of monkeys hard at work trying to correct the issue. -- Check back again soon, or click here to see if the problem was fixed.

</cffunction>

You don't have to use that paragraph but you would add your code for example getting submitted variables, getting the full url so you can try to recreate the same issue, and have it mail the error to your email.

NEVER EVER EVER STORE ERROR MESSAGES IN A DATABASE WITHOUT HAVING ONE SENT TO A LOG FILE, OR AN EMAIL! -- I learned the hard way.

Reply to this Comment

Hi Ben,

Nope. Nothing so far. It definitely looks like a bug or lack of some settings somewhere on our servers. We have escalated the issue to adobe and waiting for their response.

Anything at your end please?

Happy 2010!!! :)

Reply to this Comment

@Jody,

I finally got around to trying the suggested solution and it didn't seem to resolve the issue. It almost appears that this type of error is triggered before application.cfc has a chance to catch the error.

Reply to this Comment

@John,

That's what I am thinking - it's happening at the application server level, not the application code level.

Reply to this Comment

Another of Error: 500 case! we have our weblogic with CF application deployed on an intranet server. The same server is mapped to the internet via some extranet link. The application works great on intranet, but sometimes when accessed from the extranet "Error: 500 internal server error" comes up! Location :fb4\index.cfm

CF 8 with fusebox 4.1...

checked already the below:
1. webserver logs - no mention about this error at all
2. checked if some error reported in coldfusion server monitor - no error.
3. Cfflush in the fb4\onrequestend.cfm - Does not seem to be of good use.
4. Debugging ON in CF admin - i don't get any
message other than 500 on FF and IE

Any thoughts to go about this error?

Reply to this Comment

@Pradeep,

That's really weird. Is it an error that you can reliably reproduce? Or does it happen occasionally?

Reply to this Comment

@Ben,

Occasionally it occurs .. it ain't reproducible...

no specific module also, only clue i get is that this happens when accessed via internet.

Reply to this Comment

@Pradeep,

That's rough; when you can reproduce an error, it can be near impossible to debug. This is especially true when there's nothing in the log files.

Do you have any error handler - onError() / CFError - that mails you any errors?

Reply to this Comment

@Ben,

It seems like the 500 error got solved !!! i was not involved in it. The solution i heard was to enable "Keep Alive" in the HTTP settings of the weblogic server.

Reply to this Comment

@Pradeep,

Interesting. I don't know much about the keep alive in HTTP settings. I've used that in database sources (I think). Any idea what it does?

Reply to this Comment

In my website iframes are using to load customer records page by page as hyperlinks. So, in these pages any error occurs the site wide error handler page doesn't gets loaded and the IFRAME src as 'blank'. So user can't show the proper message.

Reply to this Comment

Well, this is an antique topic but as I know many with the same related problem will land here, this is kind a "message in a bottle" for you guys.

I'm running CF9.1 on a Win2003/IIS6 server.
Over a certain amount of MB (27 or such in my case), I was experiencing the infamous HTTP 404 error with no details nor log anywhere.

Story short: this is NOT a IIS bug or something you trick with the various ASP tips you can find while searching the web. If you use MS URLScan in your IIS (there's a LOT of chance you do, even if you don't even know what it is), then there's a limit (in Bytes) you must edit.

"If you are using Microsoft URLScan, there is a file size limit in its configuration as well. To make changes to that, you need to edit the file "UrlScan.ini" located (typically) at: C:\WINDOWS\system32\inetsrv\urlscan and change the value for "MaxAllowedContentLength" to your desired max file size value. "

Thanks to this page, I woke up from my nightmare; kudos to the authors :
ajaxuploader.com/large-file-upload-iis-debug.htm

Reply to this Comment

@Antoine,

My issue was resolved by increasing values of "postSizeLimit" and "postParametersLimit" in ColdFusion9\lib\neo-runtime.xml.

@Ben - for some reason the solution by PradeepVizz to enable Keep alive setting did not work for me.

Nicky!!

Reply to this Comment

@Nicky : Nice !!! but none of the workaround I applied worked for me prior to this technique, so that I believe it's IIS6 (with URLScan enabled) specific and it may help some users. (Note that URLScan restrictions applies before any CF action)

Reply to this Comment

Post A Comment

You — Get Out Of My Dreams, Get Into My Comments
Live in the Now
Oops!
Comment Etiquette: Please do not post spam. Please keep the comments on-topic. Please do not post unrelated questions or large chunks of code. And, above all, please be nice to each other - we're trying to have a good conversation here.