[
https://issues.apache.org/jira/browse/LOGCXX-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thorsten Schöning resolved LOGCXX-353.
--------------------------------------
Resolution: Fixed
I suspected that line as well and fixed it on trunk. Thanks!
> When a client disconnects the SocketHubAppender crashes on the next log
> message
> -------------------------------------------------------------------------------
>
> Key: LOGCXX-353
> URL: https://issues.apache.org/jira/browse/LOGCXX-353
> Project: Log4cxx
> Issue Type: Bug
> Components: Appender
> Affects Versions: 0.10.0
> Environment: Windows Vista x64 compiling with Visual Studio 2008
> Reporter: Simon Reye
> Assignee: Curt Arnold
>
> When a connected client disconnects from a SocketHubAppender log4cxx throughs
> an exception. From looking at the code, what is happening is the disconnected
> client is being erased from a output stream vector, which invalidates a
> .end() iterator which is being used in a while loop. The simple fix would be
> to reassign the end iterator after erasing the disconnected client.
> I don't have developer access so I can't check my patch in.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
