[jira] [Created] (QPID-8073) Various documentation fixes

Justin Ross created QPID-8073: - Summary: Various documentation fixes Key: QPID-8073 URL: https://issues.apache.org/jira/browse/QPID-8073 Project: Qpid Issue Type: Improvement

[jira] [Commented] (QPID-8072) Remove the obsolete Ruby management API

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

[jira] [Created] (QPID-8072) Remove the obsolete Ruby management API

Justin Ross created QPID-8072: - Summary: Remove the obsolete Ruby management API Key: QPID-8072 URL: https://issues.apache.org/jira/browse/QPID-8072 Project: Qpid Issue Type: Task

Re: Review Request 64645: authorization support for sasl delegation plugin

> On Dec. 15, 2017, 9:41 p.m., Chug Rolke wrote: > > This seems like a decent approach for starters. > > > > It may have an issue when multiple vhosts come in to the router on the same > > port. All of the connections then are sent to the same authServicePlugin > > authService port for

[jira] [Commented] (PROTON-1738) [ruby-binding] incompatible with ruby 2.0.0

[ https://issues.apache.org/jira/browse/PROTON-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319072#comment-16319072 ] Alan Conway commented on PROTON-1738: - Attached patch partially fixes the 2.0.0 issues, but there are

[jira] [Updated] (PROTON-1738) [ruby-binding] incompatible with ruby 2.0.0

[ https://issues.apache.org/jira/browse/PROTON-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1738: Attachment: 0001-WIP-Fix-for-issues-on-ruby-2.0.0.patch > [ruby-binding] incompatible with ruby

[jira] [Closed] (PROTON-1718) (Proton-J) Custom Sasl

[ https://issues.apache.org/jira/browse/PROTON-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed PROTON-1718. -- Resolution: Done > (Proton-J) Custom Sasl > -- > > Key:

[jira] [Issue Comment Deleted] (PROTON-1736) add a SASL listener to allow relevant processing as frames arrive

[ https://issues.apache.org/jira/browse/PROTON-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1736: --- Comment: was deleted (was: Github user gemmellr commented on the issue:

[jira] [Commented] (PROTON-1718) (Proton-J) Custom Sasl

[ https://issues.apache.org/jira/browse/PROTON-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318874#comment-16318874 ] Tim Taylor commented on PROTON-1718: Great! Thanks again for your help with this! > (Proton-J)

[jira] [Commented] (PROTON-1736) add a SASL listener to allow relevant processing as frames arrive

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

[GitHub] qpid-proton-j issue #13: Added API to Transport interface to allow custom sa...

Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton-j/pull/13 For completeness, a different change was made via https://issues.apache.org/jira/browse/PROTON-1736 in commit 17cef9ace9a7c75901d517f951ae1d4610819436. ---

[jira] [Commented] (PROTON-1718) (Proton-J) Custom Sasl

[ https://issues.apache.org/jira/browse/PROTON-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318865#comment-16318865 ] Robbie Gemmell commented on PROTON-1718: Glad to hear it works for you. I'll close this out now.

[jira] [Commented] (PROTON-1737) Expose set/get for maxFrameSize in the Connection.Open performative

[ https://issues.apache.org/jira/browse/PROTON-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318858#comment-16318858 ] Robbie Gemmell commented on PROTON-1737: The frame size details are already

[jira] [Created] (DISPATCH-907) cannot set address phase via qdmanage tool

Ken Giusti created DISPATCH-907: --- Summary: cannot set address phase via qdmanage tool Key: DISPATCH-907 URL: https://issues.apache.org/jira/browse/DISPATCH-907 Project: Qpid Dispatch Issue

[jira] [Resolved] (QPIDIT-97) Release qpid-interop-test 0.1.0

[ https://issues.apache.org/jira/browse/QPIDIT-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPIDIT-97. Resolution: Fixed > Release qpid-interop-test 0.1.0 > --- > >

[jira] [Comment Edited] (QPID-8064) [Broker-J] FileKeyStore should validate java keystore content to make sure that private key is present

[ https://issues.apache.org/jira/browse/QPID-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318655#comment-16318655 ] Keith Wall edited comment on QPID-8064 at 1/9/18 4:19 PM: -- I am not sure if this

[jira] [Updated] (QPID-8044) [JMS AMQP 0-x] Address minor packaging issues raised during 6.3.0 vote

[ https://issues.apache.org/jira/browse/QPID-8044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8044: - Status: Reviewable (was: In Progress) > [JMS AMQP 0-x] Address minor packaging issues raised during 6.3.0

[jira] [Updated] (QPID-8064) [Broker-J] FileKeyStore should validate java keystore content to make sure that private key is present

[ https://issues.apache.org/jira/browse/QPID-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8064: - Affects Version/s: qpid-java-6.0.8 qpid-java-broker-7.0.0

[jira] [Updated] (QPID-8064) [Broker-J] FileKeyStore should validate java keystore content to make sure that private key is present

[ https://issues.apache.org/jira/browse/QPID-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8064: - Fix Version/s: (was: qpid-java-6.1.5) (was: qpid-java-6.0.8)

[jira] [Commented] (QPID-8064) [Broker-J] FileKeyStore should validate java keystore content to make sure that private key is present

[ https://issues.apache.org/jira/browse/QPID-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318655#comment-16318655 ] Keith Wall commented on QPID-8064: -- I am not sure if this should be a responsibility of the keystore or a

[jira] [Commented] (QPID-8066) [Broker-J] Virtual host logger rules are left over in configuration store after deletion of virtual host logger on provided virtual host

[ https://issues.apache.org/jira/browse/QPID-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318648#comment-16318648 ] Keith Wall commented on QPID-8066: -- I'm guessing from the description that this wouldn't happen for a JSON

[jira] [Updated] (QPID-8066) [Broker-J] Virtual host logger rules are left over in configuration store after deletion of virtual host logger on provided virtual host

[ https://issues.apache.org/jira/browse/QPID-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8066: - Fix Version/s: qpid-java-broker-7.1.0 qpid-java-broker-7.0.1 > [Broker-J] Virtual host

[jira] [Closed] (QPID-8069) [Qpid JMS AMQP 0-x] An establishment of connection blocks for 30 seconds on TLS handshake failure

[ https://issues.apache.org/jira/browse/QPID-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed QPID-8069. Resolution: Won't Fix > [Qpid JMS AMQP 0-x] An establishment of connection blocks for 30 seconds on > TLS

[jira] [Commented] (QPID-8069) [Qpid JMS AMQP 0-x] An establishment of connection blocks for 30 seconds on TLS handshake failure

[ https://issues.apache.org/jira/browse/QPID-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318633#comment-16318633 ] Keith Wall commented on QPID-8069: -- Agreed, this is a defect, but as this client is not receiving active

[jira] [Comment Edited] (QPID-8069) [Qpid JMS AMQP 0-x] An establishment of connection blocks for 30 seconds on TLS handshake failure

[ https://issues.apache.org/jira/browse/QPID-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318633#comment-16318633 ] Keith Wall edited comment on QPID-8069 at 1/9/18 3:51 PM: -- Agreed, this is a

[jira] [Updated] (QPID-8067) [Broker-J] Default queue filter for arrival time with non-zero replay period does not filter messages as documented

[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8067: - Fix Version/s: qpid-java-broker-7.0.1 > [Broker-J] Default queue filter for arrival time with non-zero

[jira] [Commented] (QPID-8067) [Broker-J] Default queue filter for arrival time with non-zero replay period does not filter messages as documented

[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318628#comment-16318628 ] Keith Wall commented on QPID-8067: -- Alex - I agree with your analysis. I think this should be fixed on

[jira] [Updated] (QPID-8067) [Broker-J] Default queue filter for arrival time with non-zero replay period does not filter messages as documented

[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8067: - Fix Version/s: qpid-java-broker-7.1.0 > [Broker-J] Default queue filter for arrival time with non-zero

[jira] [Commented] (QPID-8061) [Broker-J] [AMQP 0-8..0-9-1] Declaring exchange with not existing alternate binding crashes the Broker

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

[jira] [Commented] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Declaring queue that specifies an alternate binding that does not exist crashes the Broker

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

[jira] [Commented] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Declaring queue that specifies an alternate binding that does not exist crashes the Broker

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

[jira] [Commented] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Declaring queue that specifies an alternate binding that does not exist crashes the Broker

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

[jira] [Commented] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Declaring queue that specifies an alternate binding that does not exist crashes the Broker

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

[jira] [Commented] (QPID-8061) [Broker-J] [AMQP 0-8..0-9-1] Declaring exchange with not existing alternate binding crashes the Broker

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

[jira] [Updated] (QPID-8067) [Broker-J] Default queue filter for arrival time with non-zero replay period does not filter messages as documented

[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8067: - Description: As per Broker documentation the replay period in arrival filter determines a time interval (

[jira] [Commented] (QPID-8068) [JMS AMQP 0-x] Change of noLocal on re-subscription of durable subscriber does not re-create the subscription

[ https://issues.apache.org/jira/browse/QPID-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318604#comment-16318604 ] Keith Wall commented on QPID-8068: -- Agreed, this is a defect, but as this client is not receiving active

[jira] [Resolved] (QPID-8068) [JMS AMQP 0-x] Change of noLocal on re-subscription of durable subscriber does not re-create the subscription

[ https://issues.apache.org/jira/browse/QPID-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8068. -- Resolution: Won't Fix > [JMS AMQP 0-x] Change of noLocal on re-subscription of durable subscriber >

[jira] [Updated] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart

[ https://issues.apache.org/jira/browse/QPID-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8070: - Fix Version/s: qpid-java-6.1.5 qpid-java-broker-7.0.1 > Qpid java broker is unable to

[jira] [Updated] (QPID-8071) Java Qpid library does not report that session was closed

[ https://issues.apache.org/jira/browse/QPID-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8071: - Component/s: (was: Broker-J) JMS AMQP 0-x > Java Qpid library does not report that

[jira] [Comment Edited] (QPID-8071) Java Qpid library does not report that session was closed

[ https://issues.apache.org/jira/browse/QPID-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318570#comment-16318570 ] Keith Wall edited comment on QPID-8071 at 1/9/18 3:15 PM: -- Hi Alojzij >From the

[jira] [Commented] (QPID-8071) Java Qpid library does not report that session was closed

[ https://issues.apache.org/jira/browse/QPID-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318570#comment-16318570 ] Keith Wall commented on QPID-8071: -- Hi Alojzi >From the stack trace, I see you are reporting a problem

[jira] [Commented] (QPID-8044) [JMS AMQP 0-x] Address minor packaging issues raised during 6.3.0 vote

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

[jira] [Commented] (QPID-8044) [JMS AMQP 0-x] Address minor packaging issues raised during 6.3.0 vote

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

[jira] [Updated] (QPID-8071) Java Qpid library does not report that session was closed

[ https://issues.apache.org/jira/browse/QPID-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alojzij Blatnik updated QPID-8071: -- Environment: slow network towards Qpid broker for instance set this to the machine that is

[jira] [Updated] (QPID-8071) Java Qpid library does not report that session was closed

[ https://issues.apache.org/jira/browse/QPID-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alojzij Blatnik updated QPID-8071: -- Description: when qpid.io_network_transport_timeout is exceeded, qpid-java library does not

[jira] [Updated] (QPID-8071) Java Qpid library does not report that session was closed

[ https://issues.apache.org/jira/browse/QPID-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alojzij Blatnik updated QPID-8071: -- Description: when qpid.io_network_transport_timeout is exceeded, qpid-java library does not

[jira] [Updated] (QPID-8071) Java Qpid library does not report that session was closed

[ https://issues.apache.org/jira/browse/QPID-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alojzij Blatnik updated QPID-8071: -- Description: when qpid.io_network_transport_timeout is exceeded, qpid-java library does not

[jira] [Updated] (QPID-8071) Java Qpid library does not report that session was closed

[ https://issues.apache.org/jira/browse/QPID-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alojzij Blatnik updated QPID-8071: -- Description: when qpid.io_network_transport_timeout is exceeded, qpid-java library does not

[jira] [Created] (QPID-8071) Java Qpid library does not report that session was closed

Alojzij Blatnik created QPID-8071: - Summary: Java Qpid library does not report that session was closed Key: QPID-8071 URL: https://issues.apache.org/jira/browse/QPID-8071 Project: Qpid Issue

[jira] [Updated] (PROTON-1738) [ruby-binding] incompatible with ruby 2.0.0

[ https://issues.apache.org/jira/browse/PROTON-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1738: Fix Version/s: proton-c-0.20.0 > [ruby-binding] incompatible with ruby 2.0.0 >

[jira] [Comment Edited] (PROTON-1738) [ruby-binding] incompatible with ruby 2.0.0

[ https://issues.apache.org/jira/browse/PROTON-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318322#comment-16318322 ] Jiri Daněk edited comment on PROTON-1738 at 1/9/18 12:18 PM: - Having fixed

[jira] [Comment Edited] (PROTON-1738) [ruby-binding] incompatible with ruby 2.0.0

[ https://issues.apache.org/jira/browse/PROTON-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318322#comment-16318322 ] Jiri Daněk edited comment on PROTON-1738 at 1/9/18 12:17 PM: - Having fixed

[jira] [Commented] (PROTON-1738) [ruby-binding] incompatible with ruby 2.0.0

[ https://issues.apache.org/jira/browse/PROTON-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318322#comment-16318322 ] Jiri Daněk commented on PROTON-1738: Having fixed the above, I get {noformat}

[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests

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

[jira] [Created] (PROTON-1738) [ruby-binding] incompatible with ruby 2.0.0

Jiri Daněk created PROTON-1738: -- Summary: [ruby-binding] incompatible with ruby 2.0.0 Key: PROTON-1738 URL: https://issues.apache.org/jira/browse/PROTON-1738 Project: Qpid Proton Issue Type: