21.03.2015 16:39, Mark Rotteveel wrote: > I have a problem when running the Jaybird 2.2 branch test suite against > Firebird 3. One of the tests fails to drop a table with the exception > (on an implicit commit by Jaybird): > > org.firebirdsql.jdbc.FBSQLException: GDS Exception. 335544345. lock > conflict on no wait transaction > unsuccessful metadata update > object TABLE "LONGTEST" is in use > > This only happens when the test is executed with a transaction setting > read_committed, rec_version, write, **no_wait** (instead of the default > which uses wait). I am wondering why using a no wait transaction in this > test prevents the table from being dropped (while this works ok in > Firebird 2.5, and use of a wait transaction works fine as well).
Are you sure you compare the same FB architectures in v2.5 vs v3.0? Dmitry ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
