[jira] [Assigned] (QPID-2796) implement support for heartbeats following IO changes to the broker and 0-8/0-9/0-9-1 client
[ https://issues.apache.org/jira/browse/QPID-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned QPID-2796: - Assignee: Rob Godfrey implement support for heartbeats following IO changes to the broker and 0-8/0-9/0-9-1 client Key: QPID-2796 URL: https://issues.apache.org/jira/browse/QPID-2796 Project: Qpid Issue Type: Bug Components: Java Broker, Java Client Affects Versions: 0.15 Reporter: Robbie Gemmell Assignee: Rob Godfrey Fix For: 0.21 The Java broker and client are not able to generate AMQP heartbeats following the updates to their IO layer. The 0-8/0-9/0-9-1 codepaths previously relied on the Mina IO layer to support this, and as such can no longer do so. The 0-10 path of the Java broker leverages much of the 0-10 implementation in common originally developed for the 0-10 Java client, which simply reflects heartbeats it receives from a broker and as such no heartbeats will ever be sent by broker or the client despite its support. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2796) implement support for heartbeats following IO changes to the broker and 0-8/0-9/0-9-1 client
[ https://issues.apache.org/jira/browse/QPID-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-2796: -- Component/s: Java Client implement support for heartbeats following IO changes to the broker and 0-8/0-9/0-9-1 client Key: QPID-2796 URL: https://issues.apache.org/jira/browse/QPID-2796 Project: Qpid Issue Type: Bug Components: Java Broker, Java Client Affects Versions: 0.15 Reporter: Robbie Gemmell Assignee: Rob Godfrey Fix For: 0.21 The Java broker and client are not able to generate AMQP heartbeats following the updates to their IO layer. The 0-8/0-9/0-9-1 codepaths previously relied on the Mina IO layer to support this, and as such can no longer do so. The 0-10 path of the Java broker leverages much of the 0-10 implementation in common originally developed for the 0-10 Java client, which simply reflects heartbeats it receives from a broker and as such no heartbeats will ever be sent by broker or the client despite its support. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4467) base the version number for the maven artefacts on the next release/even version number
Robbie Gemmell created QPID-4467: Summary: base the version number for the maven artefacts on the next release/even version number Key: QPID-4467 URL: https://issues.apache.org/jira/browse/QPID-4467 Project: Qpid Issue Type: Task Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 Currently we generate the maven artefacts based on the development/odd version number (e.g 0.19-SNAPSHOT) on trunk, then change the version number to be based on the release/even version number (e.g. 0.20-SNAPSHOT) when the release branch is created. This should be changed so we always generate the maven artifacts based on the next release version (so trunk will begin generating 0.22-SNAPSHOT releases now, rather than when the branch is created in 3 months). As per discussion in: http://mail-archives.apache.org/mod_mbox/qpid-dev/201211.mbox/%3cCAFitrpRp0-ZG-QSx4aahqfz_xcphZ6HTXoTUfxqPqjo5MAeL=g...@mail.gmail.com%3e -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4468) [Java client] restore ability to enable SSL using a connection level option rather than as a sub-option of each brokerlist entry
Robbie Gemmell created QPID-4468: Summary: [Java client] restore ability to enable SSL using a connection level option rather than as a sub-option of each brokerlist entry Key: QPID-4468 URL: https://issues.apache.org/jira/browse/QPID-4468 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.18, 0.16, 0.14, 0.12, 0.10, 0.8, 0.6 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 On old client versions it was possible to specify that SSL should be used at the connection level options. It is now only possible to specify this as part of the brokerlist sub-options (in addition to much finer-grained control over the keystores/truststores and certificates etc to be used). If you are just using the SSL system properties to define they keystore/truststore etc and have multiple brokers in the brokerlist it is actually more convenient to specify ssl=true at the connection level. Restoring this will maintain compatibility for drop-in replacement of old clients and also help prevent user confiusion resulting from the URL parsers inability to alert them to the previous ssl configuration going unused. It will be restored as an ovveride of ssl option in the brokerlist entries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4469) [Java common] remove unused sslContext parameter from OutgoingNetworkTransport#connect()
Robbie Gemmell created QPID-4469: Summary: [Java common] remove unused sslContext parameter from OutgoingNetworkTransport#connect() Key: QPID-4469 URL: https://issues.apache.org/jira/browse/QPID-4469 Project: Qpid Issue Type: Improvement Components: Java Client, Java Common Affects Versions: 0.18, 0.16, 0.14 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 OutgoingNetworkTransport#connect() takes an sslContext parameter. This is unused by the transport implementations because SSL is implemented in the client as a wrapper over the transport. The 0-10 path of the client supplies null for this arg, but the 08/0-9/0-9-1 patch still creates and supplies one. The parameter should be removed to ensure consistency now and in the future. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4468) [Java client] restore ability to enable SSL using a connection level option rather than as a sub-option of each brokerlist entry
[ https://issues.apache.org/jira/browse/QPID-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503503#comment-13503503 ] Robbie Gemmell commented on QPID-4468: -- Change made in http://svn.apache.org/viewvc?rev=1413364view=rev [Java client] restore ability to enable SSL using a connection level option rather than as a sub-option of each brokerlist entry Key: QPID-4468 URL: https://issues.apache.org/jira/browse/QPID-4468 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.6, 0.8, 0.10, 0.12, 0.14, 0.16, 0.18 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 On old client versions it was possible to specify that SSL should be used at the connection level options. It is now only possible to specify this as part of the brokerlist sub-options (in addition to much finer-grained control over the keystores/truststores and certificates etc to be used). If you are just using the SSL system properties to define they keystore/truststore etc and have multiple brokers in the brokerlist it is actually more convenient to specify ssl=true at the connection level. Restoring this will maintain compatibility for drop-in replacement of old clients and also help prevent user confiusion resulting from the URL parsers inability to alert them to the previous ssl configuration going unused. It will be restored as an ovveride of ssl option in the brokerlist entries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4469) [Java common] remove unused sslContext parameter from OutgoingNetworkTransport#connect()
[ https://issues.apache.org/jira/browse/QPID-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503504#comment-13503504 ] Robbie Gemmell commented on QPID-4469: -- Change made in http://svn.apache.org/viewvc?rev=1413363view=rev [Java common] remove unused sslContext parameter from OutgoingNetworkTransport#connect() Key: QPID-4469 URL: https://issues.apache.org/jira/browse/QPID-4469 Project: Qpid Issue Type: Improvement Components: Java Client, Java Common Affects Versions: 0.14, 0.16, 0.18 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 OutgoingNetworkTransport#connect() takes an sslContext parameter. This is unused by the transport implementations because SSL is implemented in the client as a wrapper over the transport. The 0-10 path of the client supplies null for this arg, but the 08/0-9/0-9-1 patch still creates and supplies one. The parameter should be removed to ensure consistency now and in the future. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4468) [Java client] restore ability to enable SSL using a connection level option rather than as a sub-option of each brokerlist entry
[ https://issues.apache.org/jira/browse/QPID-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-4468. --- Resolution: Fixed The changes look good, though I wonder a little about the override policy, I would think that you would only want to override where the broker list SSL had not been set at all... having ssl turned on for a broker detail where it was explicitly false (or vice versa) seems weird (though really I think any such URL is just a misconfiguration in itself) [Java client] restore ability to enable SSL using a connection level option rather than as a sub-option of each brokerlist entry Key: QPID-4468 URL: https://issues.apache.org/jira/browse/QPID-4468 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.6, 0.8, 0.10, 0.12, 0.14, 0.16, 0.18 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 On old client versions it was possible to specify that SSL should be used at the connection level options. It is now only possible to specify this as part of the brokerlist sub-options (in addition to much finer-grained control over the keystores/truststores and certificates etc to be used). If you are just using the SSL system properties to define they keystore/truststore etc and have multiple brokers in the brokerlist it is actually more convenient to specify ssl=true at the connection level. Restoring this will maintain compatibility for drop-in replacement of old clients and also help prevent user confiusion resulting from the URL parsers inability to alert them to the previous ssl configuration going unused. It will be restored as an ovveride of ssl option in the brokerlist entries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4468) [Java client] restore ability to enable SSL using a connection level option rather than as a sub-option of each brokerlist entry
[ https://issues.apache.org/jira/browse/QPID-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503512#comment-13503512 ] Robbie Gemmell commented on QPID-4468: -- I did consider doing it that way, but it was looking a little messy (the ConnectionSettings cant convey a lack of SSL option, so you then need to start looking at the BrokerDetails object as well, or switch ConnectionSettings to a Boolean to allow conveying null and add a Boolean getter instead of the boolean isUseSSL) and as you say it smacks of misconfiguration a little (I also considered throwing an Exception because of that). As its not really intended to be used together with the brokerlist option, but rather instead of it, in the end I decided just to document the overriding nature and leave it at that. [Java client] restore ability to enable SSL using a connection level option rather than as a sub-option of each brokerlist entry Key: QPID-4468 URL: https://issues.apache.org/jira/browse/QPID-4468 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.6, 0.8, 0.10, 0.12, 0.14, 0.16, 0.18 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 On old client versions it was possible to specify that SSL should be used at the connection level options. It is now only possible to specify this as part of the brokerlist sub-options (in addition to much finer-grained control over the keystores/truststores and certificates etc to be used). If you are just using the SSL system properties to define they keystore/truststore etc and have multiple brokers in the brokerlist it is actually more convenient to specify ssl=true at the connection level. Restoring this will maintain compatibility for drop-in replacement of old clients and also help prevent user confiusion resulting from the URL parsers inability to alert them to the previous ssl configuration going unused. It will be restored as an ovveride of ssl option in the brokerlist entries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-2796) implement support for heartbeats following IO changes to the broker and 0-8/0-9/0-9-1 client
[ https://issues.apache.org/jira/browse/QPID-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503521#comment-13503521 ] Rob Godfrey commented on QPID-2796: --- Added support for sending heartbeats to the Java Broker (all 0-x protocol versions) and Java Client (0-8/9/9-1 protocols). http://svn.apache.org/viewvc?rev=1413376view=rev Will be adding a system test before resolving the JIRA implement support for heartbeats following IO changes to the broker and 0-8/0-9/0-9-1 client Key: QPID-2796 URL: https://issues.apache.org/jira/browse/QPID-2796 Project: Qpid Issue Type: Bug Components: Java Broker, Java Client Affects Versions: 0.15 Reporter: Robbie Gemmell Assignee: Rob Godfrey Fix For: 0.21 The Java broker and client are not able to generate AMQP heartbeats following the updates to their IO layer. The 0-8/0-9/0-9-1 codepaths previously relied on the Mina IO layer to support this, and as such can no longer do so. The 0-10 path of the Java broker leverages much of the 0-10 implementation in common originally developed for the 0-10 Java client, which simply reflects heartbeats it receives from a broker and as such no heartbeats will ever be sent by broker or the client despite its support. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4470) Allow 'maximum queue depth' queue alerting threshold to be set from JMX/AMQP
Keith Wall created QPID-4470:
Summary: Allow 'maximum queue depth' queue alerting threshold to
be set from JMX/AMQP
Key: QPID-4470
URL: https://issues.apache.org/jira/browse/QPID-4470
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Reporter: Keith Wall
Assignee: Keith Wall
Fix For: 0.21
The Java Broker supports four queue alerting thresholds: maximum message count,
maximum message size, maximum message age and maximum queue depth.
It is possible to specify all four of these altering thresholds in the
virtualhost configuration e.g.
{noformat}
maximumMessageCount50/maximumMessageCount
maximumMessageSize2117632/maximumMessageSize
maximumMessageAge60/maximumMessageAge
maximumQueueDepth4235264/maximumQueueDepth
{noformat}
but only the first three are supported by AMQP queue-declare/JMX createNewQueue
(via the queue declare arguments x-qpid-maximum-message-count,
x-qpid-maximum-message-count, x-qpid-maximum-message-age respectively).
The change will add support for x-qpid-maximum-queue-depth.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4470) Allow 'maximum queue depth' queue alerting threshold to be set from JMX/AMQP
[
https://issues.apache.org/jira/browse/QPID-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-4470:
-
Priority: Minor (was: Major)
Allow 'maximum queue depth' queue alerting threshold to be set from JMX/AMQP
Key: QPID-4470
URL: https://issues.apache.org/jira/browse/QPID-4470
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Reporter: Keith Wall
Assignee: Keith Wall
Priority: Minor
Fix For: 0.21
The Java Broker supports four queue alerting thresholds: maximum message
count, maximum message size, maximum message age and maximum queue depth.
It is possible to specify all four of these altering thresholds in the
virtualhost configuration e.g.
{noformat}
maximumMessageCount50/maximumMessageCount
maximumMessageSize2117632/maximumMessageSize
maximumMessageAge60/maximumMessageAge
maximumQueueDepth4235264/maximumQueueDepth
{noformat}
but only the first three are supported by AMQP queue-declare/JMX
createNewQueue (via the queue declare arguments x-qpid-maximum-message-count,
x-qpid-maximum-message-count, x-qpid-maximum-message-age respectively).
The change will add support for x-qpid-maximum-queue-depth.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-2796) implement support for heartbeats following IO changes to the broker and 0-8/0-9/0-9-1 client
[ https://issues.apache.org/jira/browse/QPID-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503541#comment-13503541 ] Robbie Gemmell commented on QPID-2796: -- Changes look good so far. A couple of nitpicks and a posible problem: In the 0-10 Connection class there was a private implementation of TransportActivity added, but it isnt used. The updated connect() call passes null, which looks unsafe at first when following the subsequent method calls in IoNetowrkTransport but ultimately ends up being ok (because we dont set the reader/writer idle times at all on the 0-10 client side and rely on reflecting the brokers heartbeats if any) but possibly means we are doing socket timesouts with no effect. Given the IoReceiver ignores the ticker if it is null, could we just not create one if we arent going to really use it (as happens in the existing but now-unused IoNetworkConnection constructor)? In IdleTimeoutTicker it might be nicer if instead of checking !=0 it used 0 as happens elsewhere. Since IdleTimeoutTicker.tick() is only called when we get a SocketTimeoutException in IoReceiver, doesnt that mean its possible we can be in a writer-idle situation and yet never signal so (if the reader keeps getting data within its timeout, which is twice as long as the senders)? The old 0-8/9/9-1 clients will happily kill the connection in this situation if the broker doenst send them anything. implement support for heartbeats following IO changes to the broker and 0-8/0-9/0-9-1 client Key: QPID-2796 URL: https://issues.apache.org/jira/browse/QPID-2796 Project: Qpid Issue Type: Bug Components: Java Broker, Java Client Affects Versions: 0.15 Reporter: Robbie Gemmell Assignee: Rob Godfrey Fix For: 0.21 The Java broker and client are not able to generate AMQP heartbeats following the updates to their IO layer. The 0-8/0-9/0-9-1 codepaths previously relied on the Mina IO layer to support this, and as such can no longer do so. The 0-10 path of the Java broker leverages much of the 0-10 implementation in common originally developed for the 0-10 Java client, which simply reflects heartbeats it receives from a broker and as such no heartbeats will ever be sent by broker or the client despite its support. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2796) [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client
[ https://issues.apache.org/jira/browse/QPID-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2796: - Summary: [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client (was: implement support for heartbeats following IO changes to the broker and 0-8/0-9/0-9-1 client) [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client -- Key: QPID-2796 URL: https://issues.apache.org/jira/browse/QPID-2796 Project: Qpid Issue Type: Bug Components: Java Broker, Java Client Affects Versions: 0.15 Reporter: Robbie Gemmell Assignee: Rob Godfrey Fix For: 0.21 The Java broker and client are not able to generate AMQP heartbeats following the updates to their IO layer. The 0-8/0-9/0-9-1 codepaths previously relied on the Mina IO layer to support this, and as such can no longer do so. The 0-10 path of the Java broker leverages much of the 0-10 implementation in common originally developed for the 0-10 Java client, which simply reflects heartbeats it receives from a broker and as such no heartbeats will ever be sent by broker or the client despite its support. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4471) Add docbook for producer transaction timeout feature of Java Broker.
Keith Wall created QPID-4471: Summary: Add docbook for producer transaction timeout feature of Java Broker. Key: QPID-4471 URL: https://issues.apache.org/jira/browse/QPID-4471 Project: Qpid Issue Type: Improvement Components: Documentation, Java Broker Reporter: Keith Wall Fix For: 0.21 Add docbook for producer transaction timeout feature of Java Broker. The content is based on existing wiki page https://cwiki.apache.org/qpid/qpid-java-broker-transaction-timeouts.html (which will be marked as deprecated) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-4470) Allow 'maximum queue depth' queue alerting threshold to be set from JMX/AMQP
[
https://issues.apache.org/jira/browse/QPID-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall reassigned QPID-4470:
Assignee: Robbie Gemmell (was: Keith Wall)
Hi Robbie, can you review this commit please?
Allow 'maximum queue depth' queue alerting threshold to be set from JMX/AMQP
Key: QPID-4470
URL: https://issues.apache.org/jira/browse/QPID-4470
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Reporter: Keith Wall
Assignee: Robbie Gemmell
Priority: Minor
Fix For: 0.21
The Java Broker supports four queue alerting thresholds: maximum message
count, maximum message size, maximum message age and maximum queue depth.
It is possible to specify all four of these altering thresholds in the
virtualhost configuration e.g.
{noformat}
maximumMessageCount50/maximumMessageCount
maximumMessageSize2117632/maximumMessageSize
maximumMessageAge60/maximumMessageAge
maximumQueueDepth4235264/maximumQueueDepth
{noformat}
but only the first three are supported by AMQP queue-declare/JMX
createNewQueue (via the queue declare arguments x-qpid-maximum-message-count,
x-qpid-maximum-message-count, x-qpid-maximum-message-age respectively).
The change will add support for x-qpid-maximum-queue-depth.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-4471) Add docbook for producer transaction timeout feature of Java Broker.
[ https://issues.apache.org/jira/browse/QPID-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-4471: Assignee: Keith Wall Add docbook for producer transaction timeout feature of Java Broker. Key: QPID-4471 URL: https://issues.apache.org/jira/browse/QPID-4471 Project: Qpid Issue Type: Improvement Components: Documentation, Java Broker Reporter: Keith Wall Assignee: Keith Wall Fix For: 0.21 Add docbook for producer transaction timeout feature of Java Broker. The content is based on existing wiki page https://cwiki.apache.org/qpid/qpid-java-broker-transaction-timeouts.html (which will be marked as deprecated) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4470) Allow 'maximum queue depth' queue alerting threshold to be set from JMX/AMQP
[
https://issues.apache.org/jira/browse/QPID-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-4470:
-
Status: Ready To Review (was: In Progress)
Allow 'maximum queue depth' queue alerting threshold to be set from JMX/AMQP
Key: QPID-4470
URL: https://issues.apache.org/jira/browse/QPID-4470
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Reporter: Keith Wall
Assignee: Keith Wall
Priority: Minor
Fix For: 0.21
The Java Broker supports four queue alerting thresholds: maximum message
count, maximum message size, maximum message age and maximum queue depth.
It is possible to specify all four of these altering thresholds in the
virtualhost configuration e.g.
{noformat}
maximumMessageCount50/maximumMessageCount
maximumMessageSize2117632/maximumMessageSize
maximumMessageAge60/maximumMessageAge
maximumQueueDepth4235264/maximumQueueDepth
{noformat}
but only the first three are supported by AMQP queue-declare/JMX
createNewQueue (via the queue declare arguments x-qpid-maximum-message-count,
x-qpid-maximum-message-count, x-qpid-maximum-message-age respectively).
The change will add support for x-qpid-maximum-queue-depth.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4471) Add docbook for producer transaction timeout feature of Java Broker.
[ https://issues.apache.org/jira/browse/QPID-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-4471: - Status: Ready To Review (was: In Progress) Add docbook for producer transaction timeout feature of Java Broker. Key: QPID-4471 URL: https://issues.apache.org/jira/browse/QPID-4471 Project: Qpid Issue Type: Improvement Components: Documentation, Java Broker Reporter: Keith Wall Assignee: Keith Wall Fix For: 0.21 Add docbook for producer transaction timeout feature of Java Broker. The content is based on existing wiki page https://cwiki.apache.org/qpid/qpid-java-broker-transaction-timeouts.html (which will be marked as deprecated) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-4471) Add docbook for producer transaction timeout feature of Java Broker.
[ https://issues.apache.org/jira/browse/QPID-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-4471: Assignee: Philip Harvey (was: Keith Wall) Hi Phil, can you review this commit please? Add docbook for producer transaction timeout feature of Java Broker. Key: QPID-4471 URL: https://issues.apache.org/jira/browse/QPID-4471 Project: Qpid Issue Type: Improvement Components: Documentation, Java Broker Reporter: Keith Wall Assignee: Philip Harvey Fix For: 0.21 Add docbook for producer transaction timeout feature of Java Broker. The content is based on existing wiki page https://cwiki.apache.org/qpid/qpid-java-broker-transaction-timeouts.html (which will be marked as deprecated) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4338) Performance tests charting: Support long chart descriptions and allow colour/stroke to be controlled
[ https://issues.apache.org/jira/browse/QPID-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-4338. -- Resolution: Fixed Phil' refactoring committed. I've addressed his comments re the impact of message size chart titles (now clarified as suggested). Phil and I discussed the colour comment and agreed no further action required. Performance tests charting: Support long chart descriptions and allow colour/stroke to be controlled Key: QPID-4338 URL: https://issues.apache.org/jira/browse/QPID-4338 Project: Qpid Issue Type: Improvement Components: Java Tests Reporter: Keith Wall Assignee: Keith Wall Priority: Minor Fix For: 0.19 Attachments: 0001-QPID-4338-Java-Performance-Charts-Renamed-SeriesStok.patch Enhancements to performance chart framework to allow descriptions to be placed on summary html in order to describe fully the parameters of the test (It turns out the existing title and subtitle are not sufficient to describe all the detail you require to properly digest the chart). Also allow the control the series colour/stroke. This will allow us to make sure our baselines series always use the same colour. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPID-4338) Performance tests charting: Support long chart descriptions and allow colour/stroke to be controlled
[ https://issues.apache.org/jira/browse/QPID-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503569#comment-13503569 ] Keith Wall edited comment on QPID-4338 at 11/25/12 10:54 PM: - Phil's refactoring committed. I've addressed his comments re the impact of message size chart titles (now clarified as suggested). Phil and I discussed the colour comment and agreed no further action required. was (Author: k-wall): Phil' refactoring committed. I've addressed his comments re the impact of message size chart titles (now clarified as suggested). Phil and I discussed the colour comment and agreed no further action required. Performance tests charting: Support long chart descriptions and allow colour/stroke to be controlled Key: QPID-4338 URL: https://issues.apache.org/jira/browse/QPID-4338 Project: Qpid Issue Type: Improvement Components: Java Tests Reporter: Keith Wall Assignee: Keith Wall Priority: Minor Fix For: 0.19 Attachments: 0001-QPID-4338-Java-Performance-Charts-Renamed-SeriesStok.patch Enhancements to performance chart framework to allow descriptions to be placed on summary html in order to describe fully the parameters of the test (It turns out the existing title and subtitle are not sufficient to describe all the detail you require to properly digest the chart). Also allow the control the series colour/stroke. This will allow us to make sure our baselines series always use the same colour. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (QPID-4456) update the Java broker-only release package to account for changes in plugin system
[ https://issues.apache.org/jira/browse/QPID-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reopened QPID-4456: -- Assignee: Robbie Gemmell (was: Rob Godfrey) Reopening because I forgot to update the qpid-server.bat file for Windows to also pick up the plugins. update the Java broker-only release package to account for changes in plugin system --- Key: QPID-4456 URL: https://issues.apache.org/jira/browse/QPID-4456 Project: Qpid Issue Type: Task Components: Packaging Affects Versions: 0.19 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Blocker Fix For: 0.20 Following the simplification of the plugin system in the Java broker via QPID-4335 and the modifications to the tests in QPID-4353, the plugins are not being packaged in the broker-only release binary (as per discussion on QPID- just prior to the 0.20 beta). The build system should be updated to account for the changes and ensure the plugins are again included. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4456) update the Java broker-only release package to account for changes in plugin system
[ https://issues.apache.org/jira/browse/QPID-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503573#comment-13503573 ] Robbie Gemmell commented on QPID-4456: -- Updated the windows script and the broker startup example in the documentation: http://svn.apache.org/viewvc?rev=1413444view=rev update the Java broker-only release package to account for changes in plugin system --- Key: QPID-4456 URL: https://issues.apache.org/jira/browse/QPID-4456 Project: Qpid Issue Type: Task Components: Packaging Affects Versions: 0.19 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Blocker Fix For: 0.20 Following the simplification of the plugin system in the Java broker via QPID-4335 and the modifications to the tests in QPID-4353, the plugins are not being packaged in the broker-only release binary (as per discussion on QPID- just prior to the 0.20 beta). The build system should be updated to account for the changes and ensure the plugins are again included. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4456) update the Java broker-only release package to account for changes in plugin system
[ https://issues.apache.org/jira/browse/QPID-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4456: - Status: Ready To Review (was: In Progress) update the Java broker-only release package to account for changes in plugin system --- Key: QPID-4456 URL: https://issues.apache.org/jira/browse/QPID-4456 Project: Qpid Issue Type: Task Components: Packaging Affects Versions: 0.19 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Blocker Fix For: 0.20 Following the simplification of the plugin system in the Java broker via QPID-4335 and the modifications to the tests in QPID-4353, the plugins are not being packaged in the broker-only release binary (as per discussion on QPID- just prior to the 0.20 beta). The build system should be updated to account for the changes and ensure the plugins are again included. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-4456) update the Java broker-only release package to account for changes in plugin system
[ https://issues.apache.org/jira/browse/QPID-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4456: Assignee: Keith Wall (was: Robbie Gemmell) Hi Keith, could you review this change please? update the Java broker-only release package to account for changes in plugin system --- Key: QPID-4456 URL: https://issues.apache.org/jira/browse/QPID-4456 Project: Qpid Issue Type: Task Components: Packaging Affects Versions: 0.19 Reporter: Robbie Gemmell Assignee: Keith Wall Priority: Blocker Fix For: 0.20 Following the simplification of the plugin system in the Java broker via QPID-4335 and the modifications to the tests in QPID-4353, the plugins are not being packaged in the broker-only release binary (as per discussion on QPID- just prior to the 0.20 beta). The build system should be updated to account for the changes and ensure the plugins are again included. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4470) [Java broker] Allow 'maximum queue depth' alerting threshold to be set when declaring queue from JMX/AMQP
[
https://issues.apache.org/jira/browse/QPID-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPID-4470.
--
Resolution: Fixed
Looks good to me
[Java broker] Allow 'maximum queue depth' alerting threshold to be set when
declaring queue from JMX/AMQP
-
Key: QPID-4470
URL: https://issues.apache.org/jira/browse/QPID-4470
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Reporter: Keith Wall
Assignee: Robbie Gemmell
Priority: Minor
Fix For: 0.21
The Java Broker supports four queue alerting thresholds: maximum message
count, maximum message size, maximum message age and maximum queue depth.
It is possible to specify all four of these altering thresholds in the
virtualhost configuration e.g.
{noformat}
maximumMessageCount50/maximumMessageCount
maximumMessageSize2117632/maximumMessageSize
maximumMessageAge60/maximumMessageAge
maximumQueueDepth4235264/maximumQueueDepth
{noformat}
but only the first three are supported by AMQP queue-declare/JMX
createNewQueue (via the queue declare arguments x-qpid-maximum-message-count,
x-qpid-maximum-message-count, x-qpid-maximum-message-age respectively).
The change will add support for x-qpid-maximum-queue-depth.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4470) [Java broker] Allow 'maximum queue depth' alerting threshold to be set when declaring queue from JMX/AMQP
[
https://issues.apache.org/jira/browse/QPID-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-4470:
-
Summary: [Java broker] Allow 'maximum queue depth' alerting threshold to be
set when declaring queue from JMX/AMQP (was: Allow 'maximum queue depth' queue
alerting threshold to be set from JMX/AMQP)
[Java broker] Allow 'maximum queue depth' alerting threshold to be set when
declaring queue from JMX/AMQP
-
Key: QPID-4470
URL: https://issues.apache.org/jira/browse/QPID-4470
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Reporter: Keith Wall
Assignee: Robbie Gemmell
Priority: Minor
Fix For: 0.21
The Java Broker supports four queue alerting thresholds: maximum message
count, maximum message size, maximum message age and maximum queue depth.
It is possible to specify all four of these altering thresholds in the
virtualhost configuration e.g.
{noformat}
maximumMessageCount50/maximumMessageCount
maximumMessageSize2117632/maximumMessageSize
maximumMessageAge60/maximumMessageAge
maximumQueueDepth4235264/maximumQueueDepth
{noformat}
but only the first three are supported by AMQP queue-declare/JMX
createNewQueue (via the queue declare arguments x-qpid-maximum-message-count,
x-qpid-maximum-message-count, x-qpid-maximum-message-age respectively).
The change will add support for x-qpid-maximum-queue-depth.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4467) base the version number for the maven artefacts on the next release/even version number
[ https://issues.apache.org/jira/browse/QPID-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503576#comment-13503576 ] Robbie Gemmell commented on QPID-4467: -- Updated via: http://svn.apache.org/viewvc?rev=1413445view=rev base the version number for the maven artefacts on the next release/even version number --- Key: QPID-4467 URL: https://issues.apache.org/jira/browse/QPID-4467 Project: Qpid Issue Type: Task Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 Currently we generate the maven artefacts based on the development/odd version number (e.g 0.19-SNAPSHOT) on trunk, then change the version number to be based on the release/even version number (e.g. 0.20-SNAPSHOT) when the release branch is created. This should be changed so we always generate the maven artifacts based on the next release version (so trunk will begin generating 0.22-SNAPSHOT releases now, rather than when the branch is created in 3 months). As per discussion in: http://mail-archives.apache.org/mod_mbox/qpid-dev/201211.mbox/%3cCAFitrpRp0-ZG-QSx4aahqfz_xcphZ6HTXoTUfxqPqjo5MAeL=g...@mail.gmail.com%3e -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4467) base the version number for the maven artefacts on the next release/even version number
[ https://issues.apache.org/jira/browse/QPID-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4467: - Status: Ready To Review (was: In Progress) base the version number for the maven artefacts on the next release/even version number --- Key: QPID-4467 URL: https://issues.apache.org/jira/browse/QPID-4467 Project: Qpid Issue Type: Task Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 Currently we generate the maven artefacts based on the development/odd version number (e.g 0.19-SNAPSHOT) on trunk, then change the version number to be based on the release/even version number (e.g. 0.20-SNAPSHOT) when the release branch is created. This should be changed so we always generate the maven artifacts based on the next release version (so trunk will begin generating 0.22-SNAPSHOT releases now, rather than when the branch is created in 3 months). As per discussion in: http://mail-archives.apache.org/mod_mbox/qpid-dev/201211.mbox/%3cCAFitrpRp0-ZG-QSx4aahqfz_xcphZ6HTXoTUfxqPqjo5MAeL=g...@mail.gmail.com%3e -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
