[
https://issues.apache.org/jira/browse/FLUME-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646870#comment-13646870
]
Hudson commented on FLUME-2002:
-------------------------------
Integrated in flume-trunk #403 (See
[https://builds.apache.org/job/flume-trunk/403/])
FLUME-2002. Flume RPC Client creates 2 threads per each log attempt if the
remote flume agent goes down. (Revision
2e1b7c23c4964b8860b876cc5c8c3642c4d74ab9)
Result = SUCCESS
hshreedharan :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=2e1b7c23c4964b8860b876cc5c8c3642c4d74ab9
Files :
* flume-ng-sdk/src/main/java/org/apache/flume/api/NettyAvroRpcClient.java
* flume-ng-sdk/src/test/java/org/apache/flume/api/TestNettyAvroRpcClient.java
> Flume RPC Client creates 2 threads per each log attempt if the remote flume
> agent goes down
> -------------------------------------------------------------------------------------------
>
> Key: FLUME-2002
> URL: https://issues.apache.org/jira/browse/FLUME-2002
> Project: Flume
> Issue Type: Bug
> Components: Client SDK
> Affects Versions: v1.3.0, v1.3.1
> Reporter: Edward Sargisson
> Assignee: Mike Percy
> Fix For: v1.4.0
>
> Attachments: FLUME-2002-2.patch, Screenshot.png,
> zzzzzzzzzzzzzzzzzTest.tar.gz
>
>
> Steps to reproduce (use attached Maven project):
> 1. Start your remote flume agent
> 2. Run the Maven project and attach to it with the debugger in your favourite
> IDE (I use NetBeans)
> 3. Kill your remote flume agent
> 4. Rapidly press enter
> Each time you press Enter, 2 new threads show up. See the attached
> screenshot. Notice the panel on the left is littered with new threads. I was
> pressing Enter rapidly for 30 seconds.
> NOTE: This also happens if the remote flume agent hasn't been started at all.
--
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
