Re: Timeout Expired exception by Bernie
Bernie
Wed Mar 03 17:35:22 CST 2004
To my knowledge, a drifting clock will have no impact. The timeout process
is simply running on a timespan of the command object and it doesn't really
care about the system clock time.
Bernie
"Guogang" <nospam@no_such_domain.com> wrote in message
news:us1MYCWAEHA.712@tk2msftngp13.phx.gbl...
> Do you happen to know if drifting clock may be a cause of timeout
exception?
> For example, database server's clock is showing 12:44 pm, while the other
> computer showing time: 12:35 pm. Will this be a problem?
>
> Thanks,
> Guogang
>
> "Bernie Yaeger" <berniey@cherwellinc.com> wrote in message
> news:eysj58VAEHA.3308@TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > See the thread below on timeout errors that I posted today - it's easy
to
> > reset the timeout property - that should solve your problem, as it did
> mine.
> >
> > Bernie Yaeger
> >
> > "Guogang" <nospam@no_such_domain.com> wrote in message
> > news:O7ye21VAEHA.2292@TK2MSFTNGP12.phx.gbl...
> > > Hi,
> > >
> > > I have a question regarding the "Timeout Expired" excetpion.
> > >
> > > We have a database server running SQL 2000, and another computer
> accessing
> > > the database server using ADO.NET (via a CAT 5 cable directly).
> > > Occationally, I get a "Timeout Expired" exception tring to access
> database
> > > server.
> > >
> > > I do notice that the clock on the two computers may be drifted as far
> away
> > > as 6 minutes. Can this contribute to the timeout exception?
> > >
> > > In the sense of robust programming, what should I do in my code to
> survive
> > > these kind of exceptions?
> > >
> > > Thanks,
> > > Guogang
> > >
> > >
> >
> >
>
>