Ubuntu coldfusion2025 PDFManager not working

[iclark3509]

I am trying to get the PDF manager to work on coldfusion 2025 (developer addition) running on Ubuntu with Apache web server. I did the full GUI install (ColdFusion_2025_GUI_WWEJ_linux64.bin ) select developer addition, all add ons etc. Did no install the separate addons download. So jetty is instslled under cfusion.

After installation I can verify the PDF  Manager ( in my case the install changed the port to 8999). Like some other post I have seen I was seeing the unregistered in the log. Selecting edit and saving without any changes allowed me to verify and provided the reghistered log item:

May 2, 2025 07:15:06 AM Information [http-nio-8500-exec-4] - PDFg service manager http://127.0.0.1:8997/PDFgServlet/ unregistered.
May 2, 2025 07:15:06 AM Information [http-nio-8500-exec-4] - PDFg service manager http://127.0.0.1:8997/PDFgServlet/ registered.

I do have it connected to appache anbd the web root is set so in a file called test.cfm I have:

<cfhtmltopdf>
<h1>Hello World</h1>
</cfhtmltopdf>

When I naviage here (http://localhost/library/pfdf/test.cfm) the server tings about it and finally display this:

http://localhost/library/pfdf/test.cfm?&__&__&__&__&__&__&__&__&__&__&__&__&__&__&__&__&__&__&__&__&...

There is nothig written to the coldfusion or Jetty logs!! I an at a loss as to why. Previously I have used windows with no issues. But I need it to run on linux for a customer. Does any body have any ideas as to what is going on?

[AbhishekJha]

@iclark3509 Please reach out to cfsup@adobe.com

Thanks,

Abhishek

[BKBK]

@iclark3509  and @AbhishekJha , I hope you did eventually identify and resolve the issue. If so, could you please share?

[iclark3509 · Accepted solution]

I did not get an answer from Adobe but I found that PDFReactor required a JVM setting if it was not running with a graphicl inferface. So in the jetty start.ini I added -Djava.awt.headless=true restarted Jetty and it worked. Ubuntu has a GUI so it kind of threw me as to why this would work. But in did. This was on a developer addition of ColdFusion2025. I then had a docker container with coldfusion2023 that had the same issue. I checked it heare and it worked as well.

So for now this appears to be resolved.

[BKBK]

Thanks for sharing your solution, @iclark3509 .