Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Cached Queries Causing Null Pointer Errors

Community Beginner ,
Mar 03, 2009 Mar 03, 2009
I have a Windows 2003 server with CF 8.01 with the 8.01 cumulative hotfix installed. We've been running off the server in a production environment for several months without issue. Yesterday application we run annually went live for this year. This is the first time this particular application has run on CF8 in a production environment. After maybe an hour or so any CFQUERY that had the CACHEDWITHIN parameter set (even if it was set to 0) started generating null pointer exceptions. This wasn't restricted to just the new application. ALL pages running on our CF8 server that had cached queries were getting this error. I restarted the CF8 service, everything was fine for another hour or so, then the same thing happened again.

Some quick searching turned up kb402583 which speaks of corrupt table errors and was apparently patched. But taking this as a possibly related, I went and removed all the cachedwithin parameters from all CFQUERY tags in the new application that went live yesterday. I restarted the CF service and it's been running smooth since.

Does ColdFusion 8.01 still have a problem with cached queries? It would appear so. Is there a bug report or a kb article or something with more information on this? Has anyone else experienced this? Thanks.
386
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 03, 2009 Jul 03, 2009
LATEST

I am having the same problem in CF 8 and I've applied the cummulative hot fix. I just set Maximum number of cached queries to zero to see if that solves the problem.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources