[PROTON-119] Engine can switch from SASL to plain AMQP transport too soon

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.1, proton-0.2
• Fix Version/s: proton-0.3
• Component/s: proton-j
• Assignee: Gordon Sim
• Reporter: Gordon Sim
• Created: 05/Nov/12 19:31
• Updated: 07/Jan/16 11:28
• Resolved: 05/Nov/12 19:53

Description

The engine gets output from the AMQP engine rather than SASL wrapper as soon as the SASl negotiation is marked as done. In the case where the 'server' only supports ANONYMOUS and immediately sends an outcome without actually waiting for the initial frame from the client, this happens too soon, before the init is sent (and even the SASL header).