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
