<cfdocument> hanging

Report · Apr 22, 2008

I'm having a problem with <cfdocument> hanging and eventually timing out on one of my servers. The server is running CF 7,0,2,142559 Enterprise version with the latest hot fixes. The JVM is Sun 1.4.2_11. I've been through many of the ssl/https issues with <cfdocument>, but this seems to be something different. I've stripped the code down to the following:

<cfdocument format="PDF"><html><head><title>test</title></head><body>test</body></html></cfdocument>

Still doesn't work on an http site on this one server, but works on the three other similarly configured servers that I've tried it on. Thanks in advance for any suggestions.

Report · Apr 22, 2008

More info...

The real problem is with a server that I want to use for load balancing with an existing production server. Both are Win2k.

Server A has been running in production for a while. I recently changed the user account under which CF runs -- was using a local account, but switched to a domain account to facilitate sharing resources between the two servers. The local account that I had been using was in the Administrators group for Server A. To make the switch, all I had to do was add the domain account to the administrators group, change the "login as" for the CF service to the domain account, and restart CF. Everything worked, including calls to <cfdocument>.

Server B had been a staging server that I'm now setting up for load balancing in production with Server A. I can't say for sure whether <cfdocument> ever worked on this server. I upgraded the CF installation from version 7.0.1 to 7.0.2, and while I was at it installed the latest CF cumulative hot fix and upgraded the JVM to Sun 1.4.2_11 (Server A is running 7.0.2 without hot fixes and Sun 1.4.2_09). I added the domain account to the Administrators group, set it as the "login as" for the CF service, and restarted CF. Everything seems to work, EXCEPT calls to <cfdocument>, including the most simple:

<cfdocument format="pdf"><html><head><title>test</title></head><body>test</body></html></cfdocument>

The first request times out (30 seconds set in CF Admin) and I get the error message: "The document has no pages." Subsequent requests don't even time out -- the threads just hang ad infinitum.

Report · Apr 23, 2008

More info...

Whether or not <cfdocument> works seems to depend on how I start CF. I tried starting using the command line (.../CFusionMX7/bin>cfstart) so that I could get a thread dump -- in this case, the simple <cfdocument> example worked. Now I'm really not sure where to turn.

Report · Apr 23, 2008

This seems to summarize the current problem I'm having with <cfdocument> on one particular server:

I've taken out all of the potential image/stylesheet/ssl issues by putting a cfm in an unsecured website on the server with the following code:

<cfdocument format="pdf">
<html><head><title>test</title></head><body>test</body></html>
</cfdocument>

Server is Win2k running CF 7,0,2,142559 Enterprise with latest cumulative hot fix (chf7020003.jar) in single server configuration. (Although the same was happening before upgrading from CF 7.0.1 .)

After a reboot with the CF service set to start automatically, everything runs fine including <cfdocument>. After restarting the CF service, everything runs fine EXCEPT all calls to <cfdocument>. The first call to <cfdocument> times out after 30 seconds (default timeout set in CF Admin) and I get a "Document has no pages" error in my browser. Subsequent calls to <cfdocument> don't timeout -- they just hang.

I've tried running the CF service under different user accounts including "Local System" -- all have the same problem. I've tried setting the CF service to start manually -- after reboot, <cfdocument> doesn't work even on the initial manual start of the CF service.

I thought that I would start CF from the command line (i.e., using ...CFusionMX7/bin>cfstart) so that I could get a thread dump. When CF is started from the command line instead of as a service <cfdocument> works just fine.

I have other servers that (I believe) have identical configurations where <cfdocument> is running fine.

Any ideas? Does anyone from Adobe monitor these forums?

Report · Apr 23, 2008

mgkelly wrote:
>
> Any ideas? Does anyone from Adobe monitor these forums?
>

These forums are only for user-to-user support. They are not for
official Adobe support, though individual Adobe personnel do
occasionally make an appearance.

Search the knowledge base, there is a document that spells out exactly
what permissions a user account must have for CF to properly function.
What you are describing sounds like something, somewhere maybe locked
down in a manner that prevents CF from executing the <cfdocument...> tag.

My best guess anyway.

Report · Apr 23, 2008

Yeah, I had seen this article: http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_17279 . I thought this was the answer because <cfdocument> was working after I rebooted... but then it stopped working again after I restarted the CF service. It really seems to have to do with how CF is started -- command line is OK, automatic service start on reboot is OK, manual service start is no good. Thanks anyway!