reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1421) Transport Client inner thread is not canceled when object is disposed
Date Mon, 06 Jun 2016 15:20:20 GMT

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

Markus Weimer commented on REEF-1421:
-------------------------------------

[~shulmanb], I believe you looked into a similar issue in the past. Is this the same?

At any rate, this looks like a bug with a few lines of fix, right?

> Transport Client inner thread is not canceled when object is disposed
> ---------------------------------------------------------------------
>
>                 Key: REEF-1421
>                 URL: https://issues.apache.org/jira/browse/REEF-1421
>             Project: REEF
>          Issue Type: Bug
>          Components: REEF.NET, Wake.NET
>            Reporter: Julia
>            Assignee: Julia
>              Labels: FT
>
> Currently, StreamingTransportClient starts a new task ResponseLoop, which reads a message
with ReadAsync and sends it to the observer in a while loop with a cancellation token.
> When StreamingTransportClient object is disposed, this task should be canceled with the
cancellation token. Otherwise, the ResponseLoop will keep running and never end. However,
we don't cancel it. After the task is completed, what we see in the logs are endless exception
messages thrown from this loop as group communication has been ended. 
> The same bug is in TransportClient. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message