Brian Parks
04/24/2025, 4:27 PMSteve Logan
04/24/2025, 8:36 PMApr 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??Slackbot
04/24/2025, 8:40 PMJoseph Bullock-Palser
04/24/2025, 8:45 PMjgladnick
04/26/2025, 4:55 PMDaniel Mejia
04/26/2025, 4:57 PMDaniel Mejia
04/26/2025, 4:59 PMDaniel Mejia
04/26/2025, 5:02 PMjgladnick
04/26/2025, 5:02 PMDaniel Mejia
04/26/2025, 5:02 PMDaniel Mejia
04/26/2025, 5:05 PMBill Nourse
04/27/2025, 8:08 PMPatrick S
04/28/2025, 1:40 PMalholden
04/28/2025, 3:27 PMzackster
04/29/2025, 9:20 AMsalted
04/30/2025, 6:28 PMMaria Jose Herrera
05/01/2025, 1:21 PMGaurav Sharma
05/01/2025, 1:34 PMsalted
05/01/2025, 4:54 PMalholden
05/01/2025, 9:51 PMThe column name "EMPLOYEE_ID" is invalid. Column names must be valid variable names. They must start with a letter and can only include letters, numbers, and underscores.
gunnar
05/02/2025, 1:41 PMBill Bell
05/02/2025, 3:20 PMchinh
05/02/2025, 6:56 PMcfhtmltopdf(
source = "https://www.google.com/",
destination = "sample.pdf",
overwrite = true
);
May 2, 2025 113436 AM Information [ajp-nio-127.0.0.1-8122-exec-3] - PDFg service manager http://127.0.0.1:8995/PDFgServlet/ registered.
May 2, 2025 113852 AM Error [ajp-nio-127.0.0.1-8122-exec-5] - Error occurred while generating PDF.Steve Logan
05/06/2025, 12:48 PM"Information","DefaultQuartzScheduler_Worker-1","05/06/25","07:40:00","","Starting HTTP request {URL='<https://www.xyz.com/app/jobs/college/generate_daily_files.cfm>', method='get'}"
"Information","DefaultQuartzScheduler_Worker-1","05/06/25","07:47:57","","HTTP request completed {Status Code=200 ,Time taken=477114 ms}"
"Information","DefaultQuartzScheduler_Worker-1","05/06/25","07:40:00","","Task SDQ.SDQ - generate_daily_files.cfm triggered."
"Information","DefaultQuartzScheduler_Worker-4","05/06/25","07:50:00","","Task SDQ.SDQ - generate_daily_files.cfm triggered."
However, the job actually runs 2 additional times about 2 minutes after the first (correct) kicks off, and then about an additional 2 minutes. We added a simple email to send start time, end time, browser agent and a url flag:
1 0506_082200 Started (this is the scheduled start of the job)
2 0506_082200 Browser Agent = CFSCHEDULE
3 0506_082200 URL.job = cdf
1 0506_082357 Started (not scheduled)
2 0506_082357 Browser Agent = CFSCHEDULE
3 0506_082357 URL.job = cdf
1 0506_082657 Started (not scheduled)
2 0506_082657 Browser Agent = CFSCHEDULE
3 0506_082657 URL.job = cdf
These two extra runs are not logged in http.log or the cfscheduler log file. If you run it directly from the URL it runs correctly - one and done as expected. Any ideas on why the task scheduler seems to be running this job extra times and how we can get around that?Dave Merrill
05/06/2025, 2:58 PMemmet
05/07/2025, 4:30 PMzackster
05/08/2025, 6:17 PMBill Bell
05/08/2025, 9:03 PM