CF Instance Hangs, “too many open files” in Log
This is really quite trivial, but may be of some interest to people who don't know too much about Linux OS tweaking. Today our dev-server instance was hanging - again. Only this time I took the liberty to make our developers wait a little longer before I restarted it, so I could actually diagnose the issue and resolve it for good. As only one of our two instances was hanging, I took a peek into its logfiles first - but couldn't find anything out of the ordinary. And the Enterprise Manager reported the instance to be running, too.
ColdFusion 8 and Symlinks – Hell Awaits? (solved)
UPDATE: The issue seems to be fixed with ColdFusion Hotfix hf801-71648 (see technote kb403629). The fix is included in the Cumulative Hot Fix 2 for ColdFusion 8.0.1 (see technote kb403781). My bad - I thought I had deployed the hotfix when all I had in fact done was upload the zip-file instead of the jar. Epic fail. Anyway, the technote is a bit misleading as well - it's talking about Application.cfm path resolution when the same issue applies to cfinclude, too.
UPDATE 2: This hit us today again. I usually download the ZIP-Archives of the updates and just unzip then in place before restarting coldfusion. For some reason two of our five CF-servers decided to include chf8010002.zip into their classpath instead of the chf8010002.jar that was sitting right next to it. I cannot imagine how CF decides that a ZIP-file would be a valuable addition to its classpath, but only after I simply removed the original ZIPs and restarted the server, the JAR was correctly included and the annoying symlink resolving went away.
I recently stumbled over an issue when using symbolic links on a couple of ColdFusion applications. I intended to use symlinks to keep duplicate code between different applications to a minimum. I'm running Apache 2.2 with ColdFusion 8.0.1 on 64-bit Debian Etch. Each of our web-applications needs a "connector" while retaining an include with some site-specific config.