In the last rant about this, I speculated about how the problem may be related to Macromedia (instead of the OS) as I was unable to get it running properly on all manner of configurations (Mostly XP and Linux). Now, today I have become even more sure of this conclusion.

By messing around with the command line (in windows XP of all places), the problems with Cold Fusion MX 7 became much more obvious. Now I dont think I have to explain to any one how strange it is that the WinXP command line gave a better idea of the problem than Linux terminal window but it still happened like that.

Simply put, Macromedia ColdFusion MX & adds a “LoadModule” line to the httpd.conf file which calls the jrun_module. Seems simple, apache is driven by all these modules (see the Apache website for more) and the LoadModule line is the main part of it.

Sadly, when you run from the console in XP you see the error message. The “.so” file called by the module is trying something “unsupported” by Apache. This is causing all manner of fatal errors – most not showing up in the logs or the x-term windows. So it seems it is actually Macromedia’s fault. Looks like it is time to visit the reference documentation and see what I can learn.