I'll give that a try...
I'll go back to 10 channels, will not run as a service and check fwstart.log for further clues.
If I see anything useful I'll drop you an email.
Sent by FoxWeb Support on 11/20/2010 02:22:20 PM:
FoxWeb has not been tested extensively and is not supported on 64-bit Windows. I don't know if the fact that you are running on Windows 2003 x64 is related to the problem, but it's a possibility.
Also, 20 channels seems too high. You should probably not be running this many channels, unless your server has at least 8 cores. You will get better overall performance with request queuing, than with too many channels serving requests at the same time.
Have you checked fwstart.log? There may be helpful information in there. Also, I would temporarily stop running FoxWeb as a service, which will allow you to visually inspect channels. This may reveal issues that for some reason do not get logged.
|FoxWeb Support Team
Sent by Gabriel Badea on 11/20/2010 07:46:02 AM:
I'm running foxweb 3.6
Windows Server 2003 R2 x64
VFP9 installed (not running DLL)
Running as service
30 seconds timeout
No session support
I've been having trouble with channels not restarting for a little while now.
I'm pretty sure that these unresponsive channels have never been hit (chanel 19 and 20 in this particular case)
After reconfiguration of channels (from 10 to 20) I rebooted the server.
FWStart.log says that as soon as the server restarted foxweb these channels were unresponsive, it's been trying to restart these channels every 30 seconds ( as per timeout setting) with no success.
There is no trace in the Windows event log.