[
https://issues.apache.org/jira/browse/FLUME-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474734#comment-13474734
]
Hudson commented on FLUME-1569:
-------------------------------
Integrated in flume-trunk #313 (See
[https://builds.apache.org/job/flume-trunk/313/])
FLUME-1569: MemoryChannel uses an Integer as a lock (Revision
0b59252e772e5d82067cb694285f6bf7f9cf41a0)
Result = SUCCESS
brock :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=0b59252e772e5d82067cb694285f6bf7f9cf41a0
Files :
* flume-ng-core/src/main/java/org/apache/flume/channel/MemoryChannel.java
> MemoryChannel uses an Integer as a lock
> ---------------------------------------
>
> Key: FLUME-1569
> URL: https://issues.apache.org/jira/browse/FLUME-1569
> Project: Flume
> Issue Type: Improvement
> Affects Versions: v1.2.0, v1.3.0
> Reporter: Brock Noland
> Assignee: Daisuke Kobayashi
> Priority: Trivial
> Fix For: v1.3.0
>
> Attachments: FLUME-1569-2.patch, FLUME-1569-3.patch, FLUME-1569.txt
>
>
> MemoryChannel uses an Integer has a lock, field queueLock. Some IDEs will
> intern Integer objects. We should use new Object() here to ensure this
> doesn't happen.
--
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
