[jira] [Commented] (QPID-5429) Java Broker does not always write the reason it cannot start-up to qpid.log
[ https://issues.apache.org/jira/browse/QPID-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867623#comment-13867623 ] ASF subversion and git services commented on QPID-5429: --- Commit 1557052 from [~k-wall] in branch 'qpid/trunk' [ https://svn.apache.org/r1557052 ] QPID-5429: [Java Broker] Exceptions causing startup failure now written to qpid.log too Previously, such exceptions were only written to stderr. This change means that they written to qpid.log too, allowing configuration problems etc to be understood by refering to the one file. Java Broker does not always write the reason it cannot start-up to qpid.log --- Key: QPID-5429 URL: https://issues.apache.org/jira/browse/QPID-5429 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Keith Wall Priority: Minor If the Java Broker is unable to complete its start-up, for example, because a port it requires is already bound, it writes the exception to standard out. The error message is not however written to the qpid.log. This makes diagnosing startup issues more problematic. This is especially so for users who have embedded Qpid within other products (containers, job control systems etc), where the plumbing of the standard streams is often misconfigured. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5429) Java Broker does not always write the reason it cannot start-up to qpid.log
[ https://issues.apache.org/jira/browse/QPID-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-5429: Assignee: Andrew MacBean Andrew, could you review this commit please? Java Broker does not always write the reason it cannot start-up to qpid.log --- Key: QPID-5429 URL: https://issues.apache.org/jira/browse/QPID-5429 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Keith Wall Assignee: Andrew MacBean Priority: Minor If the Java Broker is unable to complete its start-up, for example, because a port it requires is already bound, it writes the exception to standard out. The error message is not however written to the qpid.log. This makes diagnosing startup issues more problematic. This is especially so for users who have embedded Qpid within other products (containers, job control systems etc), where the plumbing of the standard streams is often misconfigured. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5429) Java Broker does not always write the reason it cannot start-up to qpid.log
[ https://issues.apache.org/jira/browse/QPID-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867665#comment-13867665 ] Andrew MacBean commented on QPID-5429: -- Looks good to me. Java Broker does not always write the reason it cannot start-up to qpid.log --- Key: QPID-5429 URL: https://issues.apache.org/jira/browse/QPID-5429 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Keith Wall Assignee: Andrew MacBean Priority: Minor If the Java Broker is unable to complete its start-up, for example, because a port it requires is already bound, it writes the exception to standard out. The error message is not however written to the qpid.log. This makes diagnosing startup issues more problematic. This is especially so for users who have embedded Qpid within other products (containers, job control systems etc), where the plumbing of the standard streams is often misconfigured. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5429) Java Broker does not always write the reason it cannot start-up to qpid.log
[ https://issues.apache.org/jira/browse/QPID-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5429. -- Resolution: Fixed Fix Version/s: 0.27 Java Broker does not always write the reason it cannot start-up to qpid.log --- Key: QPID-5429 URL: https://issues.apache.org/jira/browse/QPID-5429 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Keith Wall Assignee: Andrew MacBean Priority: Minor Fix For: 0.27 If the Java Broker is unable to complete its start-up, for example, because a port it requires is already bound, it writes the exception to standard out. The error message is not however written to the qpid.log. This makes diagnosing startup issues more problematic. This is especially so for users who have embedded Qpid within other products (containers, job control systems etc), where the plumbing of the standard streams is often misconfigured. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5461) [Java Broker] Downgrade the severity of broker log messages like java.io.IOException: Connection reset by peer for 0-8/9/9-1 connections
Robbie Gemmell created QPID-5461: Summary: [Java Broker] Downgrade the severity of broker log messages like java.io.IOException: Connection reset by peer for 0-8/9/9-1 connections Key: QPID-5461 URL: https://issues.apache.org/jira/browse/QPID-5461 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.26 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.27 Downgrade the severity of broker log messages like java.io.IOException: Connection reset by peer for 0-8/9/9-1 connections. These exceptions are currently logged at error level which often leads to confusion, as whilst they may indicate unexpected behaviour for a client they typically do not represent an issue with the broker and so really shouldnt be error messages. The broker separately logs closure of the connection, so these exception logs will be downgraded to info level. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5462) [Java Broker] investigate logging of IOExceptions for 0-10 connections
Robbie Gemmell created QPID-5462: Summary: [Java Broker] investigate logging of IOExceptions for 0-10 connections Key: QPID-5462 URL: https://issues.apache.org/jira/browse/QPID-5462 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Robbie Gemmell While undertaking QPID-5461, I wasn't able to identify an equivalent set of logging for the 01-0 connection handling, investigate this. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5461) [Java Broker] Downgrade the severity of broker log messages like java.io.IOException: Connection reset by peer for 0-8/9/9-1 connections
[ https://issues.apache.org/jira/browse/QPID-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867976#comment-13867976 ] ASF subversion and git services commented on QPID-5461: --- Commit 1557184 from [~gemmellr] in branch 'qpid/trunk' [ https://svn.apache.org/r1557184 ] QPID-5461: downgrade sevrity of IOException log messages. Fix wording of those messages [Java Broker] Downgrade the severity of broker log messages like java.io.IOException: Connection reset by peer for 0-8/9/9-1 connections Key: QPID-5461 URL: https://issues.apache.org/jira/browse/QPID-5461 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.26 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.27 Downgrade the severity of broker log messages like java.io.IOException: Connection reset by peer for 0-8/9/9-1 connections. These exceptions are currently logged at error level which often leads to confusion, as whilst they may indicate unexpected behaviour for a client they typically do not represent an issue with the broker and so really shouldnt be error messages. The broker separately logs closure of the connection, so these exception logs will be downgraded to info level. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5463) [AMQP 1.0] assume delete-on-close if dynamic flag is set an no lifetime policy supplied
Gordon Sim created QPID-5463: Summary: [AMQP 1.0] assume delete-on-close if dynamic flag is set an no lifetime policy supplied Key: QPID-5463 URL: https://issues.apache.org/jira/browse/QPID-5463 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5463) [AMQP 1.0] assume auto-delete if dynamic flag is set and no lifetime policy supplied
[ https://issues.apache.org/jira/browse/QPID-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-5463: - Summary: [AMQP 1.0] assume auto-delete if dynamic flag is set and no lifetime policy supplied (was: [AMQP 1.0] assume delete-on-close if dynamic flag is set an no lifetime policy supplied) [AMQP 1.0] assume auto-delete if dynamic flag is set and no lifetime policy supplied Key: QPID-5463 URL: https://issues.apache.org/jira/browse/QPID-5463 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5464) [linearstore] Incompletely created journal files accumulate in EFP
Kim van der Riet created QPID-5464: -- Summary: [linearstore] Incompletely created journal files accumulate in EFP Key: QPID-5464 URL: https://issues.apache.org/jira/browse/QPID-5464 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: Kim van der Riet Assignee: Kim van der Riet Priority: Minor In tests which kill the broker during operation or in situations where the broker is rudely interrupted while creating new journal files, incomplete journal files of incorrect size accumulate in the empty file pools. The code precludes these files from being used, but they are not deleted either, so they sit indefinitely in the EFP directories tying up disk resources. These files should: 1. be moved into a separate directory if they are shown to be non-empty (for possible forensic analysis), or 2. deleted if they are empty, freeing up disk resources. This check should probably happen on broker/linearstore startup, as this is when unused journal files are repatriated to their EFPs. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5465) [C++ Messaging Client] A scheme to change default AMQP protocol version
Chuck Rolke created QPID-5465: - Summary: [C++ Messaging Client] A scheme to change default AMQP protocol version Key: QPID-5465 URL: https://issues.apache.org/jira/browse/QPID-5465 Project: Qpid Issue Type: Improvement Components: C++ Client Affects Versions: 0.27 Environment: Any client Reporter: Chuck Rolke Current qpid client connections are Amqp version 0.10 unless a connection option is given. This issue provides a method to specify a different default protocol version. I have an application where I'd like to default to amqp1.0 unless the user specifies otherwise. The code to effect this would be much simpler if the messaging client library could be loaded with a default other than amqp0.10. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5466) Dispatch - Add different forwarding semantics for addresses
Ted Ross created QPID-5466: -- Summary: Dispatch - Add different forwarding semantics for addresses Key: QPID-5466 URL: https://issues.apache.org/jira/browse/QPID-5466 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross (For version 0.2) At present, if there are multiple receivers for a particular address, Dispatch delivers a copy of each message to all of the receivers. This feature adds the ability to by-configuration deliver messages to only one of those receivers. The configuration for this feature is per-address and defines two settings: - _fanout_ is either Multiple or Single (and a placeholder for Group). Multiple fanout means all subscribers receive each message. Single fanout means that only one subscriber receives the message. - _bias_ controls how single-fanout is treated. The following values for bias are provided: - Closest - each message is delivered to the closest/least-cost subscriber. - Spread - messages are spread indeterminately across all subscribers. - Latency - (not implemented yet) Messages are delivered in a balanced way to all subscribers based on the latency of acknowledgements. This mode attempts to keep all subscribers equally fed with incoming messages. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5466) Dispatch - Add different forwarding semantics for addresses
[ https://issues.apache.org/jira/browse/QPID-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated QPID-5466: --- Description: (For version 0.2) At present, if there are multiple receivers for a particular address, Dispatch delivers a copy of each message to all of the receivers. This feature adds the ability to by-configuration deliver messages to only one of those receivers. The configuration for this feature is per-address and defines two settings: - _fanout_ is either Multiple or Single (and a placeholder for Group). Multiple fanout means all subscribers receive each message. Single fanout means that only one subscriber receives the message. - _bias_ controls how single-fanout is treated. The following values for bias are provided: -- _Closest_ - each message is delivered to the closest/least-cost subscriber. -- _Spread_ - messages are spread indeterminately across all subscribers. -- _Latency_ - (not implemented yet) Messages are delivered in a balanced way to all subscribers based on the latency of acknowledgements. This mode attempts to keep all subscribers equally fed with incoming messages. was: (For version 0.2) At present, if there are multiple receivers for a particular address, Dispatch delivers a copy of each message to all of the receivers. This feature adds the ability to by-configuration deliver messages to only one of those receivers. The configuration for this feature is per-address and defines two settings: - _fanout_ is either Multiple or Single (and a placeholder for Group). Multiple fanout means all subscribers receive each message. Single fanout means that only one subscriber receives the message. - _bias_ controls how single-fanout is treated. The following values for bias are provided: - Closest - each message is delivered to the closest/least-cost subscriber. - Spread - messages are spread indeterminately across all subscribers. - Latency - (not implemented yet) Messages are delivered in a balanced way to all subscribers based on the latency of acknowledgements. This mode attempts to keep all subscribers equally fed with incoming messages. Dispatch - Add different forwarding semantics for addresses --- Key: QPID-5466 URL: https://issues.apache.org/jira/browse/QPID-5466 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross (For version 0.2) At present, if there are multiple receivers for a particular address, Dispatch delivers a copy of each message to all of the receivers. This feature adds the ability to by-configuration deliver messages to only one of those receivers. The configuration for this feature is per-address and defines two settings: - _fanout_ is either Multiple or Single (and a placeholder for Group). Multiple fanout means all subscribers receive each message. Single fanout means that only one subscriber receives the message. - _bias_ controls how single-fanout is treated. The following values for bias are provided: -- _Closest_ - each message is delivered to the closest/least-cost subscriber. -- _Spread_ - messages are spread indeterminately across all subscribers. -- _Latency_ - (not implemented yet) Messages are delivered in a balanced way to all subscribers based on the latency of acknowledgements. This mode attempts to keep all subscribers equally fed with incoming messages. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5466) Dispatch - Add different forwarding semantics for addresses
[ https://issues.apache.org/jira/browse/QPID-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868308#comment-13868308 ] ASF subversion and git services commented on QPID-5466: --- Commit 1557260 from [~tedross] in branch 'dispatch/trunk' [ https://svn.apache.org/r1557260 ] QPID-5466 - Added configuration for address semantics by prefix - Implemented Multiple/Single fanout with Closest and Spread biases - Added tests for the above - Added a new set of system tests using a network of two routers Dispatch - Add different forwarding semantics for addresses --- Key: QPID-5466 URL: https://issues.apache.org/jira/browse/QPID-5466 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross (For version 0.2) At present, if there are multiple receivers for a particular address, Dispatch delivers a copy of each message to all of the receivers. This feature adds the ability to by-configuration deliver messages to only one of those receivers. The configuration for this feature is per-address and defines two settings: - _fanout_ is either Multiple or Single (and a placeholder for Group). Multiple fanout means all subscribers receive each message. Single fanout means that only one subscriber receives the message. - _bias_ controls how single-fanout is treated. The following values for bias are provided: -- _Closest_ - each message is delivered to the closest/least-cost subscriber. -- _Spread_ - messages are spread indeterminately across all subscribers. -- _Latency_ - (not implemented yet) Messages are delivered in a balanced way to all subscribers based on the latency of acknowledgements. This mode attempts to keep all subscribers equally fed with incoming messages. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5463) [AMQP 1.0] assume auto-delete if dynamic flag is set and no lifetime policy supplied
[ https://issues.apache.org/jira/browse/QPID-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868312#comment-13868312 ] ASF subversion and git services commented on QPID-5463: --- Commit 1557262 from [~gsim] in branch 'qpid/trunk' [ https://svn.apache.org/r1557262 ] QPID-5463: make dynamic nodes auto deleted by default [AMQP 1.0] assume auto-delete if dynamic flag is set and no lifetime policy supplied Key: QPID-5463 URL: https://issues.apache.org/jira/browse/QPID-5463 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5463) [AMQP 1.0] assume auto-delete if dynamic flag is set and no lifetime policy supplied
[ https://issues.apache.org/jira/browse/QPID-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-5463. -- Resolution: Fixed [AMQP 1.0] assume auto-delete if dynamic flag is set and no lifetime policy supplied Key: QPID-5463 URL: https://issues.apache.org/jira/browse/QPID-5463 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5467) [AMQP 1.0] delete-on-closed not handled correctly
Gordon Sim created QPID-5467: Summary: [AMQP 1.0] delete-on-closed not handled correctly Key: QPID-5467 URL: https://issues.apache.org/jira/browse/QPID-5467 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 If there is an exception e.g. in processing the filter for a queue created with lifetime-policy delete-on-close, then the queue is not released from use. Also, if two links specify delete-on-close for the same queue then the second will cause an assertion in the broker. Only the link that created the queue should attempt to set itself as the controlling user. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5467) [AMQP 1.0] delete-on-closed not handled correctly
[ https://issues.apache.org/jira/browse/QPID-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868401#comment-13868401 ] ASF subversion and git services commented on QPID-5467: --- Commit 1557272 from [~gsim] in branch 'qpid/trunk' [ https://svn.apache.org/r1557272 ] QPID-5467: fix handling of delete-on-close [AMQP 1.0] delete-on-closed not handled correctly - Key: QPID-5467 URL: https://issues.apache.org/jira/browse/QPID-5467 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 If there is an exception e.g. in processing the filter for a queue created with lifetime-policy delete-on-close, then the queue is not released from use. Also, if two links specify delete-on-close for the same queue then the second will cause an assertion in the broker. Only the link that created the queue should attempt to set itself as the controlling user. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5467) [AMQP 1.0] delete-on-closed not handled correctly
[ https://issues.apache.org/jira/browse/QPID-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-5467. -- Resolution: Fixed [AMQP 1.0] delete-on-closed not handled correctly - Key: QPID-5467 URL: https://issues.apache.org/jira/browse/QPID-5467 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 If there is an exception e.g. in processing the filter for a queue created with lifetime-policy delete-on-close, then the queue is not released from use. Also, if two links specify delete-on-close for the same queue then the second will cause an assertion in the broker. Only the link that created the queue should attempt to set itself as the controlling user. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5468) [AMQP 1.0] delete-if-unused doesn't work for initial sender
Gordon Sim created QPID-5468: Summary: [AMQP 1.0] delete-if-unused doesn't work for initial sender Key: QPID-5468 URL: https://issues.apache.org/jira/browse/QPID-5468 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 if a queue is created by establishing a sender to it, and delete-if-unused is specified, the queue is not deleted when the sender exits (even when no other links to it exist, i.e. it is unused). -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5469) [AMQP 1.0] don't override autodeletion if implied by topic policy
Gordon Sim created QPID-5469: Summary: [AMQP 1.0] don't override autodeletion if implied by topic policy Key: QPID-5469 URL: https://issues.apache.org/jira/browse/QPID-5469 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 AT present the autodelete setting of a subscription queue is always inferred from the durability and reliability of the link. However if the topic policy specifies autodeletion, links should not be able to override this. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5468) [AMQP 1.0] delete-if-unused doesn't work for initial sender
[ https://issues.apache.org/jira/browse/QPID-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868450#comment-13868450 ] ASF subversion and git services commented on QPID-5468: --- Commit 1557279 from [~gsim] in branch 'qpid/trunk' [ https://svn.apache.org/r1557279 ] QPID-5468: fix handling of delete-if-unused for sending links [AMQP 1.0] delete-if-unused doesn't work for initial sender --- Key: QPID-5468 URL: https://issues.apache.org/jira/browse/QPID-5468 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 if a queue is created by establishing a sender to it, and delete-if-unused is specified, the queue is not deleted when the sender exits (even when no other links to it exist, i.e. it is unused). -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5469) [AMQP 1.0] don't override autodeletion if implied by topic policy
[ https://issues.apache.org/jira/browse/QPID-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868451#comment-13868451 ] ASF subversion and git services commented on QPID-5469: --- Commit 1557280 from [~gsim] in branch 'qpid/trunk' [ https://svn.apache.org/r1557280 ] QPID-5469: link should not override a topic policy specifying autodeletion [AMQP 1.0] don't override autodeletion if implied by topic policy - Key: QPID-5469 URL: https://issues.apache.org/jira/browse/QPID-5469 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 AT present the autodelete setting of a subscription queue is always inferred from the durability and reliability of the link. However if the topic policy specifies autodeletion, links should not be able to override this. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5469) [AMQP 1.0] don't override autodeletion if implied by topic policy
[ https://issues.apache.org/jira/browse/QPID-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-5469. -- Resolution: Fixed [AMQP 1.0] don't override autodeletion if implied by topic policy - Key: QPID-5469 URL: https://issues.apache.org/jira/browse/QPID-5469 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 AT present the autodelete setting of a subscription queue is always inferred from the durability and reliability of the link. However if the topic policy specifies autodeletion, links should not be able to override this. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5468) [AMQP 1.0] delete-if-unused doesn't work for initial sender
[ https://issues.apache.org/jira/browse/QPID-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-5468. -- Resolution: Fixed [AMQP 1.0] delete-if-unused doesn't work for initial sender --- Key: QPID-5468 URL: https://issues.apache.org/jira/browse/QPID-5468 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 if a queue is created by establishing a sender to it, and delete-if-unused is specified, the queue is not deleted when the sender exits (even when no other links to it exist, i.e. it is unused). -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
