The Adobe team should, in any case, do a review of the changes in log4j (implementation, configuration and settings) in Update 13 of ColdFusion 2021.  ... View more

True, manually deleting the Felix cache folder has the same aim as running cfpm purgecache. However, the two methods work differently.   The first is done manually by the developer. on the Operating System. The second is performed programmatically by the ColdFusion Package Manager application. The two scenarios are therefore different. Since there is an issue with packages, of which we don't know the cause, it makes sense to try both ways of purging the Felix cache. ... View more

Hi Simon, Alas, no. It is not accepted practice to update Apache Tomcat directly in Coldfusion 2023 yourself. The reason is complexity. You don't know - and so cannot take care of - the many dependencies that must be satisfied when Tomcat is integrated in ColdFusion.   The Adobe team knows, of course. Which is why it is their responsibility to update the Apache Tomcat version.  ... View more

@Ali Sozkesen  Can you please DM me and I will share my email ID with you? So we can take this offline and share this with engineering.  By @Priyank Shrivastava.   Hi @Priyank Shrivastava. , could your colleagues in engineering please look into my earlier suggestion: @BKBK: "I suspect that this has to do with the recent changes in log4j. So ... review the settings within /lib/log4j.properties,  /lib/log4j2.properties and /lib/logging.properties, as well as the required JVM flags."   ... View more

Hi Simon, thanks for the alert. The current fix for "important" issues is Apache Tomcat 9.0.98 ... View more

At this point I would also suggest, as does Charlie, that you: delete ColdFusion2021\cfusion\bin\felix-cache, and then restart ColdFusion.   If the errors continue, then that would suggest that the manual process isn't working properly. There is another way.   Do the following (to purge the Felix cache programmatically): Stop ColdFusion. Open the Command Prompt (cmd) as Administrator; Use the DOS cd command to navigate to  {CF2021_HOME_DIR}/cfusion/bin; Type cfpm and press ENTER. You should get ColdFusion's package manager prompt cfpm; Type purgecache and press ENTER. (This runs the command to purge the Felix cache)  Restart ColdFusion.   Is everything OK now? ... View more

Hi @harshp_0559 , the object-instantiation error makes me wonder whether some packages, such as those required for Mail and Print, are missing. I would therefore suggest that you install all the packages. At least, to start with.  Assuming you are on Windows, you could do the following: Open the Command Prompt (cmd) as Administrator; Use the DOS cd command to navigate to  {CF2021_HOME_DIR}/cfusion/bin; Type cfpm and press ENTER. You should get ColdFusion's package manager prompt cfpm; Run the command install all   5.  Keep running the command install all till the result is either an irreversible error or ColdFusion tells you that "All the packages are already installed". 6. If the former, then share the error message with the forum. If the later, then restart ColdFusion in the usual way, and you're set to go. ... View more

Hi @calm_Eagle3816 , thanks for the update. ... View more

Could it be that the CF2021 installation is using a mapping of some sort? One way to find out: run the following on a CFM page <cfset scriptsDirPath=expandPath('\MyScriptDir')> <cfif directoryExists(scriptsDirPath)> <cfoutput> <p>The scripts directory is #scriptsDirPath#.<p> </cfoutput> <cfelse> <cfoutput> <p>The scripts directory #scriptsDirPath# does not exist.<p> </cfoutput> </cfif>   ... View more

Hi @rickmaz , The cfmx_compat algorithm has served ColdFusion well, but is no longer secure and so is due for change. Therefore I would strongly advise you to replace it with the new algorithms. It is definitely not waste and pain. Improving your code in this way is actually an investment in the long run.    Not only ColdFusion, but every programming language evolves. Generally for the better. We, developers, should therefore expect to change our software as time goes on.   In fact, if you think that you can avoid such maintenance, you are mistaken. Benjamin Franklin once wrote to a friend, "... in this world nothing can be said to be certain, except death and taxes". That is also true in the world of software: nothing can be said to be certain, except maintenance costs and end-of-life.    Research shows that 60 to 80% of the total lifecycle costs of a software application is spent on maintenance. For further information on this research, see the following: Software Engineering Economics and COCOMO research by Barry Boehm Software Maintenance: Concepts and Practice, by Penny Grubb and Armstrong A Takang Software Cost and Effort Estimation: Current Approaches and Future Trends, by IEEE ... View more

Excellent innavations. To maintain compatibility with old applications, will it be possible to use Java17 or not? By @Paolo Olocco Short answer: no. By this I mean: it might be possible, but it wouldn't be a good thing.   Your question mixes two separate factors: compatibility and version. Java and ColdFusion are two separate programming languages. ColdFusion's compatibility - backward or forward - depends on the ColdFusion version and Java's compatibility depends on the Java version. You should not mix the two.    However, ColdFusion uses Java. As such, it evolves along with the Java version. Any big changes in the Java language, such as in security or in the HTTP/TCP protocols, will have an impact on ColdFusion. That way, ColdFusion continually benefits from the new advances and features in the Java language.   That is the reason why new ColdFusion versions are customarily optimized to run on a recent Java version. Hence, if ColdFusion 2025 is designed to run on Java 21, it will be sub-optimal to run it on Java 17. ... View more

What version java jdk did you install? By @calm_Eagle3816    Java SE 11.0.25 (LTS) ... View more

Historic changes involving quite some pruning. Good work, Team Adobe! ... View more

