The Jaybird 2.2 tests are currently failing unexpectedly on a number of
tests when run against Firebird 3 beta 1:
1) It looks like Firebird no longer returns the number of rows requested
by the client. Jaybird (wire protocol) by default requests 400 rows and
in the past Firebird always returned the requested number of rows,
unless there were no more rows (status 100). Firebird no longer seems to
honor this request and returns a lower number of rows. Current logic in
Jaybird either expects the full number of requested rows, and only
expects a partial number of rows together with status 100 (all rows
fetched).
Is this an intentional change, if so: why?
2) failure to drop a table, but only when I run the full testsuite, not
when I run the failing tests individually (nor together with the tests
in the same class)
The error:
335544345. lock conflict on no wait transaction
unsuccessful metadata update
object TABLE "LONGTEST" is in use
As the entire database is specifically created for the test itself, it
shouldn't be influenced by other tests. The Firebird log also doesn't
contain anything interesting.
I have no idea how to troubleshoot this, as it only occurs when running
the entire set of Jaybird tests (or maybe a specific subset I haven't
found yet).
Note that the workaround for me is pretty simple, as the actual
statement that triggers this is not necessary (the entire database gets
dropped shortly after), but it probably points to a problem in Firebird.
I seem to remember having similar problems before with the Cache Writer
and Garbage Collector attachments interfering.
These problems do not occur with an earlier Firebird 3 build (3.0.0.31352).
I also tried the snapshot build (3.0.0.31467), but that seems to behave
even worse. For example events don't seem to be working; log shows:
RAMONA Fri Dec 05 16:34:12 2014
Unable to complete network request to host "Ramona".
Timeout occurred while waiting for a secondary connection for event
processing
It looks like Firebird is asking Jaybird to connect to the wrong address
(Error message from Jaybird says "Unable to complete network request to
host "0.0.0.0"", but I haven't looked into it yet so this might just be
an artifact from how Jaybird constructs its error message here. Might
this be related to the IPv6 changes?
Mark
--
Mark Rotteveel
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
