[jira] [Updated] (QPID-8160) [Broker-J] [AMQP 1.0] AccessControlException when creating sending link reported as amqp:internal-error rather than amqp:unauthorised-access

[ https://issues.apache.org/jira/browse/QPID-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8160: - Priority: Minor (was: Major) > [Broker-J] [AMQP 1.0] AccessControlException when creating sending l

[jira] [Updated] (QPID-8160) [Broker-J] [AMQP 1.0] AccessControlException when creating sending link reported as amqp:internal-error rather than amqp:unauthorised-access

[ https://issues.apache.org/jira/browse/QPID-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8160: - Affects Version/s: qpid-java-broker-7.1 > [Broker-J] [AMQP 1.0] AccessControlException when creat

[jira] [Updated] (QPID-8160) [Broker-J] [AMQP 1.0] AccessControlException when creating sending link reported as amqp:internal-error rather than amqp:unauthorised-access

[ https://issues.apache.org/jira/browse/QPID-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8160: - Description: If the Broker tries to create a sending link from a source but the user has insufficient

[jira] [Created] (QPID-8160) [Broker-J] [AMQP 1.0] AccessControlException when creating sending link reported as amqp:internal-error rather than amqp:unauthorised-access

Keith Wall created QPID-8160: Summary: [Broker-J] [AMQP 1.0] AccessControlException when creating sending link reported as amqp:internal-error rather than amqp:unauthorised-access Key: QPID-8160 URL: https

[jira] [Resolved] (QPID-8159) [Broker-J] Upgrade Jackson from 2.9.4 to 2.9.5 (CVE-2018-7489)

[ https://issues.apache.org/jira/browse/QPID-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8159. -- Resolution: Fixed > [Broker-J] Upgrade Jackson from 2.9.4 to 2.9.5 (CVE-2018-7

[jira] [Assigned] (QPID-8159) [Broker-J] Upgrade Jackson from 2.9.4 to 2.9.5 (CVE-2018-7489)

[ https://issues.apache.org/jira/browse/QPID-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8159: Assignee: Keith Wall > [Broker-J] Upgrade Jackson from 2.9.4 to 2.9.5 (CVE-2018-7

[jira] [Updated] (QPID-8159) [Broker-J] Upgrade Jackson from 2.9.4 to 2.9.5 (CVE-2018-7489)

[ https://issues.apache.org/jira/browse/QPID-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8159: - Description: QPID-8136 upgrade Jackson on master from 2.8.7 to 2.9.4 in response to CVE-2017-7525

[jira] [Created] (QPID-8159) [Broker-J] Upgrade Jackson from 2.9.4 to 2.9.5 (CVE-2018-7489)

Keith Wall created QPID-8159: Summary: [Broker-J] Upgrade Jackson from 2.9.4 to 2.9.5 (CVE-2018-7489) Key: QPID-8159 URL: https://issues.apache.org/jira/browse/QPID-8159 Project: Qpid Issue

[jira] [Commented] (QPID-8158) [Broker-J] [System Tests] Refactor BDB HA system tests

[ https://issues.apache.org/jira/browse/QPID-8158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433681#comment-16433681 ] Keith Wall commented on QPID-8158: -- As discussed, the approach being taken by the above commit does

[jira] [Assigned] (QPID-8153) [JMS AMQP 0-x] JMS AMQP 0-x should be able to send SNI as part of TLS handshake

[ https://issues.apache.org/jira/browse/QPID-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8153: Assignee: Keith Wall > [JMS AMQP 0-x] JMS AMQP 0-x should be able to send SNI as part of

[jira] [Updated] (QPID-8153) [JMS AMQP 0-x] JMS AMQP 0-x should be able to send SNI as part of TLS handshake

[ https://issues.apache.org/jira/browse/QPID-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8153: - Status: Reviewable (was: In Progress) > [JMS AMQP 0-x] JMS AMQP 0-x should be able to send SNI as p

[jira] [Updated] (QPID-8135) [JMS AMQP 0-x] Connection URL options for end-to-end encryption keystore/trustore passwords can be logged when log level for 'org.apache.qpid' loggers is lower than 'warn'

[ https://issues.apache.org/jira/browse/QPID-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8135: - Status: Reviewable (was: In Progress) > [JMS AMQP 0-x] Connection URL options for end-to-end encrypt

[jira] [Assigned] (QPID-8135) [JMS AMQP 0-x] Connection URL options for end-to-end encryption keystore/trustore passwords can be logged when log level for 'org.apache.qpid' loggers is lower than 'warn

[ https://issues.apache.org/jira/browse/QPID-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8135: Assignee: Keith Wall > [JMS AMQP 0-x] Connection URL options for end-to-end encryption > ke

[jira] [Updated] (QPID-8135) [JMS AMQP 0-x] Connection URL options for end-to-end encryption keystore/trustore passwords can be logged when log level for 'org.apache.qpid' loggers is lower than 'warn'

[ https://issues.apache.org/jira/browse/QPID-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8135: - Summary: [JMS AMQP 0-x] Connection URL options for end-to-end encryption keystore/trustore passwords can

[jira] [Updated] (QPID-8135) [JMS AMQP 0-x] Connection URL options for end to end encryption keystore/trustore passwords can be logged when log level for 'org.apache.qpid' loggers is lower than 'warn'

[ https://issues.apache.org/jira/browse/QPID-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8135: - Summary: [JMS AMQP 0-x] Connection URL options for end to end encryption keystore/trustore passwords can

[jira] [Commented] (QPID-8138) [Broker-J] Report authenticated user principals and groups as part of ACL and/or operational logging

[ https://issues.apache.org/jira/browse/QPID-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426807#comment-16426807 ] Keith Wall commented on QPID-8138: -- I am wondering if this is required required. The REST API exposes

[jira] [Updated] (QPID-8152) [Broker-J][BDB] Virtual host start-up fails with IOException: User limit of inotify instances reached or too many open files

[ https://issues.apache.org/jira/browse/QPID-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8152: - Description: Newer versions of BDB JE register {{java.nio.file.WatchService}} to detect unexpected

[jira] [Updated] (QPID-8152) [Broker-J][BDB] Virtual host start-up fails with IOException: User limit of inotify instances reached or too many open files

[ https://issues.apache.org/jira/browse/QPID-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8152: - Priority: Minor (was: Major) > [Broker-J][BDB] Virtual host start-up fails with IOException: User li

[jira] [Updated] (QPID-8152) [Broker-J][BDB] Virtual host start-up fails with IOException: User limit of inotify instances reached or too many open files

[ https://issues.apache.org/jira/browse/QPID-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8152: - Description: Newer versions of BDB JE register {{java.nio.file.WatchService}} to detect unexpected

[jira] [Updated] (QPID-8152) [Broker-J][BDB] Virtual host start-up fails with IOException: User limit of inotify instances reached or too many open files

[ https://issues.apache.org/jira/browse/QPID-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8152: - Affects Version/s: qpid-java-broker-7.0.0 > [Broker-J][BDB] Virtual host start-up fails with IOExcept

[jira] [Commented] (QPID-8152) [Broker-J][BDB] Virtual host start-up fails with IOException: User limit of inotify instances reached or too many open files

[ https://issues.apache.org/jira/browse/QPID-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424205#comment-16424205 ] Keith Wall commented on QPID-8152: -- Qpid Broker-J v7.0.0 and higher shipped Berkeley DB JE 7.4.5. This JE

[jira] [Resolved] (QPID-6825) AmqPorts should stop performing a TCP accept once the port has reached maximum concurrent connections

[ https://issues.apache.org/jira/browse/QPID-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-6825. -- Resolution: Invalid > AmqPorts should stop performing a TCP accept once the port has reached > m

[jira] [Commented] (QPID-6825) AmqPorts should stop performing a TCP accept once the port has reached maximum concurrent connections

[ https://issues.apache.org/jira/browse/QPID-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423658#comment-16423658 ] Keith Wall commented on QPID-6825: -- I think my original analysis was flawed. I was under the impression

[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

[ https://issues.apache.org/jira/browse/QPID-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8141: - Fix Version/s: qpid-java-client-0-x-6.3.1 > [JMS AMQP 0-x] Cannot publish message with address ba

[jira] [Resolved] (QPID-7925) [Broker-J] [WMC] Add ability to maintain rule-based access control provider for virtualhost

[ https://issues.apache.org/jira/browse/QPID-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7925. -- Resolution: Fixed > [Broker-J] [WMC] Add ability to maintain rule-based access control provi

[jira] [Updated] (QPID-8151) [Broker-J] Refresh mechanism that underpins unit tests

[ https://issues.apache.org/jira/browse/QPID-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8151: - Summary: [Broker-J] Refresh mechanism that underpins unit tests (was: [Broker-J] Refresh mechanism

[jira] [Created] (QPID-8151) [Broker-J] Refresh mechanism underpinned unit tests

Keith Wall created QPID-8151: Summary: [Broker-J] Refresh mechanism underpinned unit tests Key: QPID-8151 URL: https://issues.apache.org/jira/browse/QPID-8151 Project: Qpid Issue Type

[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=16420556#comment-16420556 ] Keith Wall commented on QPID-8064: -- Alex Your changes looked reasonable, but as discussed, I corrected

[jira] [Resolved] (QPID-8147) [Broker-J] Report first 8 received bytes as part of operational log message for unsupported protocol header

[ https://issues.apache.org/jira/browse/QPID-8147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8147. -- Resolution: Fixed > [Broker-J] Report first 8 received bytes as part of operational log mess

[jira] [Updated] (QPID-8147) [Broker-J] Report first 8 received bytes as part of operational log message for unsupported protocol header

[ https://issues.apache.org/jira/browse/QPID-8147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8147: - Description: Operational log message for unsupported protocol header can be improved with the inclusion

[jira] [Commented] (QPID-8147) [Broker-J] Report first 8 received bytes as part of operational log message for unsupported protocol header

[ https://issues.apache.org/jira/browse/QPID-8147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420456#comment-16420456 ] Keith Wall commented on QPID-8147: -- Changes look reasonable to me. > [Broker-J] Report first 8 recei

[jira] [Updated] (QPID-8147) [Broker-J] Report first 8 received bytes as part of operational log message for unsupported protocol header

[ https://issues.apache.org/jira/browse/QPID-8147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8147: - Description: Operational log message for unsupported protocol header can be improved with inclusion

[jira] [Updated] (QPID-8147) [Broker-J] Report first 8 received bytes as part of operational log message for unsupported protocol header

[ https://issues.apache.org/jira/browse/QPID-8147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8147: - Summary: [Broker-J] Report first 8 received bytes as part of operational log message for unsupported

[jira] [Updated] (QPID-8144) [Broker-J] Memory compaction does not run when used direct memory exceeds 2GB

[ https://issues.apache.org/jira/browse/QPID-8144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8144: - Description: The Broker-J uses direct memory for the caching of message content and IO buffers used

[jira] [Updated] (QPID-8144) [Broker-J] Memory compaction does not run when used direct memory exceeds 2GB

[ https://issues.apache.org/jira/browse/QPID-8144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8144: - Description: The Broker-J uses direct memory for the caching of message content and IO buffers used

[jira] [Updated] (QPID-8144) [Broker-J] Memory compaction does not run when used direct memory exceeds 2GB

[ https://issues.apache.org/jira/browse/QPID-8144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8144: - Fix Version/s: qpid-java-6.0.9 > [Broker-J] Memory compaction does not run when used direct memory exce

[jira] [Assigned] (QPID-8144) [Broker-J] Memory compaction does not run when used direct memory exceeds 2GB

[ https://issues.apache.org/jira/browse/QPID-8144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8144: Assignee: Keith Wall > [Broker-J] Memory compaction does not run when used direct memory exce

[jira] [Updated] (QPID-8144) [Broker-J] Memory compaction does not run when used direct memory exceeds 2GB

[ https://issues.apache.org/jira/browse/QPID-8144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8144: - Status: Reviewable (was: In Progress) > [Broker-J] Memory compaction does not run when used direct mem

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

[ https://issues.apache.org/jira/browse/QPID-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7541: - Fix Version/s: (was: qpid-java-broker-7.0.3) qpid-java-broker-7.1.0 > [Java Bro

[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-broker-7.0.3) > [Broker-J] FileKeyStore should validate java keyst

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

[ https://issues.apache.org/jira/browse/QPID-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16419855#comment-16419855 ] Keith Wall commented on QPID-8140: -- Changes look reasonable to me. > [Broker-J][BDB HA] Removal of

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

[ https://issues.apache.org/jira/browse/QPID-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8140. -- Resolution: Fixed > [Broker-J][BDB HA] Removal of non existing group member can end up in bro

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

[ https://issues.apache.org/jira/browse/QPID-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8140: - Priority: Minor (was: Major) > [Broker-J][BDB HA] Removal of non existing group member can end

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

[ https://issues.apache.org/jira/browse/QPID-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8140: - Fix Version/s: qpid-java-broker-7.1.0 > [Broker-J][BDB HA] Removal of non existing group member can end

[jira] [Updated] (QPID-8146) [AMQP 1.0] Test TransferTest#transfersWithDuplicateUnsettledDeliveryTag and TransferTest#exceedMaxMessageSizeLimit reveals QBB leaks

[ https://issues.apache.org/jira/browse/QPID-8146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8146: - Attachment: qbb_leak_detection.diff > [AMQP 1.0] Test TransferT

[jira] [Updated] (QPID-8146) [AMQP 1.0] Tests TransferTest#transfersWithDuplicateUnsettledDeliveryTag and TransferTest#exceedMaxMessageSizeLimit reveals QBB leaks

[ https://issues.apache.org/jira/browse/QPID-8146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8146: - Summary: [AMQP 1.0] Tests TransferTest#transfersWithDuplicateUnsettledDeliveryTag and TransferTest

[jira] [Updated] (QPID-8146) [AMQP 1.0] Test TransferTest#transfersWithDuplicateUnsettledDeliveryTag and TransferTest#exceedMaxMessageSizeLimit reveals QBB leaks

[ https://issues.apache.org/jira/browse/QPID-8146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8146: - Description: AMQP 1.0 tests TransferTest#transfersWithDuplicateUnsettledDeliveryTag and TransferTest

[jira] [Updated] (QPID-8146) [AMQP 1.0] Test TransferTest#transfersWithDuplicateUnsettledDeliveryTag and TransferTest#exceedMaxMessageSizeLimit reveals QBB leaks

[ https://issues.apache.org/jira/browse/QPID-8146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8146: - Attachment: org.apache.qpid.tests.protocol.v1_0.transaction.DischargeTest.txt > [AMQP 1.0] T

[jira] [Updated] (QPID-8146) [AMQP 1.0] Test TransferTest#transfersWithDuplicateUnsettledDeliveryTag and TransferTest#exceedMaxMessageSizeLimit reveals QBB leaks

[ https://issues.apache.org/jira/browse/QPID-8146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8146: - Attachment: org.apache.qpid.tests.protocol.v1_0.messaging.TransferTest.txt > [AMQP 1.0] Test TransferT

[jira] [Created] (QPID-8146) [AMQP 1.0] Test TransferTest#transfersWithDuplicateUnsettledDeliveryTag and TransferTest#exceedMaxMessageSizeLimit reveals QBB leaks

Keith Wall created QPID-8146: Summary: [AMQP 1.0] Test TransferTest#transfersWithDuplicateUnsettledDeliveryTag and TransferTest#exceedMaxMessageSizeLimit reveals QBB leaks Key: QPID-8146 URL: https

[jira] [Created] (QPID-8145) [AMQP 0-10] ConnectionTest#tooSmallFrameSize reveals QBB leak

Keith Wall created QPID-8145: Summary: [AMQP 0-10] ConnectionTest#tooSmallFrameSize reveals QBB leak Key: QPID-8145 URL: https://issues.apache.org/jira/browse/QPID-8145 Project: Qpid Issue Type

[jira] [Updated] (QPID-8144) [Broker-J] Memory compaction does not run when used direct memory exceeds 2GB

[ https://issues.apache.org/jira/browse/QPID-8144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8144: - Description: The Broker-J uses direct memory for the caching of message content and IO buffers used

[jira] [Updated] (QPID-8144) [Broker-J] Memory compaction not running when allocated direct memory exceeds 2GB

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

[jira] [Updated] (QPID-8144) [Broker-J] Memory compaction does not run when used direct memory exceeds 2GB

[ https://issues.apache.org/jira/browse/QPID-8144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8144: - Summary: [Broker-J] Memory compaction does not run when used direct memory exceeds 2GB (was: [Broker-J

[jira] [Updated] (QPID-8144) [Broker-J] Memory compaction not running when allocated direct memory exceeds 2GB

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

[jira] [Created] (QPID-8144) [Broker-J] Memory compaction not running when allocated direct memory exceeds 2GB

Keith Wall created QPID-8144: Summary: [Broker-J] Memory compaction not running when allocated direct memory exceeds 2GB Key: QPID-8144 URL: https://issues.apache.org/jira/browse/QPID-8144 Project: Qpid

[jira] [Commented] (QPID-7925) [Java Broker] [WMC] Add ability to maintain rule-based access control provider for virtualhost

[ https://issues.apache.org/jira/browse/QPID-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16417377#comment-16417377 ] Keith Wall commented on QPID-7925: -- There is a different state management defect: # Assuming

[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

[ 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] [Resolved] (QPID-8123) [Broker-J] [BDB Test] Remove compile time dependency on Qpid JMS Client AMQP 0-x

[ 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 comp

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

[ 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 SNIServerN

[jira] [Commented] (QPID-7925) [Java Broker] [WMC] Add ability to maintain rule-based access control provider for virtualhost

[ https://issues.apache.org/jira/browse/QPID-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16413947#comment-16413947 ] Keith Wall commented on QPID-7925: -- Looks reasonable # There is a state management defect when uploading

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

[ https://issues.apache.org/jira/browse/QPID-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16413862#comment-16413862 ] Keith Wall commented on QPID-7567: -- Alex - changes made by a7e1057 look reasonable to me. > [Java Bro

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

Keith Wall created QPIDJMS-372: -- Summary: [SASL] [XOAUTH2] Access token validation too restrictive Key: QPIDJMS-372 URL: https://issues.apache.org/jira/browse/QPIDJMS-372 Project: Qpid JMS

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

[ https://issues.apache.org/jira/browse/QPID-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411245#comment-16411245 ] Keith Wall edited comment on QPID-7541 at 3/23/18 11:22 AM: Thanks for the log

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

[ https://issues.apache.org/jira/browse/QPID-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411245#comment-16411245 ] Keith Wall commented on QPID-7541: -- Thanks for the log. In answer to your question, in Broker-J 6.1.4

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

[ https://issues.apache.org/jira/browse/QPID-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7541: - Description: Currently when a Queue is deleted the associated Consumers are not closed

[jira] [Resolved] (QPID-8137) [Broker-J] NPE is reported into broker logs on broker shutdown/restart when AMQP port is in ERRORED state due to port being bound by other process

[ https://issues.apache.org/jira/browse/QPID-8137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8137. -- Resolution: Fixed > [Broker-J] NPE is reported into broker logs on broker shutdown/restart when >

[jira] [Commented] (QPID-8137) [Broker-J] NPE is reported into broker logs on broker shutdown/restart when AMQP port is in ERRORED state due to port being bound by other process

[ https://issues.apache.org/jira/browse/QPID-8137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16410058#comment-16410058 ] Keith Wall commented on QPID-8137: -- Changes look reasonable to me. > [Broker-J] NPE is repor

[jira] [Updated] (QPID-8137) [Broker-J] NPE is reported into broker logs on broker shutdown/restart when AMQP port is in ERRORED state due to port being bound by other process

[ https://issues.apache.org/jira/browse/QPID-8137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8137: - Fix Version/s: qpid-java-broker-7.0.3 > [Broker-J] NPE is reported into broker logs on broker shutd

[jira] [Updated] (QPID-8137) [Broker-J] NPE is reported into broker logs on broker shutdown/restart when AMQP port is in ERRORED state due to port being bound by other process

[ https://issues.apache.org/jira/browse/QPID-8137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8137: - Priority: Minor (was: Major) > [Broker-J] NPE is reported into broker logs on broker shutdown/rest

[jira] [Updated] (QPID-8137) [Broker-J] NPE is reported into broker logs on broker shutdown/restart when AMQP port is in ERRORED state due to port being bound by other process

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

[jira] [Updated] (QPID-8137) [Broker-J] NPE is reported into broker logs on broker shutdown/restart when AMQP port is in ERRORED state due to port being bound by other process

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

[jira] [Updated] (QPID-7197) [Broker-J] Prevent deletion of objects that are in use

[ https://issues.apache.org/jira/browse/QPID-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7197: - Priority: Minor (was: Major) > [Broker-J] Prevent deletion of objects that are in

[jira] [Resolved] (QPID-7197) [Broker-J] Prevent deletion of objects that are in use

[ https://issues.apache.org/jira/browse/QPID-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7197. -- Resolution: Fixed > [Broker-J] Prevent deletion of objects that are in

[jira] [Commented] (QPIDJMS-369) Failover doesn't apply max reconnect attempts on initial connect when remote is closing on the Open frame

[ https://issues.apache.org/jira/browse/QPIDJMS-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409416#comment-16409416 ] Keith Wall commented on QPIDJMS-369: Tim - Many thanks. I confirm that this resolved the issue I

[jira] [Comment Edited] (QPIDJMS-366) [Failover] JMS commit hangs forever if peer Closes gracefully and failover.maxReconnectAttempts exhausted

[ https://issues.apache.org/jira/browse/QPIDJMS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407797#comment-16407797 ] Keith Wall edited comment on QPIDJMS-366 at 3/21/18 12:19 PM: -- Commit

[jira] [Updated] (QPIDJMS-366) [Failover] JMS commit hangs forever if peer Closes gracefully and failover.maxReconnectAttempts exhausted

[ https://issues.apache.org/jira/browse/QPIDJMS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPIDJMS-366: --- Attachment: 054e24_qpid366_initalconnattemptfailsgracefully.log > [Failover] JMS commit ha

[jira] [Commented] (QPIDJMS-366) [Failover] JMS commit hangs forever if peer Closes gracefully and failover.maxReconnectAttempts exhausted

[ https://issues.apache.org/jira/browse/QPIDJMS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407797#comment-16407797 ] Keith Wall commented on QPIDJMS-366: Commit  [054e24c|https://git-wip-us.apache.org/repos/asf?p=qpid

[jira] [Resolved] (QPID-8124) [Broker-J][REST] Sucessfully authenticated user is reported as <> in ACL operational logs when checking access to management

[ https://issues.apache.org/jira/browse/QPID-8124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8124. -- Resolution: Fixed Merged to 7.0.x branch. > [Broker-J][REST] Sucessfully authenticated user is repor

[jira] [Commented] (QPID-8124) [Broker-J][REST] Sucessfully authenticated user is reported as <> in ACL operational logs when checking access to management

[ https://issues.apache.org/jira/browse/QPID-8124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406639#comment-16406639 ] Keith Wall commented on QPID-8124: -- Changes look reasonable to me.  Verified both the interactive

[jira] [Commented] (QPID-7197) [Broker-J] Prevent deletion of objects that are in use

[ https://issues.apache.org/jira/browse/QPID-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406576#comment-16406576 ] Keith Wall commented on QPID-7197: -- As discussed, I don't think the change looks right: * it should

[jira] [Updated] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8136: - Description: CVE-2017-7525 was recently published against the Jackson-databind component.     Broker-J

[jira] [Updated] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8136: - Description: CVE-2017-7525 was recently published against the Jackson-databind component.     Broker-J

[jira] [Updated] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8136: - Description: CVE-2017-7525 was recently published against the Jackson-databind component.     Broker-J

[jira] [Updated] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8136: - Description: CVE-2017-7525 was recently published against the Jackson-databind component.     Broker-J

[jira] [Updated] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8136: - Status: Reviewable (was: In Progress) > [Broker-J] Upgrade Jackson dependenc

[jira] [Assigned] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8136: Assignee: Keith Wall > [Broker-J] Upgrade Jackson dependenc

[jira] [Updated] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8136: - Description: CVE-2017-7525 was recently published against the Jackson-databind component.     Broker-J

[jira] [Updated] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8136: - Description: CVE-2017-7525 was recently published against the Jackson-databind component.     Broker-J

[jira] [Updated] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8136: - Description: CVE-2017-7525 was recently published against the Jackson-databind component.     Broker-J

[jira] [Updated] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8136: - Description: CVE-2017-7525 was recently published against the Jackson-databind component.     Broker-J

[jira] [Updated] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8136: - Description: CVE-2017-7525 was recently published against the Jackson-databind component.     Broker-J

[jira] [Updated] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8136: - Fix Version/s: qpid-java-6.1.6 > [Broker-J] Upgrade Jackson dependenc

[jira] [Commented] (QPID-8136) [Broker-J] Upgrade Jackson dependencies

[ https://issues.apache.org/jira/browse/QPID-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406249#comment-16406249 ] Keith Wall commented on QPID-8136: -- The commit message on 906a84956baa3de2 was incorrect.  It ought

[jira] [Updated] (QPIDJMS-366) [Failover] JMS commit hangs forever if peer Closes gracefully and failover.maxReconnectAttempts exhausted

[ https://issues.apache.org/jira/browse/QPIDJMS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPIDJMS-366: --- Attachment: 4b02297_qpid-366.log > [Failover] JMS commit hangs forever if peer Closes gracefu

[jira] [Commented] (QPIDJMS-366) [Failover] JMS commit hangs forever if peer Closes gracefully and failover.maxReconnectAttempts exhausted

[ https://issues.apache.org/jira/browse/QPIDJMS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405496#comment-16405496 ] Keith Wall commented on QPIDJMS-366: Please find attached log.  I am reproducing the problem exactly

[jira] [Commented] (QPIDJMS-366) [Failover] JMS commit hangs forever if peer Closes gracefully and failover.maxReconnectAttempts exhausted

[ https://issues.apache.org/jira/browse/QPIDJMS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405339#comment-16405339 ] Keith Wall commented on QPIDJMS-366: With the work of QPIDJMS-365, I still see this issue

[jira] [Commented] (QPIDJMS-365) [Failover] failover.reconnectDelay not applied between connection attempts if peer Closes gracefully

[ https://issues.apache.org/jira/browse/QPIDJMS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405334#comment-16405334 ] Keith Wall commented on QPIDJMS-365: I reran the tests that caused me to discover this defect.  I

[jira] [Assigned] (QPID-8133) Refresh Commons-CLI dependency (1.4)

[ https://issues.apache.org/jira/browse/QPID-8133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8133: Assignee: Keith Wall > Refresh Commons-CLI dependency (

[jira] [Updated] (QPID-8133) Refresh Commons-CLI dependency (1.4)

[ https://issues.apache.org/jira/browse/QPID-8133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8133: - Status: Reviewable (was: In Progress) > Refresh Commons-CLI dependency (

<    1   2   3   4   5   6   7   8   9   10   >