On 11-08-2020 22:17, Roberto Vieweg wrote:
> Even in Jaybird 3.0.1, is the default "wait on locks" ?
>
> Because I'm getting this without setting any connection properties:
>
> org.firebirdsql.jdbc.FBSQLException: GDS Exception. 335544336. deadlock
> update conflicts with concurrent update
> concurrent transaction number is 5608174
Yes, it has been the default since before Jaybird 2.2, likely always.
An update conflict like this can occur if you're attempting to update a
record that was modified and committed by another transaction and that
transaction was started before your transaction and committed after your
transaction started. And that is assuming you're using read committed
and not another isolation level.
For a better answer, I'd need a reproducible example.
Mark
--
Mark Rotteveel