[jira] [Commented] (PROTON-975) connecting with DIGEST-MD5 fails if buffer containing outcome and first encrypted frame is received

[ https://issues.apache.org/jira/browse/PROTON-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681909#comment-14681909 ] ASF subversion and git services commented on PROTON-975: Commit

[jira] [Commented] (PROTON-975) connecting with DIGEST-MD5 fails if buffer containing outcome and first encrypted frame is received

[ https://issues.apache.org/jira/browse/PROTON-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681983#comment-14681983 ] ASF subversion and git services commented on PROTON-975: Commit

Re: [VOTE] Release Qpid Proton 0.10 (RC2)

-1 unfortunately. I've been testing against Dispatch and I'm seeing lots of timeouts on the tests. It turns out that pn_read_frame is used to parse text that is not a frame header. It's actually the AMQP header so it interprets the string AMQP as the frame length. Now that we're testing

[jira] [Commented] (PROTON-899) Unnecessary relative path in include

[ https://issues.apache.org/jira/browse/PROTON-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682152#comment-14682152 ] ASF subversion and git services commented on PROTON-899: Commit

[jira] [Commented] (PROTON-978) Framing errors after SASL exchange when max-frame-size is configured

[ https://issues.apache.org/jira/browse/PROTON-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682291#comment-14682291 ] Andrew Stitcher commented on PROTON-978: As far as I can tell this will happen on

[jira] [Updated] (PROTON-975) connecting with DIGEST-MD5 fails if buffer containing outcome and first encrypted frame is received

[ https://issues.apache.org/jira/browse/PROTON-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-975: -- Fix Version/s: (was: 0.10.1) 0.10 Bringing back in to 0.10 since we need

[CANCELLED] [VOTE] Release Qpid Proton 0.10 (RC2)

I am cancelling the vote on the seconr RC for Proton 0.10, and will shortly be preparing a third RC. The changes in RC2 uncovered a issue, that while present previously was not causing an observable problem before hand but now does following the additional validation included in RC2 and this

[jira] [Updated] (PROTON-899) Unnecessary relative path in include

[ https://issues.apache.org/jira/browse/PROTON-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-899: -- Fix Version/s: (was: 0.10.1) 0.10 Bringing back into 0.10 as we need a

[jira] [Updated] (PROTON-978) Framing errors after SASL exchange when max-frame-size is configured

[ https://issues.apache.org/jira/browse/PROTON-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-978: Attachment: commit-0d2ef9f Test update to detect the issue. Framing errors after SASL exchange when

[jira] [Commented] (PROTON-974) single symbol for mechanisms in sasl-mechanisms not recognised

[ https://issues.apache.org/jira/browse/PROTON-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682426#comment-14682426 ] ASF subversion and git services commented on PROTON-974: Commit

Re: [VOTE] Release Qpid Proton 0.10 (RC3)

+1 Built visual studio (2008, 2010, 2012, 2013)(x86, x64). Ran tests against qpidd and activemq 5.12 brokers using qpid client auth. - Original Message - From: Robbie Gemmell robbie.gemm...@gmail.com To: us...@qpid.apache.org, proton@qpid.apache.org Sent: Tuesday, August 11, 2015