Well, I didn't mean to suggest that my actions were the only method of the problem occurring. I've seen it on same server situations when an Access file gets corrupted. The point was just that Witango seems to maintain connections to the db even after they have died (on the db or odbc side) and this prevents Witango from making new connections, thus the error about the connection pool size. Is it possible that your db is set to auto-close connections after a certain time? You could try turning the Witango setting "datasourcelife=" to a lower number. This will cause the connections to refresh more often. I prefer 5 minutes since I wish this to occur frequently. A setting of zero can be used for testing/light-load and causes connections to close immediately after each execution.
Robert -----Original Message----- From: Fogelson, Steve [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 18, 2004 1:23 PM To: '[EMAIL PROTECTED]' Subject: RE: Witango-Talk: ODBC Problems Robert, Thanks for the response. I think my problem is a little different. The DB is located on the same server. And when this problem starts, it doesn't let anyone access this DB until I restart Witango. So I don't think it is a long exec unless something somehow locks the DB. Steve -----Original Message----- From: Robert Shubert [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 18, 2004 11:49 AM To: [EMAIL PROTECTED] Subject: RE: Witango-Talk: ODBC Problems The Witango error is a little misleading, but translates directly into "database isn't available". Is it possible that your db isn't responding for a moment (long exec) or is offline (auto-restart). I know I get this issue if I say, unplug the Ethernet cable to my SQL box. Witango has a fit, and does auto-close 'dead' db connections. Robert -----Original Message----- From: Fogelson, Steve [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 18, 2004 12:08 PM To: Witango User Group (E-mail) Subject: Witango-Talk: ODBC Problems Window 2003 Web Edition, R:Tango version 5 I have been getting the following error periodically in my Application Event Viewer: Unable to open to odbc.CatSites due to an error during connection. Followed by this Total Connection in Datasource Pool: 1 Max connections for the host: 0 Current connections in use for the host: 0. Once this starts, my app doesn't work until I restart Witango. The problem clears up immediately. Any ideas what is causing this. The DB is loaded on the same server. Thanks Steve Fogelson Internet Commerce Solutions ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
