[
https://issues.apache.org/jira/browse/FLUME-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652698#comment-13652698
]
Hudson commented on FLUME-1981:
-------------------------------
Integrated in flume-trunk #407 (See
[https://builds.apache.org/job/flume-trunk/407/])
FLUME-1981. Rpc client expiration can be done in a more thread-safe way.
(Revision d4c1bc07bc33e10cfdc5eca11b085e269dbea60d)
Result = FAILURE
mpercy :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=d4c1bc07bc33e10cfdc5eca11b085e269dbea60d
Files :
* flume-ng-core/src/main/java/org/apache/flume/sink/AbstractRpcSink.java
> Rpc client expiration can be done in a more thread-safe way
> -----------------------------------------------------------
>
> Key: FLUME-1981
> URL: https://issues.apache.org/jira/browse/FLUME-1981
> Project: Flume
> Issue Type: Bug
> Reporter: Hari Shreedharan
> Assignee: Hari Shreedharan
> Fix For: v1.4.0
>
> Attachments: FLUME-1981.patch
>
>
> If the destroyConnection() call happens just before a client.append() or
> client.getBatchSize(), it is possible that an EventDeliveryException is
> thrown which is caused by an NPE (since destroyConnection() will set client
> to null).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
