[jira] [Assigned] (PROTON-996) Allow Messenger API to set the allowed auth mechs

[ https://issues.apache.org/jira/browse/PROTON-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-996: -- Assignee: Andrew Stitcher > Allow Messenger API to set the allowed auth mechs > ---

Re: [jira] [Commented] (PROTON-992) Proton's use of Cyrus SASL is not thread-safe.

Thanks! I wondered about that (briefly) but thought there was nothing to be done. If you have a sketch, I would be happy to see it! - Original Message - [ https://issues.apache.org/jira/browse/PROTON-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focuse

Re: Error detection/handling

On 09/17/2015 08:37 AM, Tomáš Šoltys wrote: Here is an output from the broker when trace+ is enabled on protocol level. Thanks! This looks like the same root cause as https://issues.apache.org/jira/browse/QPID-6660, which is now fixed on trunk (but didn't make it into the 0.34 release) Sce

[jira] [Updated] (PROTON-999) Docs: pn_messenger_subscribe(): "source" is undocumented

[ https://issues.apache.org/jira/browse/PROTON-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Leggett updated PROTON-999: -- Description: The pn_messenger_subscribe() function is documented to take a const char * as a "s

[jira] [Commented] (PROTON-992) Proton's use of Cyrus SASL is not thread-safe.

[ https://issues.apache.org/jira/browse/PROTON-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802937#comment-14802937 ] Andrew Stitcher commented on PROTON-992: Upon a few days reflection I've realised

Re: Error detection/handling

Hi Gordon, thanks a lot for help. Condition gives exactly what I needs. Here is an output from the broker when trace+ is enabled on protocol level. Scenario: send 1 message with incorrect subject and afterwards send 3 messages with correct subject. 3 messages will get delivered to the queue. --