A hot fix has been created to address several issues with using COM objects in ColdFusion MX 6.1.

The hot fix resolves the following issues with COM objects:

• 53224 - Child COM objects should not be released when the parent is released
• 53243 - Empty string variables should not be passed as Nulls
• 53283 - Optional arguments should be recognized correctly
• 53114 - VT_INT arguments should be converted to VT_I4 integers
• If a null argument is passed to a COM object, it should be initialized VT_EMPTY
• 53633 - COM objects which have TypeInfo but do not make it available work with CF5 but not with CFMX *

* Issue 53633 added 12/1/03. Hot fix download updated to include the fix for this issue.

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

1. Download the hot fix (962K).
2. Stop the ColdFusion MX Application service.
3. Rename cf_root\jintegra directory to cf_root\jintegra_153.
4. Extract jintegra_1_6_1.zip from the downloaded ZIP file, into cf_root\, preserving folder names. This will create a new \jintegra directory.
5. Rename cf_root\lib\jintegra.jar tocf_root\lib\jintegra_153.jar.
6. Extract jintegra.jar from the downloaded ZIP file, into cf_root\lib\.
7. Create the directory cf_root\runtime\servers\lib if it does not exist.
8. Extract hf53633_61.jar from the downloaded ZIP file, into the following directory:
   cf_root\runtime\servers\lib\
9. Start the ColdFusion MX Application service.
10. Examine the ColdFusion MX Administrator System Information page and confirm that hot fix hf53633_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:

1. Download the hot fix (962K).
2. Rename cf_root\WEB-INF\cfusion\jintegra directory to cf_root\WEB-INF\cfusion\jintegra_153.
3. Extract jintegra_1_6_1.zip from the downloaded ZIP file, into cf_root\WEB-INF\cfusion\, preserving folder names. This will create a new \jintegra directory.
4. Rename cf_root\WEB-INF\cfusion\lib\jintegra.jar to cf_root\WEB-INF\cfusion\lib\jintegra_153.jar.
5. Extract jintegra.jar from the downloaded ZIP file, into cf_root\WEB-INF\cfusion\lib\.
6. Extract hf53633_61.jar from the downloaded ZIP file, into the cf_root/WEB-INF\lib directory.
7. Change the Context Parametercf.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/hf53633_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).
8. Stop and restart the J2EE server for changes to take effect.
9. Examine the ColdFusion MX Administrator System Information page and confirm that hot fix hf53633_61.jar shows up in the Version section like 6,1,0 hf53633_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.
10. 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

• ColdFusion MX 6.1 confirmed issues (18795)
• ColdFusion hot fixes (all versions) (17883)

Products affected