You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/02/02 19:44:35 UTC
[jira] [Commented] (HADOOP-11494) Lock acquisition on
WrappedInputStream#unwrappedRpcBuffer may race with another thread
[ https://issues.apache.org/jira/browse/HADOOP-11494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301633#comment-14301633 ]
Hudson commented on HADOOP-11494:
---------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #6977 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/6977/])
HADOOP-11494. Lock acquisition on WrappedInputStream#unwrappedRpcBuffer may race with another thread. Contributed by Ted Yu. (benoy: rev 3472e3bd6c50558870b86c9ccfea5072385fa991)
* hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/SaslRpcClient.java
> Lock acquisition on WrappedInputStream#unwrappedRpcBuffer may race with another thread
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-11494
> URL: https://issues.apache.org/jira/browse/HADOOP-11494
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
> Attachments: hadoop-11494-001.patch, hadoop-11494-002.patch
>
>
> In SaslRpcClient, starting at line 576:
> {code}
> public int read(byte[] buf, int off, int len) throws IOException {
> synchronized(unwrappedRpcBuffer) {
> // fill the buffer with the next RPC message
> if (unwrappedRpcBuffer.remaining() == 0) {
> readNextRpcPacket();
> }
> {code}
> readNextRpcPacket() may assign another ByteBuffer to unwrappedRpcBuffer, making the lock on previous ByteBuffer not useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)