Coldfusion problem IIS6 windows 2003 after a few hours of use have to restart cfmx

I have 2 x CFMX servers running and 1 file server which has all the cfmx code. the cfmx servers connect to the fileserver and produce the sites

the cfmx sites work perfectly for a few hours then after a while all i get are 404 errors, it starts at 1 site then spreads to them all after about 10 minutes of the problem occuring - seems to be load based took 5 hours to occur over nite and about 1 hour in the day

after i restart the cfmx application service ONLY it starts working again i have set the jrun.xml attribute to false

i have done a net stat and it doesnt seem like there are that many connections running so i dont think its a network limitation, these are all fresh 2003 installs
i am seriously lost as to what could be causing this, any help is greatly appreciated.

Are you using CFMX 6.1? Are you using the embedded server or the full JRun 4 J2EE server installation?

Honestly though, I haven't used CFMX with Win2003. I do know that it works and that many other folks are using that setup with no problem, so I'm trying to confirm that your CF setup is all right.

embeded jrun server

i think cfmx is having a mare with the network shares or something

That could easily be the problem, you should not really be relying on network shares if the application is under a heavy load.

can you think of a work around??

have a file server and 2 webservers is there an alternative to network shares?

not heavy load to be honest

Workaround is to have the files replicated to each web server. Though I am not sure this is the problem. I do know, though, that many people are running CFMX 6.1 on Win2003 server with no problems. So I strongly suspect there is an issue in your environment somewhere....just where will be the difficult thing to determine.

Can you set up a test set of CFML pages that do not use the network shares? When you start getting errors, do these simple test pages also fail?

You could also track some important CF server stats like number of queued requests, response time, memory usage, cache hits, cache pops, disk access, etc. Perhaps tracking that over time will lead to some hints.

Also, is anything strange showing up in the CF server error logs?