Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting to service with invalid servicename yields incorrect error message [CORE5039] #5326

Closed
firebird-issue-importer opened this issue Dec 5, 2015 · 5 comments

Comments

@firebird-issue-importer
Copy link

firebird-issue-importer commented Dec 5, 2015

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

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 5, 2015

Modified by: @mrotteveel

description: 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
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()

=>

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()

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 7, 2015

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 17, 2015

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0 RC2 [ 10048 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 17, 2015

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Done successfully

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Dec 17, 2015

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants