[
https://issues.apache.org/jira/browse/HADOOP-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834860#action_12834860
]
Hadoop QA commented on HADOOP-6572:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12436116/c6572-02.patch
against trunk revision 910741.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/10/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/10/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/10/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/10/console
This message is automatically generated.
> RPC responses may be out-of-order with respect to SASL
> ------------------------------------------------------
>
> Key: HADOOP-6572
> URL: https://issues.apache.org/jira/browse/HADOOP-6572
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc, security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Attachments: c6572-02.patch
>
>
> SASL enforces its own message ordering. When RPC server sends its responses
> back, response A may be wrapped by SASL before response B but is put on
> response queue after response B. This results in RPC client receiving wrapped
> response B ahead of A. When the received messages are unwrapped by SASL, SASL
> complaints the messages are out of order.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
