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

Jump to bottom

isql reports an incorrect, misleading and confusing error message when attemting to connect with an incorrect password. [CORE4647] #4961

Closed
firebird-automations opened this issue Dec 22, 2014 · 5 comments
Closed

isql reports an incorrect, misleading and confusing error message when attemting to connect with an incorrect password. [CORE4647] #4961

firebird-automations opened this issue Dec 22, 2014 · 5 comments
Assignees
@AlexPeshkoff
Labels
affect-version: 3.0 Beta 1 component: isql priority: minor resolution: cannot reproduce type: bug

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Peter Vandel (petervandel)

In an attempt to connect to security3.fdb while one or more connections are active, isql nicely reports "... being used by another process". Very well.
However, when no connection is active, an attempt to connect to security3.fdb by passing an incorrect password, isql also reports "... being used by another process". Passing a correct password nicely connects without an error.
Discovering the new security features of Fb3, is time consuming. A misleading error message is very confusing and doesn't really helps.
@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Are you absolutely sure that no connections are active? security3.fdb has linger set to 60 seconds in order to make series of close in time logins a little faster.
I.e. sooner of all database was in linger state when you've provided a wrong password. When you have passed correct password 60 seconds have gone.

Please connect to security3.fdb and try to
alter database set linger to 0
After it retry your experiment.

What about the message - superserver locks all opened databases at OS level and embedded attachments, trying to connect to such databases, can't detect is database accessed by current attachments or just lingered. Moreover, if some third-party process locks .fdb file this also can't be distinguished.

PS. You are connecting to security3.fdb in embedded mode - you need not provide any passwd at all.

@firebird-automations
Copy link
Collaborator Author

Commented by: Peter Vandel (petervandel)

Please REJECT this issue report.

Was unable to reproduce it. Apology for any inconvenience caused.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Cannot Reproduce [ 5 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlexPeshkoff AlexPeshkoff

Labels
affect-version: 3.0 Beta 1 component: isql priority: minor resolution: cannot reproduce type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AlexPeshkoff @firebird-automations