tracker issue : CF-3815267

select a category, or use search below
(searches all categories and all time range)
Title:

Scheduled Tasks Firing but Return 404

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/NotABug

Reporter/Name(from Bugbase): Stephen Walker / Stephen Walker (Stephen Walker)

Created: 08/29/2014

Components: Scheduler

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Win 2008 Server R2 64 bit

Vote Count: 0

I have multiple scheduled tasks that I migrated from CF10 to CF11 that no longer function properly.  The scheduled task appears to fire on schedule, but in looking at the coldfusion-out log they are returning status code 404.  The scheduled task files can be browsed on the server and remotely and work properly without error.

The only work around is to manually browse the page which sort of defeats the purpose.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3815267

External Customer Info:
External Company:  
External Customer Name: Stephen.Walker
External Customer Email:  
External Test Config: Windows 2008R2 -64bit VM

16GB RAM

4 VCPU

Attachments:

Comments:

Should have mentioned that these tasks fire daily.
Comment by External U.
11207 | August 29, 2014 09:25:58 AM GMT
So after some extensive digging, it appears that ColdFusion 11 server is attempting to fulfill the request on the old server. The DNS entries were updated and tested, DNS flush has been completed just to be safe, but yet the new CF portion of the server attempts to send the request to the old server. I say CF portion because using the browser on the server goes to the correct IP as does a ping and nslookup. This is also a problem with images in PDFs generated by ColdFusion. Does Tomcat have a DNS store that may need to be flushed?
Comment by External U.
11208 | September 03, 2014 02:25:07 PM GMT
I rebooted the server and this seems to have cleared whatever DNS caching that might have existed in Tomcat. This can be closed/withdrawn.
Comment by External U.
11209 | September 03, 2014 03:07:57 PM GMT