--- In firebird-support@yahoogroups.com, Slalom <slalom91@...> wrote:
>
> I am using D6 / IBX / FB 2.1 CS/ Windows Server 2003.  My
transaction params are [read_committed, rec_version, wait].  I have a
multi-threaded app which has a connection per thread.  I am
experiencing an issue where when I issue a "commit' on the
transaction, I get no response from the server.  When I look at the
properties of the connection through the monitoring tables, the
connection is marked as "idle".  When stepping through the code in
the debugger, I get to TIBTransaction.Committ and it does not step to
the next line of code.  So that's telling me that the server is not
responding to the Commit and the client is never disconnecting or
giving up.  I have let it sit in this state for over 6 hours.
>
> What could be causing this?  Should I be using different
transaction params?  Shouldn't the server be forcibly closing these
connections after being idle for a certain time?
>
> ----- Original Message ----
> From: "Leyne, Sean" <Sean@...>
> To: firebird-support@yahoogroups.com
> Sent: Saturday, September 27, 2008 11:58:53 AM
> Subject: RE: [firebird-support] Commit Client Transaction -
Monitoring Tables
>
>
>
> > Is there a way to issue a query to the monitoring tables which
will
> > commit the work of client connections which are open, idle and
> > uncommitted?
>
> No.
>
> A transaction can only be committed from the connection which
originated
> it.
>
> Sean
>
>
>
> [Non-text portions of this message have been removed]
>