ColdFusion 2025 FAQ
The questions we get asked most often
This is a substantial release. The highlights:
- JDK 21 LTS: The biggest performance gain. Significant improvements over older JDK versions.
- Tomcat 10.1: Modern servlet container on the Jakarta APIs. Note: javax.* is now jakarta.*.
- Updated Lockdown Guide: Adobe publishes a ColdFusion 2025 Lockdown Guide for hardening new installs.
- Language and platform additions: Subscription licensing, new spreadsheet and CSV functions, and charting enhancements.
- Removals: Flash/Flex, the CFMX_COMPAT encryption algorithm, Axis1, COM/DCOM and other legacy features are gone.
JDK 21 is required. Stick with the latest patch release for security and performance.
Adobe's ColdFusion 2025 support matrix lists JDK 21 for both Standard and Enterprise. Check Adobe's current support matrix and your JDK vendor's license terms before choosing a JDK build for production.
- Oracle JDK 21: the only JDK Adobe supports. Adobe licenses Oracle Java for use with ColdFusion (and only with ColdFusion), so ColdFusion customers do not need a separate Oracle Java SE license to run it with ColdFusion. Standalone Java use is not covered.
- Other OpenJDK builds (such as Eclipse Temurin or Amazon Corretto): not officially supported by Adobe.
Source: Charlie Arehart: Java versions supported by ColdFusion versions
The short answer: 50-70% of available system RAM for the JVM heap.
The real answer: it depends on your application. Start with 4-8GB for production, monitor actual usage, and adjust from there. Don't guess; use tools like FusionReactor or Adobe's Performance Monitoring Toolset (PMT) to see what your application actually needs.
See the JVM & Tomcat Tuning Guide for the full methodology.
Yes. ColdFusion 2025 runs well in containers. Adobe provides official Docker images, and the platform supports the stateless deployment patterns that Kubernetes expects.
The main considerations are externalizing your configuration and session storage (typically to Redis). Get those right and ColdFusion scales horizontally like any other containerized application.
The Containerization Guide walks through the full setup.
Think of cfpm like npm for ColdFusion. It's a command-line tool that lets you install only the features you need: PDF services, image processing, whatever your application requires.
The security benefit is real: features you don't install can't be exploited. For production deployments, use cfpm to keep your installation lean.
The CFPM Package Management Guide covers the commands you'll use most.
Security updates: Immediately. Within 48 hours. No exceptions.
Cumulative updates: Test in staging within 30 days, deploy to production within 60. Don't let them pile up.
JDK patches: Stay current. Security vulnerabilities in Java affect ColdFusion too.
Subscribe to Adobe Security Bulletins so you know when patches drop.
Start with the Adobe ColdFusion 2025 Lockdown Guide. Run it on every installation. It closes vulnerabilities attackers know about.
Beyond that:
- Use cfpm to remove features you don't need
- Restrict /CFIDE/administrator access by IP
- Configure secure session cookies (HttpOnly, Secure, SameSite)
- Set up your web server connector correctly; don't expose CF ports directly
- Stay current on patches
The Security Baseline Guide has the full checklist.
Yes, but the effort varies significantly based on where you're starting. CF 2018 and CF 2021 are both past the end of Adobe support (CF 2021's extended support ended November 10, 2026), so neither receives security updates.
From CF 2021 or CF 2023: Usually manageable. Test thoroughly, especially around JDK 21 compatibility.
From CF 2018: More involved, because the JDK jump is bigger.
For every source version: CF 2018, 2021 and 2023 all run on Tomcat 9 (javax.*) (Adobe: CF 2018 Update 1, CF 2021 Update 11, CF 2023 Update 26). CF 2025 runs on Tomcat 10.1, and Tomcat 10 moved the servlet APIs from javax.* to jakarta.*, so custom Java integrations, servlet filters and JSP code that use javax.* servlet classes need updating.
For both: run Adobe's Code Analyzer first. It flags compatibility issues before you discover them in production.
FusionReactor is the gold standard: deep ColdFusion integration, real-time profiling, and production debugging. It's worth the cost for any serious deployment.
Alternatives:
- SeeFusion: Good ColdFusion-specific metrics at a lower price point
- New Relic / AppDynamics: Work fine if you're already using them for other applications
- Performance Monitoring Toolset (PMT): Adobe's own tool, included with both Standard and Enterprise and installed separately; the old Server Monitor was removed in ColdFusion 2018
The Performance Monitoring Toolset Guide compares your options.
Absolutely. ColdFusion makes an excellent API backend for React, Vue, Angular, or whatever your frontend team prefers.
The pattern that works best: ColdFusion serves JSON APIs, your JavaScript framework handles the UI. ColdFusion's REST capabilities are mature, and WebSocket support handles real-time features when you need them.
You don't have to choose between "legacy" and "modern"; ColdFusion plays well with both.
ColdFusion supplies JDBC drivers for its built-in driver types, which include MySQL, PostgreSQL, SQL Server, and Oracle. Adobe's buying guide lists Enterprise Database Drivers as Enterprise-only, so check which driver types your edition offers.
That said, update them. The bundled drivers work, but database vendors release security patches and performance improvements regularly. Download the latest drivers from your database vendor and drop them in.
The Datasources & JDBC Guide shows you how.
Start with the basics, since they have the biggest impact:
- Size your heap correctly: Measure, don't guess. Too small causes OutOfMemory errors; too large causes GC pauses.
- Enable trusted cache: Eliminates filesystem checks on every request.
- Configure your datasource pools: Size them based on actual concurrent usage.
- Set up monitoring: You can't optimize what you can't measure.
The JVM & Tomcat Tuning Guide walks through the full process.
Standard covers most use cases. Enterprise adds features such as multiple server instances, instance clustering, API Manager, and the Security Code Analyzer, plus external cache engines such as Redis or Memcached for caching (Charlie Arehart's comment on the Adobe ColdFusion portal). Redis session storage is available in Standard too (Charlie Arehart on Redis sessions). Adobe's buying guide has the full edition comparison.
ColdFusion 2025 is subscription-only. Perpetual licensing is no longer available for this version.
The Developer Edition is free for development and testing. Use it to evaluate before you buy.
Details in the Licensing & Activation Guide.
Yes. Adobe continues to invest in ColdFusion with regular releases, and 2025 is proof of that. You get quarterly security updates, ongoing feature development, and enterprise support options.
The community remains active too: user groups, the CFML Slack, online meetups, and a solid ecosystem of tools and frameworks.
ColdFusion isn't going anywhere.
Adobe's ColdFusion 2025 support matrix lists Apache and IIS, both connected through Adobe's web server connectors:
- Apache (2.4.62 and later): Most common setup. Mature connector, well-documented.
- IIS 10: Native choice for Windows environments, using Adobe's ISAPI-based connector.
Adobe's web server connector documentation covers Apache and IIS and does not mention nginx. Teams that use nginx run it as a reverse proxy in front of ColdFusion and own that configuration themselves.
For development or small deployments, the built-in Tomcat works fine on its own.
The Web Server Connectors Guide covers the setup for each.
Still have questions?
Some questions need more than a FAQ answer. Convective's team can walk you through installations, optimizations, security reviews, and whatever else you're facing with ColdFusion 2025.
Get in touch