Github user mattrpav commented on the issue:
https://github.com/apache/activemq-artemis/pull/1820
Will do
---
Github user mattrpav commented on the issue:
https://github.com/apache/activemq-artemis/pull/1820
@michaelandrepearce the IBM MQ scenario I was referring to was the ability
to use a named queue to back a topic subscription, not cloned subscriptions--
this provides the separation
Github user mattrpav commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/1820#discussion_r164272477
--- Diff:
artemis-jms-client/src/main/java/org/apache/activemq/artemis/jms/client/ActiveMQSession.java
---
@@ -698,8 +699,17 @@ private
Github user mattrpav commented on the issue:
https://github.com/apache/activemq-artemis/pull/1258
I'd suggest that ServiceLocator support would be handy for plugins;
however, it would require another layer of convention as plugin writers would
have to know to build their plugins
Github user mattrpav commented on the issue:
https://github.com/apache/activemq-artemis/pull/875
@graben agreed.
Queue Consumer use cases:
# Connection(s) | # Queue(s) | Option | Desired Behavior
--- | | --- | -
1 | 1
Github user mattrpav commented on the issue:
https://github.com/apache/activemq-artemis/pull/875
@andytaylor its a couple things beyond just shard topic subscriptions (JMS
2.0). #3 being super critical and highly valuable.
1. Using queues instead of durable topic subscribers
Github user mattrpav commented on the issue:
https://github.com/apache/activemq-artemis/pull/875
@graben
re: Transacted: if the PostOffice is transacted by default, that's great.
The option in 5.x felt more like a "shore-up" to get to transacted. I don't see
a
Github user mattrpav commented on the issue:
https://github.com/apache/activemq-artemis/pull/875
I'll detail out the use cases:
1) selectorAware: This allows an interested subscriber to only receive
messages in their queue that match a given selector. This broker pre
Github user mattrpav commented on the issue:
https://github.com/apache/activemq-artemis/pull/875
Has there been mention of the transactedSend and concurrentSend options?
These are super useful for improving reliability and scalability when using
Virtual Topics.
---
If your project
