You forgot to tell us which version of FoxWeb you are running. FoxWeb 2.5 introduced some important fixes related to channel management and FoxWeb 2.6 added an important security fix to a buffer overrun problem.
Another place to look for clues is fwstart.log in the directory where you installed FoxWeb. If this file seems confusing, you may want to email this file to us at firstname.lastname@example.org, so that we can assist you.
Sent by Dan Divens on 09/20/2004 09:58:01 PM:
Visual FoxPro 8.0
The below script does indeed deliver error #12
Update: we've fixed the SQL error, and currently our error log is now empty. (pretty amazing for the large volume of traffic we run). In any case - we are still seeing channels show 'busy' without resetting after the script timeout period.
I am not running as a service, and viewing the windows so I can see what is happening - there are no pop-ups occuring. The channels eventually show 'busy' and do not restart themselves. However, I can manually close the corresponding window and the channel restarts ok.
There are no odd errors in the 'event viewer' either.
At this point, the server handles transactions for an hour or so before all the channels have filled up with the 'busy' indication w/no reset.
I checked the processor, and even with channels showing 'busy' they are only running on average around 5-15%.
Are there any other error logs besides the main one I can troubleshoot? We're really scratching our heads over here. (again, this same system has run trouble-free on NT 4 and older FoxWeb since around 96/97)
Thanks so much for your time,
Sent by FoxWeb Support on 09/20/2004 01:52:11 PM:
Please let us know a few additional details about your system:
Also, please verify that any error causes FoxWeb channels to hang. Simply create a new script with the following code in it:
The above script should generate a VFP error# 12 (Variable 'SOMENONEXISTENTVAR' is not found).
Another thing to check is whether you get a pop up window when the problem occurs. If you are running FoxWeb as a service you would not be seeing these windows, but you can temporarily disable the Run as Service option (and restart FoxWeb) to test for this. If you do see a pop up window, or some other visual indication that there's a problem with the channel, please make a screen shot and send it to us.
Sent by Dan Divens on 09/20/2004 12:51:20 PM:
Any error that is written to the error log hangs the channel indefinately.
Channel has to be killed and restarted manually.
Script timeout - 120 seconds
Session timeout - 3 minutes
Total channels - 5 (we're running dual AMD processors and a gig of ram)
Sent by Dan Divens on 09/20/2004 09:59:19 AM:
We've been using successfully since 1996 - we love your program and currently run about 70 large database websites on a single Win2003 box. We just upgraded to your newest version of FoxWeb, and are having troubles with the channels hanging and not recovering.
Whenever we get this error, the channel does not recover - we are working on fixing the bad clause, but is there a way for the channels to recover from this in the meantime? (I'm having to monitor and kill channels in real time):