[jira] [Created] (PROTON-1554) c++: remove thread_safe and returned templates

Alan Conway created PROTON-1554: --- Summary: c++: remove thread_safe and returned templates Key: PROTON-1554 URL: https://issues.apache.org/jira/browse/PROTON-1554 Project: Qpid Proton Issue

[jira] [Created] (PROTON-1553) c++ add support for wake() with MT example

Alan Conway created PROTON-1553: --- Summary: c++ add support for wake() with MT example Key: PROTON-1553 URL: https://issues.apache.org/jira/browse/PROTON-1553 Project: Qpid Proton Issue Type:

Re: Setting SASL realm

On 24/08/17 16:38, Alan Conway wrote: What I'm getting at is if we have an AMQP server that acts as multiple hosts, then you probably want to co-ordinate between whatever you regard as the 'host' (SNI, SASL, AMQP, please God let them be the same) and SASL realms. Agreed. SNI, sasl-init and

Re: Setting SASL realm

On Thu, 2017-08-24 at 16:13 +0200, Rob Godfrey wrote: > On 24 August 2017 at 15:06, Gordon Sim wrote: > > > On 24/08/17 13:42, Alan Conway wrote: > > > > > On Thu, 2017-08-24 at 08:17 +0100, Gordon Sim wrote: > > > > > > > On Tue, Aug 22, 2017, at 11:15 AM, Alan Conway wrote:

[jira] [Created] (PROTON-1552) Epoll proactor example crash when given invalid hostname

Jiri Danek created PROTON-1552: -- Summary: Epoll proactor example crash when given invalid hostname Key: PROTON-1552 URL: https://issues.apache.org/jira/browse/PROTON-1552 Project: Qpid Proton

Re: Setting SASL realm

On Thu, 2017-08-24 at 14:06 +0100, Gordon Sim wrote: > On 24/08/17 13:42, Alan Conway wrote: > > On Thu, 2017-08-24 at 08:17 +0100, Gordon Sim wrote: > > > > On Tue, Aug 22, 2017, at 11:15 AM, Alan Conway wrote: > > > > > Reading the SASL docs I think we also need to allow SASL realm to be > > > >

[jira] [Created] (PROTON-1551) Large Binary encoded incorrectly via data API

Rick Parker created PROTON-1551: --- Summary: Large Binary encoded incorrectly via data API Key: PROTON-1551 URL: https://issues.apache.org/jira/browse/PROTON-1551 Project: Qpid Proton Issue

[jira] [Resolved] (DISPATCH-802) refuse transaction coordination links if they can't be routed to a coordinator

