I need 'get queue semantics (competing consumption across
multiple consumers) out of this subscription'.
Because I have multiple MQTT consumer clients which work in loadbalance, one
of the client consume the message is enough. That is why need to use virtual
topic concept. But I do not know
Github user gaohoward commented on the issue:
https://github.com/apache/activemq-artemis/pull/2041
np at all.
---
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2418
@gemmellr your suggestions are great, i haven't ignored your comments, im
still working on small fix, it is a good idea you suggested to have this
seperated as 2 commits/prs.
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2041
Great ill merge this shortly then. Thanks for the contribution, and sorry
again for taking soo long to review it
---
GitHub user michaelandrepearce opened a pull request:
https://github.com/apache/activemq-artemis/pull/2424
ARTEMIS-2142 Patch Fix ServerJMSMessage for JMSXGROUPSEQ
This is a patch fix for JMSXGROUPSEQ.
You can merge this pull request into a Git repository by running:
$ git
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2418
@gemmellr im closing this, ive split this into two now as you had suggested.
First is the minimal changes needed to fix the immediate issue
Github user michaelandrepearce closed the pull request at:
https://github.com/apache/activemq-artemis/pull/2418
---
Github user michaelandrepearce closed the pull request at:
https://github.com/apache/activemq-artemis/pull/2423
---
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2423
im going to close this, and re-base and re-open once the fixes for group
seq are merged, so its a cleaner PR.
---
Github user gaohoward commented on the issue:
https://github.com/apache/activemq-artemis/pull/2041
@michaelandrepearce Yes that's the idea.
---
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2422
closing this in liue of solution #2423
---
Github user michaelandrepearce closed the pull request at:
https://github.com/apache/activemq-artemis/pull/2422
---
Github user jsmucr commented on the issue:
https://github.com/apache/activemq-artemis/pull/2420
There, it's done. :) The way I had to test the port usage is nasty, sorry
for that. Maybe someone will come up with something a little more
straightforward.
---
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/2420
---
Github user jbertram commented on the issue:
https://github.com/apache/activemq-artemis/pull/2420
Just for the record...I opened a JIRA for this, squashed your commits, and
referenced the JIRA in the commit message. Thanks for the contribution,
@jsmucr!
---
Github user tabish121 commented on the issue:
https://github.com/apache/activemq-artemis/pull/2423
-1
This is actually worse that before because now you've not only violated the
AMQP spec in regards to changing the User ID portion of the properties section
but also opened it
ActiveMQ virtual topic is actually put the message produced by publisher in a
queue, the message will be distributed to multiple consumers evenly who
connect to the queue.
my consumer is using MQTT, but there is no queue concept in MQTT, but only
subscribe/publish concept, then how can MQTT
Are you looking to get queue semantics (competing consumption across
multiple consumers) out of this subscription, or topic semantics (every
consumer gets every message)?
If the later, then you may be able to directly subscribe to the virtual
topic itself, as a regular topic - because it still
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2423
So on the options/ideas i put on the other pr which do you think is the
best.
---
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/2041
---
GitHub user michaelandrepearce opened a pull request:
https://github.com/apache/activemq-artemis/pull/2425
ARTEMIS-2142 Refactor of Patchfix ServerJMSMessage
Refactor ServerJMSMessage so it correctly transposes all JMSX headers
Push common JMSX mappings for JMS to Message
Github user tabish121 commented on the issue:
https://github.com/apache/activemq-artemis/pull/2423
I'd say none of them are really the right way to go. I'd suggest your
organization create a custom broker plugin that does whatever protocol
violating things are acceptable to you and
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/2426
ARTEMIS-2140 queue creation race w/AMQP shared subs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis
23 matches
Mail list logo
