Hi guys,
Hopefully you can help me.
I have transactions that were processed and dequeued in 2018. In May 2019 I
restarted the ActiveMQ instance as normal, and after it came up, it somehow
re-added those dequeued messages back into the enqueued queue.
Has this happened to anyone else?
I have
If you don't ack the message the broker doesn't know that the client has
actually tried to consume the message. It will just assume it sat in the
client's buffer and was never actually seen and that doesn't qualify as a
failed delivery.
Justin
On Fri, Jun 7, 2019 at 1:26 AM Bummer wrote:
> Got
It may work as expected, but to my knowledge it's never been tested so it
may not. The NullPointerException you're seeing the master's log file is
more concerning than anything. I'm not sure why that would happen.
Can you reproduce this on 2.9.0 [1]? I'm in the process of releasing 2.9.0
now. The
Hi again:
I looked futher into this issue.
It is strange that, something seems to be wrong with my camel route bundles.
Initially, I was not able to replicate this issue on a different system.
Then, I used my camel routes bundle that was built 2 weeks ago. And, now I
see plenty of connections. I
Hi Justin,
I added all missing parts.
Regarding FS lock, if logs are trustworthy, I can see on the master node:
2019-06-05 08:35:47,492 INFO [org.apache.activemq.artemis.core.server]
AMQ221035: Live Server Obtained live lock
So I'm assuming the lock is working.
On slave I can see:
2019-06-05
