[jira] [Created] (QPID-8101) [Broker-J] [Web Management Console] Add ability to close more than one connection at once

Keith Wall created QPID-8101: Summary: [Broker-J] [Web Management Console] Add ability to close more than one connection at once Key: QPID-8101 URL: https://issues.apache.org/jira/browse/QPID-8101

[jira] [Updated] (QPID-8100) [Broker-J] [AMQP 0-10] SESSION_BUSY sent on wrong channel leading to hung Messaging API based application

[ https://issues.apache.org/jira/browse/QPID-8100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8100: - Priority: Major (was: Minor) > [Broker-J] [AMQP 0-10] SESSION_BUSY sent on wrong channel leading to h

[jira] [Updated] (QPID-8100) [Broker-J] [AMQP 0-10] SESSION_BUSY sent on wrong channel leading to hung Messaging API based application

[ https://issues.apache.org/jira/browse/QPID-8100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8100: - Description: If, during session attachment, the Broker detects that the 0-10 session is already in use

[jira] [Updated] (QPID-8100) [Broker-J] [AMQP 0-10] SESSION_BUSY sent on wrong channel leading to hung Messaging API based application

[ https://issues.apache.org/jira/browse/QPID-8100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8100: - Summary: [Broker-J] [AMQP 0-10] SESSION_BUSY sent on wrong channel leading to hung Messaging API based

[jira] [Updated] (QPID-8100) [Broker-J] [AMQP 0-10] SESSION_BUSY sent on wrong channel

[ https://issues.apache.org/jira/browse/QPID-8100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8100: - Description: If, during session attachment, the Broker detects that the 0-10 session is already in use

[jira] [Created] (QPID-8100) [Broker-J] [AMQP 0-10] SESSION_BUSY sent on wrong channel

Keith Wall created QPID-8100: Summary: [Broker-J] [AMQP 0-10] SESSION_BUSY sent on wrong channel Key: QPID-8100 URL: https://issues.apache.org/jira/browse/QPID-8100 Project: Qpid Issue Type: Bug

[jira] [Assigned] (QPID-8098) [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count

[ https://issues.apache.org/jira/browse/QPID-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8098: Assignee: Keith Wall > [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the deliv

[jira] [Updated] (QPID-8098) [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count

[ https://issues.apache.org/jira/browse/QPID-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8098: - Status: Reviewable (was: In Progress) > [Broker-J] [AMQP 0-10] Queue browsers erroneously increm

[jira] [Updated] (QPID-8098) [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count

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

[jira] [Created] (QPID-8099) [Broker-J] [AMQP Management] Operation Queue#getMessageInfo response returned as serialised java object rather list of maps

Keith Wall created QPID-8099: Summary: [Broker-J] [AMQP Management] Operation Queue#getMessageInfo response returned as serialised java object rather list of maps Key: QPID-8099 URL: https://issues.apache.org/jira

[jira] [Updated] (QPID-8098) [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count

[ https://issues.apache.org/jira/browse/QPID-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8098: - Description: On the AMQP 0-10 protocol path within the Broker, deliveries to queue browsers erroneously

[jira] [Updated] (QPID-8098) [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count

[ https://issues.apache.org/jira/browse/QPID-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8098: - Summary: [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count (was: [AMQP 0-10

[jira] [Created] (QPID-8098) [AMQP 0-10] Queue browsers increment the delivery count

Keith Wall created QPID-8098: Summary: [AMQP 0-10] Queue browsers increment the delivery count Key: QPID-8098 URL: https://issues.apache.org/jira/browse/QPID-8098 Project: Qpid Issue Type: Bug

[jira] [Commented] (QPID-8091) [Broker-J] [AMQP 1.0] Store transaction timeout feature

[ https://issues.apache.org/jira/browse/QPID-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358608#comment-16358608 ] Keith Wall commented on QPID-8091: -- Alex - we paired on ffd5ad0, 46c49cf. I reviewed your remaining work

[jira] [Commented] (QPID-8097) NullPointerException in AMQP 1.0 plugin using OpenJDK

[ https://issues.apache.org/jira/browse/QPID-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358273#comment-16358273 ] Keith Wall commented on QPID-8097: -- Sorry for the jargon. By "using AMQP 1.0 against Broker-J"

[jira] [Commented] (QPID-8097) NullPointerException in AMQP 1.0 plugin using OpenJDK

[ https://issues.apache.org/jira/browse/QPID-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16354274#comment-16354274 ] Keith Wall commented on QPID-8097: -- Thanks for reporting the problem. Firstly, let me point out if you

[jira] [Updated] (QPID-8096) [Broker-J] PUTting a user preference to the BDB backed configuration store fails with NPE

[ https://issues.apache.org/jira/browse/QPID-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8096: - Fix Version/s: qpid-java-broker-7.1.0 > [Broker-J] PUTting a user preference to the BDB bac

[jira] [Assigned] (QPID-8096) [Broker-J] PUTting a user preference to the BDB backed configuration store fails with NPE

[ https://issues.apache.org/jira/browse/QPID-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8096: Assignee: Keith Wall > [Broker-J] PUTting a user preference to the BDB backed configuration st

[jira] [Updated] (QPID-8096) [Broker-J] PUTting a user preference to the BDB backed configuration store fails with NPE

[ https://issues.apache.org/jira/browse/QPID-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8096: - Summary: [Broker-J] PUTting a user preference to the BDB backed configuration store fails with NPE

[jira] [Updated] (QPID-8096) [Broker-j] PUTting a user preference to the BDB backed configuration store fails with NPE

[ https://issues.apache.org/jira/browse/QPID-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8096: - Description: As an authenticated user, putting (HTTP PUT) a user preference to the store when using

[jira] [Updated] (QPID-8096) [Broker-j] PUTting a user preference to the BDB backed configuration store fails with NPE

[ https://issues.apache.org/jira/browse/QPID-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8096: - Description: Putting (HTTP PUT) a user preference to the store when using a configuration store backed

[jira] [Updated] (QPID-8096) [Broker-j] PUTting a user preference to the BDB backed configuration store fails with NPE

[ https://issues.apache.org/jira/browse/QPID-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8096: - Description: Putting (HTTP PUT) a user preference to the store when using a configuration store backed

[jira] [Created] (QPID-8096) [Broker-j] PUTting a user preference to the BDB backed configuration store fails with NPE

Keith Wall created QPID-8096: Summary: [Broker-j] PUTting a user preference to the BDB backed configuration store fails with NPE Key: QPID-8096 URL: https://issues.apache.org/jira/browse/QPID-8096

[jira] [Commented] (QPID-8092) [Broker-J][Web Management Console] Fix label for max history of file loggers

[ https://issues.apache.org/jira/browse/QPID-8092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350266#comment-16350266 ] Keith Wall commented on QPID-8092: -- Ported to 7.0.x. > [Broker-J][Web Management Console] Fix la

[jira] [Resolved] (QPID-8081) [Broker] FileLogger with "roll on restart" set to "true" does not roll log file on broker restart when "roll daily" is "true"

[ https://issues.apache.org/jira/browse/QPID-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8081. -- Resolution: Fixed > [Broker] FileLogger with "roll on restart" set to "true" do

[jira] [Commented] (QPID-8081) [Broker] FileLogger with "roll on restart" set to "true" does not roll log file on broker restart when "roll daily" is "true"

[ https://issues.apache.org/jira/browse/QPID-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350269#comment-16350269 ] Keith Wall commented on QPID-8081: -- Ported to 7.0.x. > [Broker] FileLogger with "roll on rest

[jira] [Resolved] (QPID-8092) [Broker-J][Web Management Console] Fix label for max history of file loggers

[ https://issues.apache.org/jira/browse/QPID-8092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8092. -- Resolution: Fixed > [Broker-J][Web Management Console] Fix label for max history of file logg

[jira] [Updated] (QPID-8093) [Broker-J] [Logback] Meaning of maxHistory attribute unclear

[ https://issues.apache.org/jira/browse/QPID-8093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8093: - Description: The meaning of the BrokerLogger attribute {{maxHistory}} is confused.  As reported by QPID

[jira] [Created] (QPID-8093) [Broker-J] [Logback] Meaning of maxHistory attribute unclear

Keith Wall created QPID-8093: Summary: [Broker-J] [Logback] Meaning of maxHistory attribute unclear Key: QPID-8093 URL: https://issues.apache.org/jira/browse/QPID-8093 Project: Qpid Issue Type

[jira] [Commented] (QPID-8092) [Broker-J][Web Management Console] Fix label for max history of file loggers

[ https://issues.apache.org/jira/browse/QPID-8092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350246#comment-16350246 ] Keith Wall commented on QPID-8092: -- The need for this tells us that the model is incorrect.   The two

[jira] [Updated] (QPID-8081) [Broker] FileLogger with "roll on restart" set to "true" does not roll log file on broker restart when "roll daily" is "true"

[ https://issues.apache.org/jira/browse/QPID-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8081: - Priority: Minor (was: Major) > [Broker] FileLogger with "roll on restart" set to "true&

[jira] [Commented] (QPID-8081) [Broker] FileLogger with "roll on restart" set to "true" does not roll log file on broker restart when "roll daily" is "true"

[ https://issues.apache.org/jira/browse/QPID-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350231#comment-16350231 ] Keith Wall commented on QPID-8081: -- I think the changes look functionally correct.  As we are sub-classing

[jira] [Updated] (QPID-8081) [Broker] FileLogger with "roll on restart" set to "true" does not roll log file on broker restart when "roll daily" is "true"

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

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

[ https://issues.apache.org/jira/browse/QPID-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8066. -- Resolution: Fixed > [Broker-J] Virtual host logger rules are left over in configuration store >

[jira] [Resolved] (QPID-8090) [Broker-J] Allow to specify all possible BoneCP configuration settings via context

[ https://issues.apache.org/jira/browse/QPID-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8090. -- Resolution: Fixed > [Broker-J] Allow to specify all possible BoneCP configuration settings

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

[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8067. -- Resolution: Fixed > [Broker-J] Default queue filter for arrival time with non-zero replay period >

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

[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348969#comment-16348969 ] Keith Wall commented on QPID-8067: -- Changes look reasonable, ported to the 7.0.x branch. > [Broke

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

[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8067: - Priority: Minor (was: Major) > [Broker-J] Default queue filter for arrival time with non-zero rep

[jira] [Comment Edited] (QPID-8090) [Broker-J] Allow to specify all possible BoneCP configuration settings via context

[ https://issues.apache.org/jira/browse/QPID-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348645#comment-16348645 ] Keith Wall edited comment on QPID-8090 at 2/1/18 2:32 PM: -- I see

[jira] [Commented] (QPID-8090) [Broker-J] Allow to specify all possible BoneCP configuration settings via context

[ https://issues.apache.org/jira/browse/QPID-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348645#comment-16348645 ] Keith Wall commented on QPID-8090: -- Isn't \{{ServerScopedRuntimeException}} a bit extreme?  I think

[jira] [Comment Edited] (QPID-8086) [Broker-J] Create tool to permit recovery from QPID-8066

[ https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344976#comment-16344976 ] Keith Wall edited comment on QPID-8086 at 2/1/18 12:55 PM: --- Tactical change

[jira] [Created] (QPID-8091) [Broker-J] [AMQP 1.0] Store transaction timeout feature

Keith Wall created QPID-8091: Summary: [Broker-J] [AMQP 1.0] Store transaction timeout feature Key: QPID-8091 URL: https://issues.apache.org/jira/browse/QPID-8091 Project: Qpid Issue Type

[jira] [Updated] (QPID-7183) Use timed acquisitions to improve message flow amongst competing consumers

[ https://issues.apache.org/jira/browse/QPID-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7183: - Fix Version/s: Future > Use timed acquisitions to improve message flow amongst competing consum

[jira] [Closed] (QPID-7452) [Java Tests] URLConnection can be spuriously open twice in RestTestHelper whilst making a test HTTP request to the Broker causing test failures

[ https://issues.apache.org/jira/browse/QPID-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed QPID-7452. Resolution: Won't Fix If there is a defect here, it must in the JDK itself.   AFAIK we haven't seen

[jira] [Updated] (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 updated QPID-7567: - Status: Reviewable (was: In Progress) > [Java Broker] Select appropriate certificate for TLS ba

[jira] [Updated] (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 updated QPID-7567: - Fix Version/s: (was: Future) qpid-java-broker-7.1.0 > [Java Broker] Sel

[jira] [Assigned] (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 reassigned QPID-7567: Assignee: Keith Wall > [Java Broker] Select appropriate certificate for TLS based on SNIServerN

[jira] [Updated] (QPID-7909) [Java Broker] CancelledKeyException can be thrown from a selector thread when accepting new connection on Broker shutdown

[ https://issues.apache.org/jira/browse/QPID-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7909: - Fix Version/s: (was: Future) > [Java Broker] CancelledKeyException can be thrown from a selec

[jira] [Resolved] (QPID-7909) [Java Broker] CancelledKeyException can be thrown from a selector thread when accepting new connection on Broker shutdown

[ https://issues.apache.org/jira/browse/QPID-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7909. -- Resolution: Duplicate > [Java Broker] CancelledKeyException can be thrown from a selector thread w

[jira] [Resolved] (QPID-8085) [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker sending link endpoint

[ https://issues.apache.org/jira/browse/QPID-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8085. -- Resolution: Fixed Seems reasonable to me. > [Broker-J][AMQP 1.0] Optimize the sending of f

[jira] [Updated] (QPID-8085) [Broker-J][AMQP 1.0] Optimize the sending of flow performatives from broker sending link endpoint

[ https://issues.apache.org/jira/browse/QPID-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8085: - Fix Version/s: qpid-java-broker-7.1.0 > [Broker-J][AMQP 1.0] Optimize the sending of flow performati

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

[ https://issues.apache.org/jira/browse/QPID-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8066. -- Resolution: Fixed Tactical change for 7.0.x and 6.1.x looks good. > [Broker-J] Virtual host log

[jira] [Updated] (QPID-7632) [AMQP 0-10] NPE from QueueQuery when queue argument omitted

[ https://issues.apache.org/jira/browse/QPID-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7632: - Fix Version/s: (was: qpid-java-broker-7.0.1) Future > [AMQP 0-10] NPE f

[jira] [Resolved] (QPID-8086) [Broker-J] Create tool to permit recovery from QPID-8066

[ https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8086. -- Resolution: Fixed > [Broker-J] Create tool to permit recovery from QPID-8

[jira] [Commented] (QPID-8086) [Broker-J] Create tool to permit recovery from QPID-8066

[ https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344976#comment-16344976 ] Keith Wall commented on QPID-8086: -- Merged into 7.0.x and 6.1.x > [Broker-J] Create tool to per

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

[ https://issues.apache.org/jira/browse/QPID-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8066: - Status: Reviewable (was: In Progress) > [Broker-J] Virtual host logger rules are left o

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

[ https://issues.apache.org/jira/browse/QPID-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344958#comment-16344958 ] Keith Wall commented on QPID-8066: -- Alex, I incorporated the changes we agreed following the review

[jira] [Closed] (QPID-7547) [Java Broker] Refactor closing and deletion of AbstractConfiguredObjects

[ https://issues.apache.org/jira/browse/QPID-7547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed QPID-7547. Resolution: Duplicate Fixed by QPID-8066 > [Java Broker] Refactor closing and delet

[jira] [Commented] (QPID-8062) [Broker-J][AMQP 1.0] Fix handling of routing errors when target destination cannot route received message

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344800#comment-16344800 ] Keith Wall commented on QPID-8062: -- Changes look reasonable to me. > [Broker-J][AMQP 1.0] Fix handl

[jira] [Commented] (QPID-8032) [AMQP1.0] AsyncAutoCommitTransaction optimisation

[ https://issues.apache.org/jira/browse/QPID-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344798#comment-16344798 ] Keith Wall commented on QPID-8032: -- Changes look good to me. > [AMQP1.0] AsyncAutoCommitTransact

[jira] [Updated] (QPID-8087) [BDB] [HA] Virtualhostnode fails to go into ERROR state following failure to recover

[ https://issues.apache.org/jira/browse/QPID-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8087: - Status: Reviewable (was: In Progress) > [BDB] [HA] Virtualhostnode fails to go into ERROR state follow

[jira] [Updated] (QPID-8087) [BDB] [HA] Virtualhostnode fails to go into ERROR state following failure to recover

[ https://issues.apache.org/jira/browse/QPID-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8087: - Fix Version/s: qpid-java-broker-7.0.1 > [BDB] [HA] Virtualhostnode fails to go into ERROR state follow

[jira] [Assigned] (QPID-8087) [BDB] [HA] Virtualhostnode fails to go into ERROR state following failure to recover

[ https://issues.apache.org/jira/browse/QPID-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8087: Assignee: Keith Wall > [BDB] [HA] Virtualhostnode fails to go into ERROR state following fail

[jira] [Created] (QPID-8088) Pull-up bindingAdress attribute to Port

Keith Wall created QPID-8088: Summary: Pull-up bindingAdress attribute to Port Key: QPID-8088 URL: https://issues.apache.org/jira/browse/QPID-8088 Project: Qpid Issue Type: Improvement

[jira] [Created] (QPID-8087) [BDB] [HA] Virtualhostnode fails to go into ERROR state following failure to recover

Keith Wall created QPID-8087: Summary: [BDB] [HA] Virtualhostnode fails to go into ERROR state following failure to recover Key: QPID-8087 URL: https://issues.apache.org/jira/browse/QPID-8087 Project

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

[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6933: - Fix Version/s: qpid-java-broker-7.1.0 > Factor out a JMS client neutral messaging test suite from sys

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

[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-6933. -- Resolution: Fixed > Factor out a JMS client neutral messaging test suite from system te

[jira] [Updated] (QPID-8074) [Qpid JMS AMQP 0-x] Build framework to run JMS client system tests

[ https://issues.apache.org/jira/browse/QPID-8074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8074: - Fix Version/s: qpid-java-client-0-x-6.3.1 > [Qpid JMS AMQP 0-x] Build framework to run JMS client sys

[jira] [Resolved] (QPID-8074) [Qpid JMS AMQP 0-x] Build framework to run JMS client system tests

[ https://issues.apache.org/jira/browse/QPID-8074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8074. -- Resolution: Fixed > [Qpid JMS AMQP 0-x] Build framework to run JMS client system te

[jira] [Updated] (QPID-8074) [Qpid JMS AMQP 0-x] Build framework to run JMS client system tests

[ https://issues.apache.org/jira/browse/QPID-8074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8074: - Status: Reviewable (was: In Progress) > [Qpid JMS AMQP 0-x] Build framework to run JMS client sys

[jira] [Updated] (QPID-8086) [Broker-J] Add ability to the Broker to permit recovery from QPID-8066

[ https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8086: - Status: Reviewable (was: In Progress) > [Broker-J] Add ability to the Broker to permit recovery from Q

[jira] [Updated] (QPID-8086) [Broker-J] Create tool to permit recovery from QPID-8066

[ https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8086: - Summary: [Broker-J] Create tool to permit recovery from QPID-8066 (was: [Broker-J] Add ability

[jira] [Assigned] (QPID-8086) [Broker-J] Add ability to the Broker to permit recovery from QPID-8066

[ https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8086: Assignee: Keith Wall > [Broker-J] Add ability to the Broker to permit recovery from QPID-8

[jira] [Updated] (QPID-8086) [Broker-J] Add ability to the Broker to permit recovery from QPID-8066

[ https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8086: - Description: Defect QPID-8066 has the potential to leave the Broker in a state where it cannot

[jira] [Created] (QPID-8086) [Broker-J] Add ability to the Broker to permit recovery from QPID-8066

Keith Wall created QPID-8086: Summary: [Broker-J] Add ability to the Broker to permit recovery from QPID-8066 Key: QPID-8086 URL: https://issues.apache.org/jira/browse/QPID-8086 Project: Qpid

[jira] [Updated] (QPID-8086) [Broker-J] Add ability to the Broker to permit recovery from QPID-8066

[ https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8086: - Description: Defect QPID-8066 has the potential to leave the Broker in a state where it cannot

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

[ https://issues.apache.org/jira/browse/QPID-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16337659#comment-16337659 ] Keith Wall edited comment on QPID-8066 at 1/24/18 2:33 PM: --- I think the nub

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

[ https://issues.apache.org/jira/browse/QPID-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16337659#comment-16337659 ] Keith Wall edited comment on QPID-8066 at 1/24/18 2:33 PM: --- I think the nub

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

[ https://issues.apache.org/jira/browse/QPID-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16337659#comment-16337659 ] Keith Wall commented on QPID-8066: -- I think the nub of the problem is that when deleting an object

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

[ https://issues.apache.org/jira/browse/QPID-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8066: - Attachment: QPID-8066.tar.bz2 > [Broker-J] Virtual host logger rules are left over in configuration st

[jira] [Commented] (QPID-8032) [AMQP1.0] AsyncAutoCommitTransaction optimisation

[ https://issues.apache.org/jira/browse/QPID-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16337444#comment-16337444 ] Keith Wall commented on QPID-8032: -- Changes looks reasonable to me but as discussed we should make

[jira] [Updated] (QPID-8032) [AMQP1.0] AsyncAutoCommitTransaction optimisation

[ https://issues.apache.org/jira/browse/QPID-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8032: - Status: Open (was: Reviewable) > [AMQP1.0] AsyncAutoCommitTransaction optimisat

[jira] [Commented] (QPID-8062) [Broker-J][AMQP 1.0] Fix handling of routing errors when target destination cannot route received message

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335538#comment-16335538 ] Keith Wall commented on QPID-8062: -- Changes look reasonable to me.   Ready for back porting. > [Broke

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

[ https://issues.apache.org/jira/browse/QPID-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8066: - Summary: [Broker-J] Virtual host logger rules are left over in configuration store after deletion

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

[ https://issues.apache.org/jira/browse/QPID-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8066: Assignee: Keith Wall > [Broker-J] Virtual host logger rules are left over in configuration st

[jira] [Created] (QPID-8083) [REST] Refactor REST system test suite

Keith Wall created QPID-8083: Summary: [REST] Refactor REST system test suite Key: QPID-8083 URL: https://issues.apache.org/jira/browse/QPID-8083 Project: Qpid Issue Type: Improvement

[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: - Issue Type: Improvement (was: Bug) > [Broker-J] FileKeyStore should validate java keystore cont

[jira] [Assigned] (QPID-8062) [Broker-J][AMQP 1.0] When a pre-settled message published over "anonymous relay" is rejected by the destination, the Broker should detach the link for non-transactional c

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8062: Assignee: Keith Wall > [Broker-J][AMQP 1.0] When a pre-settled message published over "a

[jira] [Updated] (QPID-8062) [Broker-J][AMQP 1.0] When a pre-settled message published over "anonymous relay" is rejected by the destination, the Broker should detach the link for non-transactional ca

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8062: - Affects Version/s: qpid-java-broker-7.0.0 > [Broker-J][AMQP 1.0] When a pre-settled message published o

[jira] [Updated] (QPID-8062) [Broker-J][AMQP 1.0] When a pre-settled message published over "anonymous relay" is rejected by the destination, the Broker should detach the link for non-transactional ca

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8062: - Fix Version/s: qpid-java-broker-7.0.1 > [Broker-J][AMQP 1.0] When a pre-settled message published o

[jira] [Resolved] (QPID-8046) [Broker-J] Allow SASL mechanisms PLAIN and XOAUTH2 to not require initial response

[ https://issues.apache.org/jira/browse/QPID-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8046. -- Resolution: Fixed > [Broker-J] Allow SASL mechanisms PLAIN and XOAUTH2 to not require init

[jira] [Commented] (QPID-8017) [Broker-J] [BDB] JE log events written at JUL level FINE and below not included in the log produced by a BrokerLogger

[ https://issues.apache.org/jira/browse/QPID-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328834#comment-16328834 ] Keith Wall commented on QPID-8017: -- Merged to 7.0.x branch. > [Broker-J] [BDB] JE log events writ

[jira] [Comment Edited] (QPID-8080) [Broker-J] Broker can crash when JDBC message store opens to many SQL connections to the RDBMS exceeding the maximum connection limit

[ https://issues.apache.org/jira/browse/QPID-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328794#comment-16328794 ] Keith Wall edited comment on QPID-8080 at 1/17/18 1:58 PM: --- This problem

[jira] [Comment Edited] (QPID-8080) [Broker-J] Broker can crash when JDBC message store opens to many SQL connections to the RDBMS exceeding the maximum connection limit

[ https://issues.apache.org/jira/browse/QPID-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328794#comment-16328794 ] Keith Wall edited comment on QPID-8080 at 1/17/18 1:58 PM: --- This problem

[jira] [Commented] (QPID-8080) [Broker-J] Broker can crash when JDBC message store opens to many SQL connections to the RDBMS exceeding the maximum connection limit

[ https://issues.apache.org/jira/browse/QPID-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328794#comment-16328794 ] Keith Wall commented on QPID-8080: -- This problem will manifest in a number of places: recovery dequeuing

[jira] [Commented] (QPID-8046) [Broker-J] Allow SASL mechanisms PLAIN and XOAUTH2 to not require initial response

[ https://issues.apache.org/jira/browse/QPID-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328668#comment-16328668 ] Keith Wall commented on QPID-8046: -- Changes looked reasonable to me, ported to 7.0.x, > [Broker-J] Al

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

[ https://issues.apache.org/jira/browse/QPID-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8061. -- Resolution: Fixed > [Broker-J] [AMQP 0-8..0-9-1] Declaring exchange with not existing altern

[jira] [Resolved] (QPID-8025) [Java Broker] Improve detach error message on unsubscribing from JMS shared subs

[ https://issues.apache.org/jira/browse/QPID-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8025. -- Resolution: Fixed > [Java Broker] Improve detach error message on unsubscribing from JMS shared >

[jira] [Commented] (QPID-8025) [Java Broker] Improve detach error message on unsubscribing from JMS shared subs

[ https://issues.apache.org/jira/browse/QPID-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328555#comment-16328555 ] Keith Wall commented on QPID-8025: -- Change looks reasonable to me. > [Java Broker] Improve detach er

[jira] [Updated] (QPID-8025) [Java Broker] Improve detach error message on unsubscribing from JMS shared subs

[ https://issues.apache.org/jira/browse/QPID-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8025: - Priority: Minor (was: Major) > [Java Broker] Improve detach error message on unsubscribing from

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