One other comment on this - we're positive that the user scoped variables in general are not getting reset or changed, because the query that is issued against the wrong data source uses both a user scope and a request scope variable in it. And in the profiler when we see the query those two values are correct -
So, the query against the wrong data source has "WHERE (S1.Survey_id=1255 AND S1.Question_id=16)" the 1255 is from <@var user$survey_id> and the 16 is from <@var local$question_id> These values are the correct values for the request and match the equivalent query that is issued against the correct data source in the next action. If the session was being confused with another session, wouldn't those values change? ----- Original Message ----- From: "Dave Machin" <[EMAIL PROTECTED]> To: <[email protected]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, January 25, 2006 10:46 AM Subject: Re: Witango-Talk: Select 1 From xxx where 1=0 > Thanks for the feedback. > > We're still stumped. We've confirmed that the ODBC variable is set > correctly before and after our two test queries, and yet one of the two (or > sometimes both) execute against the wrong data source. Queries that happen > later or earlier in the request execute against the correct data source. > > I've compiled some notes of one example from this morning, if anyone has > some time they could take a look and see what we're seeing. > > You can download the document here: > www.benchmarkportal.com/witango_error_notes.zip > > In short, we're showing that queries execute correctly at first; the user > variable is correct before the query in question; the first test query then > executes against the wrong data source; the second test query executes > against the correct data source; and then the next query executes correctly > as well. > > This happens in 5.5.009 on three different servers. The current production > server is a new, clean build with the latest updates and the latest MDAC > drivers. This .taf does not use the user reference argument, and relies on > the cookie. What's confusing is that one query in the middle of a a > sequence of ten goes wrong and the others work fine - all in the same > request. > > We're going to downgrade from 5.5 back to 5.0 to see if the problem goes > away, because we can't find anything else to change. > > ----- Original Message ----- > From: "Customer Support" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Tuesday, January 24, 2006 5:32 PM > Subject: Re: Witango-Talk: Select 1 From xxx where 1=0 > > > > > Is it unusual that our production server doesn't issue the > > > heartbeat query before each DB action? > > > > Yes. It may be going to another DB or DB Server as it is based on > > the datasource and tables in the db. > > > > > On our development machine, I wrote a .taf application that issued > > > an identical DB action 20 times (just copied and pasted the same > > > DBMS action over and over). In SQL profiler, when that application > > > is executed, I see the heartbeat and then the query repeated 20 > > > times in pairs as expected. > > > > > > But on our production server, we often see cases where there is no > > > heartbeat query before a DBMS action. Sometimes we see two or > > > three DB actions execute before we see another heartbeat query. > > > > If you are running the same version of the Witango Server, OS, ODBC > > and DB on all servers and they are exhibiting different behaviors > > then you probably have a difference in the configuration of one or > > more of Witango Server, OS, ODBC and/or DB processes. > > > > Your problem sounds like tafs interacting with eachother, hard coded > > user references, lost user reference cookies or lost user references > > argument. If you do not use user reference arguments and rely on the > > user reference cookie make sure that it is working and has a value or > > the server will fall back to issuing a new user reference cookie. > > > > If you are using iframes or AJAX check that you do not have one taf > > interacting with another under the same user reference reseting a > > variable when you are not expecting it. > > > > > > Witango Support > > ________________________________________________________________________ > > 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
