Subject Re: Jaybird driver not returning from simple update.
Author scott_fedelta
--- In, Roman Rokytskyy <roman@...>
> > Our full dump shows no deadlocks and nothing waiting
> > for a monitor (We visually analyzed and ran through a Thread Dump
> > Analyzer to confirm). The thread in question is runnable (no
> > monitor deadlock) and just seems like it is waiting for a reply
> > the database after execution of the sql statement via a socket
> Reason for this can be also a deadlock on the server. You can check
> this is a case by reducing the deadlock timeout on server via its
> config. Alternatively you can play with transaction parameters
> (WAIT/NO_WAIT transactions).
> The only thing that does not really fit the picture is the INSERT,
> under normal conditions should not deadlock. But, if I am not
> the deadlock is still possible even for inserts in rare cases
(IIRC, it
> is related to allocating new pages or index updating...).
> Roman

Firebird.conf has default of 10 seconds:
#DeadlockTimeout = 10

We are waiting much longer than that (many minutes). Am I in the
wrong place?

Otherwise... WAIT/NOWAIT - Any documentation on the use and possible
side effects? Due to the fact that this is in production we have to
be careful of playing with settings.

Finally - would you see any use at all in updating Jaybird / Firebird
or would this symptom be just as likely in the latest versions?

Thanks for the quick reply.