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 "Kan Zhang (JIRA)" <ji...@apache.org> on 2010/02/17 18:25:27 UTC

[jira] Commented: (HADOOP-6572) RPC responses may be out-of-order with respect to SASL

    [ https://issues.apache.org/jira/browse/HADOOP-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834848#action_12834848 ] 

Kan Zhang commented on HADOOP-6572:
-----------------------------------

An error log we observed.

Error: javax.security.sasl.SaslException: DIGEST-MD5: Out of order sequencing of messages from server. Got: 9 Expected: 8 at com.sun.security.sasl.digest.DigestMD5Base$DigestIntegrity.unwrap(DigestMD5Base.java:1015) at com.sun.security.sasl.digest.DigestMD5Base.unwrap(DigestMD5Base.java:201) at org.apache.hadoop.security.SaslInputStream.readMoreData(SaslInputStream.java:97) at org.apache.hadoop.security.SaslInputStream.read(SaslInputStream.java:231) at java.io.FilterInputStream.read(FilterInputStream.java:116) at org.apache.hadoop.ipc.Client$Connection$PingInputStream.read(Client.java:329) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.DataInputStream.readInt(DataInputStream.java:370) at org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:620) at org.apache.hadoop.ipc.Client$Connection.run(Client.java:565) 

> 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
>
> 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.