You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Cliff Jansen (JIRA)" <ji...@apache.org> on 2019/04/04 20:22:00 UTC
[jira] [Created] (PROTON-2027) Proactor connection wake after
memory freed when using pn_proactor_disconnect().
Cliff Jansen created PROTON-2027:
------------------------------------
Summary: Proactor connection wake after memory freed when using pn_proactor_disconnect().
Key: PROTON-2027
URL: https://issues.apache.org/jira/browse/PROTON-2027
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: proton-j-0.32.0
Reporter: Cliff Jansen
Assignee: Cliff Jansen
The normal cleanup procedure for epoll and win_iocp proactors waits for all async activity to complete before freeing memory.
pn_proactor_disconnect can't actually force a close so it launches a separate async activity piggy-backed on the internal wake mechanism of any connections to be closed.
If the disconnect is happening at the same time as a separate thread doing a normal close, a new wake can result after concluding there are none left.
The solution is to mark the connection as "already awake" before entering the cleanup code so new wakes are no-ops. The libuv proactor doesn't need this as the disconnect function is managed within libuv and never competes with the normal close operation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org