Subject | Re: [Firebird-Java] Re: Jaybird driver not returning from simple update. |
---|---|
Author | Roman Rokytskyy |
Post date | 2009-03-02T12:44:29Z |
> We are waiting much longer than that (many minutes). Am I in theThe place is correct...
> wrong place?
> Otherwise... WAIT/NOWAIT - Any documentation on the use and possibleBy default all transactions are WAIT (see file
> side effects? Due to the fact that this is in production we have to
> be careful of playing with settings.
isc_tpb_mapping.properties in Jaybird's jar). You can create a file
isc_tpb_mapping.properties on a file system and prepend that directory
to the classpath. Changing from WAIT to NOWAIT is easy - you replace the
text "isc_tpb_wait" to "isc_tpb_nowait".
The consequence is that your application can crash very quickly in
no-wait case. This is due to a reason that you get exception from the
server as soon as it discovers concurrent transaction with conflicting
lock. In WAIT mode Firebird waits (e.g. few milliseconds), concurrent
transaction commits, and your lock request is next to be processed. In
NOWAIT Firebird simply returns an error. You have to check how your
application behaves with NOWAIT.
> Finally - would you see any use at all in updating Jaybird / FirebirdThere was big change re. synchronization between Jaybird 1.5.x and 2.x,
> or would this symptom be just as likely in the latest versions?
and Jaybird should also work with Firebird 1.5.x, but you have to check
as well.
And I cannot tell anything about upgrading Firebird - better ask the
developers.
Roman