OK, so I discovered ActiveMQPooledConnectionFactor uses pooled, anonymous
producers, for which advisories are not generated, which explains my issue.
Reference:
https://issues.apache.org/jira/browse/AMQ-4176
http://activemq.apache.org/how-do-i-use-jms-efficiently.html
--
Sent from: http://act
I think you'd probably be better off posting your questions to the Apache
JMeter community as they are all specifically related to JMeter and not
Apache ActiveMQ.
Justin
On Thu, Sep 28, 2017 at 6:50 AM, Juleian wrote:
> Hello everybody,
>
> I used ActiveMQ for a pub/sub system as central topic
Facing the same problem. I had done all possible solutions but still problem
remains unsolved
http://www.menstwilight.com/kamagra.html
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Your configuration looks OK to me. Do you have a reproducible test-case
for this scenario?
Justin
On Fri, Sep 22, 2017 at 3:24 AM, gkocur
wrote:
> Thank you for your reply.
> What you described is exactly what I was expecting - current message count
> close to 0.
> I can see the number of jou
When using network replication between a live and a backup it is extremely
important that the network connection between the two brokers is reliable
because if the network connection dies and there are only those 2 nodes
operating in the cluster then there will be a "split brain" where both the
liv
https://issues.apache.org/jira/browse/AMQ-5290 sounds like it should have
eliminated this issue, but the fact that you're seeing this using MQTT (or
are you using STOMP?) on 5.15.0 means something else is going on.
One question: have you enabled conduitSubscriptions between A and B?
Tim
On Sep 2
Ah, sorry, in my case it was simply because the test message was not marked
as "persistent". Nevermind.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi,
We've just noticed the same behaviour with ActiveMQ 5.15.0 using the default
kahaDb persistence provider.
For example: Using the Web GUI (http://localhost:8161), create a queue named
"test" and send a simple text message to the queue. The message then appears
as "enqueued". Restart the broker
