Never mind my most recent questions. I found a post where Gary Tully said
that advisory messages should be turned off when the number of brokers gets
into the double digits. We are approaching triple digits so we've decided to
just remove the use of temp queues with request/reply messages and turn
Thanks for the reply but I still not clear on what I will put in my
activemq.xml file for the physicalName attribute of the tempQueue element.
What is in the string that replyQWildcard.getPhysicalName() returns?
I'm not sure why you think I would need two non-duplex networkConnectors but
I have a
Yes, I want to use statically defined queues exclusively. The hub is in NY
and the spokes are all around the world, network outages are not rare and
one of our uses for AMQ is propagating usage data to a central location. As
a result, we have a long expiration on the messages (2 weeks) and want
I just upgraded from 5.5 to 5.10 and got bit by this one too. What a pain. I
am glad to see it is still possible to both restrict dynamically included
destinations and still use temp queues however, I do not understand the unit
test that has been presented as an example of how to do that.
My
Issue can be reproduced without debugger by using thread.sleep in the
listener.
I created a Jira entry: *AMQ-5107* /In-flight queue message redelivered to
multiple listeners upon broker shutdown/
Description lists updated listener code that pauses for one minute during
consumption.
All help is
Final test.
I reproduced this in CentOS 6.0 under Java 1.7.0_09-icedtea and a clean
ActiveMQ 5.9.0 install.
Same steps as before. I issued a Terminate jvm(int) or Stop() command from
Hawtio console to trigger the same behaviour.
I don't get this problem when sending activemq stop from from
/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Mon, Mar 10, 2014 at 2:41 AM, gregg lt;
garlakg@
gt; wrote:
Don't think that is possible because I have a breakpoint in each
consumer.
The delivery counter information was inspected when all consumers were
paused concurrently
!
gtully wrote
Can you share your code?
On 12 Mar 2014 17:40, gregg lt;
garlakg@
gt; wrote:
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Same-message-redelivered-to-multiple-consumers-after-failover-tp4678640p4678922.html
Sent from the ActiveMQ - User mailing
Don't think that is possible because I have a breakpoint in each consumer.
The delivery counter information was inspected when all consumers were
paused concurrently in a debug session during consumption. If I don't set a
breakpoint I still get the same problem.
Would have to do some more
All redelivered messages have the same messageId key and the
redeliveryCounter is incremented for each listener - ending at 3 because
same message got redelivered to 3 listeners.
The problem seems to happen immediately after I terminate the running broker
by sending CTRL-C in the running window.
I have been doing some Master/Slave failover testing and have encountered an
issue.
1) Both Master X and Slave Y broker are pointing to the same kabadb
directory
2) I have one single message on the queue and a listener A actively
processing it (paused). Listeners B,C,D are idle.
3) I shutdown
Christian,
Thanks for a quick response. When you mentioned not supported during
faults, did you mean brokers going down within the network, or consumer
failures during message processing and subsequent session rollbacks? Please
elaborate if possible.
Thanks,
Greg
--
View this message in
Hi,
Can someone please confirm that the current version of ActiveMQ (5.9.0)
continues to only support the JMSXGroupID property strictly in a
Master/Slave configuration?
If this is no longer true, then please provide any network of brokers
configurations that can be used reliably with message
13 matches
Mail list logo
