2018 Update
ColdFusion (2018 release) Update 1
This updates below are cumulative and the later ones contain all updates from previous ones. If you are skipping updates, you can apply the latest update, not those you are skipping. Further, you must take note of any changes that are implemented in each of the updates you are skipping.
To see a list of all previous ColdFusion updates, refer to the update page.
For Application Servers
Additionally, on JEE installations, set the following JVM flag, "-Djdk.serialFilter= !org.mozilla.**;!com.sun.syndication.**;!org.apache.commons.beanutils.**", in the respective startup file depending on the type of Application Server being used.
For example:
- On Apache Tomcat Application Server, edit JAVA_OPTS in the ‘Catalina.bat/sh’ file
- On WebLogic Application Server, edit JAVA_OPTIONS in the ‘startWeblogic.cmd’ file
- On a WildFly/EAP Application Server, edit JAVA_OPTS in the ‘standalone.conf’ file
Set the JVM flags on a JEE installation of ColdFusion, not on a standalone installation.
ColdFusion (2018 release) Update 1 (release date, 11 September 2018) includes the following changes:
- Several important bug fixes.
- A new function GetCanonicalPath.
- Addresses security vulnerabilities as mentioned in the security bulletin APSB18-33.
- Tomcat is upgraded to version 9.0.10.
- OpenSSL is upgraded to 1.0.2p for PDFgServlet.
For more information, refer to the release notes.
To view all ColdFusion (2018 release) updates, see the Updates page.
Applying update for Server Auto-Lockdown
ColdFusion must always be running as a service.
If you want to apply Update 1 in case you server has been locked down using Server Auto-Lockdown, here's how you can do so:
Update using ColdFusion Admin in Windows
Uppdating via Administrators will not proceed as expected as the required permissions will not be present with a few folders.
In Linux, you can apply the update via the Administrator.
Update using java -jar in Windows
- Lock down the ColdFusion instance.
- Download the latest update and install it using the java -jar command.
After the installation, there will be a few files with permission-related issues.
As a work-around, run the following:
- icacls [Path to ColdFusion instance] /grant:r /[Administrator user](OI)(CI)F /T /Q /C
- icacls [Path to ColdFusion instance] /grant:r /[ColdFusion Runtime user](OI)(CI)F /T /Q /C
Update via java -jar in Linux
Lock down the ColdFusion instance.
Download the latest update and install it using the java -jar command.
After the installation, there will be a few files with permission-related issues. The update installer changes the file permissions of all the files inside the directory of the instance.
As a work-around, run the following:
- sudo chown -R [ColdFusion Runtime User] [Path to ColdFusion instance]
Bugs fixed
For the detailed list of bugs fixed in this update, refer to Bugs fixed list.
Known issues
Prerequisites
- On 64-bit computers, use 64-bit JRE for 64-bit ColdFusion.
- If the ColdFusion server is behind a proxy, specify the proxy settings for the server to get the update notification and download the updates. Specify proxy settings using the system properties below in the jvm.config for a stand-alone installation, or corresponding script file for JEE installation.
- http.proxyHost
- http.proxyPort
- http.proxyUser
- http.proxyPassword
- For ColdFusion running on JEE application servers, stop all application server instances before installing the update.
Installation
For instructions on how to install this update, see Server Update section. For any questions related to updates, see this FAQ.
- The update can be installed from the Administrator of a ColdFusion instance or through the command-line option.
- Windows users can launch the ColdFusion Administrator using Start > All Programs > Adobe > Coldfusion 2018 > Administrator.
- Microsoft Windows 8.1, Windows 10, Windows Server R2 2012, and Windows Server 2016 users must use the “Run as Administrator” option to launch wsconfig tool at {cf_install_home}/{instance_name}/runtime/bin.
- If you get the following error when installing the update using the Download and Install option, ensure that the folder {cf_install_home}/{instance_name}/hf_updates has write permission: "An error occurred when performing a file operation write on file {cf_install_home}/{instance_name}/hf-updates/hotfix_001.properties".
- The connector configuration files are backed up at {cf_install_home}/config/ wsconfig /backup. Add back any custom changes made to the worker.properties file after reconfiguring the connector.
Connector configuration
The Update 1 includes connector fixes for IIS. To incorporate these fixes, upgrade the connector by using either the GUI or the command line, as mentioned below:
<cf_home>/<instance_name>/runtime/bin/wsconfig.exe -upgrade
For more information on configuring the connector using the GUI, see Using GUI mode.
In the GUI mode, launch wsconfig , select the configurations, and click Upgrade.
Installing the update manually
- Click the link to download the JAR.
- Execute the following command on the downloaded JAR. You must have privileges to start or stop ColdFusion service and full access to the ColdFusion root directory.
Windows: <cf_root>/jre/bin/java.exe -jar <jar-file-dir>/hotfix-001-311402.jar
Linux-based platforms: <cf_root>/jre/bin/java -jar <jar-file-dir>/hotfix-001-311402.jar
Ensure that the JRE bundled with ColdFusion is used for executing the downloaded JAR. For standalone ColdFusion, this must be at, <cf_root>/jre/bin.
Install the update from a user account that has permissions to restart ColdFusion services and other configured webservers .
For further details on how to manually update the application, see the help article.
Post installation
After applying this update, the ColdFusion build number should be 2018,0,01,311402.
Uninstallation
To uninstall the update, perform one of the following:
- In ColdFusion Administrator, click Uninstall in Server Update > Updates > Installed Updates.
- Run the uninstaller for the update from the command prompt. For example, java -jar {cf_install_home}/{instance_home}/hf_updates/hf-2018-00001-311402/uninstall /uninstaller.jar
If you can't uninstall the update using the above-mentioned uninstall options, the uninstaller could be corrupted. However, you can manually uninstall the update by doing the following:
- Delete the update jar from {cf_install_home}/{instance_name}/lib/updates.
- Copy all folders from {cf_install_home}/{instance_name}/hf-updates/{hf-2018-00001-311402}/backup directory to {cf_install_home}/{instance_name}/
Connector configuration
|
Connector recreation required |
---|---|
Update 1 |
Yes |
Adobe
Recevez de l’aide plus rapidement et plus facilement
Nouvel utilisateur ?