Skip to main content
Inspiring
January 27, 2010
Answered

CFSCHEDULE gives "Connection Failure: Status code unavailable"

  • January 27, 2010
  • 2 replies
  • 3685 views

G'day

I've got a template being called as a scheduled task (via <cfschedule>).  On my local dev environment, it runs fine.  On the production server it errors with:

Connection Failure: Status code unavailable

Stack trace:

coldfusion.tagext.net.HttpTag$HttpConnectionFailureException: Connection Failure: Status code unavailable      at coldfusion.tagext.net.HttpTag.connHelper(HttpTag.java:975)      at coldfusion.tagext.net.HttpTag.runCall(HttpTag.java:1090)      at coldfusion.scheduling.CronTabEntry.runCall(CronTabEntry.java:561)      at coldfusion.scheduling.CronServiceImpl.runCall(CronServiceImpl.java:308)      at coldfusion.tagext.lang.ScheduleTag.doStartTag(ScheduleTag.java:515)      at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:2661)      at cfscheduletasks2ecfm1737508129.runPage(D:\inetpub\wwwroot\travel\app_templates\admin\cfadmin\scheduletasks.cfm:29)      at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:196)      at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:370)      at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)      at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:279)      at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:48)      at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40)      at coldfusion.filter.PathFilter.invoke(PathFilter.java:86)      at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70)      at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)      at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)      at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46)      at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)      at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)      at coldfusion.CfmServlet.service(CfmServlet.java:175)      at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)      at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)      at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)      at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)      at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)      at jrun.servlet.FilterChain.service(FilterChain.java:101)      at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)      at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)      at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)      at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)      at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)      at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)      at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

Other tasks on the production server run fine, as did this one up until this week (no changes to the code in that time, and no environmental changes that I'm aware of).

It's not the code in the template being called, because I factored that right down to a single <cfset>:

<cfset foo="bar">

And there's no Application.cfm consideration as I've put a "blocking" one in the same dir.

There's a bit of stuff on Google about this sort of thing, but none - that I've found - relate to my issue here.  I continue to google...

I'm not sure how to troubleshoot this, really... scheduled tasks have always just worked for me in the past, so haven't had any practise fixing problems.

Any thoughts?

Cheers.

--

Adam

    This topic has been closed for replies.
    Correct answer Adam Cameron.

    Groan: PEBKAC.

    Didn't notice that that box doesn't listen to port 80 for internal traffic, needed to use a different port.

    That took three hours to realise...

    What a tw@t.

    --

    Adam

    2 replies

    Adam Cameron.AuthorCorrect answer
    Inspiring
    January 27, 2010

    Groan: PEBKAC.

    Didn't notice that that box doesn't listen to port 80 for internal traffic, needed to use a different port.

    That took three hours to realise...

    What a tw@t.

    --

    Adam

    Participating Frequently
    January 27, 2010

    Is the scheduled task calling a domain different from the others?  Maybe a firewall or networking change prevents CF server from connecting?  CF also caches DNS (actually it is java) so if any IP changes have happened CF may be looking in the wrong server or place.  A restart of CF will clear that cache.

    Inspiring
    January 27, 2010

    Nah, it's just running as localhost (same as the others that are still working fine).

    I can't restart the CF service without scheduling it with the network support bods (I don't manage this particular server), which requires a fairly good explanation.

    Cheers for the suggestion though...

    --

    Adam