cfchart does not generate HTTP headers. When no headers are provided, IIS 6 examines the data and presumes headers are included in the data (for legacy ISAPI extensions). If the image data accidentally contains a binary value that looks like a line-end near the beginning of the data, IIS 6 misinterprets the beginning of the image data as an HTTP header.
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.
Follow the instructions below to install the hot fix for ColdFusion MX 6.1 in the J2EE configuration with a J2EE server including JRun:
- 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)
- 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).
- Deployment Descriptor Context Parameters can be changed usingthe 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.