Accessibility
 
Home / Products / ColdFusion / Support / Release Notes
Macromedia ColdFusion Support Center Release Notes


ColdFusion MX Updater Release 3
Release Notes Part 1 -
Known Problems and Installation Instructions

March 19, 2003

This document contains information about the ColdFusion MX Updater Release 3. The Updater Release 3 works with ColdFusion MX Server and ColdFusion MX for J2EE Application Servers. Updater 3 is the first Updater release that you can use with all available ColdFusion MX editions and releases.

This release of the ColdFusion MX Updater does not support versions of ColdFusion MX for IBM WebSphere purchased from the IBM Passport licensing program. If you have purchased ColdFusion MX through Passport, you must obtain a copy of the Updater directly from IBM.

Updater releases are cumulative; Updater 3 includes all fixes from Updaters 2 and 1. As a result, you do not have to install Updater 1 or 2 before you install Updater 3, and the bugs listed in both Part 2 -- Issues Fixed in this Updater Release and Part 3 -- Issues Fixed in Previous Updater Releases are fixed by Updater 3.


Notes
  • For more information about the Updater, see the FAQ for ColdFusion MX connector configuration.
  • To determine whether Updater 3 is installed, open the ColdFusion MX Administrator and click the Version Information link at the top of the page. The Server Details list on the Version Information page identifies ColdFusion MX Server with Updater 3 as Version as 6,0,0,58500. It identifies ColdFusion MX for J2EE Application Servers with Updater 3 as Version 6,0,0,58096.

Because of their length, these Release Notes are divided into four parts.


Contents of Part 1
Known Issues with this Release
Installing the ColdFusion MX Server Update on Windows
Installing the ColdFusion MX Server Update on UNIX
ColdFusion MX Server Installation Notes
Installing the ColdFusion MX for J2EE Update
Installing the Update with Apache Web Server

Other Parts of the Release Notes
Part 2 -- Issues Fixed in this Updater Release
Part 3 -- Issues Fixed in Previous Updater Releases
Part 4 -- Installed Files, Uninstalling, and Installing the Update Silently

Note: In these Release Notes, cf_root refers to the directory where ColdFusion is installed or deployed. By default, you install ColdFusion MX Server in C:\CFusionMX on Windows and /opt/coldfusionmx on UNIX. You deploy ColdFusion MX for J2EE Application Servers in a directory that depends on the application server.


 

Known Issues with this Release

The following known issues exist with this Updater. These issues are additional to any listed elsewhere. For more information on known issues in ColdFusion MX, see ColdFusion MX TechNote Known ColdFusion MX Issues.


Issue ID

Windows updater installs only (Original installer not affected). InstallAnywhere requires 256 colors or the installer crashes trying to paint the first screen (either immediate crash or 100% CPU utilization). Users often have servers set to 16 colors or when going through Terminal Services, many systems use 16 colors.

Console mode (text) installation is not available on Windows to get around this problem

51673

If you use ColdFusion MX with Apache web server 2.0.x, Updater 3 requires you to have version 2.0.43 or later and has been tested using Apache 2.0.44. If you have an earlier version of Apache web server 2, you must install an updated version as described in Installing the Update with Apache web server. Updater 2 required 2.0.41 through 2.0.43, and Updater 1 required 2.0.40.

Note: If you use ColdFusion MX with Apache web server 1.3.x, Updater 3 is supported with version 1.3.26 or later.

N/A

If you install Updater 3 on ColdFusion MX for J2EE with JRun 4 as your application server, you must use one of the following techniques to enable web services in ColdFusion:

Technique 1:

  • Replace JRun_root\webservices.jar with cf_root\WEB-INF\cfusion\lib\webservices.jar. For example, if JRun_root is C:\JRun4 and cf_root is C:\JRun4\servers\default\cfusion, copy C:\JRun4\servers\default\cfusion\WEB-INF\cfusion\lib\webservices.jar to C:\JRun4\lib and replace the existing file.

  • Replace the includes line in cf_root\WEB-INF\cfusion\lib\jrun.properties with the following line:
    includes=org.xml.,org.w3c.,org.apache.commons

