serf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bert Huijben (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SERF-33) double close() with second calling close(-1)
Date Mon, 02 Nov 2015 22:38:28 GMT

     [ 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)

Mime
View raw message