Skip to content
New issue

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

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

Already on GitHub? # to your account

During shutdown op_disconnect may be sent to invalid handle #7296

Closed
AlexPeshkoff opened this issue Sep 7, 2022 · 2 comments
Closed

During shutdown op_disconnect may be sent to invalid handle #7296

AlexPeshkoff opened this issue Sep 7, 2022 · 2 comments

Comments

@AlexPeshkoff
Copy link
Member

Reported privately by artyom.abakumov artyom.abakumov@red-soft.ru

In Dispatcher::shutdown() providers are first disabled and then service and attachment interfaces are searched for and disabled. For remote provider connections are closed via force_close(), which is why release() of attachments and/or services cause sending op_disconnect using incorrect port_handle value.

@AlexPeshkoff
Copy link
Member Author

Found related bug, caused by this fix: #7504 (Segfault when closing SQL statement in remote provider during shutdown)

@AlexPeshkoff AlexPeshkoff reopened this Mar 17, 2023
AlexPeshkoff added a commit that referenced this issue Mar 17, 2023
…id handle; fixed segfault caused by too early destroyed port_context
AlexPeshkoff added a commit that referenced this issue Mar 24, 2023
…id handle; fixed segfault caused by too early destroyed port_context

(cherry picked from commit 017f313)
@AlexPeshkoff
Copy link
Member Author

Postfixes added to affected branches

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

No branches or pull requests

1 participant