Board index » delphi » idletimer

2007-01-25 12:31:41 AM
delphi249
Hello there! I still fighting with deadlock errors... I wander if this would
help a bit, until I can change all my components to ClientDatasets (as far
as I know, that is the only way to solve my problem)
AutoStopAction := saCommit;
DefaultAction := TACommit;
IdleTimer := 10000;
* Some more questions:
- When a transaction is idle?
- If I open an TIBQuery and show the data on a grid. How long will wait the
server to do de DefaultAction?
- What is read-only transaction? I didn't found that property in
TIBTransaction. It is just a transaction started by a select comand?
- I have these setings in my *ONLY ONE* TIBTransaction component along all
the system.
read_committed
rec_version
nowait
And (this is happening from 2 weeks) it seems that some client leaves a
transaction open for ever and sudenly I start having a lot of deadlock
conflicts in some PCs. Can I change some setting in order to tell the server
to stop that transactions?
Hope I am clear! And I am very sorry to post so many messages with similar
problems, bu so far I can not find the solution. I have already added a lot of
"commitretainings" almost everywhere!!
Sergio.
 

Sergio Gonzalez writes:
note that IdleTimer isn't exact. ISTR the actual commit interval can be
double the IdleTimer value. At any rate, using it is not recommended.
it's active or when IdleTimer kicks in.
the visual params editor).
Using read-only, read-committed transactions means that in IB 7.1+ you
can keep the transaction open forever without hurting server
performance. In IB 6 and earlier it is still a problem.
Note that IBX questions would be better in
borland.public.delphi.database.interbaseexpress
--
Craig Stuntz [TeamB] ?Vertex Systems Corp. ?Columbus, OH
Delphi/InterBase Weblog : blogs.teamb.com/craigstuntz
Want to help make Delphi and InterBase better? Use QC!
qc.borland.com -- Vote for important issues