[jira] [Created] (QPID-8142) Federated Bindings Do not properly propagate in Line or Star Topology When Brokers are not directly connected to each other

2018-03-27 Thread Tom Peterson (JIRA)
Tom Peterson created QPID-8142: -- Summary: Federated Bindings Do not properly propagate in Line or Star Topology When Brokers are not directly connected to each other Key: QPID-8142 URL:

[jira] [Commented] (PROTON-1809) [python, ruby] Unable to receive messages when max-frame-size is set to more than 2^20

2018-03-27 Thread Alan Conway (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416268#comment-16416268 ] Alan Conway commented on PROTON-1809: - I can reproduce this problem in plain C by patching the

[jira] [Assigned] (DISPATCH-939) Router aborts transfer, closes connection with error on QIT amqp_large_contnet_test

2018-03-27 Thread Ganesh Murthy (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-939: -- Assignee: Ganesh Murthy > Router aborts transfer, closes connection with error on

[jira] [Commented] (DISPATCH-947) system tests on master branch failing when run against latest master proton

2018-03-27 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416170#comment-16416170 ] ASF subversion and git services commented on DISPATCH-947: -- Commit

[jira] [Commented] (DISPATCH-947) system tests on master branch failing when run against latest master proton

2018-03-27 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416149#comment-16416149 ] ASF subversion and git services commented on DISPATCH-947: -- Commit

[GitHub] qpid-dispatch pull request #272: DISPATCH-947: fix system_tests_two_routers....

2018-03-27 Thread kgiusti
Github user kgiusti closed the pull request at: https://github.com/apache/qpid-dispatch/pull/272 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-947) system tests on master branch failing when run against latest master proton

2018-03-27 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416132#comment-16416132 ] ASF subversion and git services commented on DISPATCH-947: -- Commit

[jira] [Commented] (DISPATCH-947) system tests on master branch failing when run against latest master proton

2018-03-27 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416133#comment-16416133 ] ASF GitHub Bot commented on DISPATCH-947: - Github user kgiusti closed the pull request at:

[GitHub] qpid-dispatch pull request #272: DISPATCH-947: fix system_tests_two_routers....

2018-03-27 Thread kgiusti
GitHub user kgiusti opened a pull request: https://github.com/apache/qpid-dispatch/pull/272 DISPATCH-947: fix system_tests_two_routers.test_17_address_wildcard You can merge this pull request into a Git repository by running: $ git pull https://github.com/kgiusti/dispatch

[jira] [Commented] (DISPATCH-947) system tests on master branch failing when run against latest master proton

2018-03-27 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416105#comment-16416105 ] ASF GitHub Bot commented on DISPATCH-947: - GitHub user kgiusti opened a pull request:

[jira] [Commented] (DISPATCH-947) system tests on master branch failing when run against latest master proton

2018-03-27 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416084#comment-16416084 ] ASF subversion and git services commented on DISPATCH-947: -- Commit

[jira] [Commented] (DISPATCH-947) system tests on master branch failing when run against latest master proton

2018-03-27 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416000#comment-16416000 ] ASF subversion and git services commented on DISPATCH-947: -- Commit

[jira] [Commented] (DISPATCH-947) system tests on master branch failing when run against latest master proton

2018-03-27 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415965#comment-16415965 ] ASF subversion and git services commented on DISPATCH-947: -- Commit

[jira] [Resolved] (QPIDJMS-372) [SASL] [XOAUTH2] Access token validation too restrictive

2018-03-27 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPIDJMS-372. Resolution: Fixed PR merged, thanks Keith. > [SASL] [XOAUTH2] Access token validation too

[jira] [Resolved] (PROTON-1814) core/terminus.rb:239:in `block in apply': undefined method[s ...] for # (NoMethodError)

2018-03-27 Thread Alan Conway (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1814. - Resolution: Fixed Fix Version/s: (was: proton-c-0.23.0)

[jira] [Assigned] (QPIDJMS-372) [SASL] [XOAUTH2] Access token validation too restrictive

2018-03-27 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPIDJMS-372: -- Assignee: Robbie Gemmell > [SASL] [XOAUTH2] Access token validation too restrictive >

[jira] [Updated] (QPIDJMS-372) [SASL] [XOAUTH2] Access token validation too restrictive

2018-03-27 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPIDJMS-372: --- Fix Version/s: 0.32.0 > [SASL] [XOAUTH2] Access token validation too restrictive >

[jira] [Commented] (QPIDJMS-372) [SASL] [XOAUTH2] Access token validation too restrictive

2018-03-27 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415888#comment-16415888 ] ASF subversion and git services commented on QPIDJMS-372: - Commit

[GitHub] qpid-jms pull request #16: QPIDJMS-372: [SASL] [XOAUTH2] Make access token v...

2018-03-27 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/qpid-jms/pull/16 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDJMS-372) [SASL] [XOAUTH2] Access token validation too restrictive

2018-03-27 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415887#comment-16415887 ] ASF subversion and git services commented on QPIDJMS-372: - Commit

[jira] [Commented] (PROTON-1814) core/terminus.rb:239:in `block in apply': undefined method[s ...] for # (NoMethodError)

2018-03-27 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415890#comment-16415890 ] ASF subversion and git services commented on PROTON-1814: - Commit

[jira] [Commented] (QPIDJMS-372) [SASL] [XOAUTH2] Access token validation too restrictive

2018-03-27 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415889#comment-16415889 ] ASF GitHub Bot commented on QPIDJMS-372: Github user asfgit closed the pull request at:

[jira] [Comment Edited] (QPID-7541) [Java Broker] Close Consumers when a Queue is deleted

2018-03-27 Thread Artyom Safronov (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415860#comment-16415860 ] Artyom Safronov edited comment on QPID-7541 at 3/27/18 4:18 PM: I found

[jira] [Updated] (QPID-7541) [Java Broker] Close Consumers when a Queue is deleted

2018-03-27 Thread Artyom Safronov (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artyom Safronov updated QPID-7541: -- Attachment: batch_responses.log > [Java Broker] Close Consumers when a Queue is deleted >

[jira] [Commented] (QPID-7541) [Java Broker] Close Consumers when a Queue is deleted

2018-03-27 Thread Artyom Safronov (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415860#comment-16415860 ] Artyom Safronov commented on QPID-7541: --- I found other odd behavior. Next steps were done: * 3

[jira] [Comment Edited] (QPID-7541) [Java Broker] Close Consumers when a Queue is deleted

2018-03-27 Thread Artyom Safronov (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415809#comment-16415809 ] Artyom Safronov edited comment on QPID-7541 at 3/27/18 3:39 PM: Deleting of

[jira] [Commented] (QPID-7541) [Java Broker] Close Consumers when a Queue is deleted

2018-03-27 Thread Artyom Safronov (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415809#comment-16415809 ] Artyom Safronov commented on QPID-7541: --- Deleting of a queue is a exceptional situation. But it was

[jira] [Resolved] (PROTON-1696) Go test of SASL fails if it can't find saslpasswd2

2018-03-27 Thread Alan Conway (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1696. - Resolution: Fixed > Go test of SASL fails if it can't find saslpasswd2 >

[jira] [Commented] (PROTON-1696) Go test of SASL fails if it can't find saslpasswd2

2018-03-27 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415803#comment-16415803 ] ASF subversion and git services commented on PROTON-1696: - Commit

[jira] [Updated] (PROTON-1814) core/terminus.rb:239:in `block in apply': undefined method[s ...] for # (NoMethodError)

2018-03-27 Thread Alan Conway (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1814: Fix Version/s: proton-c-0.23.0 > core/terminus.rb:239:in `block in apply': undefined method[s ...]

[jira] [Commented] (QPID-8141) [JMS AMQP 0-x] Cannot publish message with address based destinations falsely identified as resolved due to unset routing key and exchange name

2018-03-27 Thread Alex Rudyy (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415747#comment-16415747 ] Alex Rudyy commented on QPID-8141: -- It is a regression introduced in 6.0.3 as part of QPID-5816 > [JMS

[jira] [Updated] (QPID-8141) [JMS AMQP 0-x] Cannot publish message with address based destinations falsely identified as resolved due to unset routing key and exchange name

2018-03-27 Thread Alex Rudyy (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8141: - Summary: [JMS AMQP 0-x] Cannot publish message with address based destinations falsely identified as

[jira] [Commented] (PROTON-1696) Go test of SASL fails if it can't find saslpasswd2

2018-03-27 Thread Alan Conway (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415697#comment-16415697 ] Alan Conway commented on PROTON-1696: - +1 that's what I'm doing now, and the same for ruby: ---

[jira] [Commented] (PROTON-1696) Go test of SASL fails if it can't find saslpasswd2

2018-03-27 Thread Andrew Stitcher (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415683#comment-16415683 ] Andrew Stitcher commented on PROTON-1696: - It would be better to just skip in this case (even

[jira] [Commented] (PROTON-1696) Go test of SASL fails if it can't find saslpasswd2

2018-03-27 Thread Andrew Stitcher (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415674#comment-16415674 ] Andrew Stitcher commented on PROTON-1696: - There - I've changed the bug title to reflect the true

[jira] [Updated] (PROTON-1696) Go test of SASL fails if it can't find saslpasswd2

2018-03-27 Thread Andrew Stitcher (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-1696: Summary: Go test of SASL fails if it can't find saslpasswd2 (was: Go test of anonymous

[jira] [Commented] (QPIDJMS-372) [SASL] [XOAUTH2] Access token validation too restrictive

2018-03-27 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415643#comment-16415643 ] ASF GitHub Bot commented on QPIDJMS-372: GitHub user k-wall opened a pull request:

[jira] [Commented] (PROTON-1696) Go test of anonymous SASL fails if it can't find saslpasswd2

2018-03-27 Thread Alan Conway (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415641#comment-16415641 ] Alan Conway commented on PROTON-1696: - [~astitcher] These are not failing in anonymous tests, they

[GitHub] qpid-jms pull request #16: QPIDJMS-372: [SASL] [XOAUTH2] Make access token v...

2018-03-27 Thread k-wall
GitHub user k-wall opened a pull request: https://github.com/apache/qpid-jms/pull/16 QPIDJMS-372: [SASL] [XOAUTH2] Make access token validation comply wit… Makes the client's validation of OAUTH-2 access tokens RFC-6749 compliant. You can merge this pull request into a Git

[jira] [Updated] (QPID-8141) [JMS AMQP 0-x] Routing key and exchange name might not be set on address based destinations falsely identified as resolved

2018-03-27 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8141: - Summary: [JMS AMQP 0-x] Routing key and exchange name might not be set on address based destinations

[jira] [Updated] (PROTON-1814) core/terminus.rb:239:in `block in apply': undefined method[s ...] for # (NoMethodError)

2018-03-27 Thread JIRA
[ https://issues.apache.org/jira/browse/PROTON-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated PROTON-1814: --- Description: {noformat} bin/cli-proton-ruby-receiver -c 1 --log-msgs dict --broker

[jira] [Created] (PROTON-1814) core/terminus.rb:239:in `block in apply': undefined method[s ...] for # (NoMethodError)

2018-03-27 Thread JIRA
Jiri Daněk created PROTON-1814: -- Summary: core/terminus.rb:239:in `block in apply': undefined method[s ...] for # (NoMethodError) Key: PROTON-1814 URL: https://issues.apache.org/jira/browse/PROTON-1814

[jira] [Updated] (PROTON-1809) [python, ruby] Unable to receive messages when max-frame-size is set to more than 2^20

2018-03-27 Thread JIRA
[ https://issues.apache.org/jira/browse/PROTON-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated PROTON-1809: --- Priority: Minor (was: Major) > [python, ruby] Unable to receive messages when max-frame-size is set

[jira] [Updated] (QPID-8141) [JMS AMQP 0-x] Routing key and exchange name might not be set on address based destinations falsly identified as resolved

2018-03-27 Thread Alex Rudyy (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8141: - Description: Address based destination resolution functionality {{AMQSession#resolveAddress}} sets a

[jira] [Created] (QPID-8141) [JMS AMQP 0-x] Routing key and exchange name might not be set on address based destinations falsly identified as resolved

2018-03-27 Thread Alex Rudyy (JIRA)
Alex Rudyy created QPID-8141: Summary: [JMS AMQP 0-x] Routing key and exchange name might not be set on address based destinations falsly identified as resolved Key: QPID-8141 URL:

[jira] [Updated] (QPID-8140) [Broker-J][BDB HA] Removal of non existing group member can end up in broker crash due to uncaught MemberNotFoundException

2018-03-27 Thread Alex Rudyy (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8140: - Attachment:

[jira] [Updated] (QPID-8140) [Broker-J][BDB HA] Removal of non existing group member can end up in broker crash due to uncaught MemberNotFoundException

2018-03-27 Thread Alex Rudyy (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8140: - Description: When two concurrent requests are made to delete a group member using REST API for remote

[jira] [Updated] (QPID-8140) [Broker-J][BDB HA] Removal of non existing group member can end up in broker crash due to uncaught MemberNotFoundException

2018-03-27 Thread Alex Rudyy (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8140: - Description: When two concurrent requests are made to delete a group member using REST API for remote

[jira] [Created] (QPID-8140) [Broker-J][BDB HA] Removal of non existing group member can end up in broker crash due to uncaught MemberNotFoundException

2018-03-27 Thread Alex Rudyy (JIRA)
Alex Rudyy created QPID-8140: Summary: [Broker-J][BDB HA] Removal of non existing group member can end up in broker crash due to uncaught MemberNotFoundException Key: QPID-8140 URL:

[jira] [Resolved] (QPID-8123) [Broker-J] [BDB Test] Remove compile time dependency on Qpid JMS Client AMQP 0-x

2018-03-27 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8123. -- Resolution: Fixed Fix Version/s: qpid-java-broker-7.1.0 > [Broker-J] [BDB Test] Remove compile

[jira] [Resolved] (QPID-7567) [Java Broker] Select appropriate certificate for TLS based on SNIServerName

2018-03-27 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7567. -- Resolution: Fixed > [Java Broker] Select appropriate certificate for TLS based on SNIServerName >