|
Has anyone ever seen this error in the witango
events log?
[ 1892] 2003-11-19 10:22:12
RUNTIME WARNING Unable to open to (null) due to an error
during connection
[ 1892] 2003-11-19 10:22:12 RUNTIME INFO Max connections: 0 Current connections: 0 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.
We are using R:Tango 5 on windows 2003 server, but
we had this problem as well back on R:Tango 2000 when we were on a different
machine running NT 4.
It seems to error in specific places and not in
others but it doesnt error every time it hits those actions, only about 1% of
the time and it seems to error more often within loops (but maybe thats just
because more DBMS's are being executed?). That 1% is starting to become a
bigger problem though as we have an increased number of users.
Has anyone had any kind of experience like
this? We have caching on so might it be a problem of memory corruption in
the cache or something?
Thanks,
Alan
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf |
- Re: Witango-Talk: strange error Alan Wolfe
- Re: Witango-Talk: strange error Bill Downall
- Re: Witango-Talk: strange error Alan Wolfe
- RE: Witango-Talk: strange error Robert Shubert
- RE: Witango-Talk: strange error Troy Sosamon
- RE: Witango-Talk: strange error Bill Downall
- Re: Witango-Talk: strange error Alan Wolfe
- Re: Witango-Talk: strange error Bill Downall
- Re: Witango-Talk: strange error Alan Wolfe
- RE: Witango-Talk: strange error Ben Johansen
- Re: Witango-Talk: strange error Alan Wolfe
