As you can see, there's not much activity here anymore.

You can find more of Nat's wisdom at webapper.

Erik is now blogging at psykel.

Happy Trails, grumps

I lamented on the inability to run CFMX as a true 64-bit app, but felt haughty enough to overcome the problem.

Alas, I am giving up. The crux of the issue seems to be that although JRun will run with Java 1.5, it will not run with Java 1.5 on the AMD64 version.

We got a new dev server: dual Opteron, 4GB RAM, dual raid, etc. So far very happy; now I'm trying to install through-and-through 64-bit applications on it.

I have Windows Server 2003 64-bit installed, and planned to use IIS 6. Sun JVM (latest being 1.5.0_05) has an AMD64 version. But how can I run CF7 on it?

I found this mm.com article, this other mm.com article, this descriptive MM forums thread, some old threads on CF-Talk, and blog entries by Ben Forta, Steven Erat and Pete Frietag.

But it just seems too darn silly! Am I really going to have Tomcat or another Java/J2EE server to run CF7 as a war? Jrun 4 seems like older technology (although Jrun updater 5 does support Java 1.5).

Any advice from someone who has either tried and failed or tried and succeeded in getting an all 64-bit platform running? I want 64-bit hardware running a 64-bit OS, with a 64-bit JVM with IIS running in 64-bit mode (rather than IIS5 isolation mode), and 64-bit capable ColdFusion, if that means running a 64-bit capable Java server with CF on top.

I suppose this is just another example of Macromedia claiming that ColdFusion is enterprise-worthy when anyone, anywhere in any enterprise knows for god sakes that it sure as hell ain't.

You know how in ColdFusion, an array (and a struct) can take any type of variable as a member? For example, you can create an array named "mydates", then proceed to stick strings and booleans in it:

But what happens when you try #dateformat(mydates[2])#? It will blow up, that's what.

That is something that has always irked me about ColdFusion.

[More]

Everyone knows you're *supposed* to close() your db connections each and every time you open one in Java. The hard part is tracking down that one place where you forgot to close it once your app starts crashing.

Luckily on Tomcat, there is an easy solution.

[More]

Apache Tomcat 5.5.9, IIS 6 on Win2k3, JK2 0.4, Sun JDK 1.5.0.02, all works, thanks much to Mister TJ. Much thanks, TJ.

One thing not so carefully covered in that doc is that if you want to set up a specific web site (rather than the global web server site), it doesn't matter where you point the document root to in IIS. Heck point it to the default if you want. Any URLs matching an entry in workers2.properties are forwarded to Tomcat.

And for that matter, pay *special* attention to the URI entries in workers2.properties. By default, 5.5.9 puts the examples in a different place than the workers2.properties thinks they are. That means that when TJ says to browse to the examples to see them run, they won't run because they won't match entries in the workers file. So mod your workers file like he modded his.

[EDITED on 12/12/2005] This article looks very good too.

If you're ever looking into a JDBC driver for MSSQL, don't, DON'T use the MS one provided on their site.

I heard the same advice and was all, "Like, whatever dude, I'm not a performance freak." That was until I spent about three days trying to figure out why my frigging result set was mangled. Swapped it out for jtds and voila.

http://jtds.sourceforge.net/

I've been working on a ticket/bug tracker over the last many weeks (maybe 2 months?). It's the first Java project beyond HelloWorld. It uses JSPs and Servlets, a tiny MVC framework, JSTL, Jakarta Commons, runs on Tomcat 5 and MSSQL (using jtds). No plans to release it for public use at this time, but I've sure learned a hell of a lot about Java building it. If you're a client, get ready to start using it instead of calling me on the phone all the damn time.