tracker issue : CF-3850183

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

"Clear Trusted Cache" breaks REST Services

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Jörg Zimmer / Jörg Zimmer (Jörg Zimmer)

Created: 11/11/2014

Components: REST Services

Versions: 10.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: Final /

Priority/Frequency: Major / All users will encounter

Locale/System: English / Platforms All

Vote Count: 8

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on September 04, 2019 using build 2016.0.01.298513
Problem Description:
When performing a "clear template Cache" Operation in the Administrator or via Admin-API the REST Service responds to further requests with a 500 internal server error until you press the refresh-button on the rest-service.
This turns Rest-Services into something unuseable for us, as we are running our production machines with trusted cache turned on.
Copying a new file to the server and clearing the trusted cache would cause the rest-api to stop working - NOT acceptable!

Steps to Reproduce:
- Create Rest Service
- Make sure its working
- Press clear template cache button
- rerun rest operation

Actual Result:
500 - internal server error

Expected Result:
REST service still working

Any Workarounds:
none found

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

Watson Bug ID:	3850183

External Customer Info:
External Company:  
External Customer Name: Joerg.Zimmer
External Customer Email:  
External Test Config: My Hardware and Environment details:

Win 7 x64 with CF 10 Update 14 x64

also on Production:

Linux Ubuntu x64 with CF Std. 10 Update 14 x64

Attachments:

Comments:

Is there a way to work on a rest service without having to push the refresh-button on the rest-service after every change to a file? this drives me crazy - I can't find a working solution to this. But this doesn't fit into my CF-experiences since 4.0...
Comment by External U.
10159 | November 11, 2014 08:23:40 AM GMT
Verified this issue also exists in CF11 Update 3 (11,0,03,292245(PreRelease)), using the following repro: Application.cfc --------------- component { THIS.name = "ticket_CF-3850183"; public boolean function onRequestStart() { if(structKeyExists(URL, "reinit")) { restInitApplication(expandPath("./"), "ticketCF-3850183", {useHOST=true}); } return true; } } R.cfc ----- component restpath="{a}" {remote string function sayHello() httpmethod="GET" {return "b";}} 1) go to http://www.domain.com/?reinit, to init REST app 2) go to http://www.domain.com/rest/ticketCF-3850183/a and see "b" 3) in CF Admin, click Clear Template Cache Now 4) go to http://www.domain.com/rest/ticketCF-3850183/a and see "HTTP Error 500.0 - The CFC [path to CFC] is modified and the application is not refreshed." 5) in CF Admin, click Refresh icon for REST service -or- repeat #1 6) repeat #2 and see "b" Thanks!, -Aaron
Comment by External U.
10160 | November 27, 2014 04:44:56 AM GMT
+1 ......................
Vote by External U.
10170 | November 27, 2014 04:45:12 AM GMT
+1. Should not need to tell CF to recompile stuff. Especially when the error message demonstrates CF *knows* what the issue is, just doesn't bother to do anything about it.
Vote by External U.
10171 | January 07, 2015 01:31:54 AM GMT
We've had some customers experience this too in CF 11. Hope it will be fixed soon.
Vote by External U.
10172 | March 11, 2015 11:40:30 AM GMT
+100 Seem to be running into this issue, super frustrating!
Vote by External U.
10173 | September 21, 2015 08:50:51 PM GMT
I think I'm running into this problem, perhaps from a ColdFusion garbage collector.?. I don't click the "Clear Template Cache", but it randomly happens (sometimes within minutes, sometimes hours, even days later). The specific error I'm getting is "500 The application ___ is modified and not refreshed." This is extremely frustrating and is to the point that REST services are unusable!
Comment by External U.
10161 | September 21, 2015 08:58:30 PM GMT
This really needs to be fixed soon. We just released a REST base api that is constantly not working and needs to be restarted. There are no issues in development as template caching is not needed for development. However, as soon as we deployed to out Production farm, random endpoints just suddenly stop working as the template caches are automatically flushed. Is there a better work around than polling each endpoint and restarting REST whenever a problem arises?
Vote by External U.
10174 | September 29, 2015 01:34:06 PM GMT
+1 - driving me nuts. about to take the path of not using built in cf rest. seeing issue on cf11, btw.
Vote by External U.
10175 | October 07, 2015 10:22:27 AM GMT
Adobe, I see this is now Closed/Fixed. What CF10 and CF11 builds is this fixed in? Thanks!, -Aaron
Comment by External U.
10162 | December 03, 2015 03:55:43 AM GMT
We can consider this for next update for both CF10 and CF11
Comment by HariKrishna K.
10163 | December 03, 2015 05:11:58 AM GMT
a little more than 1 year to fix this... till today this bugged me about 300 times... no great performance here Adobe...
Comment by External U.
10164 | December 03, 2015 05:21:04 AM GMT
Hi Hari, Awesome, thanks very much! -Aaron
Comment by External U.
10165 | December 03, 2015 05:28:44 AM GMT
Seeing the issue in CF 11 also. Stay away from the REST crap.
Vote by External U.
10176 | December 18, 2015 01:57:55 PM GMT
Getting this issue in CF10. Appears when clearing cache or changing a file with no caching turned on.
Vote by External U.
10177 | January 12, 2016 04:28:01 PM GMT
When can we see this released? Can I get ahold of a hotfix?
Comment by External U.
10166 | January 12, 2016 04:28:45 PM GMT
anitkumar85 [01/19/2016 6:36 AM] @wilgeno: The fix is targeted for next CF version. We will also try to include it in next CF10/CF11 updates.
Comment by External U.
10167 | January 19, 2016 11:46:25 AM GMT
Was this fixed in CF10? Still seeing this error.
Comment by External U.
10168 | August 15, 2016 09:34:07 AM GMT
This fix would be available in next update of CF10.
Comment by HariKrishna K.
10169 | October 23, 2016 11:21:59 PM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). Thanks!, -Aaron
Comment by Aaron N.
31274 | September 04, 2019 09:37:02 AM GMT