>> It looks as though this issue still recurred though I have no new >information >> to go with the issue. I will probably make some adjustments later on to >see >> if that helps > >Try checking the runtime logs as well as the CF logs. > >http://www.coldfusionmuse.com/index.cfm/2005/6/23/coldfusion_logs > >I particularly find the *servername*-event.log and the *servername*-out.log >useful as they can show up errors that dont show up in the standard CF >logs. > >Paul
Hi, It looks as though this issue was resolved. The above I think was a total red herring. There was a task running on another server calling a script that in turn occaisionally (if it thought an unrelated webservice had halted) cleared the trusted cache. This in turn was able to trigger the CFC to reload perhaps at a bad time causing corruption. What pointed us to this was that a script we have that triggers clearing the trusted cache (for internal use) was being logged as being called by user agent "coldfusion", which should have never happened. I expect this was more possible when 2 threads tried to call the same web service however the cache got cleared between them or similar. Since removing that functionality it has been 100% stable for the last 3 days, so all being well that's the end of that. Thanks for the help Paul ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:328123 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
