[
https://issues.apache.org/jira/browse/BOOKKEEPER-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152982#comment-13152982
]
Sijie Guo commented on BOOKKEEPER-79:
-------------------------------------
I have tried running 'make check' several times. it is OK for me, only one time
there is an Exception thrown in socket.close, the exception indicates closing a
Not Connect socket.
I think the exception is due to shut down a channel:
{code}
void DuplexChannel::kill() {
...
socket.cancel();
socket.shutdown(boost::asio::ip::tcp::socket::shutdown_both);
socket.close();
...
}
{code}
I think we can change using cancel/shutdown/close to
cancel(&error)/shutdown(&error)/close(&error), which returning an error code
instead of throwing exception.
http://www.boost.org/doc/libs/1_48_0/doc/html/boost_asio/reference/basic_stream_socket/close/overload2.html
I am not sure the problems described in your comments, could you give more
information about them?
> randomly startDelivery/stopDelivery will core dump in c++ hedwig client
> -----------------------------------------------------------------------
>
> Key: BOOKKEEPER-79
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-79
> Project: Bookkeeper
> Issue Type: Bug
> Components: hedwig-client
> Affects Versions: 4.0.0
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.0.0
>
> Attachments: BOOKKEEPER-79.patch_v2, BOOKKEEPER-79.patch_v3,
> bookkeeper-79.patch, pubsubtest.cpp
>
>
> in our test program, we tried to startDelivery/stopDelivery different
> subscriptions randomly. And it core dump.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
