ColdFusion 8.01 on Windows - should I go 64 bit?

I'm in the process of specifying a new web server, which will be running ColdFusion 8.01 Enterprise (as well as IIS etc.).

The server will be running ~6 active instances of ColdFusion - and will initially be configured with 4GB RAM - with the option of upgrading in the future as required.

We will be using Windows 2003 Enterprise as the operating system.

What will the benefits and downsides be of going for the x64 OS compared with the x32 OS, taking the following into consideration:

  • The system will only be used as web application server
  • The system will initially be set up with 4GB RAM - and will never have more than 8GB.
  • The high number of instances of CF mean that if we did set the JVM Heap size over the ~1200 MB x32 limit, then we'd run a distinct possibility of running out of memory. (The reason for having so many instances of CF is to enable separation of CF Mail queues - 2 of the instances don't get any front end traffic at all, and are just responsible for sending out large batches of email)

Any advice would be appreciated...

What is wrong with Internet Explorer?

I'm currently in the process of setting up a new development machine with all the software I need (Oh what fun!)

I was working may way through my list of essentials (about 90 items and counting!) - installing from disk for stuff on disk, and downloading the most recent versions of apps available on line.

Shortly after installing MS-Office (and running MS Update and rebooting), I tried to download iTunes... I.E. crashed as soon as I had clicked the save to disk button.  I tried again... I.E. crashed again.  So I thought - lets download FireFox and use that instead... I.E. crashed again.

[More]

Beware Windows 2003 SP2 (Especially if using DTC)

If you are using Distributed Transaction Co-ordinator to manage MS SQL server cross-server transactions across machines which are not in the same domain, be careful when installing Windows 2003 SP2.

To enable cross domain SQL transactions using DTC, it is necessary to drop the required security from "Mutual Authentication Required" to "No Authentication Required".

Quite helpfully, installing Windows 2003 SP2 will cause the security settings for DTC to be reset to the default - "Mutual Authentication Required" - preventing Distributed transactions from occuring.

SQL server will give a really helpul message along the lines of "Unable to enlist in transaction" (which is the same message you get if there are any network issues between the 2 servers).

Only took me 5.5 hours to spot what the issue was - Thanks Microsoft :P

BlogCFC was created by Raymond Camden. This blog is running version 5.5.1, hosted by TalkWebSolutions.