I am trying to make ActiveMQ 5.12 and Wildfly 8.2 work on AWS
I have came up with following configuration:
- two ActiveMQ servers (AMQ1, AMQ2) with static network connectors pointing
to each other.
- one ActiveMQ (AMQW1, AMQW2, ...) server per each Wildfly server (WF1, WF2,
...) with static netwo
It seems to be fixated to the first consumer that had a message? I think
ideally it would be first come first serve.
Setting prefetch=0 doesn’t seem to have any impact. I *kind* of think this
is why the redelivery is set on the client but I might be wrong.
It seems weird to me to set the redeli
If there are multiple consumers, having each consumer reject out-of-order
messages as Art suggested is only going to work if you use message groups,
so take his last paragraph as good general advice but ignore it if you
choose to implement the rest of his suggestions.
But if you're using message g
I believe that setting prefetch=0 only changes how that message gets
dispatched to the first consumer (pull vs. push); once it's there, I
wouldn't expect the broker's behavior w.r.t. that dispatched message to
change (and indeed you say it didn't). But as you say, closing the
connection returns al
I did some more debugging and compared 5.11.1 to 5.12.0. What I noticed is
that 5.11.1 uses v6.MessageIdMarshaller, while 5.12.0 uses v11. Is 5.11.1
supposed to use the v6 version?
v6 doesn't have the line where the error occurs
(info.setTextView(looseUnmarshalString(dataIn));).
Let me know if yo
