>
>
> You have to remember that the specs are generally written from the
> application developer's standpoint. As a result, application developers
> must assume that for a portable application to work, the below is true.
> NOte that it doesn't say that the client must throw an exception, etc.
> Th
Kevin,
You have to remember that the specs are generally written from the
application developer's standpoint. As a result, application developers
must assume that for a portable application to work, the below is true.
NOte that it doesn't say that the client must throw an exception, etc.
This is
The JMS threading restrictions are here:
https://docs.oracle.com/cd/E19340-01/820-6767/aeqdb/index.html
which basically say if you're using a MessageListener you have to work with
that message/session within the given onMessage function.
However, I don't think that's true WRT ActiveMQ is it?
I
Nevermind! I had a weird bug in my test. Turns out it does exactly what I
expected it to do. New messages aren't dispatched until you call
acknowledge() or commit.. which is just what I want!
KEvin
On Sat, Oct 31, 2015 at 10:49 AM, Kevin Burton wrote:
> I'm finding the documentation for usePr
I'm finding the documentation for usePrefetchExtension to be rather lacking
What exactly does it do?
The documentation says:
> the prefetch extension is used when a message is delivered but not acked,
such that the broker can dispatch another message (e.g., prefetch == 0),
the idea being that th
Notice it would work with a topic subscription and filters. Queues are
different.
-- Clebert Suconic typing on the iPhone.
> On Oct 31, 2015, at 10:43, Tim Bain wrote:
>
> ActiveMQ supports your use case. Artemis apparently does not, though I'd
> love to hear why not. I can't speak for
I would like to see a test working on activemq 5. And we could then figure out
how it was implemented
Last time I checked it was the same. But for someone provide me a working test
I will figure out how it works.
-- Clebert Suconic typing on the iPhone.
> On Oct 31, 2015, at 10:43, Tim B
ActiveMQ supports your use case. Artemis apparently does not, though I'd
love to hear why not. I can't speak for other JMS providers since I
haven't used them; you'd need to investigate them on a case-by-case basis
rather than making the blanket assumption that they don't.
On Oct 31, 2015 8:08 AM
Thank you for your reply.
I already 'redistribution-delay' configuration.
If consumer B connect to Node A, consumer B get all producing messages
produced down time (they remain node A queue). I can't understand this
situation. There is no consistency. Artemis doesn't support message
redistribut