Technique 2:

  • Change the WEB-INF/jrun-web.xml file of each J2EE application in the JRun server instance that runs ColdFusion MX for J2EE to set the enable-jrun-web-services element to false. This setting change disables JRun native web service support.

    The ColdFusion Updater adds this entry to the ColdFusion MX J2EE application, but does not add it to any other J2EE applications that are deployed on the same JRun server instance as ColdFusion MX. (The CFIDE application that you install if ColdFusion is deployed at a context root other than / does not have a jrun-web.xml file and does not need this entry.)

  • By default, each JRun server includes a default-ear application. If you have a default configuration, and have not deleted the default-ear application from the JRun server instance that runs ColdFusion, set the enable-jrun-web-services element to false in the JRun_root\servers\cf_app_server_name\default-ear\default-war\WEB-INF\jrun-web.xml file.

    To set the enable-jrun-web-services element to false, add the line as a top-level element; for example:

    < jrun-web-app>
         < enable-jrun-web-services>false</enable-jrun-web-services>
    ...

49694

The following issue applies to ColdFusion MX for J2EE only. It does not apply to the stand alone ColdFusion MX Server:

For application servers other than IBM WebSphere 4, you must make the following addition to the JVM's security policy file, java.policy (for example, /opt/jdk1.3.1_03/jre/lib/security/java.policy):

grant codeBase "<file:cf_root/WEB-INF/cfusion/lib/*>" {
permission java.security.AllPermission;
};
grant codeBase "<file:cf_root/WEB-INF/lib/*>" {
permission java.security.AllPermission;
};

Where cf_root is the deployed location of the cfusion.war application archive.

This information replaces any instructions in the ColdFusion MX for J2EE Installation instructions that require you to grant AllPermission for all files.

See also the Fixed in this Release entry for bug 48718

48718
If the Updater installation fails before completing, it might leave an incomplete backup directory. If you rerun the Updater, it will not properly back up your old configuration. To ensure a complete backup when you rerun the Updater after a failed update, first delete the cf_root cfmx_updater/cfmx_updater_xx folder, where xx identifies the Updater number; for example, 03 for Updater 3. 50119

You must now include the underscores in web services parameter names. Prior to Updater 3, if a web services parameter name contained underscores (_), you had to omit the underscores from the name. For example, to specify the auction_id parameter of the EbayWatcherService web service, you specified auctionid. Now you must include the underscore in the parameter name, auction_id.

This change is required because ColdFusion MX previously used an Axis beta release that did not properly handle underscores in WSDL names. Updater 3 uses Axis 1.0 for web services, which properly supports underscores.

N/A
Due to compiler changes in this Updater, some ColdFusion application code must be recompiled to work properly. To ensure this occurs, the updater installer renames the existing cfclasses folder, located at cf_root\wwwroot\WEB-INF, to cfclasses_backup. For more information, see the Installation Notes 49999

If you update a ColdFusion MX for J2EE Phase 1 installation, the following task applies. (ColdFusion MX for J2EE Phase 1 consisted of the originally released versions for ColdFusion JRun 4, WebSphere Application Server version 4, and Sun ONE Web Server 6, and included an integrated installer.)

After running the Updater, but before starting the ColdFusion MX Administrator, open the WEB-INF/cfusion/lib/wizzardconfig.xml file in a text editor and change the runsetup value from true to false.

49725
The web server connectors that are included in Updater 3 do not work with ColdFusion MX Server versions prior to Updater 3. N/A
If you use the cfhttp tag to retrieve pages in a language other than English, see the entry for bug 47450. 47450
The fix for bug 39460 exposes a known bug (Oracle bug number 984040) in the Oracle 8i implementation of getUpdatecount(), which can cause the Oracle OCI driver to hang on updates. Oracle has fixed this bug in Oracle8i Patch Set Version 8.1.7.4.1. For more information, see the Patch Set documentation on the Oracle website. 39460
Users who get Apache 1.3 EAPI warnings must compile an EAPI version of the Apache web server connector from source. For instructions see fix for bug 49684. 49684
46503
33365

The following problem applies to the ColdFusion MX Server Update on Windows only; it does not apply to ColdFusion MX for J2EE updates.

