I've got a current hotfix issue. Both our production and staging are ACF2021. I updated both (cmd prompt java command) to the latest hotfix today, and we've lost the PDF service. In talking with charlie, the first thing we noticed is that jetty-ipaccess.xml was missing, as was the entire jetty/etc/extra folder. I then tried a couple 2023 ACFs and the same thing. When verifying the PDF service from CFAdmin we get:

Apr 24, 2025 16:33:53 PM Error [http-nio-8501-exec-8] - Connect to 127.0.0.1:8993 [/127.0.0.1] failed: Connection refused: connect <http://127.0.0.1:8993/PDFgServlet/verify>
Apr 24, 2025 16:33:53 PM Error [http-nio-8501-exec-8] - Connection verification failed.
Apr 24, 2025 16:33:54 PM Error [http-nio-8501-exec-9] - Connect to 127.0.0.1:8993 [/127.0.0.1] failed: Connection refused: connect <http://127.0.0.1:8993/PDFgServlet/verify>

The ACF 2023 also needed the neo-document.xml edited to put in the

<var name='engine'>
  <string>PdfReactor</string>
</var>

So now I can get the PDF page to load in admin, but it gives the same connection refused error. So to recap, 4 servers - 2x ACF2021 and 2x ACF2023 (3 standard, 1 dev license) all had their PDF service seemingly broken by this update. Any ideas??

Did you not yet try installing the refreshed add-on installer? Even if left in the alternative folder, not installed into cfusion/jetty? It would listen on a different port and you'd point a new "pdf service" at that.

I haven't tried that yet - will give that a go tomorrow here at home. At least this machine I can uninstall and reinstall from scratch since it's just dev.

Yep. In the meantime, sure, maybe someone here has more insight into this issue that is affecting some people

Woah!!! In CFAdmin I changed the port from 8993 to 8995 and it verified! I did notice in jetty/start.ini the jetty port was 8995 too.

In the one in cfusion/jetty? That should not have changed because of the cf update, if you may be wondering that. Anyway, all sorted for now?

yes cfusion/jetty/start.ini is 8995. my guess is that a previous ACF2021 install had 8993 and when installing ACF2023 it read that file and picked 8995 maybe? Looks like I'm down to a local code error so I'm going to put this aside for now and will mess with staging tomorrow and see if we have the same port discrepancy there since those machines originally had ACF2016 on them.

Ok, wait. As I'd shared with you by email before you opened this thread, the pdfreactor error was because you'd imported your settings (or neo-document.xml itself) from your previous version. That's what also brought that 8993

So I just took a look at staging (ACF2021). Both start.ini and the PDF service were 8993, but the add on service wouldn't start. I changed both to 8995, restarted ACF and then was able to start the add on service. But it still failed the validation even after doing an edit / make no changes. I'll keep digging further tomorrow morning.