[
https://issues.apache.org/jira/browse/PROTON-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher closed PROTON-758.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.10
I think this is almost certainly fixed by the new SASL support
> proton-c: assertion failure when SASL fails (PN_SASL_FAIL)
> ----------------------------------------------------------
>
> Key: PROTON-758
> URL: https://issues.apache.org/jira/browse/PROTON-758
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.8
> Reporter: Dominic Evans
> Fix For: 0.10
>
>
> As discussed on IRC
> When SASL negotiation fails (e.g., wrong type, bad user+pass etc.) and you're
> running on a debug build (no-optimization) you hit an assertion failure in
> 0.8 that didn't previously occur in 0.7
> qpid-proton-0.8/proton-c/src/transport/transport.c:1073: transport_consume
> Assertion `n == (-1)' failed.
> It looks like this is because pn_sasl_input is returning PN_ERR when
> PN_SASL_FAIL has occurred.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
