Build number reference for ColdFusion MX, JRun4, and wsconfig.

More reference material on build numbers and how to collect them programmatically and via commandline. Useful for when the ColdFusion Administrator is not available or when coding different behaviors based on build number or version.

Having wsconfig build numbers is especially important when using distributed configuration where you want to make sure that you are using a version of wsconfig that shipped with the version of JRun you are trying to connect to.


ColdFusion MX JDBC Driver Versions

This post is just to be a handy reference for CFMX JDBC driver versions. Using the following code (once posted to CFTalk by Dave Carabetta), JDBC driver version information was generated and written to the {servername}-out.log.


RHEL 4 Released

Red Hat announced today that RH Enterprise Linux 4.0 has been released. Fedora Linux users will be most familiar with RHEL 4 features since the Fedora Project is simply a public beta of RHEL under the guise of community-based project or distribution. I'll defer a review of RHEL 4 to a nice overview found in this month's online edition of Red Hat Magazine, Introducing Red Hat Enterprise Linux 4.

Notable in this release is the inclusion of Security Enhanced Linux (SELinux in RH4). This Mandatory Access Control feature is configured in RHEL4 to have a targeted policy enabled. In short this means that most core applications on the system are configured in the SELinux security policy, and violations of the policy will result in security errors.

For ColdFusion users this news shouldn't be terribly relevant since there are no versions of ColdFusion officially supported to run on RHEL4 (or Fedora, or Mandrake, or Debian, or Ubuntu for that matter), but knowing how CF fanatics have an affinity for testing ColdFusion on every Linux distribution imaginable and then unleashing havoc, I'm sure someone is testing the bits as I write. Nevertheless, let's get the perfunctory warning over with anyway:

Red Hat Enterprise Linux 4.0 is not supported by ColdFusion at this time.

However, if you venture out into this unsupported territory you might want to read last week's blog entry about those pesky "Permission Denied" errors when using Fedora Core 3 Linux with ColdFusion while SELinux is enabled. Frankly, while I use supported versions of Linux for testing real ColdFusion problems on behalf of others, I use Fedora Linux on my laptop to run ColdFusion for myself. Other than the SELinux issue mentioned earlier, I haven't found any problems with my limited use of CF on that OS.

Roses are red, blogs are blue

As a Valentine's Day gift, I spent this weekend building a new blog for my wife based on Ray Camden's BlogCFC, merged with the Aura skin.

The new blog is called Casa ArbaÃ’il, the name of her family's second home in a small village up in the Pyrenees of Spain, where my wife spent many summers growing up and where we continue to travel each Christmas. As a native of Barcelona, a Catalan speaker, a current resident of Massachusetts, and a chemist by profession you'll find future blog entries on these categories. As soon as her we get her domain name mapped to our ISP then the blog will located there, until then it remains on


Running ColdFusion MX on Fedora Core 3 Linux when SELinux is enabled

When configuring ColdFusion MX for the Apache webserver on Fedora Core 3 Linux (FC3), you might find "Permission Denied" errors during several events, including when you try to start Apache.

This is because SELinux (Security Enhanced Linux) in FC3 is enabled, a default setting. During FC3 installation you have the option to configure SELinux as

  • Active
  • Warning
  • Disabled


Powered by Detroit CF/Flash Conference April 9-10 2005

Powered by Detroit Conference is designed to promote the use of Flash and ColdFusion together as the dynamic medium for the future of the internet.

From beginners, to professional designers, to marketing professionals looking for creative new ideas, you won't want to miss this event!

Attendees will hear presentations from expert speakers and have an opportunity to be a part of the Flash and ColdFusion community.

This conference will emphasize Flash development and design, as well as ColdFusion development of websites.

If you are ready to get serious about Flash and/or ColdFusion development, this is a must attend event!

All CFUG and MMUG managers are offered a special rate of $99!!!

Example of a code induced memory leak that crashes CFMX

Recently I helped someone who reported a rapid memory leak in ColdFusion MX 6.1 server where memory for the jrun.exe process grew from 300 MB upon startup to 1200 MB within about 15 minutes, followed by a JVM crash.

A thread dump was obtained from when the memory was peaking and reviewed along with the ColdFusion and JRun log files.

The thread dump showed several jrpp threads where the individual stack for a jrpp was hundreds and hundreds of lines, composed primarily of a repeating sequence. The repeating sequence appeared to be a type of long or infinite loop where cfm A called cfm B which called cfm C which called cfm A again. The sequence repeated until it used the maximum heap available to the JVM, 1.2GB, and then crashed the server.


Tracing wsconfig with Ethereal Network Analyzer

Tracing the wsconfig utility's TCP communications to a JRun server reveals communication over ports other than the JNDI port. In fact, after wsconfig establishes a connection over the JNDI port, the JRun server instructs wsconfig that JRun will now listen on a random port and that wsconfig is to complete the communications over that new port through a new TCP connection.

The wsconfig utility is used by ColdFusion and JRun servers to configure external webservers to the appropriate application server. One type of configuration is referred to as Distributed Mode where the webserver is on one machine and it will use the JRun connector to communicate with the ColdFusion or JRun server on another machine. In this situation there may be a firewall between the two machines, for example, which could potentially block the required TCP communication between wsconfig and JRun when initially installing the connector for the webserver.


Exception occured trying to get an MBean

When attempting to configure an external webserver for ColdFusion MX or JRun with the wsconfig utility, if the Java executable used to run wsconfig is version 1.5 or greater then this error will occur.

Trying to force java 1.5 to be compatible with 1.4 getters with the -Djmx.invoke.getters=true switch did not work.


Simultaneous Requests in CFMX 7

Watch that setting! While ColdFusion MX 7 Server Configuration installs with a default value for Simultaneous Request at 8, the Multi-server configuration has a default setting of 25 for this parameter.

ColdFusion MX 7 has the same rule of thumb for starting values on this parameter, just 3 to 5 per CPU on the machine. The default Server Configuration setting falls into that range for a 2 CPU machine, but the Multiserver Configuration value of 25 Simultaneous Requests may be too high for your application.


Previous Entries / More Entries