I prefer to use very short datasource lives, 5 minutes for production, 1 minute on development. One of the real benefits of Witango 5 is that the creation of new datasource connections is a very quick process. Data source connections can go stale, on the part of the network, the database, etc. Interestingly, in my experience, Witango has always been the one to maintain connections the longest. In any case, using a short datasourcelife allows for fresh connections to be generated constantly and this, at least in my configuration, seems to work well.
Robert PS. Make sure your threading options are set correctly. Depending on which database you are using, you might have to adjust these settings. -----Original Message----- From: Alan Wolfe [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 8:02 PM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: strange error Hi Bill, Thanks for the response (: We have our datasource life set to 1440 as well but we dont use variables for datasource names so maybe your user scope really isnt being dropped and were both experiencing the same problem. For us, this error happens a handful of times a day, not just the first login of the morning or anything. ----- Original Message ----- From: "Bill Downall" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 19, 2003 3:25 PM Subject: Re: Witango-Talk: strange error > Alan, > > Yes. It it most likely to happen at the first login on a Saturday or Sunday, > when the application has been sitting unused for several hours. I'm > wondering if Windows is "detaching" resources. > > I have the witango.ini DATASOURCELIFE setting at 1440 (24 hours) > > Do you use variables in the Deployment Data Source Name field? If so, are > they USER scope? I'm thinking of changing these to custom or application > scope variables. (There could be some other side effects there, like the > inability to be have one user testing on one data source and another user > using on the other data source) I also can't find any evidence that the user > scope has expired, and I always check for current login user scope > variables at the top of every TAF. > > Bill > > On Wed, 19 Nov 2003 11:41:53 -0800, Alan Wolfe wrote: > > >We are having some strange errors where as far as we can tell, witango > is "forgetting" the datasource name for some DBMS actions every now and > then and is passing null instead which causes an error. When this error > occurs, its coupled by an entry like the above in the witango events log. > > > > > > > > > > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
