Problem solved, thanks to Tim's help:
I replaced jms & nested prefixes by nms prefix, and removed one property
that was not supported, and consumer-side configuration now works.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Thanks Tim.
Do you know of any references or examples that include configuration options
for message re-delivery?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
As Christian Posta wrote in the first response, if you (or your load
balancer) are trying to determine the health of the broker by simply
opening a TCP socket to the OpenWire port and then closing it, you're going
to get these warnings in the broker logs.
Unfortunately, I'm not sure there's a grea
I'd suggest you use a JMX viewer such as JConsole, and navigate through the
org.apache.activemq MBeans to find the subscription in question. On the
Attributes page under the subscription, you'll see counts for the number of
messages enqueued and dequeued.
If those don't match, it means your messag
I've never seen that, and I couldn't reproduce it locally on my 5.14.5
installation.
Are there any errors in your broker's logs that indicate that anything is
amiss? And does the problem continue after a broker restart?
What version are you using, and can you share your activemq.xml file so
someo
I searched the 5.14.5 codebase and couldn't find anywhere in the code that
would build a message with that text. Is that an exact quote
(character-for-character), or are you paraphrasing?
Also, please include the version you're using in every question you post.
Tim
On Sat, Apr 7, 2018 at 6:25 AM
Can you add some context please ?
On Fri, Apr 6, 2018 at 12:42 PM alainkr wrote:
> Hello
>
> What could be the cause of DQL for "Duplicate non transacted delivery"
> reason ?
>
> Thanks
>
>
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>
--
Clebert
