Did your .taf use a transaction ? Maybe in some case, the transaction get'n validate or closed, so you run in a loop...
rs Daniel ----- Original Message ----- From: "Dave Machin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 15, 2004 5:37 PM Subject: Witango-Talk: Is this normal? - web connection's queue up till no response > We have various WiTango app's (W2K, MS-SQL 2000, WiTango 5.0.1.054) that talk to a few different databases, but are all running on the same IIS machine (there's only one WiTango service running on this machine). > > Some times a query or process on database A will block other queries for a long time and we see the count of current connections to IIS start to climb as more and more .taf's are waiting for the database to respond. > > However, what confuses me, is that other .taf applications that make queries to the same SQL server, but to database B are also stuck waiting. Even though these queries have nothing to do with the blocked tables. Eventually, the count of current connections to IIS reaches about 260 and levels off. At this point, no WiTango applications respond at all. When the blocking query finishes (or is killed) the requests start completing and everything gets back to normal. > > I'm confused as to why table blocking on database A would affect WiTango applications that are talking to database B. It seems that WiTango is holding unrelated requests in queue until the one's that are blocked complete. Is this what's happening? If so, is there anything we can do about it? > > Dave Machin > > > E-Mail. [EMAIL PROTECTED] > Tel. 805.614.0123 x 30 > Address: 3130 Skyway Drive #702 > Santa Maria, CA 93455________________________TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
