Re: [jira] [Commented] (PROTON-950) SASL PLAIN over cleartext should be supported

Hi, I see there is a new function pn_sasl_set_allow_insecure_mechs(pn_sasl_t *sasl, bool insecure) Is there a way how I can get an access to "pn_sasl_t *sasl" object? Regards, Tomas 2015-07-28 20:55 GMT+02:00 ASF subversion and git services (JIRA) < j...@apache.org>: > > [ > https://issues

[jira] [Created] (PROTON-966) [proton-j] empty frames are logged/traced when sent but not when received

Robbie Gemmell created PROTON-966: - Summary: [proton-j] empty frames are logged/traced when sent but not when received Key: PROTON-966 URL: https://issues.apache.org/jira/browse/PROTON-966 Project: Qp

[jira] [Created] (PROTON-967) make empty frame logging actually mention that it is an empty frame.

Robbie Gemmell created PROTON-967: - Summary: make empty frame logging actually mention that it is an empty frame. Key: PROTON-967 URL: https://issues.apache.org/jira/browse/PROTON-967 Project: Qpid Pr

Re: [jira] [Commented] (PROTON-950) SASL PLAIN over cleartext should be supported

Oh, I found a solution. pn_sasl(pn_transport_t *transport); Tomas 2015-07-30 10:41 GMT+02:00 Tomáš Šoltys : > Hi, > > I see there is a new function pn_sasl_set_allow_insecure_mechs(pn_sasl_t > *sasl, bool insecure) > > Is there a way how I can get an access to "pn_sasl_t *sasl" object? > > Rega

[jira] [Updated] (PROTON-967) [proton-j] make empty frame logging actually mention that it is an empty frame.

[ https://issues.apache.org/jira/browse/PROTON-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-967: -- Summary: [proton-j] make empty frame logging actually mention that it is an empty frame. (was:

[jira] [Commented] (PROTON-967) [proton-j] make empty frame logging actually mention that it is an empty frame.

[ https://issues.apache.org/jira/browse/PROTON-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647484#comment-14647484 ] ASF subversion and git services commented on PROTON-967: Commit 77

[jira] [Commented] (PROTON-966) [proton-j] empty frames are logged/traced when sent but not when received

[ https://issues.apache.org/jira/browse/PROTON-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647483#comment-14647483 ] ASF subversion and git services commented on PROTON-966: Commit 77

[jira] [Resolved] (PROTON-967) [proton-j] make empty frame logging actually mention that it is an empty frame.

[ https://issues.apache.org/jira/browse/PROTON-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-967. --- Resolution: Fixed > [proton-j] make empty frame logging actually mention that it is an empty

[jira] [Resolved] (PROTON-966) [proton-j] empty frames are logged/traced when sent but not when received

[ https://issues.apache.org/jira/browse/PROTON-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-966. --- Resolution: Fixed > [proton-j] empty frames are logged/traced when sent but not when received

[jira] [Commented] (PROTON-905) Long-lived connections leak sessions and links

[ https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647621#comment-14647621 ] Robbie Gemmell commented on PROTON-905: --- All the prior changes in this JIRA have now

[jira] [Commented] (PROTON-941) pn_transport_set_server should fail if invoked after binding.

[ https://issues.apache.org/jira/browse/PROTON-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647628#comment-14647628 ] Robbie Gemmell commented on PROTON-941: --- Is anything being targetted at 0.10 for thi

[jira] [Commented] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647638#comment-14647638 ] Robbie Gemmell commented on PROTON-950: --- [~astitcher] is this done? [~tedross], [~gs

[jira] [Commented] (PROTON-905) Long-lived connections leak sessions and links

[ https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647648#comment-14647648 ] Ken Giusti commented on PROTON-905: --- I'm fine with that. > Long-lived connections leak

[jira] [Created] (PROTON-968) [proton-j] channel-max handling is broken

Robbie Gemmell created PROTON-968: - Summary: [proton-j] channel-max handling is broken Key: PROTON-968 URL: https://issues.apache.org/jira/browse/PROTON-968 Project: Qpid Proton Issue Type: B

[jira] [Updated] (PROTON-842) proton-c should honor channel_max

[ https://issues.apache.org/jira/browse/PROTON-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-842: -- Fix Version/s: 0.10 Component/s: (was: proton-j) proton-c Correctin

[jira] [Commented] (PROTON-842) proton-c should honor channel_max

[ https://issues.apache.org/jira/browse/PROTON-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647710#comment-14647710 ] Robbie Gemmell commented on PROTON-842: --- proton_tests.engine.ConnectionTest.test_cha

[jira] [Commented] (PROTON-961) messenger doesn't handle multi-frame transfers

[ https://issues.apache.org/jira/browse/PROTON-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647929#comment-14647929 ] ASF subversion and git services commented on PROTON-961: Commit 09

[jira] [Updated] (PROTON-961) messenger doesn't handle received multi-frame transfers

[ https://issues.apache.org/jira/browse/PROTON-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-961: -- Affects Version/s: (was: 0.11) (was: 0.10) Fix Version/s:

[jira] [Commented] (PROTON-961) messenger doesn't handle multi-frame transfers

[ https://issues.apache.org/jira/browse/PROTON-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647946#comment-14647946 ] Robbie Gemmell commented on PROTON-961: --- I've checked in Gordons suggested fix. It

[jira] [Resolved] (PROTON-961) messenger doesn't handle received multi-frame transfers

[ https://issues.apache.org/jira/browse/PROTON-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-961. --- Resolution: Fixed > messenger doesn't handle received multi-frame transfers >

[jira] [Updated] (PROTON-905) Long-lived connections leak sessions and links

[ https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-905: -- Affects Version/s: 0.10 Fix Version/s: (was: 0.10) 0.11 > Lon

[jira] [Commented] (PROTON-905) Long-lived connections leak sessions and links

[ https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647951#comment-14647951 ] Robbie Gemmell commented on PROTON-905: --- Ok, I've bumped the versions accordingly.

0.10 beta2?

I think it would be good to do a second(/final) beta for 0.10 and keep the process moving, hopefully then being able to spin an RC early next week. One of the previous blockers has been reverted and bumped to 0.11 due to various issues with the earlier change. The other has had some work done for

[jira] [Commented] (PROTON-961) messenger doesn't handle received multi-frame transfers

[ https://issues.apache.org/jira/browse/PROTON-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647989#comment-14647989 ] Philip Preston commented on PROTON-961: --- I'll have a test with the original OpenMAMA

[jira] [Commented] (PROTON-953) Travis CI tox tests fail to correctly build python 2.6 extension lib

[ https://issues.apache.org/jira/browse/PROTON-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648093#comment-14648093 ] ASF subversion and git services commented on PROTON-953: Commit 7f

[jira] [Created] (PROTON-969) Cyrus SASL module calls sasl_server_init once for every incoming connection

Ted Ross created PROTON-969: --- Summary: Cyrus SASL module calls sasl_server_init once for every incoming connection Key: PROTON-969 URL: https://issues.apache.org/jira/browse/PROTON-969 Project: Qpid Proton

[jira] [Created] (PROTON-970) SASL options for setting path and name should not be transport-specific

Ted Ross created PROTON-970: --- Summary: SASL options for setting path and name should not be transport-specific Key: PROTON-970 URL: https://issues.apache.org/jira/browse/PROTON-970 Project: Qpid Proton

[jira] [Commented] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648105#comment-14648105 ] Andrew Stitcher commented on PROTON-950: At this point I don't think master is blo

[jira] [Resolved] (PROTON-953) Travis CI tox tests fail to correctly build python 2.6 extension lib

[ https://issues.apache.org/jira/browse/PROTON-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-953. --- Resolution: Fixed > Travis CI tox tests fail to correctly build python 2.6 extension lib > ---

[jira] [Commented] (PROTON-970) SASL options for setting path and name should not be transport-specific

[ https://issues.apache.org/jira/browse/PROTON-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648223#comment-14648223 ] Andrew Stitcher commented on PROTON-970: This is more-or-less the same as PROTON-8

[jira] [Commented] (PROTON-970) SASL options for setting path and name should not be transport-specific

[ https://issues.apache.org/jira/browse/PROTON-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648226#comment-14648226 ] Andrew Stitcher commented on PROTON-970: >From an API stand point I believe that d

[jira] [Updated] (PROTON-969) Cyrus SASL module calls sasl_server_init once for every incoming connection

[ https://issues.apache.org/jira/browse/PROTON-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-969: --- Priority: Major (was: Blocker) > Cyrus SASL module calls sasl_server_init once for every inco

[jira] [Commented] (PROTON-969) Cyrus SASL module calls sasl_server_init once for every incoming connection

[ https://issues.apache.org/jira/browse/PROTON-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648268#comment-14648268 ] Andrew Stitcher commented on PROTON-969: I'm pretty sure this isn't a blocker. The

[jira] [Assigned] (PROTON-969) Cyrus SASL module calls sasl_server_init once for every incoming connection

[ https://issues.apache.org/jira/browse/PROTON-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-969: -- Assignee: Andrew Stitcher > Cyrus SASL module calls sasl_server_init once for every inc