You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@serf.apache.org by "Bert Huijben (JIRA)" <ji...@apache.org> on 2015/11/02 23:38:28 UTC
[jira] [Resolved] (SERF-33) double close() with second calling
close(-1)
[ https://issues.apache.org/jira/browse/SERF-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bert Huijben resolved SERF-33.
------------------------------
Resolution: Fixed
The problem is our pool cleanup handler that runs *after* the APR pool cleanup handler on the socket itself.
I changed the order of registration so the connection cleanup is registered after the socket. That way we cleanup before apr and the apr close is then properly unregistered.
(We had a similar problem in our new test code)
> double close() with second calling close(-1)
> --------------------------------------------
>
> Key: SERF-33
> URL: https://issues.apache.org/jira/browse/SERF-33
> Project: serf
> Issue Type: Bug
> Reporter: Serf Importer
> Labels: Priority-Medium, Type-Defect
>
> *What steps will reproduce the problem?*
> 1. any use of the library will cause a double-close() on context desctruction
> Original issue reported by *postwait*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)