What kind of script are you calling during your test? If your script takes too long to complete (but less than your script timeout setting) and you have too many requests arriving at the same time, you could end up in a situation where queued requests time out, with the first error you mentioned (Channel Timeout Error - No Available Channels). Here's how it works:
When a request comes in, the FoxWeb Channel Broker attempts to match it with a free channel. If all open channels are already busy serving previous requests, this request is placed in a first-in, first-out (FIFO) queue, until a channel becomes available. If a request waits in the queue for longer than (ScriptTimeout * 3 / TotalChannels) + 5 seconds, then the broker stops trying to match it with a channel and returns the Channel Timeout Error.
Let's assume that your script timeout is 30 seconds and that you have configured FoxWeb to run 20 channels. This means that if a request is in the queue for longer than (30 * 3 / 20) + 5 = 9.5 seconds, you will get the error.
How are you testing? You should probably throttle the software that originates the requests to a maximum number of active requests, so that you don't end up with too many requests in the queue.
The second error (FoxWeb Broker Timed Out) is related to the first one.
The third error (FoxWeb Service Has Been Temporarily Paused) indicates that FoxWeb was paused, buy selecting the "Pause FoxWeb" option on the tray icon, or from the Services applet in the Control Panel.
Sent by James Williams on 02/11/2009 04:37:24 AM:
I am getting the following error messages, I need to know what causes them (why foxweb thinks it should display the message).
Here are some details of whats running:
Window 2003 std sp2
20 foxweb channels
3gb mem buffer
Channel Timeout Error - No Available Channels
FoxWeb Broker Timed Out
FoxWeb Service Has Been Temporarily Paused
We are currently testing the scripts under heavy load (what loads we can get away with)
Current loads are about 12 scripts per second
We get no Errors in the error log and no restarting of channels in the start.log