This is true, and the cache clearing mechanism is another area of improvement in 5.5. I do want to add that for whatever reason, I have not found this to be the case personally. So this problem might be on a case by case basis. I would be hard pressed to explain why. Robert
-----Original Message----- From: John McGowan [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 03, 2004 11:29 AM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: WiTango .65 unstable Dave, This sounds exactly like the behaviour that I found that was related to a problem with the caching and cache clearing functions of witango. The problems with cache clearing that cause the server to get locked up and never return are NOT going to be fixed in 5.0.X Phil said that they could not fix it and that the problems wouldn't exist in 5.5. The only way around it for me is to be very careful when clearing the cache and be ready to restart the server if it fails. it also helps sometimes to restart the server instead of clearing the cache, because if the service gets in that state it takes a long time to kill... /John Dave Machin wrote: >We've started having some troubling stability issues with WiTango .65 on W2K SP4. > >Pages stop loading and it seems that WiTango is not responding. Connections to IIS keep stacking up until we get about 260 connections and eventually the page requests time out. IIS logs write code 500 errors but the WiTango log is completely missing any entries for the time until I kill and restart the process. The log entries prior to the missing section seem completely normal. There are no errors in the WiTango log and no events in the witangoevents.log file. WiTango does not respond when asked to stop from Services and I have to kill it using an application in order to restart it - at which point everything seems fine for several hours or days. > >The server processor is not overly busy, but it isn't completely idle either. During the outage the databases the applications talk to are free of any blocks, so it doesn't seem that WiTango is waiting for database response. The database is MS-SQL 2000, and the ODBC driver is version 2000.85.1022.00. > >I'm at a bit of a loss as to what to even look at as to the possible cause of the problem. Any idea what I should check? > >Dave Machin > > >E-Mail. [EMAIL PROTECTED] >Tel. 805.614.0123 x 30 >Address: 3201 Airpark Drive, Suite 104 >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 ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
