[
https://issues.apache.org/jira/browse/HBASE-15278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263525#comment-15263525
]
Heng Chen commented on HBASE-15278:
-----------------------------------
{quote}
Seems the latest patch still modifies AsyncRpcChannel?
{quote}
The changes in AsyncRpcChannel is just to ensure close be called when
connection closed.
{quote}
Could you explain why we can get a exception other than the injected one?
{quote}
It seems like close(null) which i added in AsyncRpcChannel was called before
AsyncServerResponseHandler.exceptionCaught.
But it couldn't reproduced now on my machine, Let me check the logic again.
> AsyncRPCClient hangs if Connection closes before RPC call response
> -------------------------------------------------------------------
>
> Key: HBASE-15278
> URL: https://issues.apache.org/jira/browse/HBASE-15278
> Project: HBase
> Issue Type: Bug
> Reporter: Enis Soztutar
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-15278.patch, hbase-15278_v00.patch
>
>
> The test for HBASE-15212 discovered an issue with Async RPC Client.
> In that test, we are closing the connection if an RPC call writes a call
> larger than max allowed size, the server closes the connection. However the
> async client does not seem to handle connection closes with outstanding RPC
> calls. The client just hangs.
> Marking this blocker against 2.0 since it is default there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
