[GitHub] activemq-artemis issue #875: ARTEMIS-550 Add virtual topic support
Github user rlodge commented on the issue: https://github.com/apache/activemq-artemis/pull/875 @mtaylor What I'm hearing is that basically, following changes in 780, a client would be able to send to an address "RecordUpdateNotifications", other clients could subscribe to "RecordUpdateNotifications::SystemARecordUpdateNotifications" and it would act essentially like virtual topics do now; all "RecordUpdateNotifications::*" subscriptions would read from queues coming from the single address? If so, do OpenWire clients need to use a specific queue / address naming scheme, or would it happen automatically somehow (and could it be mapped from the VirtualTopic.* naming scheme)? It's not a terribly large problem for us to go through and change our queues from VirtualTopic.* to a slightly different naming scheme, though we'd rather change nothing about the clients; it would be more difficult to somehow change the API's we were calling... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis issue #875: ARTEMIS-550 Add virtual topic support
Github user rlodge commented on the issue: https://github.com/apache/activemq-artemis/pull/875 @andytaylor We have a single topic, like "VirtualTopic.RecordUpdateNotifications". The system doesn't have a list of who's receiving it; downstream systems subscribe to Queues with the right name pattern and receive the updates. To them, it's like any other Queue. The upstream system and the broker configuration aren't modified when a new consumer comes on line. The key is no server or application configuration to make it work, and also all queue features (especially message groups) being available. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis issue #875: ARTEMIS-550 Add virtual topic support
Github user rlodge commented on the issue: https://github.com/apache/activemq-artemis/pull/875 A discussion on the dev list would at the very least leave those of us who don't subscribe out of the discussion . . . Our use case for virtual topics in ActiveMQ is fairly straightforward: we want to be able to broadcast a message to an unknown number of different subscribers without doing something like camel multiplex on the application end. The consumers must be able to do concurrent processing (multiple consumers) with queue semantics. We need the consumers to be able to create and delete their own subscriptions without restarting the broker or doing any application configuration on our end; the consumers must be able to go offline and come back and find their messages waiting for them; waiting messages can't expire or be thrown away. This probably has to be done with the latest ActiveMQ client library and without code changes. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis issue #875: ARTEMIS-550 Add virtual topic support
Github user rlodge commented on the issue: https://github.com/apache/activemq-artemis/pull/875 @andytaylor I'm not sure what you mean by "implements topic style addressing using queues" --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis issue #875: ARTEMIS-550 Add virtual topic support
Github user rlodge commented on the issue: https://github.com/apache/activemq-artemis/pull/875 @andytaylor How does Artemis provide the same functionality by default (without configuration for each "virtual topic / queue" being added to the broker's configuration)? This is one of the only (maybe the only) feature keeping us from attempting to migrate to Artemis from ActiveMQ. I've looked through the documentation and haven't been able to find a similar feature other than diverts, which seem to need broker configuration and broker restart, which would be a dealbreaker, since our environment requires clients to to be able to dynamically create the queue (not just queue-like) destinations on the fly without broker reconfiguration or restart. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