If you use a web server other than the ColdFusion MX built in web server, and the jrun.exe process is running when you install the updater, the procedure that updates the web server connectors might not be able to replace the Jrunwin32.dll file, resulting in the following error message:

Exception in thread "main" java.lang.UnsatisfiedLinkError: isIISJrunVirtualDir

This error can also occur if you run wsconfig.exe, wsconfig.jar, or any of the bat files in cf_root/bin/connectors to upgrade a connector.

If you encounter this error, ensure that both your web server and jrun.exe are stopped and reinstall the Update. For more information, see step 3 of Installing the ColdFusion Server Update in Windows. You can also view cf_root/runtime/lib/wsconfig/wsconfig.log to ensure that the jrunwin32.dll was not locked by another process and was replaced correctly.

50038
If you unconfigure all websites with wsconfig.jar -uninstall and immediately configure the connector again, especially in IIS, the connector installer might not recognize the running JRun server. In this case it, displays the error: "Could not connect to any JRun servers on host localhost. Confirm that the JRun server is started."

If you get this error, restart the ColdFusion MX Application Server and rerun the connector installer (wsconfig.jar).

50281
The following issue applies to ColdFusion MX for J2EE only. It does not apply to ColdFusion MX Server:

Attempting to connect to a SQL Server or database running on Windows that is set up to use code page 437 returns the exception: "[DataDirect][SQLServer JDBC Driver]Character set 437 not found in com.ddtek.util.transliteration.properties."

To resolve this problem, do the following:

  1. Start command prompt and set your working directory to cf_root/lib

  2. Use the following command on a single line to extract the transliteration.properties file from macromedia_drivers.jar:

    jar -xf macromedia_drivers.jar macromedia/util/transliteration.properties

  3. Add the following lines to the resulting cf_root/lib/macromedia/util/tranliteration.properies file:

    translit.type.437=VM
    translit.name.437=Cp437

  4. Use the following command on a sinlge line to update macromedia_drivers.jar with the edited transliteration.properties file:

    jar -uf macromedia_drivers.jar macromedia/util/transliteration.properties

  5. Delete the cf_root\lib\macromedia\util and cf_root\lib\macromedia directories.
35691
48051
ColdFusion MX versions are inconsistent in whether a cfquery that does not return a record set, such as an update query, creates an empty query object with the name specified by the name attribute. The following table indicates which versions create an empty query:

Version Returns empty query
ColdFusion 5 No
ColdFusion MX Server Yes
ColdFusion MX Server with Updater 2 No
ColdFusion MX Server with Updater 3 No
ColdFusion MX for J2EE phase 1 Yes
ColdFusion MX for J2EE phase 2 Yes
ColdFusion MX for J2EE with Updater 3 No
50329
Whitespace management is supported in ColdFusion MX for J2EE on JRun 4, but it is disbled by default and you cannot set it in the ColdFusion MX Administrator. To enable whitespace management, shut down ColdFusion MX and change the setting of the first boolean value in the cf_root/WEB-INF/cfusion/lib/neo-runtime.xml to true:

<wddxPacket version='1.0'>
<header/>
<data>
<array length='11'>
<boolean value='true'/>

A Boolean value of true enables whitespace management; a value of false disbles it. After you have edited and saved the file, restart ColdFusion MX.

50337
The ReplaceNoCase and FindNoCase functions may produce unexpected results on strings which have a different number of characters in the upper case and lower case representations. An example of this is the German ß character (scharfes S or double S) which is a single character in lower case, but is two characters in upper case.
50304

Back to Contents



Installing the ColdFusion MX Server Update in Windows

This section explains how to install a ColdFusion MX Update in a Windows platform. Read the Installer Notes before you install the updater.

