[
https://issues.apache.org/jira/browse/QPID-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450038#comment-13450038
]
Chuck Rolke commented on QPID-4257:
-----------------------------------
I've posted an improved patch for review. With this patch the connection
closure is signalled through to clients and the clients wake up. The one-second
timeout clamp is not necessary any more.
https://reviews.apache.org/r/6948/
Description
-------
Based on original work by Kerry Bonin in QPID-4257. The Windows SslConnector
fails to properly relay connection events causing memory leaks and client hangs.
With this patch the memory leaks are improved[1] and clients doing
fetch(FOREVER) are woken properly.
Diff: https://reviews.apache.org/r/6948/diff/
[1] Windows clients using SSL or not still seem to leak about 1Kb per
connection even with this patch. That may be treated as a separate issue.
> Windows+SSL: Client hang on broker close, broker memory leak
> ------------------------------------------------------------
>
> Key: QPID-4257
> URL: https://issues.apache.org/jira/browse/QPID-4257
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker, C++ Client
> Affects Versions: 0.12, 0.13, 0.14, 0.15, 0.16, 0.17, 0.18, 0.19
> Environment: Windows client on Windows 7, Windows broker on Server
> 2K8, using SSL.
> Reporter: Kerry Bonin
> Labels: patch
> Fix For: 0.19
>
> Attachments: windows_ssl_hang_r1377724.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Windows clients hang when broker dies via SSL connection - fetch never
> returns even w/ IMMEDIATE timeout.
> Windows broker memory grows linearly with SSL connection count, leak per
> connection, until broker exhausts memory and crashes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
