[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152019#comment-13152019
 ] 

Ivan Kelly edited comment on BOOKKEEPER-79 at 11/17/11 12:21 PM:
-----------------------------------------------------------------

I'm running the testcase (without the fix) and I'm getting a number of 
different errors. What error do you get which shows this problem?

Also, I'm not sure the fix is correct. I don't think it's possible for 
receiving to be false, while stopReceivingBefore is false, because there's a 
lock,   
{code}
boost::lock_guard<boost::mutex> lock(receiving_lock);
{code}
which explicitly stops this situation.

What this change seems to do is that, once you stopReceiving, the channel can 
never start receiving again? 
                
      was (Author: ikelly):
    I'm running the testcase (without the fix) and I'm getting a number of 
different errors. What error do you get which shows this problem?

Also, I'm not sure the fix is correct. I don't think it's possible for 
receiving to be false, while stopReceivingBefore is false, because there's a 
lock,   
{code}
boost::lock_guard<boost::mutex> lock(receiving_lock);
{code}
which explicitly stops this situation.
                  
> 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
>
>
> 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

        

Reply via email to