To install a ColdFusion MX Update in Windows:

  1. Ensure that you are installing the latest Updater available for ColdFusion MX. For more information, see http://www.macromedia.com/support/coldfusion.


  2. Close any applications that are currently running on your computer.


  3. Stop the following services:
    • ColdFusion MX Application Server
    • ColdFusion MX ODBC Agent
    • ColdFusion MX ODBC Server
    • (if you use IIS as your web server for ColdFusion MX)World Wide Web Publishing Service.
    • (if you use a web server other than IIS or the ColdFusion MX built-in web server)
      the web server.

  4. Run cfmx_updater_windows_r3.exe. The installation wizard starts.

  5. Follow the instructions in the wizard, and let it run to completion.

    Note: if you do not shut down IIS in step 3, ColdFusion attempts to shut each site down individually and restart it after installing the update. If you have large numbers of sites, this might take a long time.


  6. After the Pre-Installation Summary pane, the Updater copies updated files to your computer and upgrades any configured web server connectors.


  7. After the installation is complete, restart the services that you stopped in step 3. You might also have to restart your web server after running the Updater.
Back to Contents


 

Installing the ColdFusion MX Server Update on UNIX

This section explains how to install a ColdFusion MX Update on UNIX. Read the Installer Notes before you install the updater.

Note: These instructions use the general term cfmx_updater_file to refer to the Updater file. The specific Updater 3 filename depends on the operating system, as follows:

Linux cfmx_updater_linux_r3.bin
Solaris cfmx_updater_solaris_r3.bin
HPUX cfmx_updater_hpux_r3.bin

To install a ColdFusion MX update on UNIX:

  1. Ensure that you are installing the latest Updater available for ColdFusion MX. For more information, see http://www.macromedia.com/support/coldfusion.


  2. Log in as root.


  3. Stop ColdFusion MX with the following command:
    /cf_root/bin/coldfusion stop


  4. Stop your web server.

  5. Using the cd command, go to the directory with the Cold Fusion MX Updater file.


  6. Modify the Updater file with the following command:
    chmod 755 cfmx_updater_file


  7. Start the installation with the following command:
    ./cfmx_updater_file
    The installation program starts.

  8. Follow the prompts, and let the program run to completion.


  9. After the Updater program finishes, start your web server.

  10. Start ColdFusion MX with the following command:
    /cf_root/bin/coldfusion start.

 

Back to Contents


 

ColdFusion MX Server Installation Notes

In the following notes, cf_webroot refers to the directory that contains the ColdFusion MX CFIDE directory. This directory is typically the active web server's root document directory. For example, for the ColdFusion MX internal web server, this directory is cf_root\wwwroot. If ColdFusion MX uses another web server, such as Microsoft IIS or Apache, the directory might have a different path. You specify the location of this directory in one of the Updater installation program steps.

  • The Updater writes the following information files to the cf_root directory:

    Macromedia_ColdFusion_MX
    _Updater_InstallLog.log
    Log file providing installation details, including the files installed.
    cfmx_updater_installer_debug.txt Detailed debugging information.

  • The Updater checks for the existence of the following files before installing the Update. If any of these files is missing, the Updater reports an error and does not install the Update.

    In Windows cf_root\bin\cfstart.bat
    cf_root\lib\cfusion.jar
    cf_webroot\CFIDE\administrator\Application.cfm
    On UNIX cf_root/bin/coldfusion
    cf_root/lib/cfusion.jar
    cf_webroot/CFIDE/administrator/Application.cfm

  • The Updater puts copies of the original versions of all files that it updates in the cf_root/cfmx_updater/cfmx_updater_XX directory tree. (XX is a number, such as 01, that indicates the update that saved the backup files.) Each files location in this directory tree reflects the original files location relative to the cf_root directory.
  • If you reinstall an update that has already created backup files, the installation does not overwrite the original backup files.

  • Due to compiler changes in this updater, ColdFusion application code must be recompiled to work properly. To ensure this occurs, the updater installer renames the existing cfclasses folder, located at cf_root\wwwroot\WEB-INF, to cfclasses_backup.

    You can use the updater_compile script installed in the cf_root\bin directory to recompile your ColdFusion applications. Recompiling your application helps to improve initial page request time, but is not necessary for the proper functioning of ColdFusion applications. Use the following commands to run this script:

    Windows:
    updater_compile.bat cf_web_root [cf_app_file_dir
    ]

    UNIX:
    ./updater_compile.sh -cfuser username -webroot cf_web_root
                        [-dir cf_app_file_dir]

    cf_web_root specifies your web root directory, such as C:\inetpub\wwwroot.

    cf_app_file_dir is the directory that contains the CFML files to be compiled. It must be underneath the web root directory. If you omit this attribute, the script recompiles all coldfusion pages in the web root directory and all its subdirectories.

    In the UNIX command, username specifies the ColdFusion runtime user, and must correspond the the user who installed ColdFusion MX (typically, nobody).

    After successfully recompiling and testing your applications, you can remove the cfclasses_backup folder created by this installation.

  • The Updater automatically upgrades all configured web connectors. In some cases, you might have to upgrade all configured connectors independently of the Updater; for example, following installation of a security patch. To upgrade the connectors in Windows, run the cf_root\bin\connectors\Upgrade_all_connectors.bat script. The script takes no arguments.

