Welcome to ColdFusion 2016, a creative progression in Adobe's efforts to help web developers build robust Internet applications.

The following are the download locations for ColdFusion 2016:

Release Highlights | What's New for Adobe ColdFusion (2016 release)

Adobe ColdFusion 2016 is a feature packed version of ColdFusion with benefits ranging from better security, performance, scalability, PDF improvements, and language enhancements along with the all new API Manager.

List of bugs fixed in ColdFusion (2016 release)

For a list of all bugs fixed in the 2016 release, see the pdf document.

Known Issues in Adobe ColdFusion (2016 release)

The following are known issues for Adobe ColdFusion (2016 release):

1. The 2016 release of ColdFusion does not work with WebSphere application server. ColdFusion compiles on JDK 1.8, whereas WebSphere 8.5 and below use IBM JDK 1.7. We shall provide support for WebSphere after the release of WebSphere 9.
2. If you update the PDF service settings in ColdFusion Administrator, you can see a blank page sometimes. As a workaround, restart the server.
3. Deploying a JEE archive created using the Packaging and Deployment > J2EE Archives page in the ColdFusion Administrator does not work.
4. Deploying a ColdFusion archive (.car) file on another instance of ColdFusion (2016 release) does not migrate the Allow REST Discovery setting.
5. The CFExchangeFilter tag does not filter the messages for filtertype : "message" and "requiredAttendees" using Exchange 2013
6. When you use ORM and MS-SQL Server, one-to-many relations using struct type and struct key as the primary key do not work. This is an issue with Hibernate.
7. Use the flag -Dcoldfusion.udf.reuseTagInstances=false, if you see the following. Clear cfclasses directory located at \ColdFusion2016\cfusion\wwwroot\WEB-INF\cfclasses and restart the server.
   1. Premature termination of the loop when invoking a UDF recursively while using CFLOOP to loop over a query that is defined as a var function local variable
   2. Incorrect struct modification issue when the CFHTTP tag is using a struct that has been passed to it via the CFTHREAD tag
   3. Timeout error when using CFLOCK and increasing the value of the timeout attribute does not help
8. While installing ColdFusion API Manager, if you cancel the installation, the extracted files remain behind.
9. On some windows platforms, post-installation, you might find CFIDE OR cf_scripts directory under {cf_install} directory. A copy operation to move the folder to {cf_root}/wwwroot/ has failed. You can go ahead and delete the same, as it does not impact the functionality.
10. If you are a non-root user and try to uninstall API Manager on Mac OS, the installation fails. As a work-around run the following command:  sudo /Applications/ColdFusion2016APIManager/uninstall/Uninstall/APIManager.app/Contents/MacOS/Uninstall\ APIManager where "/Applications/ColdFusion2016APIManager/" is the API Manager installation directory.
11. The last page of a PDF fails to add the stamp if the page attribute is specifed as page="*". As a workaround, specify the last page number and perform the add stamp operation.
12. You can sometimes see an IllegalStateException error if you use the cfstop.bat file to stop ColdFusion. Ignore the error.
13. In Solaris, DDX operations, such as, export/import comments/metadata, add attachments, process ddx , and set info and archiving might not work properly due to a class loading issue. As a workaround, delete lib/xmpcoreold.jar and restart ColdFusion.

Known Issues in API Manager

1. Pagination does not work when you import more than ten users in an external user store in the API Manager Administrator Portal.
2. If you update the domain URL of a node that is a part of a cluster, the node appears twice in the Cluster page of the API Administrator portal. The node also appears in the cluster.xml file.
3. Failover URL and load balancer types are not applicable to generated REST endpoints while using SOAP to REST conversion.
4. API Manager installer does not inform you of a previous installation if a previous installation already exists. It overwrites few existing files and fails to start subsequently.
5. API Manager does not provide a start-up script to start the service on system reboot on non-windows platforms. As a result, start API Manager manually after a system reboot.
6. When you try-out a SOAP Proxy API on IE, you can see the error message - "There was some error while invoking the API. Verify and try again".
7. In a cluster environment, when you create a REST API from SOAP and click Generate Rest Endpoints, the API Manager does not generate the resources and endpoints for the first time. You have to select the Apply to all resources check-box and then click Generate Rest Endpoints.
8. Copy buttons do not work on Internet Explorer.
9. The API Manager can sometimes send duplicate email notifications for Lifecycle Change and Throttle limit exceeded events.
10. The API Manager does not send notifications to a Publisher and Subscribers for any change in SLA plans.