Hi, Don`t know about specific transactions (can`t imagine the client suddenly trying to use an externally closed transaction), but you could use the monitoring tables and kill attachments, which have transactions that were started too long ago. I expect the other applications can handle network issues (and if they can`t - they should :P) and being 'kicked' from the server looks basically the same from the client side.
2015-02-17 17:12 GMT+02:00 [email protected] [firebird-support] < [email protected]>: > > > Hi, > > we have a problem with third part systems connection to our DB. Actually > we provide a database for data exchange between our system and third party > systems. > The problem is, that sometimes the third party systems leave transactions > open. Of course this leads to a transaction diff, ending in a bad > performing system. > The third party suppliers will not fix the problem, even if caused by them. > So the idea was, if the FB had a possibility to automatically close > transaction after a configured timeout (Maybe configured per attachment) > and to do a rollback in such cases. > It might be that data is lost in such a case, but the external systems > have do deal with this issue.... > > > Any suggestion? > > Thanks in advance and BR > Harald > > > >
