One correction to my previous posting. I've just been advised by our Development Team, that ODBC SPAWN Issue is in fact not caused by the version of Witango Engine, or MDAC version. Rather it is the side effect of the way we're handling user sessions combined with the Size of RAM available to Witango Server.
There has been some very extensive research performed on this particular issue recently. The solution lies in use of Shared Application Scope. Hopefully it is just our unique issue that is not going to show up on other web sites. Sincerely. Andre Rekhtine, Sr. IS Consultant, MCSE Moveable Online Inc. [EMAIL PROTECTED] > > Hi, John. > > First of all let's clarify what exactly are you going to migrate to and > from (O/S and AppServer Versions). > > The obvious difference between Tango2000 and Witango5 was the Default > User Scope in Witango Config. For some of the older applications we had > to force to 'user', instead of Witango native 'request'. > > Migrating from all-in-one box setup to a tiered environment involved > changing push/pull mode for Witango. Developers should know what I'm > talking about. > > Another point to pay attention to would be the load, on your Tango Driven > web sites. if you approach a threshold of 200 simultaneous users per > Witango Daemon, you might face unpleasant preformance issues up to a > complete crash. That very much depends on Complexity of the Application > Code of course. The AppServer begins to spawn multiple ODBC Connections, > while failing to close them. At certain point the Server gets frozen, only > kill and restart can help to recover. There's unproven statements that in > regards of ODBC issues Windows 2000 SP3 is the most stable configuration > for Witango 5 (Most stable version of MDAC). We don't have a way to > disprove this, since our web farm is completely Windows2003 based. And it > is prone to ODBC SPAWN issue under huge traffic spikes. The only way we > found so far to combat this issue is Load Splitting, which is getting less > effective as we grow. > > I would strongly suggest to do a site by site migration. Migrate and > test, let it run, see if any issues come up. Add one more and test > again. Always plan for roll back. 50 sites might be very hard to find a > bug in such a big pile. > > Good luck. > > Andre Rekhtine, > Sr. IS Consultant, MCSE > Moveable Online Inc. > [EMAIL PROTECTED] > >> Hello folks, >> >> I am in the process of moving my sites (50 of them) along with email >> servers, dbs, etc., to a new location. I have brand new in-the-box >> servers all loaded with Win2k server software. I know, I know, but I >> love win2k, very stable platform. I currently loaded Witango 2000 and >> moved 6 of the sites over last night. I am seriously considering >> upgrading. I really haven't been paying much attention to the caveats >> that others have run into. Is an upgrade fairly straightforward? Any >> problems running new versions on win2k? Another problem I have is that I >> want to run Witango on 2 boxes. I currently have the corporate version >> (paid dearly for it) and that allows me the ability to load Witango on >> as many boxes as I want. I see the licensing has changed and was >> wondering if others are running multiple instances and whether they got >> a break on the price. If worse comes to worse, I suppose I could >> continue to run 2000 on one of the boxes. Not sure if that is allowed, >> but as far as I can tell, I gotta pay full pop anyway. >> >> I have always been a "don't fix if it ain't broke" type of guy. The >> version of Witango and Win2k have been rock solid for the past 6 years >> and I am apprehensive about upgrading. I have thousands of taf files and >> I need to make sure that this is going to work out for me. >> >> Any suggestions, things to look for or other information would be >> appreciated. >> >> Thanks! >> >> ________________________________________________________________________ >> 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
