The bug manifests itself only on Linux and Solaris platforms when you install ColdFusion and then Updater 2 without starting ColdFusion and going to the Administrator between the two steps. If you do not go to the Administrator between the steps, all requests for CFM pages (whether you use Apache or the default web server) will come back as 404s.
If you are installing CFMX on Linux or Solaris from scratch, you must do so in this order:
- Install ColdFusion MX.
- Load the Administrator. (Log in for good measure.)
- Install updater 2.
- Install Apache 1.3.27 or 2.0.43.
- To configure CFMX to work with Apache, start ColdFusion MX (/opt/coldfusionmx/bin/coldfusion start) and run the wsconfig program to install the Apache connector. The command should look something like this:
/opt/coldfusionmx/jre/bin/java -jar \ /opt/coldfusionmx/runtime/lib/wsconfig.jar -ws apache \ -dir /usr/local/apache/conf -a -bin \ /usr/local/apache/bin/httpd -script /usr/local/apache/bin/apachectl -v
I’m not sure if it’s simply starting the server between installs, loading a single CFM page, or specifically loading the Administrator, but it works if you load the Administrator, so I would stick with what works for now. Macromedia is aware of the bug and is able to reproduce it, which is the first step toward fixing it.
Please let me know if you have any additional information regarding this problem.