This content has been marked as final. Show 6 replies
Assistance would be appreciated
Have you had any luck with this?
I receive the same error but under different circumstances
I too have just run into this problem on a production site, which is running CF MX 7 on Windows Advanced Server 2003, so it doesn't seem to be an OS-specific bug. It happens when going from the site index to a cached page. I noticed that I am also occasionally receiving this error:
ColdFusion could not delete the file "C:\CFusionMX7\cache\cfcache_16D2F95B7C39C4F3BC185ECA2F3469CF.tmp" for an unknown reason. <br>The error occurred on line 1.
Is this evidence of some kind of race condition? Do I need to use cflock when flushing the cache?
I have not yet determined the problem. On the bright side, I have found numerous ways to not fix it.
Since my original posting on 11/27 I have tried the following:
1) Found somethign on the web indicating that "Macromedia" does not recmmend using ServerCache as and "action" type. I changed it to plain old "cache", but still receive the error.
2) Moved the server cache directory to a custom location (to ease debugging). My expectations that this would not help were fulfilled.
3) Added server and port params to match what was used by default in previous version of ColdFusion, but which no longer are defaults. Didn't help.
4) Attempted cflock, but that caused an error no matter where it was placed.
5) Removed all timeout/timespan params from the cache tag, then set up a scheduled task to run action="flush" every x minutes. Didn't help.
I'm currently at a loss for what else to try. The only solution I can think of is to remove the cfcache altogether and hope browser caching of the file will relieve the server enough.
It does indeed appear to me to be a race condition, but I can't get cflock to work - not sure what to wrap in the cflock tag.
Well I've continued to receive these errors, but I did find one interesting piece of information: they only seem to occur with a user agent of MSIE. I could not find any other browser associated with these. Statistically, it seems unlikely that they are unrelated. Can you check your logs to see if that's true?
On the site experiencing this issue we are not capturing browser information in the web server (Apache) logs, so I can't answer your question. I don't believe the issue would be considered weighty enough by those above me in my organization to allow changing the log settings either.
I found one bug report since my last post that I thought would be appropo, as apparently cfcache works in tandem with cfhttp in the background: http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=95f66fd8 indicates
that intermittent connection issues between CFHTTP and CFMX when CFMX is used in combination with Sun 1.3 and 1.4 JVM's. I tried the recommended solution, however, and it didn't fix anything. I am still in search of an answer. At this point I receive one of these errors about every 4 days.