ColdFusion 8.0.1 Kills our Apache

Report · Jan 12, 2009

We just installed ColdFusion 801 64bit on a brand new Solaris server.
The install did not properly configure the Apache web server to connect
to ColdFusion. When we manually ran the wsconfig tool, the connection
is made but then Apache will no longer serve up any content, ColdFusion,
HTML or plain text. If we stop the JRun4 cfusion server, Apache starts
serving up standard content. Of course it no longer serves up
ColdFusion files.

We can not find anything out of the ordinary, but it just does not seem
to work. Anybody got any ideas on what we can do to track down and|or
resolve this problem?

Report · Jan 13, 2009

Ian Skinner wrote:
> We just installed ColdFusion 801 64bit on a brand new Solaris server.
> The install did not properly configure the Apache web server to connect
> to ColdFusion. When we manually ran the wsconfig tool, the connection
> is made but then Apache will no longer serve up any content, ColdFusion,
> HTML or plain text. If we stop the JRun4 cfusion server, Apache starts
> serving up standard content. Of course it no longer serves up
> ColdFusion files.
>
> We can not find anything out of the ordinary, but it just does not seem
> to work. Anybody got any ideas on what we can do to track down and|or
> resolve this problem?

What output/error do you get from apache when trying to access the
standard content ? Anything in apache log files ?

You can try setting Verbose to true in the apache jrun config:
"JRunConfig Verbose true"

--
Mack

Report · Jan 13, 2009

Mack wrote:
>
> What output/error do you get from apache when trying to access the
> standard content ? Anything in apache log files ?
>
> You can try setting Verbose to true in the apache jrun config:
> "JRunConfig Verbose true"
>

That was part of the problem the log files where not showing anything.
Apparently we had to manually compile the connector to work with our
Apache 2.0.63 version as apposed to the officially supported Apache
2.0.43 version.