[jira] [Commented] (ZOOKEEPER-1375) SendThread is exiting after OOMError

["Jeremy Stribling (Commented) (JIRA)" <ji...@apache.org>]

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

Jeremy Stribling commented on ZOOKEEPER-1375:
---------------------------------------------

Rakesh, would your patch attached to ZOOKEEPER-1100 fix this problem?  I think it would, I just want to make sure . . .
                
> SendThread is exiting after OOMError
> ------------------------------------
>
>                 Key: ZOOKEEPER-1375
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1375
>             Project: ZooKeeper
>          Issue Type: Bug
>    Affects Versions: 3.4.0
>            Reporter: Rakesh R
>
> After reviewing the ClientCnxn code, there is still chances of exiting the SendThread without intimating the users. Say if client throws OOMError and entered into the throwable block. Here again while sending the Disconnected event, its creating "new WatchedEvent()" object.This will throw OOMError and leads to exit the SendThread without any Disconnected event notification.
> {noformat}
> try{
>     //...
> } catch (Throwable e)
> {
>     //..
>     cleanup();
>    if(state.isAlive()){
>         eventThread.queueEvent(
>         new WatchedEvent(Event.EventType.None, Event.KeeperState.Disconnected, null) )
>    }
>    //....
> }
> {noformat}

--
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