Skip to main content
Known Participant
July 22, 2018
Answered

ColdFusion 10 Scheduled Task

  • July 22, 2018
  • 1 reply
  • 1310 views

I have a scheduled task in CF 10. It has been running successfully however, now it runs but actually it does not. The scheduler log says it is triggering but actually does not. When the task's URL accessed directly from browser the CF page actually get executed.

The scheduled task calls all other tasks using CFHTTP.

Any advise would be of great help on what could be the issue with scheduled task. I have restarted the CF instance with no success. The log set in the task says "Connection Failure".

This topic has been closed for replies.
Correct answer Charlie Arehart

Try running the URL (of the task) in a CFHTTP call, and dump the cfhttp variable after that, to see what happens.

And you ARE confirming that it’s an https url? You probably WILL find that it’s about an issue of the JVM underlying CF having an issue with the SSL/TLS support of the server being called (in the URL). It MAY be that you need a certificate added to CF (to the JVM underlying CF), if the site you’re calling has something requiring you to have a client cert in CF.

But more typically it’s just that the TLS/SSL support in the server being called has changed and is now of a level which the underlying CF JVM can’t support. In such cases, the solution nearly always is just a need to update the JVM CF is using, especially to Java 8. You mention being on CF10. The JVM CF originally came with was Java 6 (1.6). Later installers (in 2013) updated it to Java 7. And CF10’s update 14 also allowed you to update to Java 8. More at https://coldfusion.adobe.com/2014/10/coldfusion-10-and-11-support-with-java-8/.

And if you try to update the JVM and have trouble, consider the many possible problems and solutions that I outline in a blog post here:

http://www.carehart.org/blog/client/index.cfm/2014/12/11/help_I_updated_CFs_JVM_and_it_wont_start

/charlie

1 reply

Community Expert
July 22, 2018

When you say the task's URL is accessed directly from the browser, do you mean a browser on the same machine running CF, or another machine? It's common for servers not to have access to the same DNS records as workstations do.

Dave Watts, Fig Leaf Software

Dave Watts, Eidolon LLC
BhaveshKPAuthor
Known Participant
July 23, 2018

@Dave Watts: No,I accessed the URL from another machine. After searching I found somebody mentioned that it may be because of SSL certificates updated in IIS but not in cacerts file. In my case, I am not sure if SSL certificates were updated and I believe the certificates have been updated in past but this issue was not there.

Thank you for your reply.

Charlie Arehart
Community Expert
Charlie ArehartCommunity ExpertCorrect answer
Community Expert
July 24, 2018

Try running the URL (of the task) in a CFHTTP call, and dump the cfhttp variable after that, to see what happens.

And you ARE confirming that it’s an https url? You probably WILL find that it’s about an issue of the JVM underlying CF having an issue with the SSL/TLS support of the server being called (in the URL). It MAY be that you need a certificate added to CF (to the JVM underlying CF), if the site you’re calling has something requiring you to have a client cert in CF.

But more typically it’s just that the TLS/SSL support in the server being called has changed and is now of a level which the underlying CF JVM can’t support. In such cases, the solution nearly always is just a need to update the JVM CF is using, especially to Java 8. You mention being on CF10. The JVM CF originally came with was Java 6 (1.6). Later installers (in 2013) updated it to Java 7. And CF10’s update 14 also allowed you to update to Java 8. More at https://coldfusion.adobe.com/2014/10/coldfusion-10-and-11-support-with-java-8/.

And if you try to update the JVM and have trouble, consider the many possible problems and solutions that I outline in a blog post here:

http://www.carehart.org/blog/client/index.cfm/2014/12/11/help_I_updated_CFs_JVM_and_it_wont_start

/charlie

/Charlie (troubleshooter, carehart. org)