[ https://issues.apache.org/jira/browse/DISPATCH-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-802. Resolution: Fixed > refuse transaction coordination links if they can't be routed to a

[jira] [Commented] (DISPATCH-802) refuse transaction coordination links if they can't be routed to a coordinator

[ https://issues.apache.org/jira/browse/DISPATCH-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140097#comment-16140097 ] ASF GitHub Bot commented on DISPATCH-802: - Github user asfgit closed the pull request at:

[jira] [Commented] (DISPATCH-802) refuse transaction coordination links if they can't be routed to a coordinator

[ https://issues.apache.org/jira/browse/DISPATCH-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140096#comment-16140096 ] ASF subversion and git services commented on DISPATCH-802: -- Commit

[GitHub] qpid-dispatch pull request #190: DISPATCH-802 - Additional fixes - 1. Modifi...

Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/190 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Commented] (DISPATCH-802) refuse transaction coordination links if they can't be routed to a coordinator

[ https://issues.apache.org/jira/browse/DISPATCH-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140079#comment-16140079 ] ASF GitHub Bot commented on DISPATCH-802: - Github user gemmellr commented on the issue:

[GitHub] qpid-dispatch issue #190: DISPATCH-802 - Additional fixes - 1. Modified erro...

Github user gemmellr commented on the issue: https://github.com/apache/qpid-dispatch/pull/190 Tested the latest version and the attach target is now null as needed to indicate refusal, and the updated error details look good. --- If your project is set up for it, you can reply to

[jira] [Updated] (QPID-7894) SSL client auth with multiple connections does not properly use ssl_cert_name connection property

[ https://issues.apache.org/jira/browse/QPID-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-7894: - Fix Version/s: (was: qpid-cpp-1.36.0) Clearing the fix-version since no change was actually

Re: Setting SASL realm

On 24 August 2017 at 15:06, Gordon Sim wrote: > On 24/08/17 13:42, Alan Conway wrote: > >> On Thu, 2017-08-24 at 08:17 +0100, Gordon Sim wrote: >> >>> On Tue, Aug 22, 2017, at 11:15 AM, Alan Conway wrote: > Reading the SASL docs I think we also need to allow SASL realm

[jira] [Commented] (QPID-7894) SSL client auth with multiple connections does not properly use ssl_cert_name connection property

[ https://issues.apache.org/jira/browse/QPID-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140058#comment-16140058 ] Chris Richardson commented on QPID-7894: See discussion at

[jira] [Closed] (QPID-7894) SSL client auth with multiple connections does not properly use ssl_cert_name connection property

[ https://issues.apache.org/jira/browse/QPID-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Richardson closed QPID-7894. -- Resolution: Not A Bug Fix Version/s: qpid-cpp-1.36.0 Closing this issue as it appears to

Re: Setting SASL realm

On 24/08/17 13:42, Alan Conway wrote: On Thu, 2017-08-24 at 08:17 +0100, Gordon Sim wrote: On Tue, Aug 22, 2017, at 11:15 AM, Alan Conway wrote: Reading the SASL docs I think we also need to allow SASL realm to be set on a per-connection basis, in CONNECTION_BOUND - and expose that in all

Re: Setting SASL realm

On Thu, 2017-08-24 at 08:17 +0100, Gordon Sim wrote: > On 24/08/17 05:53, Andrew Stitcher wrote: > > I think connection bound is after authentication - unless I'm forgetting > > things due to vacation all events are after authentication. > > Having been poking around in this area recently, I can

Re: Setting SASL realm

On Thu, 2017-08-24 at 00:53 -0400, Andrew Stitcher wrote: > I think connection bound is after authentication - unless I'm forgetting > things due to vacation all events are after authentication. Not according to my tests - the connection parameters are copied to the sasl object in bind() but the

[jira] [Resolved] (PROTON-1375) Compile without warnings under clang 4.0

[ https://issues.apache.org/jira/browse/PROTON-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek resolved PROTON-1375. Resolution: Resolved > Compile without warnings under clang 4.0 >

[jira] [Updated] (PROTON-1375) Compile without warnings under clang 4.0

[ https://issues.apache.org/jira/browse/PROTON-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated PROTON-1375: --- Description: The following warnings prevent me from compiling proton-c with clang 4.0 snaphot # (/)

[jira] [Commented] (PROTON-1375) Compile without warnings under clang 4.0

[ https://issues.apache.org/jira/browse/PROTON-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139843#comment-16139843 ] Jiri Danek commented on PROTON-1375: The second problem was since removed in a commit related to

[jira] [Created] (QPID-7898) [Java 0-8...0-9-1 Client] Calling getJMSReplyTo on a received message can lead to NullPointerException

Lorenz Quack created QPID-7898: -- Summary: [Java 0-8...0-9-1 Client] Calling getJMSReplyTo on a received message can lead to NullPointerException Key: QPID-7898 URL: https://issues.apache.org/jira/browse/QPID-7898

Re: Setting SASL realm

I think connection bound is after authentication - unless I'm forgetting things due to vacation all events are after authentication. A On Tue, Aug 22, 2017, at 11:15 AM, Alan Conway wrote: > Reading the SASL docs I think we also need to allow SASL realm to be > set on a per-connection basis, in

[jira] [Closed] (QPID-7890) Qpid C++ Broker 1.36 Max Connections Per User Option not working

[ https://issues.apache.org/jira/browse/QPID-7890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Spud Strumpet closed QPID-7890. --- Resolution: Feedback Received Moved to mailing list as query. > Qpid C++ Broker 1.36 Max Connections

Re: Setting SASL realm

On 24/08/17 05:53, Andrew Stitcher wrote: I think connection bound is after authentication - unless I'm forgetting things due to vacation all events are after authentication. Having been poking around in this area recently, I can confirm that CONNECTION_BOUND will occur *before* the

[GitHub] qpid-jms pull request #12: QPIDJMS-315: Add support for Netty KQueue transpo...

GitHub user michaelandrepearce opened a pull request: https://github.com/apache/qpid-jms/pull/12 QPIDJMS-315: Add support for Netty KQueue transport Add KQueue support Also add safer epoll and kqueue env check to protect from lib loading failure (as found in apache activemq

[jira] [Commented] (QPIDJMS-315) Add support for Netty KQueue transport

[ https://issues.apache.org/jira/browse/QPIDJMS-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139683#comment-16139683 ] ASF GitHub Bot commented on QPIDJMS-315: GitHub user michaelandrepearce opened a pull request:

[jira] [Commented] (QPIDJMS-315) Add support for Netty KQueue transport

[ https://issues.apache.org/jira/browse/QPIDJMS-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139662#comment-16139662 ] ASF GitHub Bot commented on QPIDJMS-315: Github user michaelandrepearce closed the pull request

[jira] [Commented] (QPIDJMS-315) Add support for Netty KQueue transport

[ https://issues.apache.org/jira/browse/QPIDJMS-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139661#comment-16139661 ] ASF GitHub Bot commented on QPIDJMS-315: GitHub user michaelandrepearce opened a pull request:

[GitHub] qpid-jms pull request #11: QPIDJMS-315: Add support for Netty KQueue transpo...

Github user michaelandrepearce closed the pull request at: https://github.com/apache/qpid-jms/pull/11 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] qpid-jms pull request #11: QPIDJMS-315: Add support for Netty KQueue transpo...

GitHub user michaelandrepearce opened a pull request: https://github.com/apache/qpid-jms/pull/11 QPIDJMS-315: Add support for Netty KQueue transport Add KQueue support Also add safer epoll and kqueue env check to protect from lib loading failure (as found in apache activemq

[jira] [Created] (QPIDJMS-315) Add support for Netty KQueue transport

Michael Andre Pearce created QPIDJMS-315: Summary: Add support for Netty KQueue transport Key: QPIDJMS-315 URL: https://issues.apache.org/jira/browse/QPIDJMS-315 Project: Qpid JMS