Skip to main content
Inspiring
March 25, 2008
Question

I'm stumped - CF8 stops rendering mid-page

  • March 25, 2008
  • 5 replies
  • 424 views
Now THIS is a stumper! I don't think anyone's seen this.

I'm using CF8 Developer on a Windows XP Pro SP2 rig (using the Admin Pack so I have IIS 6 rather than 5.1) Anyways, this problem does not happen on ANY PAGE except Coldfusion Markup. What happens is, randomly, CF8 will either render the complete page (as expected) or it'll stop some random point within the page. Here's some other facts.

Problem happens in Firefox 2.0.0.12 AND MSIE 6/7, so it seems independent of the browser.
The EXACT SAME source code can be taken to my work PC (WinXP Pro SP2 w/ IIS6) and it will work FLAWLESSLY, serving the page completely each refresh.
I have fully uninstalled and reinstalled CF8 twice, and the same problem exists.
I AM utilizing my own form of SES for clean URLs that basically parses the 404; http://localhost/file.cfm value that CF catches and reparsing it to build the page, but again, this works flawlessly on my work PC.
I have flushed out the cache on the browsers and still have the problem.
Problem DOES NOT exist when I load .html, .asp or any other type of file. Those pages render completely each time (making me think it isn't IIS' fault either)

When I view an incomplete page, sure enough it'll have stopped randomly in some code, like:

<a href="this/that/file.cfm" titl

That's it... nothing more...

This is driving me BATTY. I left Vistax64 because of (among other things), the lack of Coldfusion support, and now that I get back I CAN'T DO MY CODING! :(

My PC's stats (if they'd have anything to do with it) are Q6600, 4GB, 890GB of HDD space. I really hope you guys have some ideas or have seen this before.
    This topic has been closed for replies.

    5 replies

    Inspiring
    March 27, 2008
    For the life of me, I cannot figure out how to test it on the JRun server. Never had any experience using that - all previous installations of Coldfusion 8 always worked flawlessly until now.
    Inspiring
    March 26, 2008
    > I'll know that it's not CF, but IIS and
    > it's handling of the request.

    Well it could still be the data that CF sends back to IIS. I'm not sure
    how best to troubleshoot this sort of thing.


    > I'm not familiar with how to use the JRun web server. Do I just navigate to
    > the same location but pop in the 8500 port? ie:
    >
    > http://localhost:8500/mywebsite/file

    By default, that's the port, yes. I run the multi-server install of CF,
    and for that, the file to check for the port is [Jrun]/servers/[insatnce
    name]/SERVER-INF/jrun.xml. I've not used the standard install for about
    five years, so dunno where to look for it in that. But the node to look
    for in whatever file it is is:

    <service class="jrun.servlet.http.WebService" name="WebService">
    <attribute name="port">8302</attribute>

    You'll have to check the [cfusion]/WEB-INF/jrun-web.xml to see if you need
    to create any virtual directories and that sort of thing.

    --
    Adam
    Inspiring
    March 25, 2008
    Ok, here's what happened:

    I loaded up the cyan page, loaded fine. loaded the blue page, loaded fine, loaded the green page, errored out.

    It seems now because the .CFM processing doesn't work, I cannot even get into the CFAdministrator to view the logs. So I just opened the log file and here's its contents:

    "Severity","ThreadID","Date","Time","Application","Message"
    "Information","jrpp-1","03/25/08","19:22:35",,"C:\ColdFusion8\logs\aaronmartonecom.log initialized"
    "Information","jrpp-1","03/25/08","19:22:35","APPAARONMARTONECOM","cyan loaded successfully."
    "Information","jrpp-1","03/25/08","19:22:57","APPAARONMARTONECOM","blue loaded successfully."
    "Information","jrpp-2","03/25/08","19:22:58","APPAARONMARTONECOM","green loaded successfully."

    As you can see, it looks like green loaded. So does this confirm that the problem is IIS and not CF? If so I guess I got to go to another forum...
    Inspiring
    March 25, 2008
    That's a unique way of seeing it.

    When I get home today I will do that. I'll add an onRequestEnd to my app.cfc and then have it create a log that'll say which page color (I keep a REQUEST scope variable holding the name of a color theme, depending where the user is)

    So if I understand you correctly, CF will be at fault here if the onRequestEnd did not fire off on a page that errored. I could load the blue page, and it works fine, I'll have an entry in the log saying "Blue loaded.", I could go to the green page and it'll load fine and it'll add another entry saying "Green loaded", and then go back to the blue page and it fails to load, and if I see another (the latest) "Blue loaded", I'll know that it's not CF, but IIS and it's handling of the request.

    I looked through the IIS logs, and the majority of HTTP status codes returned are 304 , with an occasional 200 and 302 in there.

    I'm not familiar with how to use the JRun web server. Do I just navigate to the same location but pop in the 8500 port? ie:

    http://localhost:8500/mywebsite/file
    Inspiring
    March 25, 2008
    In your OnRequestEnd.cfm (or Application.cfc equivalent), write something
    to a log file as the last thing you do. Replicate the error situation,
    then check the log. If the entry is there (I suspect it will be), then the
    problem could lie not with CF processing the request, but with its return
    of the result to the web server, or the web server returning the result to
    the browser.

    What happens if you use the inbuilt JRun web server instead of IIS in these
    situations? Same thing?

    --
    Adam