I'll go with bad networking. Check for full duplex, good cables, move to secondary ports if you have them etc. Also, try to restart everything by shutting the power off to both the Witango and sql servers as well as the Ethernet switch. Do you use jumbo frames or anything unusual with the networking? Finally, if it's not physical, then it might be the ODBC layer. Try reinstalling the latest MDAC (2.8 I think) on both servers. I know that Witango 5.0/5.5 and MS SQL SP3 both don't mind. IF you're running an earlier MDAC, you'll also get a performance boost. You might want to try installing Witango again, although that's a long shot.
-----Original Message----- From: Dave Machin [mailto:[EMAIL PROTECTED] Sent: Thursday, December 09, 2004 6:08 PM To: [EMAIL PROTECTED] Subject: Witango-Talk: URGENT: MS-SQL hanging -processnon-yielding A new piece of information on our problem. Our datasourcelife variable is set to 30 minutes. However, new database connections are opened many times per second. Also, we get many of these messages in the log file: [Warning] Existing data source no longer alive, disposing... I literally got hundreds of these messages (logging level is set to 3) and the server was only up from 13:39:09 through 13:53:14 Why should a data source expire that often given our datasourcelife setting? Or does this message mean something else? Dave Machin (FYI - we set the datasourcelife variable to 0 and no longer receive these messages (in the last hour). ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
