As we all know, Coldfusion MX7 does not have native support for 64-Bit OSes, which is really my only real gripe about the app server. It will run on 64-bit systems in 32-bit mode, with a 32-bit JVM. It's a pretty straightforward install on the windows platform - the only gotcha there is that one must enable 32-bit compatibility in IIS:
cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 true
(
Microsoft's Info Here)
But there are few more things to be dealt with when running cfmx in a 64-bit linux enviro:
1. IPv6. The Apache connector configuration fails to find a running JRun server in most SuSe Linux installations. The SuSE 9.x default installation configures IPv6. The connector installer is incompatible with IPv6. To avoid this issue, you should inspect and, if necessary, change the configuration to IPv4 before configuring the Apache connector. To do so, comment out the feature in the appropriate .conf file as follows, and restart the operating system.
On SuSE 9.0:
/etc/modules.conf
#alias net-pf-10 ipv6
On SuSE 9.1-9.3:
/etc/modprobe.conf
#alias net-pf-10 ipv6.
NOTE:
You need to also edit the /etc/hosts file to remove IPv6 from localhost
You want to be sure that /etc/hosts registers "localhost" using the old-fashioned IPv4 numbers, not as a new IPv6 number.
If "localhost" is defined both ways, the IPv6 way will take precedence - and possibly mess up Verity access.
If you find a line in /etc/hosts like this:
::1 localhost ipv6-localhost ipv6-loopback
you should comment it out with a #, or at least remove the "localhost" name from the list.
There should already be a line in /etc/hosts like this to define the IPv4 address:
127.0.0.1 localhost linux.site linux
2.For RedHat 3.0 and SuSE users, ensure that the "Legacy Software Applications" (RedHat) or "Compat" (SuSE) package is installed; this installs the correct compat-∗ libraries to run the connector. If it isn't installed, the Apache connector hangs.
rpm -q libstdc++
rpm -q glibc (If glibc 2.2.5.x or higher, this compatibility package is required.)
To avoid this issue, you can also recompile the connector:
∗ Edit the cfmx-connector.sh file if you are installing the multiserver edition, or the apache-connector.sh file if you are installing the server configuration and add the -apxs switch. Run the script to install and compile the connector.
∗ Select the [Advanced] options / [Build Apache module from source...] check box in the Web Server Configuration Tool (wsconfig.jar).
All compile options require GNU Compiler Collection (GCC).
The following Novell SuSE Linux versions may be affected:
∗SuSE Linux Enterprise Server 8
∗SuSE 8.1 (2.4.19 kernel)
∗SuSE 7.3 (2.4.10 kernel)
∗SuSE 9.x
Note: SuSE Pro versions require Apache 2.0 and GCC Red Het Package Manager (RPM) to compile the connector.
3. Finally, the 64 bit version requires that the mod_jrun shared object be built on the server, in order to do this, the apache-devel packages must be installed. additionally, there is a bug in the build script that tries to compile the module - for apache2, the apxs utility that gets installed is actually called apxs2, but the build scripts call apxs, that means you need to create a sym link in /usr/sbin/ to create an alias to apxs2 called apxs.
in order to tell the installer to build the module, you need to edit the file /opt/coldfusionmx7/bin/cfmx-connectors.sh and add -apxs switch to the command line call to wsconfig.jar - NOT the apache-connector.sh file as referenced in the tech note. also, you must comment out a section in both the connector script and the coldfusion script:
#if [ ! "$SUSEFLAG" ]; then
#LD_ASSUME_KERNEL=2.2.9
#export LD_ASSUME_KERNEL
#fi
once the connector is installed, you then need to stop and start apache2
