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

[ https://issues.apache.org/jira/browse/QPID-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8071. -- Resolution: Won't Fix Development of the Qpid JMS AMQP 0-x client is ceased.  As discussed please use

[jira] [Updated] (QPID-8076) [0-91] [Publisher Confirms] basic.ack returned to client before message is sync'd to disk

[ https://issues.apache.org/jira/browse/QPID-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8076: - Status: Reviewable (was: In Progress) > [0-91] [Publisher Confirms] basic.ack returned to client bef

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

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

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

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

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

[ https://issues.apache.org/jira/browse/QPID-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8070: - Fix Version/s: (was: qpid-python-1.35.0) > Qpid java broker is unable to reconnect to database af

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

[ https://issues.apache.org/jira/browse/QPID-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327266#comment-16327266 ] Keith Wall commented on QPID-8070: -- Changes looked reasonable to me.  Port to 7.0.x and 6.1.x branches

[jira] [Updated] (QPID-8076) [0-91] [Publisher Confirms] basic.ack returned to client before message is sync'd to disk

[ https://issues.apache.org/jira/browse/QPID-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8076: - Fix Version/s: qpid-java-broker-7.0.0 > [0-91] [Publisher Confirms] basic.ack returned to client bef

[jira] [Assigned] (QPID-8076) [0-91] [Publisher Confirms] basic.ack returned to client before message is sync'd to disk

[ https://issues.apache.org/jira/browse/QPID-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8076: Assignee: Keith Wall > [0-91] [Publisher Confirms] basic.ack returned to client before mess

[jira] [Resolved] (QPID-8077) [AMQ 0-91] [Publisher Confirms] Improve validations when switching to confirms mode.

[ https://issues.apache.org/jira/browse/QPID-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8077. -- Resolution: Invalid > [AMQ 0-91] [Publisher Confirms] Improve validations when switching to > co

[jira] [Assigned] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8079: Assignee: Keith Wall > [Broker-J] If the future associated with an AsyncCommand comple

[jira] [Updated] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8079: - Status: Reviewable (was: In Progress) > [Broker-J] If the future associated with an AsyncComm

[jira] [Commented] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327190#comment-16327190 ] Keith Wall commented on QPID-8079: -- Given this defect does not currently cause a defect, I don't think

[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: - Description: Some AMQP 1.0 messaging use-cases would benefit from the {{AsyncAutoCommitTransactions

[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: Reviewable (was: In Progress) > [AMQP1.0] AsyncAutoCommitTransaction optimisat

[jira] [Commented] (QPID-8077) [AMQ 0-91] [Publisher Confirms] Improve validations when switching to confirms mode.

[ https://issues.apache.org/jira/browse/QPID-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327055#comment-16327055 ] Keith Wall commented on QPID-8077: -- Invalid.  I see now that QPID-6164 went beyond Rabbit's capabilities

[jira] [Comment Edited] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327037#comment-16327037 ] Keith Wall edited comment on QPID-8079 at 1/16/18 11:54 AM

[jira] [Comment Edited] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327037#comment-16327037 ] Keith Wall edited comment on QPID-8079 at 1/16/18 11:54 AM

[jira] [Updated] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8079: - Priority: Minor (was: Major) > [Broker-J] If the future associated with an AsyncCommand comple

[jira] [Comment Edited] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327037#comment-16327037 ] Keith Wall edited comment on QPID-8079 at 1/16/18 11:49 AM

[jira] [Commented] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327037#comment-16327037 ] Keith Wall commented on QPID-8079: -- {{ServerTransaction.EnqueueAction}} are used in three places

[jira] [Created] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

Keith Wall created QPID-8079: Summary: [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back Key: QPID-8079 URL: https://issues.apache.org/jira/browse

[jira] [Updated] (QPID-8077) [AMQ 0-91] [Publisher Confirms] Improve validations when switching to confirms mode.

[ https://issues.apache.org/jira/browse/QPID-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8077: - Summary: [AMQ 0-91] [Publisher Confirms] Improve validations when switching to confirms mode. (was: [AMQ

[jira] [Created] (QPID-8077) [AMQ 0-91] [Publisher Confirms] Improve validations when switch to confirms mode.

Keith Wall created QPID-8077: Summary: [AMQ 0-91] [Publisher Confirms] Improve validations when switch to confirms mode. Key: QPID-8077 URL: https://issues.apache.org/jira/browse/QPID-8077 Project: Qpid

[jira] [Commented] (QPID-8076) [0-91] [Publisher Confirms] basic.ack returned to client before message is sync'd to disk

[ https://issues.apache.org/jira/browse/QPID-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326952#comment-16326952 ] Keith Wall commented on QPID-8076: -- My analysis is partly duff.   The problem actually only affects the HA

[jira] [Updated] (QPID-8076) [0-91] [Publisher Confirms] basic.ack returned to client before message is sync'd to disk

[ https://issues.apache.org/jira/browse/QPID-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8076: - Description: QPID-6164 added RabbitMQ's publish confirms [1] feature to Broker-J.   Concerning when

[jira] [Updated] (QPID-8076) [0-91] [Publisher Confirms] basic.ack returned to client before message is sync'd to disk

[ https://issues.apache.org/jira/browse/QPID-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8076: - Description: QPID-6164 added RabbitMQ's publish confirms [1] feature to Broker-J.   Concerning when

[jira] [Created] (QPID-8076) [0-91] [Publisher Confirms] basic.ack returned to client before message is sync'd to disk

Keith Wall created QPID-8076: Summary: [0-91] [Publisher Confirms] basic.ack returned to client before message is sync'd to disk Key: QPID-8076 URL: https://issues.apache.org/jira/browse/QPID-8076

[jira] [Assigned] (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 reassigned QPID-8032: Assignee: Keith Wall > [AMQP1.0] AsyncAutoCommitTransaction optimisat

[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=16322309#comment-16322309 ] Keith Wall commented on QPID-8017: -- In the end I opted for a simple context variable that forces the BDB

[jira] [Commented] (QPID-8042) [Broker-J][AMQP 1.0] Support for pipelined connection open containing SASL frames broken

[ https://issues.apache.org/jira/browse/QPID-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320356#comment-16320356 ] Keith Wall commented on QPID-8042: -- Changes merge to 7.0.x. As discussed, QPID-8038 (06e53d7) was merged

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

[ https://issues.apache.org/jira/browse/QPID-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320294#comment-16320294 ] Keith Wall commented on QPID-8071: -- This JIRA is not the best place to continue this conversation. May I

[jira] [Updated] (QPID-8042) [Broker-J][AMQP 1.0] Support for pipelined connection open containing SASL frames broken

[ https://issues.apache.org/jira/browse/QPID-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8042: - Summary: [Broker-J][AMQP 1.0] Support for pipelined connection open containing SASL frames broken

[jira] [Updated] (QPID-8042) [Broker-J][AMQP 1.0] Support for pipelined connection open containing sail frames broken

[ https://issues.apache.org/jira/browse/QPID-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8042: - Description: Opening of connection with pipelined SASL header, sasl mechanism frame (for plain), sasl

[jira] [Updated] (QPID-8042) [Broker-J][AMQP 1.0] Support for pipelined connection open containing sail frames broken

[ https://issues.apache.org/jira/browse/QPID-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8042: - Summary: [Broker-J][AMQP 1.0] Support for pipelined connection open containing sail frames broken

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[jira] [Commented] (QPID-8042) [Broker-J][AMQP 1.0] Add support for pipelined connection open containing sasl frames

[ https://issues.apache.org/jira/browse/QPID-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316512#comment-16316512 ] Keith Wall commented on QPID-8042: -- The functional change looks reasonable but I am unhappy

[jira] [Resolved] (QPID-8058) [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer of management temporary destination

[ https://issues.apache.org/jira/browse/QPID-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8058. -- Resolution: Fixed > [Broker-J][AMQP 1.0] Broker does not respond to drain request from consu

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

[ https://issues.apache.org/jira/browse/QPID-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316470#comment-16316470 ] Keith Wall commented on QPID-8060: -- Additional changes look okay to me, okay to port the functional

[jira] [Commented] (QPID-8065) [Broker-J] Add into Consumer configured object a derived attribute exposing consumer session

[ https://issues.apache.org/jira/browse/QPID-8065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16302379#comment-16302379 ] Keith Wall commented on QPID-8065: -- Didn't QPID-7316 do this already? > [Broker-J] Add into Consu

[jira] [Updated] (QPID-8040) [Broker-J] Uncaught java.nio.channels.CancelledKeyException seen during Broker shutdown

[ https://issues.apache.org/jira/browse/QPID-8040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8040: - Status: Open (was: Reviewable) We had another one of these failures yesterday. 2017-12-21. I think our

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

[ https://issues.apache.org/jira/browse/QPID-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301655#comment-16301655 ] Keith Wall commented on QPID-8060: -- I find {{org/apache/qpid/server/protocol/v0_8/AMQChannel.java:3134

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

[ https://issues.apache.org/jira/browse/QPID-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8060: - Status: Open (was: Reviewable) > [Broker-J] [AMQP 0-8..0-9-1] Declaring queue that specifies an altern

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

[ https://issues.apache.org/jira/browse/QPID-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8060: - Summary: [Broker-J] [AMQP 0-8..0-9-1] Declaring queue that specifies an alternate binding that does

[jira] [Commented] (QPID-8058) [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer of management temporary destination

[ https://issues.apache.org/jira/browse/QPID-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301644#comment-16301644 ] Keith Wall commented on QPID-8058: -- Looks okay to me, okay for porting. > [Broker-J][AMQP 1.0] Bro

[jira] [Resolved] (QPID-8057) [JMS AMQP 0-x][AMQP 0-10] IoReceiver thread can block itself for 60 seconds after sending session close controls and waiting for broker responses

[ https://issues.apache.org/jira/browse/QPID-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8057. -- Resolution: Fixed > [JMS AMQP 0-x][AMQP 0-10] IoReceiver thread can block itself for 60 seconds >

[jira] [Resolved] (QPID-8027) [Broker-J][AMQP 0-8..0-9-1] Receiving BasicAck with unknown tag crashes the broker

[ https://issues.apache.org/jira/browse/QPID-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8027. -- Resolution: Fixed > [Broker-J][AMQP 0-8..0-9-1] Receiving BasicAck with unknown tag cras

[jira] [Commented] (QPID-8027) [Broker-J][AMQP 0-8..0-9-1] Receiving BasicAck with unknown tag crashes the broker

[ https://issues.apache.org/jira/browse/QPID-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301628#comment-16301628 ] Keith Wall commented on QPID-8027: -- Looks reasonable to me. > [Broker-J][AMQP 0-8..0-9-1] Receiv

[jira] [Updated] (QPID-8047) [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown session

[ https://issues.apache.org/jira/browse/QPID-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8047: - Priority: Minor (was: Major) > [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown sess

[jira] [Resolved] (QPID-8047) [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown session

[ https://issues.apache.org/jira/browse/QPID-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8047. -- Resolution: Fixed > [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown sess

[jira] [Commented] (QPID-6793) (0-10) Sending messages with large header string throws AssertionError

[ https://issues.apache.org/jira/browse/QPID-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16298595#comment-16298595 ] Keith Wall commented on QPID-6793: -- QPID-6786 has made the Qpid JMS AMQP 0-x client fail gracefully

[jira] [Closed] (QPID-6793) (0-10) Sending messages with large header string throws AssertionError

[ https://issues.apache.org/jira/browse/QPID-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed QPID-6793. Resolution: Won't Fix > (0-10) Sending messages with large header string throws AssertionEr

[jira] [Commented] (QPID-8058) [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer of management temporary destination

[ https://issues.apache.org/jira/browse/QPID-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16286043#comment-16286043 ] Keith Wall commented on QPID-8058: -- I think the change looks reasonable to me. I think this problem would

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

[ https://issues.apache.org/jira/browse/QPID-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16286001#comment-16286001 ] Keith Wall commented on QPID-8060: -- * * The AMQP 0-10 behaviour for {{queue.declare}} when

[jira] [Updated] (QPID-8060) [Broker-J] [AMQP 0-8..0-9-1] Declaring queue with not existing alternate binding crashes the Broker

[ https://issues.apache.org/jira/browse/QPID-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8060: - Status: Open (was: Reviewable) > [Broker-J] [AMQP 0-8..0-9-1] Declaring queue with not existing altern

[jira] [Updated] (QPID-8057) [JMS AMQP 0-x][AMQP 0-10] IoReceiver thread can block itself for 60 seconds after sending session close controls and waiting for broker responses

[ https://issues.apache.org/jira/browse/QPID-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8057: - Fix Version/s: qpid-java-client-0-x-6.3.1 > [JMS AMQP 0-x][AMQP 0-10] IoReceiver thread can block its

[jira] [Updated] (QPID-8057) [JMS AMQP 0-x][AMQP 0-10] IoReceiver thread can block itself for 60 seconds after sending session close controls and waiting for broker responses

[ https://issues.apache.org/jira/browse/QPID-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8057: - Priority: Minor (was: Major) > [JMS AMQP 0-x][AMQP 0-10] IoReceiver thread can block itself for

[jira] [Commented] (QPID-8057) [JMS AMQP 0-x][AMQP 0-10] IoReceiver thread can block itself for 60 seconds after sending session close controls and waiting for broker responses

[ https://issues.apache.org/jira/browse/QPID-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285971#comment-16285971 ] Keith Wall commented on QPID-8057: -- I think the change made looks reasonable. There is deeper problem

[jira] [Commented] (QPID-8040) [Broker-J] Uncaught java.nio.channels.CancelledKeyException seen during Broker shutdown

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

[jira] [Resolved] (QPID-8031) [Broker-J, System Tests] Bump version of AMQP 0-x client to 6.3.0

[ https://issues.apache.org/jira/browse/QPID-8031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8031. -- Resolution: Fixed > [Broker-J, System Tests] Bump version of AMQP 0-x client to 6.

[jira] [Commented] (QPID-8027) [Broker-J][AMQP 0-8..0-9-1] Receiving BasicAck with unknown tag crashes the broker

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

[jira] [Commented] (QPID-8047) [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown session

[ https://issues.apache.org/jira/browse/QPID-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285906#comment-16285906 ] Keith Wall commented on QPID-8047: -- Looks reasonable to me. Okay for merging,. > [Broker-J][AMQP 0

[jira] [Updated] (QPID-8014) [Broker-J][WMC] Loading of WMC fails on systems with high CPU usage

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

[jira] [Commented] (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:comment-tabpanel=16276770#comment-16276770 ] Keith Wall commented on QPID-7632: -- I wonder if we should apply a similar annotation based idea like we

[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: Future) qpid-java-broker-7.0.1 > [AMQP 0-10] NPE f

[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: - Priority: Minor (was: Major) > [AMQP 0-10] NPE from QueueQuery when queue argument omit

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

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

[jira] [Resolved] (QPID-7942) [Java Broker] AppenderUtilsTest does not work on Windows

[ https://issues.apache.org/jira/browse/QPID-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7942. -- Resolution: Fixed > [Java Broker] AppenderUtilsTest does not work on Wind

[jira] [Updated] (QPID-7942) [Java Broker] AppenderUtilsTest does not work on Windows

[ https://issues.apache.org/jira/browse/QPID-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7942: - Fix Version/s: qpid-java-broker-7.0.0 > [Java Broker] AppenderUtilsTest does not work on Wind

[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: - Fix Version/s: qpid-java-broker-7.0.1 > [Java Broker] Improve detach error message on unsubscribing f

[jira] [Updated] (QPID-8026) [Java Broker] [AMQP 1.0] Add support for max-message-size on consumer attach

[ https://issues.apache.org/jira/browse/QPID-8026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8026: - Fix Version/s: qpid-java-broker-7.1.0 > [Java Broker] [AMQP 1.0] Add support for max-message-s

[jira] [Updated] (QPID-8014) [Broker-J][WMC] Loading of WMC fails on systems with high CPU usage

[ https://issues.apache.org/jira/browse/QPID-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8014: - Fix Version/s: qpid-java-broker-7.0.1 > [Broker-J][WMC] Loading of WMC fails on systems with high

[jira] [Updated] (QPID-8031) [Broker-J, System Tests] Bump version of AMQP 0-x client to 6.3.0

[ https://issues.apache.org/jira/browse/QPID-8031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8031: - Fix Version/s: qpid-java-broker-7.1.0 > [Broker-J, System Tests] Bump version of AMQP 0-x client to 6.

[jira] [Updated] (QPID-8040) [Broker-J] Uncaught java.nio.channels.CancelledKeyException seen during Broker shutdown

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

[jira] [Updated] (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:all-tabpanel ] Keith Wall updated QPID-8017: - Fix Version/s: (was: Future) qpid-java-broker-7.0.1 > [Broker-J] [BDB] JE

[jira] [Updated] (QPID-7996) [Broker-J] Make operations regarding link registry thread safe

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

[jira] [Updated] (QPID-8029) [Broker-J] [AMQP 0-8..0-91] tx.rollback on non-transacted channel should not rollback the channel

[ https://issues.apache.org/jira/browse/QPID-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8029: - Fix Version/s: qpid-java-broker-7.0.1 > [Broker-J] [AMQP 0-8..0-91] tx.rollback on non-transacted chan

[jira] [Updated] (QPID-8036) [Broker-J] [BDB HA] If ReplicationEnvironment fails when creating a node for the first time, clean up any directory left behind by BDB

[ https://issues.apache.org/jira/browse/QPID-8036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8036: - Description: If the {{ReplicatedEnvironment}} constructor fails for a new node, any directory left behind

[jira] [Updated] (QPID-8036) [Broker-J] [BDB HA] If ReplicationEnvironment fails when creating a node for the first time, clean up any directory left behind by BDB

[ https://issues.apache.org/jira/browse/QPID-8036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8036: - Fix Version/s: qpid-java-broker-7.0.1 > [Broker-J] [BDB HA] If ReplicationEnvironment fails when creat

[jira] [Updated] (QPID-8042) [Broker-J][AMQP 1.0] Add support for pipelined connection open containing sasl frames

[ https://issues.apache.org/jira/browse/QPID-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8042: - Fix Version/s: qpid-java-broker-7.0.1 > [Broker-J][AMQP 1.0] Add support for pipelined connection o

[jira] [Comment Edited] (QPID-8047) [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown session

[ https://issues.apache.org/jira/browse/QPID-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276613#comment-16276613 ] Keith Wall edited comment on QPID-8047 at 12/4/17 10:56 AM: Obviously, a well

[jira] [Commented] (QPID-8047) [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown session

[ https://issues.apache.org/jira/browse/QPID-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276613#comment-16276613 ] Keith Wall commented on QPID-8047: -- Does this Broker fail? > [Broker-J][AMQP 0-10] NPE on receiv

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