[
https://issues.apache.org/jira/browse/QPID-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kerry Bonin updated QPID-4257:
------------------------------
Attachment: windows_ssl_hang_r1377724.patch
Patch to correct.
GetQueuedCompletionStatus was not being signaled properly when an SSL
connection was closed remotely, so it never returned from a INFINITE timeout.
Patched to clamp timeout to 1 second, existing logic handled return w/
numTransferred=0 case, and GetQueuedCompletionStatus did return false without
signaled exit when SSL had been remotely closed. This corrected the hang.
Added SslConnector::redirectDisconnect, as the eof() logic in
qpid::client::TCPConnector wasn't properly signalling closure and releasing
resources.
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
