ColdFusion MX 6.1: Hot Fix for duplicate, GetHTTPRequestData and DateDiff functions
Macromedia has created a hot fix to address the following issues with the duplicate, GetHTTPRequestData, and DateDiff functions in Macromedia ColdFusion MX 6.1:
- 53469 -
duplicatefunction makes shallow copies of ColdFusion arrays - 53813 -
duplicatefunction makes shallow copies of CF arrays, non-CF arrays, & queries - 53902 -
duplicatefunction makes shallow copies of non-ColdFusion arrays - 53875 -
GetHTTPRequestDatafunction misinterprets quoted Content-Type headers - 53972 -
DateDifffunction incorrectly accounts for Daylight Saving Time - 55054 -
cfdumpofcferrorscope causes infinite loop - 55306 - FlashGateway cannot use cached queries after applying previous versions of
duplicatehot fix (prior to 5/5/04)
ColdFusion MX 6.1 - Server Configuration
Follow the instructions below to install the hot fix for ColdFusion MX 6.1 in the server configuration. For J2EE servers including JRun, use the instructions under the J2EE Configuration section.
Windows
- Download the hot fix (37K).
- Stop ColdFusion.
- Create the directory cf_root\runtime\servers\lib if it does not exist.
- Extract hf53813_61.jar from the downloaded ZIP file, into the following directory:
cf_root\runtime\servers\lib\ - Restart ColdFusion.
- Examine the ColdFusion MX Administrator System Information page and confirm that hf53813_61.jar shows in the Java Class Path list.
Unix
- Download the hot fix (37K).
- Stop ColdFusion.
- Create the directory cf_root/runtime/servers/lib if it does not exist.
- Extract hf53813_61.jar from the downloaded ZIP file, into the following directory :
cf_root/runtime/servers/lib/ - Edit the filecf_root/runtime/bin/jvm.config:
- Locate the JVM classpath section.
- Add {application.home}/runtime/servers/lib as the first entry in the java.class.path list.
For example:
# JVM classpath java.class.path={application.home}/runtime/servers/lib, {application.home}/runtime/../../src, {application.home}/lib/cfusion.jar, {application.home}/runtime/lib/webservices.jar
- Restart ColdFusion.
- Examine the ColdFusion MX Administrator System Information page and confirm that hf53813_61.jar shows in the Java Class Path list.
ColdFusion MX 6.1 - J2EE Configuration
ColdFusion MX 6.1 - J2EE Configuration with JRun
Follow the instructions below to install the hot fix for ColdFusion MX 6.1 in the J2EE configuration with a J2EE server including JRun:
- Download the hot fix (37K).
- Extract hf53813_61.jar from the downloaded ZIP file, into thecf_root/WEB-INF/lib directory.
- Change the Context Parameter cf.class.path
in the Deployment Descriptor (cf_root/WEB-INF/web.xml)
for the Web Application "Macromedia ColdFusion MX" (cfusion.war)
from:
./WEB-INF/cfusion/lib/cfusion.jar
to:
./WEB-INF/lib/hf53813_61.jar,./WEB-INF/cfusion/lib/cfusion.jar
- Note that the two paths in cf.class.path each start with a period and are separated by a comma.
- Do not confuse ./WEB-INF/lib (which contains the hot fix jar file) with ./WEB-INF/cfusion/lib (which contains cfusion.jar).
- Stop and restart the J2EE server for changes to take effect.
- Examine the ColdFusion MX Administrator System Information page and confirm that hf53813_61.jar shows up in the Version section like 6,1,0 hf53813_61. Note: You will not see this jar in the Java Class Path because the hot fix jar is being loaded in the Coldfusion Class Path.
- Repeat steps for each deployed instance of ColdFusion.
About changing the Deployment Descriptor
- Deployment Descriptor Context Parameters can be changed using the J2EE Administrator Control Panel (WebLogic and JRun) or by using the Application Assembly Tool (Websphere). If your J2EE server does not have such a tool, you must make sure that the Context Parameter change is made for all deployed instances of ColdFusion. It may be necessary to un-deploy CFMX, make the change, then re-deploy CFMX. See your J2EE documentation for other methods.
- Be sure to Persist (WebLogic) or Save (Websphere) your changes after you change the value for cf.class.path.
- You will usually need to stop and restart your J2EE server to make these changes effective.
Additional Information
This content requires Flash
To view this content, JavaScript must be enabled, and you need the latest version of the Adobe Flash Player.
Download the free Flash Player now!
