[
https://issues.apache.org/jira/browse/FLUME-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roshan Naik updated FLUME-2159:
-------------------------------
Attachment: FLUME-2159.v2.patch
The failure was becase, in some runs, there was one extra thread that was
running at the start, which was no longer running in the end (perhaps a gc
thread?). The test asserts to ensure that the number of threads at the
start== threads at end for detecting thread leaks.
If the #start < #end , then indeed this can be considered a thread leak.
However in some cases it can be that #start > #end. So relaxed the assertion
accordingly.
> Sporadic failures in TestNettyAvroRpcClient.spinThreadsCrazily()
> -----------------------------------------------------------------
>
> Key: FLUME-2159
> URL: https://issues.apache.org/jira/browse/FLUME-2159
> Project: Flume
> Issue Type: Bug
> Components: Test
> Affects Versions: v1.4.0
> Environment: centos 5
> Reporter: Roshan Naik
> Assignee: Roshan Naik
> Labels: sdk, test
> Attachments: FLUME-2159.patch, FLUME-2159.v2.patch
>
>
> TestNettyAvroRpcClient.spinThreadsCrazily() checks to see if the active
> thread count at the end is the same as the count when it started. I see that
> once in while the count is off by 1 due to a thread taking a bit longer to
> wind up.
--
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
