Issue

The IIS connector truncates headers larger than 8k bytes. This creates issues for a very small number of applications that use headers slightly larger than 8k. Both the IIS 5 and 6 connectors are affected. See TechNote 7fe403f8 for the JRun4 Updater 6 patch.

Note: ColdFusion MX 7.0.1 and MX 7.0.2 (Server or Multiserver editions) use JRun 4 Updater 5 and are affected by this patch.

Products Affected

  • ColdFusion MX 7.0, 7.0.1 Multiserver edition, 7.0.2 Multiserver edition
  • JRun 4.0 Updater 5

This is logged as issue 55816.

Solution

This TechNote provides a new web server configuration file (wsconfig.jar) to replace the IIS connector components.

Installation instructions

ColdFusion MX

  1. Backup the existing cf_root/runtime/lib/wsconfig.jar to wsconfig.jar.bu.
  2. Download the hot fix (2.2MB).

    Note: Internet Explorer may try to change the name of wsconfig.jar to wsconfig.zip. If this occurs, be sure to save the file as wsconfig.jar.

  3. Stop all ColdFusion MX servers and IIS (WWW Publishing Services) and the Windows Management Instrumentation service to unlock the IIS connector.



    Note: This step is important for ISPs. With IIS running, the connector installer shuts down and restarts each site during the upgrade, causing the upgrade to take much longer.
  4. Navigate to the cf_root/runtime/lib directory and runthe connector upgrade:
    cd cf_root/runtime/libcf_root\runtime\jre\bin\java -Dtrace.ci=1 -jar wsconfig.jar -upgrade -v
  5. Make sure the upgrade completed successfully.
    • Inspect cf_root/runtime/lib/wsconfig/wsconfig.log for errors
    • Check the version tab ofcf_root/runtime/lib/wsconfig/N/jrun_iis6_wildcard.dll or jrun.dll. The "Product Version" item name field should indicate 4,0,5,107672 (the old connector version is 4,0,5,92909).



      Another way to check the version is to query the wsconfig.jar directly as shown below: cf_root\runtime\jre\bin\java -jar wsconfig.jar -info

JRun 4

  1. Backup the existing jrun_root/lib/wsconfig.jar to wsconfig.jar.bu.
  2. Download the hot fix (2.2MB).

  3. Stop all JRun servers and IIS (WWW Publishing Services) and the Windows Management Instrumentation service to unlock the IIS connector.



    Note: This step is important for ISPs. With IIS running, the connector installer shuts down and restarts each site during the upgrade, causing the upgrade to take much longer.
  4. Navigate to the /jrun4/lib directory and run the connector upgrade:
    cd jrun_root/lib java -Dtrace.ci=1 -jar wsconfig.jar -upgrade -v
  5. Make sure the upgrade completed successfully.
    • Inspect jrun_root/lib/wsconfig/wsconfig.log for errors
    • Check the version tab ofjrun_root/lib/wsconfig/N/jrun_iis6_wildcard.dll or jrun.dll. The "Product Version" item name field should indicate 4,0,5,107672 (the old connector version is 4,0,5,92909).



      Another way to check the version is to query the wsconfig.jar directly as shown below: java -jar wsconfig.jar -info

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy