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

Failing isc_que_events causes that other operations with DB on same handle are blocked [CORE5597] #5863

Closed
firebird-automations opened this issue Aug 24, 2017 · 7 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Slavomir Skopalik (skopaliks)

Duplicates CORE3718

32 bits gds32.dll from 2.5.7
In case that connection to DB was successfully but auxiliary event connection failed to establish, other operations on same DB handle are blocked.

Call of isc_cancel_events not help.

If I use fbclient.dll from Firebird-3.0.3.32798-0_Win32, it is working fine.

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Could you provide us with reproducible test case ?

@firebird-automations
Copy link
Collaborator Author

Commented by: Slavomir Skopalik (skopaliks)

Test is simple:
1. Configure FB server but on firewall open only 3050. Block all other ports.
2. On client side connect to DB (this will be successful)
3. Try to register events. but this will failed due to server firewall.
4. After that, you cannot do any operation with DB using handle obtained in step 2.

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Is it the same as CORE3718 ?

@firebird-automations
Copy link
Collaborator Author

Commented by: Slavomir Skopalik (skopaliks)

Yes, it is same. Sorry I miss it.

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Link: This issue duplicates CORE3718 [ CORE3718 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

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

resolution: Duplicate [ 3 ]

@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
Projects
None yet
Development

No branches or pull requests

1 participant