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

Sijie Guo commented on BOOKKEEPER-79:
-------------------------------------

I have run 'make clean check' against latest trunk (including BOOKKEEPER-114 
and BOOKKEEPER-115) for several times. most is OK, sometimes I got following 2 
exceptions.

first one is Exception during socket.close, as commented in previous comments.

second one is SERVER_DOWN exception thrown in publish_thread (running more than 
~250 seconds) in #testRandomDelivery, which due to hub server disconnect to zk. 
I added code in publish thread to catch such exception to avoid it.
{code}
2011-11-19 11:59:46,856 - INFO  
[Thread-2-SendThread(feelpartfirm-lm.local:2181):             
ClientCnxn$SendThread@1057] - Client session timed out, have not heard from 
server in 2908ms  for sessionid 0x133b9f6474f0006, closing socket connection 
and attempting reconnect
2011-11-19 11:59:46,988 - ERROR [Thread-2-EventThread:ZkUtils@75] - Topic:      
              randomDeliveryTopic subscriberId: mysub-randomDelivery could not 
set subscription state:      consumeSeqId: local:21950,zkPath: 
/hedwig/CppUnitTest/topics/randomDeliveryTopic/subscribers/ mysub-randomDelivery
org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = 
              ConnectionLoss for 
/hedwig/CppUnitTest/topics/randomDeliveryTopic/subscribers/mysub-          
randomDelivery
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
        at 
org.apache.hedwig.zookeeper.ZkUtils.logErrorAndCreateZKException(ZkUtils.java:74)
        at org.apache.hedwig.server.subscriptions.ZkSubscriptionManager$3.      
              safeProcessResult(ZkSubscriptionManager.java:186)        at 
org.apache.hedwig.zookeeper.SafeAsyncZKCallback$StatCallback.                   
   processResult(SafeAsyncZKCallback.java:30)        at 
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:554)
        at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:497)
2011-11-19 11:59:46,991 - WARN  [Thread-2-EventThread:ZkTopicManager$2@94] - ZK 
client has    been disconnected to the ZK server! 2011-11-19 11:59:47,054 - 
INFO  [Thread-2-SendThread(feelpartfirm-lm.local:2181):             
ClientCnxn$SendThread@933] - Opening socket connection to server 
/127.0.0.1:21812011-11-19 11:59:47,058 - INFO  
[Thread-2-SendThread(localhost:2181):ClientCnxn$SendThread@   846] - Socket 
connection established to localhost/127.0.0.1:2181, initiating 
session2011-11-19 11:59:47,069 - INFO  
[Thread-2-SendThread(localhost:2181):ClientCnxn$SendThread@   1181] - Session 
establishment complete on server localhost/127.0.0.1:2181, sessionid =        
0x133b9f6474f0006, negotiated timeout = 4362
2011-11-19 11:59:47,069 - INFO  [Thread-2-EventThread:ZkTopicManager$2@98] - ZK 
client has    been reconnected to the ZK server!
{code}


                
> 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_v4, bookkeeper-79.patch, make-check-errors.txt, 
> 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

        

Reply via email to