You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that wire protocols 12 and older are disabled by default (#733), it is more likely users will received isc_connect_reject (i.e. when connecting to Firebird 2.5 and older). To avoid bug reports/support questions, we need to add an extra explanation to this exception message and/or replace it with a Jaybird specific exception message (e.g. explaining this common case, and maybe link to the FAQ for more info).
The text was updated successfully, but these errors were encountered:
Is isc_connect_reject raised inside jaybird?
I ask cause this is client-only error code in FB, it never comes from the server (may be except Execute Statement On External). And there may be other reazons except incompatible protocol - first of all non-fb listener on 3050.
Yes, it is raised by Jaybird when op_reject is received, just like the fbclient does (IIRC). I know there are other reasons (I have documented a number of them in the Jaybird FAQ), but now that Jaybird no longer tries protocol 10, 11 and 12 by default, I expect its frequency to increase for people stuck on older versions.
Now that wire protocols 12 and older are disabled by default (#733), it is more likely users will received
isc_connect_reject
(i.e. when connecting to Firebird 2.5 and older). To avoid bug reports/support questions, we need to add an extra explanation to this exception message and/or replace it with a Jaybird specific exception message (e.g. explaining this common case, and maybe link to the FAQ for more info).The text was updated successfully, but these errors were encountered: