Date:  07/24/2012 03:18:02 PM Msg ID:  004492
From:  FoxWeb Support Thread:  004489
Subject:  Re: Channel mix up???
On a completely unrelated matter, setting the script timeout to 260 seconds can cause a lot of problems, because channels can remain unresponsive for a long time before being restarted. Even if you have a small number of scripts that can take this long to run, it is recommended that you set the default channel timeout to something a lot shorter (10-20 seconds) and override it programmatically with Server.AddScriptTimeout() in the scripts in question.
FoxWeb Support Team email
Sent by Ali Koumaiha on 07/24/2012 10:04:52 AM:
 Running FoxWeb 4.5
 Script Timeout: 260 seconds
Session Timeout: 60 (min)
Channels: 15
Buffer mem: 1399
running DLL and running as a service
VFP 9 SP2 is backend dbf/dbc
Sent by Ali Koumaiha on 07/24/2012 09:51:59 AM:
 I am seeing a strange behavior on one of my client.
they have usre's they use an app that send a small xml to update some tables at the corporate server.  the app post the xml to foxweb. FoxWeb, takes the xml, turns it into a cursor, then, upon success, the fwx script, does:
the app reads the success reponse and does its thing on the user's end.
Also, there is a Portal system, (other pages) where employees, and users, and customers can view their invoices, have a shopping cart, etc..
some employees that are NOT using the xml scripts at all (and they cannot), are seeing the "success" from another script.
1- POS app posts xml to SyncDBF.fwx
2- SyncDBF.fwx processes the xml and does respone.write("success")
user: navigates the portal and accesses PreviousOrders.fwx 
users: seeing "success" (once in a while).
they sent me a snap shot of the webpage, which is the url has previousorders.fwx, and the only fwx EVER on that server that has "success" as response.write is SyncDBF.fwx
what should I do?