On 22-7-2018 16:14, Dimitry Sibiryakov wrote:
22.07.2018 14:56, Mark Rotteveel wrote:
If I change one of the two test classes that triggers this problem to
create a single database for the entire test class, the problem
changes from a too large buffer being read (which causes the hang) to
an error
Unsupported or unexpected operation code 16777216 in processOperation
[SQLState:08000, ISC error code:337248276]
This error means that Jaybird received a response packet with an
operation code of 16777216 instead of a valid operation code
(op_response (9), op_fetch_response (66) or op_sql_response (78)).
It looks like the previous packet was a little smaller than you
expected because 16777216 is "01 00 00 00" which may be a valid piece of
status vector.
It is entirely possible the problem already occurred with an earlier
read, but given that Jaybird itself does nothing with the
TcpRemoteBufferSize setting of Firebird, it would suggest the problem is
on the side of Firebird, because the only difference is that setting.
I don't have this problem if TcpRemoteBufferSize has the default value,
nor with some other values, and only if wire encryption is used.
When I tested it back in March, it worked fine with TcpRemoteBufferSize
value 8192, 32755, 32756, 32760, 32761 and 32764, but broke with 8191,
32759, 32765, 32766 and 32767 (I haven't retested all those values).
Mark
--
Mark Rotteveel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel