You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2015/06/04 16:23:38 UTC

[jira] [Created] (PROTON-900) [proton-j] the transport still emits AMQP header and frames after SASL failure

Robbie Gemmell created PROTON-900:
-------------------------------------

             Summary: [proton-j] the transport still emits AMQP header and frames after SASL failure
                 Key: PROTON-900
                 URL: https://issues.apache.org/jira/browse/PROTON-900
             Project: Qpid Proton
          Issue Type: Bug
          Components: proton-j
    Affects Versions: 0.9.1
            Reporter: Robbie Gemmell


After the SASL outcome is determined to be failed, the transport still emits the AMQP header and any frames it can such as Open+Close frames.

Most if not all of the code that I have seen creates and opens a Connection object locally at the same time as initiating the SASL exchange. If the SASL outcome is a failure, shared error handling might also lead to the Connection object being closed. In this case I wouldnt expect the transport to emit anything further, but it does currently emit the AMQP header, and open + close frames.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)