Fix available for CF11 update 18 query caching bug

March 22, 2019
ColdFusion troubleshooter
Wizard 33 posts
Followers: 35 people
5

Fix available for CF11 update 18 query caching bug

ColdFusion troubleshooter
Wizard 33 posts
Followers: 35 people
March 22, 2019

If you have moved to CF11 update 18, or plan to, note that there is a known bug affecting use of query caching, such as via the cachedwithin attribute of cfquery, causing it to sporadically return incorrect results.

Some good news is that Adobe has a fix available, in the form of special update jar you can obtain from Adobe, by emailing cfsup@adobe.com to request it. You can refer to the bug report about this, cf-4204066:

https://tracker.adobe.com/#/view/CF-4204066

As explained there, the update will of course be rolled into a later full update (no date set yet).

Some may wonder are whether the issue affects cf2016 or 2018, but it seems it does not. It’s also curious that update 18 would have introduced this, when it was meant only to address a security issue common to all 3 current cf versions.

Anyway, hope this is helpful to those using cf11 and running update 18.

Comments (5)
2019-03-24 21:48:27
2019-03-24 21:48:27

Thanks for sharing this, Charlie.

Are you (or any of the readers, for that matter) aware of whether this would be expected to impact all query caching? Or CF11U18 on all platforms?

We don’t use it in very many places in our apps, and I’ve tried and tried to replicate this behavior on one of our dev boxes running CF11U18 in one of the areas where we do use query caching. So far, I can’t replicate the behavior.

And I agree completely that it is curious that this showed up in a hotfix that was intended to just address a security issue (which on the surface would seem to have very little to do with this caching breakage). It would be helpful to have the Adobe CF team clear that up.

Like
(2)
>
R.Stewart
's comment
2019-03-27 03:07:36
2019-03-27 03:07:36
>
R.Stewart
's comment

Well, no, not “all query caching”. That’s why I indicated that the bug’s been found to cause such query caching to “sporadically return incorrect results”, so that may be why you can’t force it. I’ve not heard of any way to force/replicate the problem. As for platforms, I’ve similarly not heard of it being limited to some. Perhaps Adobe or others may have more to say on that, or on your last your point.

Like
(1)
>
Charlie Arehart
's comment
2019-03-27 11:30:02
2019-03-27 11:30:02
>
Charlie Arehart
's comment

Thanks, Charlie. I will admit I didn’t pick up on the characterization as being sporadic here or in the forum/tracker threads.

Like
2019-03-22 11:37:40
2019-03-22 11:37:40

Thanks for posting this Charlie.  I was unaware.

Like
(1)
>
Miguel Fernandez
's comment
2019-03-22 12:53:55
2019-03-22 12:53:55
>
Miguel Fernandez
's comment

And thanks for saying so, Miguel. Such encouragement is always appreciated.

Like
(1)
Add your comment