Back to Contents


Installing the ColdFusion MX for J2EE Update

This section explains how to install a ColdFusion MX Update on a system that is running ColdFusion MX for J2EE Application Servers. It applies to all operating systems and all versions of ColdFusion MX for J2EE released to date, including the first, or "phase 1", release that worked with Macromedia JRun 4, IBM WebSphere 4, and Sun One Web Server 6 only, and the second, or "phase 2", release that you deploy as an archive.

The Updater for ColdFusion MX for J2EE fully replaces your current ColdFusion MX for J2EE installation. The Updater backs up your existing configuration and ColdFusion application files and installs the updated ColdFusion MX for J2EE. You then restore your configuration and ColdFusion application files.

Notes:

  • These instructions refer to the ColdFusion MX for J2EE installation instructions for your application server. The installation instructions are available online at http://www.macromedia.com/go/cfmxj2ee-cert. The Archive File Installation column of the "Supported J2EE application servers" table includes links to the appropriate installation instructions for supported servers. (Do not use the links in the Integrated installer column.) The "Unsupported application servers for the archive install" section includes links to installation instructions for additional servers.

  • The updater replaces the phase 1 version of ColdFusion MX for J2EE with a phase 2 format installation. As a result, the installation documentation that applied to phase 1 no longer applies. Use the phase 2 installation instructions, instead.
  • Ensure that you are installing the latest Updater available for ColdFusion MX for J2EE. For more information, see http://www.macromedia.com/support/coldfusion .

  • If you install Updater 3 on ColdFusion MX for J2EE with JRun 4 as your application server, you must use one of the techniques listed for bug 49694 in the Known Problems section to enable web services in ColdFusion.

  • If you install Updater 3 on ColdFusion MX for J2EE with JRun 4 as your application server, you do not need to follow the special instructions for getting ColdFusion to run on JRun 4 that are included in the JRun 4 SP1a release notes.

