Anyone know how to get the latest JVM update for ColdFusion 2023? We are experiencing a PKIX path building failed error. Thanks!

Hello all! We are looking for more speaker submissions for this year's 30th Anniversary edition of CFSummit in Vegas. We have some already, but are looking for more. While these tracks are not locked in stone yet, you can use them generally to fit your talk into a theme: Track 1: ColdFusion Mastery This track focuses on learning the essentials of how to program in Adobe ColdFusion in a modern and scalable way. You can submit talks that range from Junior to Master level, as long as you are teaching ways to output excellent, high quality code and leveraging ColdFusion to it's max. Get creative! Track 2: ColdFusion Product & Architecture Here we move a bit past the baseline of coding and into how ColdFusion can be optimized, architected, integrated, and batched. We are looking for how to create workflows, leverage ColdFusion in enterprise environments, push the limits of cloud integrations, and more. These talks can discuss server level items, databases, cloud products, security, enterprise suites, etc. Track 3: AI Push past the basics. We've all seen the "hey copilot can write cf" talks. We want to dive deeper. Talk about metrics. Training. Big integrations. These talks can explore AI as adjacent to ColdFusion, can delve into the core concepts of the architectures which underpin AI, or even explore team culture shifts and adaptations to where AI is heading in software development. Show us how you're incorporating AI in your SDLC, your CI/CD, your security, your team development workflows. And beyond. Speakers receive a free room at Resorts world for their stay, as well as a generous speaker gift (and there's a nice speaker dinner the day before summit starts). Come be a part of this historic 30th anniversary celebration of ColdFusion! Submit your talk proposals here: https://cfsummit.adobeevents.com/speaker-application/

So - we applied Update 20 to our CF2021 environment - and of course (because legacy code) - we have an issue with the "remote method parameters" change. SO... Per the instructions - we tried to implement the "-Dcoldfusion.runtime.remotemethod.matchArguments" JVM flag and set it to false. THAT apparently breaks the isapiredirect connection with IIS. WHen I look at the isapiredirect logs - it says it can't connect to the backend and that Tomcat is likely down. So - my question is - is there a known issue with that JVM flag?

I'm pretty sure there was an HTMX video posted here a while ago - if I'm not hallucinating can someone provide a link? I've watched several videos but they tend to be pretty basic examples, I'm interested in doing CRUD, search and paging with HTMX for the many maintain screens we have. Thanks! (I'm also looking at cbwire - a livewire port - which has so far been very interesting)

FYI tracker appears to be broken.

Just updated ACF2025 to Update 2 and now getting this when using cfhtmltopdf: coldfusion/image/Image The specific sequence of files included or processed Tried restarting, reconnecting the PDF service, etc. Nothing. I'm so frustrated with these latest round of updates.

Anyone had issues with encrypted PDF's post Cf2021 update 20 (from 18 -> 19 -> 20 + 18 -> 20 ) ? the whole pdf system was broken to begin with but now its just encrypted PDF's not working. Have done the following so far (so many files missing....) 1. Delete /cfusion/bin/felix-cache folder (will require an eventual CF restart to rebuild - fixes an ORM error) 2. Copy \cfusion\jetty\etc\extra\jetty-ipaccess.xml -> \cfusion\jetty\etc\jetty-ipaccess.xml (add on service threw an error and wouldnt start before this) 3. Add bcprov-jdk15on-1.53.jar -> \cfusion\wwwroot\WEB-INF\lib\ 4. Add bcprov-jdk15on-153.jar -> \cfusion\jetty\webapps\PDFgServlet\WEB-INF\lib 5. Add xalan.jar -> \cfusion\lib

I'm seeing a behavior on 2021.0.20 where, on startup, my clients scheduled tasks which write to a log file all log something along the lines of this in the

scheduler.log

file:

Security violation: Scheduled task 'JOB NAME HERE' attempted to execute unauthorized path: c:\websites\temp\my-job-log.html. To allow it, whitelist the path in cf-root/lib/pathfilter.json against key schedulerexecutionpaths.

And then all of the scheduled tasks are DELETED right out of the

neo-cron.xml

! 😳 Is this a new behavior? Does anyone have a link handy to where it's documented? Do all output logs have to be whitelisted, or are some allowed by default? More in 🧵

"Jun 4, 2025 093432 AM Error [http-nio-32000-exec-7] - Function checkAdminCredentials does not support PASSWORD as an argument in F:\ColdFusion2023\cfusion\wwwroot\CFIDE\lockdown\lockdown.cfc The specific sequence of files included or processed is: F:\ColdFusion2023\cfusion\wwwroot\CFIDE\lockdown\lockdown.cfc''" I got this error message, if i try to install the auto lockdown on coldfusion 2023. the Installer says "Entered credentials for ColdFusion administrator are incorrect", but the credentials are correct.

Anyone else using CF to populate PDF formfields and seeing an error in the coldfusion-error.log? It doesn't impact the actual populating of the fields and it still flattens the PDFs, so I don't think it's mission critical, but it just writes a log entry in coldfusion-error.log. I wondered if it was CF2025-specific, so I tested in CF2021 and see a similar but different error. First lines of the log entries start: CF 2025:

java.lang.NullPointerException: Cannot invoke "com.adobe.internal.pdftoolkit.core.cos.CosDictionary.get(com.adobe.internal.pdftoolkit.core.types.ASName)" because "iconObject" is null

and then CF 2021:

java.lang.NullPointerException at com.adobe.internal.pdftoolkit.pdf.interactive.forms.PDFFieldNode.setBase64ImgImpl(PDFFieldNode.java:752)

Thought it might be because they were old PDFs so I created one from scratch (using Acrobat 32-bit) and saw the same issue. Sound familiar? Any work-arounds/solutions or just wince and ignore it?

Anybody noticed any oddities with cfhttp making a bunch of calls for one call? I have a call that works the first time, but then, according to the http.log, it repeats the call multiple times, triggering rate limiting on the external API. This worked fine before this last update, but I don't know if it's because UPS changed something, or there's an issue with cfhttp. (This log is from a test page with a single call on it.)

"Information","ajp-nio-127.0.0.1-8022-exec-6","06/05/25","17:34:32","","Starting HTTP request {URL='<https://onlinetools.ups.com/ups.app/xml/Rate>', method='POST'}"
"Information","ajp-nio-127.0.0.1-8022-exec-6","06/05/25","17:34:33","","HTTP request completed  {Status Code=200 ,Time taken=917 ms}"
"Information","ajp-nio-127.0.0.1-8022-exec-5","06/05/25","17:34:34","","Starting HTTP request {URL='<https://onlinetools.ups.com/ups.app/xml/Rate>', method='POST'}"
"Information","ajp-nio-127.0.0.1-8022-exec-5","06/05/25","17:34:34","","HTTP request completed  {Status Code=429 ,Time taken=123 ms}"
"Information","ajp-nio-127.0.0.1-8022-exec-5","06/05/25","17:34:34","","Starting HTTP request {URL='<https://onlinetools.ups.com/ups.app/xml/Rate>', method='POST'}"
"Information","ajp-nio-127.0.0.1-8022-exec-5","06/05/25","17:34:34","","HTTP request completed  {Status Code=429 ,Time taken=84 ms}"
"Information","ajp-nio-127.0.0.1-8022-exec-10","06/05/25","17:34:36","","Starting HTTP request {URL='<https://onlinetools.ups.com/ups.app/xml/Rate>', method='POST'}"
"Information","ajp-nio-127.0.0.1-8022-exec-10","06/05/25","17:34:36","","HTTP request completed  {Status Code=429 ,Time taken=105 ms}"
"Information","ajp-nio-127.0.0.1-8022-exec-10","06/05/25","17:34:36","","Starting HTTP request {URL='<https://onlinetools.ups.com/ups.app/xml/Rate>', method='POST'}"
"Information","ajp-nio-127.0.0.1-8022-exec-10","06/05/25","17:34:36","","HTTP request completed  {Status Code=429 ,Time taken=98 ms}"
"Information","ajp-nio-127.0.0.1-8022-exec-2","06/05/25","17:34:37","","Starting HTTP request {URL='<https://onlinetools.ups.com/ups.app/xml/Rate>', method='POST'}"
"Information","ajp-nio-127.0.0.1-8022-exec-2","06/05/25","17:34:37","","HTTP request completed  {Status Code=429 ,Time taken=104 ms}"
"Information","ajp-nio-127.0.0.1-8022-exec-2","06/05/25","17:34:37","","Starting HTTP request {URL='<https://onlinetools.ups.com/ups.app/xml/Rate>', method='POST'}"
"Information","ajp-nio-127.0.0.1-8022-exec-2","06/05/25","17:34:37","","HTTP request completed  {Status Code=429 ,Time taken=94 ms}"

I'm trying to use the auto-lockdown tool for CF2025, and after it prompts for the administrator login info, it tells me

Entered credentials for ColdFusion administrator are incorrect

. Thing is, I know they aren't. I've copy/pasted the username and password into the Cf admin, and it logs in. Do the same here, and it yells at me.

Anyone else noticed that the new "complex password" requirements in CF2025 no longer allows spaces in the password?

Has anyone ever run into this lovely stack trace while using the Redis package for session storage? Specifically, with CF2023u14 (stack in thread)

is this a known issue? considering the following code, acf 2025 resolves the ternary different than every other engine

bob = 0;
writeOutput(val(bob) ? " <strong>truthy</strong> " : " <strong>falsy</strong> ");
if ( val(bob) ) {
    writeOutput('<strong>i am true</strong>');
} else {
    writeOutput('<strong>i am false</strong>');
}

any other (cf, lucee, bx) = falsy i am false acf 2025 = truthy i am false https://trycf.com/gist/8f25f265335cdf90c03c28d79d951227/acf2025?theme=monokai

Testing our code for compatibility with ACF 2025, and ran into an issue I can't seem to find any info about. We have a virtual directory at the root of a drive, mapped to a document library on another server. ACF 2021 recognizes the virtual directory path as a directory, and directoryExists() comes back TRUE for it. ACF 2025 is seeing it as a file (I assume looking at the symlink) and directoryExists() comes back FALSE for it and any subfolders. This seems to be an undocumented change in behavior. Does anyone have a fix or a workaround?

We are planning to move from ACF 2021 to ACF 2023. On our ACF 2021 server we have been using this for Java garbage collection: -XX:+UseG1GC Our new 2023 install has this (which I believe is the default): -XX:+UseParallelGC We're thinking of changing 2023 to G1GC, but wondered if anyone has any recommendations. Thank you!

I'm working on setting up a new CommandBox-based prod server for a client and I'd like to have them just use the CommandBox feature to manage their java installation, which uses the Eclipse Temurin builds of OpenJDK. This client has a support contract with Adobe in case anything goes wrong with their servers. Does anyone know if it is an issue to use OpenJDK on your servers and get support? In other words, does Adobe require you use the Oracle Java builds specifically, or will they support any version? I don't want to cause them any headaches down the road getting support.

Am I misunderstanding something, or should I be able to have public static variables on a component? (I can get public static methods to work, but variables don't seem to be working for me)

Some deprecation announcements in case you've missed them: IMPORTANT DEPRECATION ANNOUNCEMENT: Updates to COM... - Adobe Product Community - 15348306 If you are currently using these technologies and have comments, questions or concerns, please send detailed inquiries to cf-deprecation@adobe.com.

What's the current license for use of ckeditor with that tag ?

Any plans for Adobe to allow a ColdFusion to be a MCP server for AI? Anyone else working on this?

@Mark Takata (Adobe) what are the chances we can get some kind of remote MCP for CF documentation ?

Coming up starting tomorrow: ColdFusion Developer Week 2025! Don't miss this amazing chance to learn from experts in the community and the developers themselves in a week-long, fully remote, and fully free online conference. You can register here for free: https://adobe-cold-fusion-developer-week-2025.meetus.adobeevents.com/registration/select

Am I right that ColdFusion's only use of Apache Tomcat is for the admin UI?

I have following list of issues while running project over cf2025, could anyone found the similar?

The time has come once again for Mark to disappear for a while. Starting Thursday morning I am on PTO for about 10 days. I'll be pretty darn far out of range of cell phones for a lot of the time (I think). I will be back on the clock on July 7th. If you have issues or needs from me during that time, no you don't lol. If you need to hit someone up during this time, please contact Kishore (Director, marketing) at kishore@adobe.com (marketing related inquiries), Adobe Support cfsup@adobe.com (support questions), or Gaurav Yadav (Manager, world-wide customer success) gyadav@adobe.com for licensing/customer success issues. Thanks all and hope everyone here (in the US) has a good holiday next week.

Greetings, I’m having a problem setting up the server portion of the CFBuilder plugin for VS Code. FWIW, I am running CF2023 using CommandBox on my MacBook Air. What I’m trying to do is set up the sever section of the plugin. In the local server settings, I enter what I thought was the path to server, but I get the following message: Invalid server home When I go into the terminal and type box server info --verbose it gives me Server Home: /Users/larryclyons/.CommandBox/server/A97212312E0187463C865244A087EA30-aces-6090/adobe-2023.0.14.330784 which I assume is the path to the server. Or so I thought. I’m not sure what I’m doing wrong in this case, Any suggestions on getting this resolved will be very appreciated.

Was having some issues with XML validation on CF2021 post update 20 and it seems there is a new argument for

xmlValidate

that is not documented - anyone know where i might find what

parseroptions

might take? CF throws the following on an invalid argument to xmlValidate now: The Valid Parameter for function XMLVALIDATE are [xml, validator, parseroptions]

Is anyone else having some issues with cfpm today? I get the following error for a lot of modules.

An error has occurred while installing the package awss3. Exception : Connect to <http://cfmodules.adobe.com:443|cfmodules.adobe.com:443> [<http://cfmodules.adobe.com/23.64.250.136|cfmodules.adobe.com/23.64.250.136>, <http://cfmodules.adobe.com/2600:1407:1800:496:0:0:0:1efd|cfmodules.adobe.com/2600:1407:1800:496:0:0:0:1efd>, <http://cfmodules.adobe.com/2600:1407:1800:494:0:0:0:1efd|cfmodules.adobe.com/2600:1407:1800:494:0:0:0:1efd>] failed: Network is unreachable (connect failed)