The original problem shows the importance of doing updates in time - and across the board, too. So I would do the following:  Update ColdFusion 2021 to the latest update level, which is Update 17.  Update the Java on which ColdFusion 2021 runs to the latest official version, Java SE 11.0.25 (LTS).  Include the required security certificates. ... View more

OK.  I can confirm that I have tested your other jvm.config settings, and they work without any problems. ... View more

I don't think that Djdk.lang.Process.allowAmbiguousCommands had anything to do with ColdFusion not starting.   I repeat my suggestion: your jvm.config setting   Java.home=C:\\Programfiles\\java\jdk-11   is likely incorrect.   Try instead:   java.home=C:\\Program Files\\Java\\jdk-11   Please let us know whether that resolves the issue of ColdFusion starting. That is important information to share with us, fellow developers. ... View more

Is it now possible to start ColdFusion? ... View more

Try   java.home=C:\\Program Files\\Java\\jdk-11     ... View more

I have given you a suggestion about that. A mistake probably occurred in jvm.config when you modified it. The most likely culprit is the setting java.home. ... View more

The Coldfusion application service did not start   By @calm_Eagle3816 That means there is likely an error in the settings in jvm.config. Take a good look at the contents of the file.  Could you share the contents with the forum? ... View more

The logs might tell you why ColdFusion didn't start. So, what do the logs say?  ... View more

@brado70491931 , ColdFusion uses version 4 of CKEditor. To see this, launch the following URL - or its equivalent - in a browser: http://127.0.0.1:8500/cf_scripts/scripts/ajax/ckeditor/samples/ .   Relatively speaking, version 4 isn't old, since the current version of the editor is CKEditor 5. What is important is to address any vulnerabilitiy that a CKEditor version may have. That is what Update 13 of ColdFusion 2021 did.  ... View more

A further insight: the ColdFusion Performance Monitoring Toolset (PMT) includes integration with an ElasticSearch client. PMT uses ElasticSearch as the backend for indexing and searching logs, metrics and performance data.    So, do you use the ColdFusion Performance Monitoring Toolset (PMT)? If so, then that is most likely where the error came from.   For example, a previous thread in this forum talks about an error caused by the ElasticSearch sniffer used by PMT.  The solution there was to shut down both the local PMT service and the datastore, and to restart the ColdFusion instance. It might, in addition, be necessary to make some configuration changes. The thread explains how. ... View more

In which log file(s) does the error appear? The issue does not seem to be related to the ColdFusion server. Rather, to a client 'ElasticSearch' application running on the ColdFusion server.   Apparently, the issue arose because an external service failed to connect with the ElasticSearch client. Do you make use of ElasticSearch Sniffer?   ... View more

    Then clicked Update and instead of updating, it removed the PDF service altogether.   By @AdeptDeveloper   Removing the last PDF Service Manager? That points to a serious problem right there. I expect ColdFusion to hang on to at least one PDF Service Manager, and to prevent you from deleting the last one.   Those retries you did might have upset the settings. I would therefore suggest a reset of the PDF engine.   Try the following steps and see if they help:  In the ColdFusion Administrator, go to the page Server Settings. Check whether the setting 'Default ScriptSrc Directory' is correct. The default is /cf_scripts/scripts/ (relative to the web root). Incorrect values have been known to cause PDF problems.  Next, proceed to reinstall the PDF packages. Go to the page Data & Services > PDF Service. Click on the 'Disable' button to temporarily disable the PDF Service Manager.  Open the command prompt (CMD) as administrator;  Use the DOS command CD to navigate to C:\ColdFusion2023\cfusion\bin;  Type cfpm.bat and press ENTER. That should bring up ColdFusion's Package Manager tool.  Type install all and press ENTER. The Package Manager should then temporarily install all packages.  Type update packages and press ENTER, instructing the Package Manager to update all packages. When ColdFusion finishes, type quit and press ENTER.  Close the CMD window.  Restart ColdFusion 2023.   Open Windows Services and restart the ColdFusion 2023 Add-on Services.  Open the ColdFusion Administrator and return to the page Data & Services > PDF Service. Click on the 'Enable' button, then on the button 'Verify All Service Managers'. You should get Connection Status 'OK' .    Run @jascomp 's test code: <cfhtmltopdf orientation="landscape"> <h3>Test Landscape Output</h3> </cfhtmltopdf>​ Does that work as expected? ... View more

  I even had the same issue with error adding PDF service manager and then restarted and it came back.   By @AdeptDeveloper You should have updated the existing PDF Service Manager, instead of adding a new PDF Service Manager. See my previous post. An attempt to add a new service manager might result in settings that differ between the servers. ... View more

Timely support, @Vikram Kumar M . ... View more

  You say, "...I then proceeded to set the alias for the CF_SCRIPTS folder (and added server mapping and MySQL datasources).". However, when I read that, it is unclear to me what you actually did.  Could you please explain what you actually did, for example, in steps. ... View more

Hi @Priyank Shrivastava. , On the Prerelease website, the current instructions for installing the VS Code extension are still unclear. That is partly because the word "extension" has a double meaning in this case.   Please replace the instructions with something similar to what you've given here: 1. The VS Code Extension for ColdFusion Next is offered as a .ZIP download. Download it . 2. Change the file-extension from .ZIP to .VSIX. 3. Launch the VS Code program and use the .VSIX file to install the VS Code Extension for ColdFusion Next. ... View more