I typically find that dynamically including the destinations is a more
flexible approach rather than statically including them (among other
things, you can use wildcards so you don't have to know the names at
configuration time); would that solve the problem you're hitting with the
temp queues? If
No.
In a pub-sub paradigm, neither publishers nor messages know about the
consumers who might or might not eventually consume them. That is, in fact,
exactly the point of pub-sub.
However, ActiveMQ does provide the ability to detect and respond to slow
consumers, and to publish advisory messages
Hello!
I'm using Apache ActiveMQ 5.15.5 and getting the following issue in logs.
Here is my config from activemq.xml
And here are errors
DCRL-COVTXAPP1 2018-09-13 00:59:28,455 WARN [ActiveMQ Transport:
tcp:///10.1.143.193:48753@61616][Transport] Tran
Version 5.8.0 is nearly 6 years old and there have been hundreds (maybe
thousands) of commits since then and one of them could have addressed your
issue even if you didn't find an exact match in Jira. However, no one is
going to remember that far back to see if it is a known issue so you will
just
Hi,Tim
This problem happened twice recently...
I try to use static bridge, it really worded,and solve the problem.but we
steel use temp-queue to use request-reply mode by camel,and this need
translate message between different broke,so I can not use static bridge.
I found another this that, when