Installing the updater on ColdFusion MX for J2EE


  1. Close any applications that are currently running on your computer.


  2. If you are running Windows and installed support for ODBC data sources, stop the following services:

       ColdFusion MX ODBC Agent
       ColdFusion MX ODBC Server


  3. As appropriate for your application server, either stop the ColdFusion application and RDS application (if it is running), or stop the application server.

  4. Run the ColdFusion MX for J2EE Updater.
    For Windows, Linux, or Solaris, run the executable that you downloaded, as follows:

    Windows coldfusion-j2ee-win.exe
    Linux coldfusion-j2ee-linux.bin
    Solaris coldfusion-j2ee-solaris.bin

    For other platforms, use the following command to run the coldfusion-j2ee-java.jar file:

       java_home/java -jar coldfusion-j2ee-java.jar -i console

  5. In the Updater, follow the steps for archive file installation of ColdFusion MX for J2EE. Installation instructions are available online at http://www.macromedia.com/go/cfmxj2ee-cert. If you previously used the archive file installation (sometimes referred to as phase 2 installation), follow the steps that you used when you installed ColdFusion MX for J2EE; for example, select EAR or WAR file deployment as required by your J2EE server.

    The Updater has the following steps that are additional to those in the original phase 2 ColdFusion MX for J2EE installer and are not documented in the ColdFusion MX for J2EE installation instructions:

    1. When asked whether to create a backup of your configuration and custom files, select Yes.

    2. Select a directory in which to place the backup files. The Updater will save in this directory all files in your ColdFusion J2EE application directory tree that it cannot safely replace, including configuration files and any files that are not part of the ColdFusion installation. You will copy these files back to the ColdFusion MX application in step 9.

    3. Specify the directory where ColdFusion MX for J2EE is deployed. In the ColdFusion installation instructions, this directory is often referred to as cf_root. It contains the CFIDE, and WEB-INF (including WEB-INF\cfusion) directories and, if you installed the ColdFusion examples, the cfdocs, directory. In some application servers, it has the same name as your ColdFusion application context root.


  6. Undeploy your ColdFusion MX J2EE application from your application server, using the standard undeployment procedure for your application server.

  7. Deploy the EAR file or WAR file(s) that you created in step 5 in the same directory on your application server that you used previously. Follow the deployment steps in the ColdFusion MX for J2EE installation instructions for your application server. Do only the deployment steps in the installation instructions. In particular:

    • Do not open the ColdFusion MX Administrator or run the Startup wizard.
    • You should not need to perform the postdeployment steps in the ColdFusion MX for J2EE installation instructions, such as configuring security settings or Verity support.

  8. Stop the ColdFusion J2EE application if it is running. On some application servers, you might have to stop the J2EE application server.

  9. Copy the files in the backup directory that you specified in step 5b back to your cf_root directory. Ensure that the files from the backup directory tree overwrite any files with the same names in the cf_root directory tree.

  10. On some application servers, you might have to rename the file cf_root\WEB-INF\cfusion\lib\tools.jar to something else (for example, tools.old). To determine if you must do this step, see the ColdFusion MX for J2EE installation instructions for your application server.

  11. When updating ColdFusion MX for J2EE running on a phase 1 server (that is, JRun 4, WebSphere Application Server version 4, or Sun ONE Web Server 6). Open the WEB-INF/cfusion/lib/wizzardconfig.xml file in a text editor and change the runsetup value from true to false.

  12. Restart the ColdFusion J2EE application or the J2EE server.

  13. If you stopped any services in step 3, restart them. Also You might have to restart your web server after running the Updater.
Back to Contents


 

Installing the Update with Apache Web Server

If you use a version of the Apache web server 2.0.x earlier than 2.0.43 with ColdFusion MX Server or ColdFusion MX for J2EE with JRun, you must install a new version of Apache before you can use ColdFusion MX. As a result, if you installed Updater 2 with any version of Apache 2.0. other than 2.0.43, you must install a new version of Apache.

Note: If you use ColdFusion MX with Apache web server 1.3.x, Updater 3 is supported with version 1.3.26 or later.

If you must install an updated Apache web server, use the following procedure to update ColdFusion MX Server. If you are using JRun, follow the standard procedures for uninstalling and installing a web server connector.
  1. Uninstall the web server connector. At a command prompt, run the following line.
    In Windows:
    cf_root\runtime\jre\bin\java -jar cf_root/runtime/lib/wsconfig.jar-v -u
    On UNIX:
    cf_root/jre/bin/java -jar cf_root/runtime/lib/wsconfig.jar-v -u

  2. Stop ColdFusion MX.

  3. Install Apache 2.0.43 or later. The version you install must have the same MODULE_MAGIC_NUMBER_MAJOR (Apache magic number) value as version 2.0.43.

  4. Install the ColdFusion MX Updater.

  5. Restart ColdFusion MX.

  6. Install the web server connector to the new Apache web server installation using the following line.
    In Windows:
    cf_root\runtime\jre\bin\java -cp cf_root/lib -jar cf_root/runtime/lib/wsconfig.jar-ws Apache -dir Apache_conf_dir -v -map .cfm,.cfc.,.cfml -coldfusion
    On UNIX:
    cf_root/jre/bin/java -cp cf_root/lib -jar cf_root/runtime/lib/wsconfig.jar-ws Apache -dir Apache_conf_dir -v -map .cfm,.cfc.,.cfml -coldfusion

Note: To determine the Apache magic number value, run one of the following commands:

In Windows
apache_root\bin\Apache.exe -V

On UNIX
apache_root/bin/httpd -V | grep "Magic Number"


Back to Contents
Part 2 -- Issues Fixed in this Updater Release
Part 3 -- Issues Fixed in Previous Updater Releases
Part 4 -- Installed Files, Uninstalling, and Installing the Update Silently