[jira] [Assigned] (QPID-8195) [Broker-J] Improve AmqpErrorException#toString

[ https://issues.apache.org/jira/browse/QPID-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8195: Assignee: Keith Wall > [Broker-J] Improve AmqpErrorException#toStr

[jira] [Updated] (QPID-8195) [Broker-J] Improve AmqpErrorException#toString

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

[jira] [Created] (QPID-8195) [Broker-J] Improve AmqpErrorException#toString

Keith Wall created QPID-8195: Summary: [Broker-J] Improve AmqpErrorException#toString Key: QPID-8195 URL: https://issues.apache.org/jira/browse/QPID-8195 Project: Qpid Issue Type: Improvement

[jira] [Updated] (QPID-8195) [Broker-J] Improve AmqpErrorException#toString

[ https://issues.apache.org/jira/browse/QPID-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8195: - Description: The {{AmqpErrorException#toString}} does not include the details of the underlying {{Error

[jira] [Updated] (QPID-8194) [Protocol Tests] [AMQP 1.0] TransferTests seems to fail on Windows

[ https://issues.apache.org/jira/browse/QPID-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8194: - Description: The following two TransferTests fail consistently on Windows

[jira] [Updated] (QPID-8194) [Protocol Tests] [AMQP 1.0] TransferTests seems to fail on Windows

[ https://issues.apache.org/jira/browse/QPID-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8194: - Description: The following two TransferTests fail consistently on Windows

[jira] [Updated] (QPID-8194) [Protocol Tests] [AMQP 1.0] TransferTests seems to fail on Windows

[ https://issues.apache.org/jira/browse/QPID-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8194: - Description: The following two TransferTests fail consistently on Windows

[jira] [Created] (QPID-8194) [Protocol Tests] [AMQP 1.0] TransferTests seems to fail on Windows

Keith Wall created QPID-8194: Summary: [Protocol Tests] [AMQP 1.0] TransferTests seems to fail on Windows Key: QPID-8194 URL: https://issues.apache.org/jira/browse/QPID-8194 Project: Qpid Issue

[jira] [Updated] (QPID-7153) Allow expired messages to be sent to DLQ

[ https://issues.apache.org/jira/browse/QPID-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7153: - Description: Currently the Java Broker simply discards messages that expire (TTL). The behaviour should

[jira] [Commented] (QPID-7153) Allow expired messages to be sent to DLQ

[ https://issues.apache.org/jira/browse/QPID-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477544#comment-16477544 ] Keith Wall commented on QPID-7153: -- Thanks, I'll take a look > Allow expired messages to be sent to

[jira] [Updated] (QPID-8141) [JMS AMQP 0-x] Sending message to address based destinations that matches the address of a previously resolved address fails

[ 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] Sending message to address based destinations that matches the address

[jira] [Updated] (QPID-8141) [JMS AMQP 0-x] Sending message to address based destinations that matches the address of a previously resolved address fails

[ https://issues.apache.org/jira/browse/QPID-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8141: - Description: Address based destination resolution functionality {{AMQSession#resolveAddress}} sets

[jira] [Commented] (QPID-8167) [Broker-J] Broker command line option '-mmqv/--management-mode-quiesce-virtualhosts' does not quiesce virtual hosts

[ https://issues.apache.org/jira/browse/QPID-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475444#comment-16475444 ] Keith Wall commented on QPID-8167: -- Changes reviewed.  Documentation corrected. > [Broker-J] Bro

[jira] [Updated] (QPID-8167) [Broker-J] Broker command line option '-mmqv/--management-mode-quiesce-virtualhosts' does not quiesce virtual hosts

[ https://issues.apache.org/jira/browse/QPID-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8167: - Priority: Minor (was: Major) > [Broker-J] Broker command line option > '-mmqv/--management-mode-q

[jira] [Updated] (QPID-8167) [Broker-J] Broker command line option '-mmqv/--management-mode-quiesce-virtualhosts' does not quiesce virtual hosts

[ https://issues.apache.org/jira/browse/QPID-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8167: - Fix Version/s: qpid-java-broker-7.1 > [Broker-J] Broker command line option > '-mmqv/--managemen

[jira] [Resolved] (QPID-8167) [Broker-J] Broker command line option '-mmqv/--management-mode-quiesce-virtualhosts' does not quiesce virtual hosts

[ https://issues.apache.org/jira/browse/QPID-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8167. -- Resolution: Fixed > [Broker-J] Broker command line option > '-mmqv/--management-mode-q

[jira] [Updated] (QPID-8172) [Broker-J] OAuth2 authentication provider should not mandate setting of client secret

[ https://issues.apache.org/jira/browse/QPID-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8172: - Affects Version/s: qpid-java-6.0 qpid-java-6.1 > [Broker-J] OAuth2 authenticat

[jira] [Updated] (QPID-8172) [Broker-J] OAuth2 authentication provider should not mandate setting of client secret

[ https://issues.apache.org/jira/browse/QPID-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8172: - Fix Version/s: qpid-java-broker-7.1.0 > [Broker-J] OAuth2 authentication provider should not mand

[jira] [Resolved] (QPID-8172) [Broker-J] OAuth2 authentication provider should not mandate setting of client secret

[ https://issues.apache.org/jira/browse/QPID-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8172. -- Resolution: Fixed > [Broker-J] OAuth2 authentication provider should not mandate setting of >

[jira] [Commented] (QPID-8172) [Broker-J] OAuth2 authentication provider should not mandate setting of client secret

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

[jira] [Commented] (QPID-8172) [Broker-J] OAuth2 authentication provider should not mandate setting of client secret

[ https://issues.apache.org/jira/browse/QPID-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474021#comment-16474021 ] Keith Wall commented on QPID-8172: -- [39bfa6a|https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h

[jira] [Updated] (QPID-8172) [Broker-J] OAuth2 authentication provider should not mandate setting of client secret

[ https://issues.apache.org/jira/browse/QPID-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8172: - Status: Open (was: Reviewable) > [Broker-J] OAuth2 authentication provider should not mandate sett

[jira] [Commented] (QPID-8167) [Broker-J] Broker command line option '-mmqv/--management-mode-quiesce-virtualhosts' does not quiesce virtual hosts

[ https://issues.apache.org/jira/browse/QPID-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474002#comment-16474002 ] Keith Wall commented on QPID-8167: -- I note that {{--management-mode-quiesce-virtualhosts}} is now misnamed

[jira] [Updated] (QPID-8165) [Broker-J][WMC] Validation of configured object names is too restrictive in Web Management Console

[ https://issues.apache.org/jira/browse/QPID-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8165: - Description: WMC only allows to create (or edit) configured objects with names consisting only from any

[jira] [Commented] (QPID-8165) [Broker-J][WMC] Validation of configured object names is too restrictive in Web Management Console

[ https://issues.apache.org/jira/browse/QPID-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473983#comment-16473983 ] Keith Wall commented on QPID-8165: -- Changes looked reasonable to me. I corrected the JIRA description

[jira] [Updated] (QPID-8165) [Broker-J][WMC] Validation of configured object names is too restrictive in Web Management Console

[ https://issues.apache.org/jira/browse/QPID-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8165: - Description: WMC only allows to create (or edit) configured objects with names consisting only from any

[jira] [Updated] (QPID-8165) [Broker-J][WMC] Validation of configured object names is too restrictive in Web Management Console

[ https://issues.apache.org/jira/browse/QPID-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8165: - Description: WMC only allows to create (or edit) configured objects with names consisting only from any

[jira] [Updated] (QPID-8185) [JMS AMQP 0-x][AMQP 0-8..0-91] Make sure that client closes TCP connection on failure with sending connection.close and avoid spurious NPEs whilst awaiting channel closure

[ https://issues.apache.org/jira/browse/QPID-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8185: - Summary: [JMS AMQP 0-x][AMQP 0-8..0-91] Make sure that client closes TCP connection on failure

[jira] [Resolved] (QPID-8185) [JMS AMQP 0-x][AMQP 0-8..0-91] Make sure that client closes TCP connection on failure with sending connection.close

[ https://issues.apache.org/jira/browse/QPID-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8185. -- Resolution: Fixed > [JMS AMQP 0-x][AMQP 0-8..0-91] Make sure that client closes TCP connect

[jira] [Commented] (QPID-8185) [JMS AMQP 0-x][AMQP 0-8..0-91] Make sure that client closes TCP connection on failure with sending connection.close

[ https://issues.apache.org/jira/browse/QPID-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473947#comment-16473947 ] Keith Wall commented on QPID-8185: -- Changes look reasonable to me. > [JMS AMQP 0-x][AMQP 0-8..0-91] M

[jira] [Commented] (QPID-8181) [Broker-J] Add statistics for a total number of connections established on AMQP port

[ https://issues.apache.org/jira/browse/QPID-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470320#comment-16470320 ] Keith Wall commented on QPID-8181: -- Merge looks good too. > [Broker-J] Add statistics for a total num

[jira] [Resolved] (QPID-8181) [Broker-J] Add statistics for a total number of connections established on AMQP port

[ https://issues.apache.org/jira/browse/QPID-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8181. -- Resolution: Fixed > [Broker-J] Add statistics for a total number of connections established on >

[jira] [Updated] (QPID-8190) [JMS AMQP 0-x] Release Qpid JMS AMQP 0-x 6.3.1

[ https://issues.apache.org/jira/browse/QPID-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8190: - Description: Defect release for the legacy client. https://cwiki.apache.org/confluence/display/qpid

[jira] [Created] (QPID-8190) [JMS AMQP 0-x] Improve error message associated with the channel not found during frame dispatch

Keith Wall created QPID-8190: Summary: [JMS AMQP 0-x] Improve error message associated with the channel not found during frame dispatch Key: QPID-8190 URL: https://issues.apache.org/jira/browse/QPID-8190

[jira] [Updated] (QPID-8190) [JMS AMQP 0-x] Release Qpid JMS AMQP 0-x 6.3.1

[ https://issues.apache.org/jira/browse/QPID-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8190: - Issue Type: Task (was: Bug) > [JMS AMQP 0-x] Release Qpid JMS AMQP 0-x 6.

[jira] [Updated] (QPID-8190) [JMS AMQP 0-x] Release Qpid JMS AMQP 0-x 6.3.1

[ https://issues.apache.org/jira/browse/QPID-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8190: - Summary: [JMS AMQP 0-x] Release Qpid JMS AMQP 0-x 6.3.1 (was: [JMS AMQP 0-x] Improve error message

[jira] [Created] (QPID-8189) [Broker-J] Release Qpid Broker-J 7.0.4

Keith Wall created QPID-8189: Summary: [Broker-J] Release Qpid Broker-J 7.0.4 Key: QPID-8189 URL: https://issues.apache.org/jira/browse/QPID-8189 Project: Qpid Issue Type: Task

[jira] [Updated] (QPID-8189) [Broker-J] Release Qpid Broker-J 7.0.4

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

[jira] [Commented] (QPID-8139) [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or JMSCorrelationID expressed using the AMQP type encoded form values fail to select target message

[ https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470114#comment-16470114 ] Keith Wall commented on QPID-8139: -- I don't think the patches go in the right direction. I think

[jira] [Updated] (QPID-8139) [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or JMSCorrelationID expressed using the AMQP type encoded form values fail to select target message

[ https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8139: - Description: (2018-05-10 - rewritten JIRA title/description) When using the Qpid JMS AMQP 1.0 Client

[jira] [Updated] (QPID-8139) [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or JMSCorrelationID expressed using the AMQP type encoded form values fail to select target message

[ https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8139: - Description: (2018-05-10 - rewritten JIRA title/description) When using the Qpid JMS AMQP 1.0 Client

[jira] [Updated] (QPID-8139) [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or JMSCorrelationID expressed using the AMQP type encoded form values fail to select target message

[ https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8139: - Summary: [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or JMSCorrelationID expressed

[jira] [Updated] (QPID-8139) [Broker-J] Selector containing JMSMessageID expressions might not find the message when expression JMSMessageID value starts with 'ID:' prefix but the real message id does

[ https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8139: - Affects Version/s: qpid-java-broker-7.0.0 > [Broker-J] Selector containing JMSMessageID expressions mi

[jira] [Updated] (QPID-8182) [Broker-J] [Message Conversion] Message id fidelity lost when converting from AMQP 1.0 to 0-10 when message-id-string carries a ID: prefixed UUID

[ https://issues.apache.org/jira/browse/QPID-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8182: - Summary: [Broker-J] [Message Conversion] Message id fidelity lost when converting from AMQP 1.0 to 0-10

[jira] [Updated] (QPID-8182) [Broker-J] [Message Conversion] Message id fidelity lost when converting from AMQP 1.0 to 0-10 when message-id-string carries a ID: prefixed UUID

[ https://issues.apache.org/jira/browse/QPID-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8182: - Status: Reviewable (was: In Progress) > [Broker-J] [Message Conversion] Message id fidelity lost w

[jira] [Commented] (QPID-8182) [Broker-J] [Conversion] Message id fidelity lost when converting from AMQP 1.0 to 0-10 when message-id-string carries a ID: prefixed UUID

[ https://issues.apache.org/jira/browse/QPID-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468791#comment-16468791 ] Keith Wall commented on QPID-8182: -- On reflection, I decided that my first point in my comment was invalid

[jira] [Assigned] (QPID-8182) [Broker-J] [Conversion] Message id fidelity lost when converting from AMQP 1.0 to 0-10 when message-id-string carries a ID: prefixed UUID

[ https://issues.apache.org/jira/browse/QPID-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8182: Assignee: Keith Wall > [Broker-J] [Conversion] Message id fidelity lost when converting from A

[jira] [Commented] (QPID-8182) [Broker-J] [Conversion] Message id fidelity lost when converting from AMQP 1.0 to 0-10 when message-id-string carries a ID: prefixed UUID

[ https://issues.apache.org/jira/browse/QPID-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465947#comment-16465947 ] Keith Wall commented on QPID-8182: -- I find other similar problems: When publishing with Qpid JMS Client

[jira] [Updated] (QPID-8182) [Broker-J] [Conversion] Message id fidelity lost when converting from AMQP 1.0 to 0-10 when message-id-string carries a ID: prefixed UUID

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

[jira] [Updated] (QPID-8182) [Broker-J] [Conversion] Message id fidelity lost when converting from AMQP 1.0 to 0-10 when message-id-string carries a ID: prefixed UUID

[ https://issues.apache.org/jira/browse/QPID-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8182: - Affects Version/s: qpid-java-broker-7.0.0 > [Broker-J] [Conversion] Message id fidelity lost w

[jira] [Updated] (QPID-8139) [Broker-J] Selector containing JMSMessageID expressions might not find the message when expression JMSMessageID value starts with 'ID:' prefix but the real message id does

[ https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8139: - Description: JMS specification requires JMSMessageID value to start with prefix "ID:". The

[jira] [Created] (QPID-8182) [Broker-J] [Conversion] Message id fidelity lost when converting from AMQP 1.0 to 0-10 when message-id-string carries a ID: prefixed UUID

Keith Wall created QPID-8182: Summary: [Broker-J] [Conversion] Message id fidelity lost when converting from AMQP 1.0 to 0-10 when message-id-string carries a ID: prefixed UUID Key: QPID-8182 URL: https

[jira] [Updated] (QPID-8181) [Broker-J] Add statistics for a total number of connections established on AMQP port

[ https://issues.apache.org/jira/browse/QPID-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8181: - Priority: Minor (was: Major) > [Broker-J] Add statistics for a total number of connections establis

[jira] [Commented] (QPID-8181) [Broker-J] Add statistics for a total number of connections established on AMQP port

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

[jira] [Updated] (QPID-8180) [JMS AMQP 0-8..0-91] Improve error message associated with the channel not found during frame dispatch

[ https://issues.apache.org/jira/browse/QPID-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8180: - Fix Version/s: qpid-java-client-0-x-6.3.1 > [JMS AMQP 0-8..0-91] Improve error message associa

[jira] [Updated] (QPID-8180) [JMS AMQP 0-8..0-91] Improve error message associated with the channel not found during frame dispatch

[ https://issues.apache.org/jira/browse/QPID-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8180: - Status: Reviewable (was: In Progress) > [JMS AMQP 0-8..0-91] Improve error message associa

[jira] [Assigned] (QPID-8180) [JMS AMQP 0-8..0-91] Improve error message associated with the channel not found during frame dispatch

[ https://issues.apache.org/jira/browse/QPID-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8180: Assignee: Keith Wall > [JMS AMQP 0-8..0-91] Improve error message associated with the chan

[jira] [Updated] (QPID-8180) [JMS AMQP 0-8..0-91] Improve error message associated with the channel not found during frame dispatch

[ https://issues.apache.org/jira/browse/QPID-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8180: - Description: A defect report against a 0.32 derivative client included a seemingly spontaneous

[jira] [Created] (QPID-8180) [JMS AMQP 0-8..0-91] Improve error message associated with the channel not found during frame dispatch

Keith Wall created QPID-8180: Summary: [JMS AMQP 0-8..0-91] Improve error message associated with the channel not found during frame dispatch Key: QPID-8180 URL: https://issues.apache.org/jira/browse/QPID-8180

[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: - Status: Reviewable (was: In Progress) > [JMS AMQP 0-x] Cannot publish message with address ba

[jira] [Assigned] (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 reassigned QPID-8141: Assignee: Keith Wall > [JMS AMQP 0-x] Cannot publish message with address based destinati

[jira] [Comment Edited] (QPID-8178) [Broker-J] [Websocket] Support authentication from bearer token carried by authentication header

[ https://issues.apache.org/jira/browse/QPID-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460986#comment-16460986 ] Keith Wall edited comment on QPID-8178 at 5/2/18 12:57 PM: --- Yes, for the SASL

[jira] [Commented] (QPID-8178) [Broker-J] [Websocket] Support authentication from bearer token carried by authentication header

[ https://issues.apache.org/jira/browse/QPID-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460986#comment-16460986 ] Keith Wall commented on QPID-8178: -- Yes, for the SASL case, I think presenting a EXTERNAL SASL

[jira] [Comment Edited] (QPID-8178) [Broker-J] [Websocket] Support authentication from bearer token carried by authentication header

[ https://issues.apache.org/jira/browse/QPID-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460636#comment-16460636 ] Keith Wall edited comment on QPID-8178 at 5/2/18 7:44 AM: -- It could work

[jira] [Commented] (QPID-8178) [Broker-J] [Websocket] Support authentication from bearer token carried by authentication header

[ https://issues.apache.org/jira/browse/QPID-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460636#comment-16460636 ] Keith Wall commented on QPID-8178: -- It could work in a similar way to the external authentication

[jira] [Created] (QPID-8178) [Broker-J] [Websocket] Support authentication from bearer token carried by authentication header

Keith Wall created QPID-8178: Summary: [Broker-J] [Websocket] Support authentication from bearer token carried by authentication header Key: QPID-8178 URL: https://issues.apache.org/jira/browse/QPID-8178

[jira] [Updated] (QPID-8176) [Broker-J][WMC] Infinite loop in Web Management Console restart operation when OAuth2 authentication provider is configured on http port

[ https://issues.apache.org/jira/browse/QPID-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8176: - Summary: [Broker-J][WMC] Infinite loop in Web Management Console restart operation when OAuth2

[jira] [Resolved] (QPID-8176) [Broker-J][WMC] Infinite redirect loop in Web Management Console restart operation when OAuth2 authentication provider is configured on http port

[ https://issues.apache.org/jira/browse/QPID-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8176. -- Resolution: Fixed > [Broker-J][WMC] Infinite redirect loop in Web Management Console rest

[jira] [Commented] (QPID-8176) [Broker-J][WMC] Infinite redirect loop in Web Management Console restart operation when OAuth2 authentication provider is configured on http port

[ https://issues.apache.org/jira/browse/QPID-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459722#comment-16459722 ] Keith Wall commented on QPID-8176: -- It seems fragile that the web management console needs to know the URL

[jira] [Updated] (QPID-8176) [Broker-J][WMC] Infinite redirect loop in Web Management Console restart operation when OAuth2 authentication provider is configured on http port

[ https://issues.apache.org/jira/browse/QPID-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8176: - Summary: [Broker-J][WMC] Infinite redirect loop in Web Management Console restart operation when OAuth2

[jira] [Updated] (QPID-8139) [Broker-J] Selector containing JMSMessageID expressions might not find the message when expression JMSMessageID value starts with 'ID:' prefix but the real message id does

[ https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8139: - Status: Reviewable (was: In Progress) > [Broker-J] Selector containing JMSMessageID expressions mi

[jira] [Commented] (QPID-8172) [Broker-J] OAuth2 authentication provider should not mandate setting of client secret

[ https://issues.apache.org/jira/browse/QPID-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450199#comment-16450199 ] Keith Wall commented on QPID-8172: -- Furthermore, I notice that "2.3.1. Client Password" goes

[jira] [Updated] (QPID-8171) [Broker-J] Failed to start broker under Windows when QPID_JAVA_GC is set

[ https://issues.apache.org/jira/browse/QPID-8171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8171: - Priority: Minor (was: Major) > [Broker-J] Failed to start broker under Windows when QPID_JAVA_GC is

[jira] [Resolved] (QPID-8171) [Broker-J] Failed to start broker under Windows when QPID_JAVA_GC is set

[ https://issues.apache.org/jira/browse/QPID-8171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8171. -- Resolution: Fixed > [Broker-J] Failed to start broker under Windows when QPID_JAVA_GC is

[jira] [Updated] (QPID-8171) [Broker-J] Failed to start broker under Windows when QPID_JAVA_GC is set

[ https://issues.apache.org/jira/browse/QPID-8171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8171: - Fix Version/s: qpid-java-broker-7.0.4 qpid-java-broker-7.1 > [Broker-J] Failed to st

[jira] [Commented] (QPID-8164) [Broker-J] [AMQP 1.0] [BINDMAP] Dynamic nodes created with the temporary-queue capability do not enforce connection exclusivity

[ https://issues.apache.org/jira/browse/QPID-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447786#comment-16447786 ] Keith Wall commented on QPID-8164: -- See https://issues.oasis-open.org/browse/AMQPBINDMAP-42 > [Broke

[jira] [Updated] (QPID-8164) [Broker-J] [AMQP 1.0] [BINDMAP] Dynamic nodes created with the temporary-queue capability do not enforce connection exclusivity

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

[jira] [Updated] (QPID-8164) [Broker-J] [AMQP 1.0] [BINDMAP] Dynamic nodes created with the temporary-queue capability do not enforce connection exclusivity

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

[jira] [Commented] (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 'war

[ https://issues.apache.org/jira/browse/QPID-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443926#comment-16443926 ] Keith Wall commented on QPID-8135: -- Changes at  [bcb5f70|https://git-wip-us.apache.org/repos/asf?p=qpid

[jira] [Resolved] (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 resolved QPID-8135. -- Resolution: Fixed > [JMS AMQP 0-x] Connection URL options for end-to-end encryption > keystore/tr

[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=16438847#comment-16438847 ] Keith Wall commented on QPID-8158: -- Changes look like an improvement to me. > [Broker-J] [System Te

[jira] [Updated] (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:all-tabpanel ] Keith Wall updated QPID-8158: - Fix Version/s: qpid-java-broker-7.1 > [Broker-J] [System Tests] Refactor BDB HA system te

[jira] [Created] (QPID-8166) [Broker-J] Remove use of ${QPID_HOME}/etc from default configuration

Keith Wall created QPID-8166: Summary: [Broker-J] Remove use of ${QPID_HOME}/etc from default configuration Key: QPID-8166 URL: https://issues.apache.org/jira/browse/QPID-8166 Project: Qpid

[jira] [Updated] (QPID-8163) [Broker-J] [ACL] Owner ACL rules

[ https://issues.apache.org/jira/browse/QPID-8163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8163: - Attachment: 0001-QPID-8163.patch > [Broker-J] [ACL] Owner ACL ru

[jira] [Assigned] (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 reassigned QPID-8160: Assignee: Keith Wall > [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: - Fix Version/s: qpid-java-broker-7.1.0 > [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: - Affects Version/s: qpid-java-broker-7.0.3 qpid-java-broker-7.0.0 > [Broke

[jira] [Updated] (QPID-8164) [Broker-J] [AMQP 1.0] [BINDMAP] Dynamic nodes created with the temporary-queue capability do not enforce connection exclusivity

[ https://issues.apache.org/jira/browse/QPID-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8164: - Summary: [Broker-J] [AMQP 1.0] [BINDMAP] Dynamic nodes created with the temporary-queue capability do

[jira] [Created] (QPID-8164) [Broker-J] [AMQP 1.0] [BINDMAP] temporary-queue do not enforce connection exclusivity

Keith Wall created QPID-8164: Summary: [Broker-J] [AMQP 1.0] [BINDMAP] temporary-queue do not enforce connection exclusivity Key: QPID-8164 URL: https://issues.apache.org/jira/browse/QPID-8164 Project

[jira] [Updated] (QPID-8163) [Broker-J] [ACL] Owner ACL rules

[ https://issues.apache.org/jira/browse/QPID-8163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8163: - Description: [http://qpid.2158936.n2.nabble.com/Java-Broker-Temporary-queues-ACLs-for-multiple-users

[jira] [Updated] (QPID-8163) [Broker-J] [ACL] Owner ACL rules

[ https://issues.apache.org/jira/browse/QPID-8163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8163: - Description: [http://qpid.2158936.n2.nabble.com/Java-Broker-Temporary-queues-ACLs-for-multiple-users

[jira] [Updated] (QPID-8162) [Broker-J] [Model] Configured Object should have a notion of owner

[ https://issues.apache.org/jira/browse/QPID-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8162: - Description: Configured objects ought to have an {{owner}} which should be a {{Principal

[jira] [Created] (QPID-8163) [Broker-J] [ACL] Owner ACL rules

Keith Wall created QPID-8163: Summary: [Broker-J] [ACL] Owner ACL rules Key: QPID-8163 URL: https://issues.apache.org/jira/browse/QPID-8163 Project: Qpid Issue Type: Improvement

[jira] [Created] (QPID-8162) [Broker-J] [Model] Configured Object should have a notion of owner

Keith Wall created QPID-8162: Summary: [Broker-J] [Model] Configured Object should have a notion of owner Key: QPID-8162 URL: https://issues.apache.org/jira/browse/QPID-8162 Project: Qpid Issue

[jira] [Commented] (QPID-8161) [Broker-J] [BDB] Broker failed due to lock timeout exception on MESSAGE_METADATA_SEQ

[ https://issues.apache.org/jira/browse/QPID-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435350#comment-16435350 ] Keith Wall commented on QPID-8161: -- In the case of this problem, the Broker had been up for two hours

[jira] [Comment Edited] (QPID-8161) [Broker-J] [BDB] Broker failed due to lock timeout exception on MESSAGE_METADATA_SEQ

[ https://issues.apache.org/jira/browse/QPID-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435350#comment-16435350 ] Keith Wall edited comment on QPID-8161 at 4/12/18 11:01 AM: In the case

[jira] [Created] (QPID-8161) [Broker-J] [BDB] Broker failed due to lock timeout exception on MESSAGE_METADATA_SEQ

Keith Wall created QPID-8161: Summary: [Broker-J] [BDB] Broker failed due to lock timeout exception on MESSAGE_METADATA_SEQ Key: QPID-8161 URL: https://issues.apache.org/jira/browse/QPID-8161 Project

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

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