You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <qp...@incubator.apache.org> on 2010/06/01 20:53:36 UTC
[jira] Commented: (QPID-2636) disconnect() callback on broker
results in leaked connections
[ https://issues.apache.org/jira/browse/QPID-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874151#action_12874151 ]
Gordon Sim commented on QPID-2636:
----------------------------------
The leaks appear to correspond to the occasions when the disconnect() rather than eof() callback path is followed. The queueWriteClose() is then invoked on a handle that never becomes writable and thus socketClosed() is never called.
> disconnect() callback on broker results in leaked connections
> -------------------------------------------------------------
>
> Key: QPID-2636
> URL: https://issues.apache.org/jira/browse/QPID-2636
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Reporter: Gordon Sim
> Assignee: Gordon Sim
> Fix For: 0.7
>
>
> E.g. run qpid-perftest --size 10 --count 10000 --nsubs 500 --npubs 500 and then kill the client process while running. Then run qpid-stat -c. This often results in connections not being properly deleted (and still being reported by qpid-stat).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org