Adobe ColdFusion (2023) Release Notes

What's new and changed

Adobe Coldusion (2023 release) is a completely reimagined solution that offers a modular, secure, and containerized approach to building applications that can run across multiple cloud providers or on-premises. You can now switch between cloud service providers without having to rewrite your application.

For more information, see:

• What's new in ColdFusion (2023 release)
• System requirements
• Frequently Asked Questions
• Ask the community

Bugs fixed in this release

Known issues in this release

• CF archive migration of scheduled tasks, fails from ColdFusion 2018 to ColdFusion 2023. Additionally, certain task attributes are not migrated when migrating from ColdFusion 2021. To manually migrate the tasks, copy <cf_home>/cfusion/lib/neo-cron.xml from your old ColdFusion instance to the new one, and restart ColdFusion.
• The Install time migration wizard window for migration from the previous ColdFusion installation on the same host, may not show up post installation upon first ColdFusion admin login on macOS and Ubuntu platforms. Follow the instructions in the migration guide to manually perform migration in such cases. Error reported for certain settings (SAML, cloud configuration and cloud credentials) that are not configured in migration source ColdFusion are inconsequential and can be ignored. To migrate noSQL datasources, simply copy the neo-nosql-datasource.xml from the <cf_home>/cfusion/lib directory of the old ColdFusion installation to the new one.
  
• Attempting to generate a SAML Service Provider in API Manager administrator results in an error.
• For creating REST API from SOAP, copy tools.jar file to the <apim_home>/lib directory and restart APIM for the library to be loaded.
• Model generation fails when an "and" or "or" operators is used in the schema. As a workaround, inline queries can be used where schema is not compiled, thus it will work without any issue.
• If a CFML request using ormsearch feature, fails with no output, uninstall the ormsearch package, delete the contents of <cf_home>cfusion/bin/felix-cache directory, reinstall the ormsearch package and restart CF.
• If ColdFusion is configured with a JRE older than the default java 17, you may run into issues connecting to Apache Derby datasources. To resolve the issue. install an older version of the derby package by following the instructions below:
  1. Use CF admin or the cfpm utility tool to uninstall the default derby package.
  2. Download the attached derby jar and the bundlesdependency_custom.json file. Place the files in <cf_home>/bundles directory.
  3. Download the attached derby-combined-10.11.jar and place it in the<cf_home>/bundles/repo directory.
  4. Clear <cf_home>/cfusion/bin/felix-cache directory and restart ColdFusion.
  5. Install the derby package with version derby-2023.0.08.330668. Download the zip file (at the end of the document) and unzip to extract the jar file.
• On macOS, before launching the ColdFusion installer, run "xattr -rc” command against the installer dmg.
• On macOS, additional CF instances, created using ColdFusion enterprise manager, copies resources (certain directories and CF admin pages) are that not required in a child instance.
• Silent installation of ColdFusion 2023 lockdown installer is presently not functional.
• The CCS server does not run as a daemon.
• If ColdFusion does not start after Sandbox is enabled, add the following JVM argument to the args list in <cf_home>/cfusion/bin/jvm.config: "-Djdk.lang.Process.allowAmbiguousCommands=true".
• If using an AWS package based API results in a class-not-found error, delete the content of <cf_home>/cfusion/bin/felix-cache and restart ColdFusion.
• Coldfusion 2023 Date functions on date value returned by a query (mySQL DB) throw an error. To resolve the error, add -Dcoldfusion.jdbc.mysql.datetime.str=true to java.args.