Connecting to service with invalid servicename yields incorrect error message [CORE5039] #5326
Comments
Modified by: @mrotteveeldescription: In Firebird 3 (confirmed in 3.0.0.32199, but I have also seen in earlier versions) connecting to a non-existent service name (eg "doesnotexist" instead of "service_mgr" yields the wrong error message "unavailable database" (isc_unavailable, 335544375) instead of the expected "Cannot attach to services manager" (isc_service_att_err, 335544792). The problem seems to be in the combination of Firebird client and server version. The problem is reproducible using Not reproducible with: This is probably caused by unifying attachment logic for services and databases. This can be reproduced using the Jaybird test org.firebirdsql.gds.ng.jnaTestJnaServer.testBasicStatusVectorProcessing_wrongService() => In Firebird 3 (confirmed in 3.0.0.32199, but I have also seen in earlier versions) connecting to a non-existent service name (eg "doesnotexist" instead of "service_mgr" yields the wrong error message "unavailable database" (isc_unavailable, 335544375) instead of the expected "Cannot attach to services manager" (isc_service_att_err, 335544792). Firebird 2.5.5 behaves as expected. The problem seems to be in the combination of Firebird client and server version. The problem is reproducible using Not reproducible with: This is probably caused by unifying attachment logic for services and databases. This can be reproduced using the Jaybird test org.firebirdsql.gds.ng.jnaTestJnaServer.testBasicStatusVectorProcessing_wrongService() |
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 RC2 [ 10048 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Done successfully |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @mrotteveel
In Firebird 3 (confirmed in 3.0.0.32199, but I have also seen in earlier versions) connecting to a non-existent service name (eg "doesnotexist" instead of "service_mgr" yields the wrong error message "unavailable database" (isc_unavailable, 335544375) instead of the expected "Cannot attach to services manager" (isc_service_att_err, 335544792).
Firebird 2.5.5 behaves as expected.
The problem seems to be in the combination of Firebird client and server version. The problem is reproducible using
Client 3.0.0.32199 with Firebird server 3.0.0.32199
Not reproducible with:
Client 3.0.0.32199 with Firebird server 2.5.5.26952
Client 2.5.5.26952 with Firebird server 2.5.5.26952
Client 2.5.5.26952 with Firebird server 3.0.0.32199
This is probably caused by unifying attachment logic for services and databases.
This can be reproduced using the Jaybird test org.firebirdsql.gds.ng.jnaTestJnaServer.testBasicStatusVectorProcessing_wrongService()
Commits: cb0dfc1 FirebirdSQL/fbt-repository@a2fa650
The text was updated successfully, but these errors were encountered: