[PROTON-562] More gracefully handle connections to non-1.0 parties

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: proton-0.7
• Fix Version/s: proton-0.9
• Assignee: Andrew Stitcher
• Reporter: Justin Ross
• Created: 11/Apr/14 18:30
• Updated: 07/Jan/16 12:13
• Resolved: 11/May/15 20:08

Description

Right now, attempting a connection from messenger to a 0-10 only qpidd results in a "SASL header mismatch". That's correct but less helpful than it might be.

jross@localhost bailey$ LD_LIBRARY_PATH=/tmp/tmp.mXaVrrHF8a/lib64 PYTHONPATH=/tmp/tmp.mXaVrrHF8a/lib64/proton/bindings/python/ PN_TRACE_FRM=1 python ~/test.py
[0x2418e30]:  -> SASL
[0x2418e30]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS, initial-response=b""]
[0x2418e30]:ERROR[-2] SASL header mismatch: 'AMQP\x01\x01\x00\x0a'
 
[0x2418e30]:  <- EOS
[0x2418e30]:ERROR[-2] SASL header mismatch: ''
 
[0x2418e30]:  <- EOS
CONNECTION ERROR connection aborted (remote)

See https://issues.apache.org/jira/browse/PROTON-561?focusedCommentId=13966905&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13966905

Issue Links

• is related to: PROTON-561 Using the java broker, messenger apparently doesn't propagate error back from broker to messenger
• is related to: PROTON-574 proton-c: Messenger doesn't indicate when connection is aborted for a SASL negotation failure