Hi, are you using queues or topic destination? I'm also experiencing it right
now. I'm using topics.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/After-failover-earlier-messages-are-lost-tp4706630p4716097.html
Sent from the ActiveMQ - User mailing list archive at Nabbl
Issue is now resolved!!
I just deleted the shared folder's data and tried again. It worked!!
I'm not sure what was causing the issue though.
I'll look more on "master not getting recognized after a failover" issue and
post my findings.
@Tim: Thanks a lot for replying.
--
View this message i
The persistence I'm referring to can only be set when the message is sent,
so your setDeliveryMode() call is what matters, and the XML setting
shouldn't matter.
Can you confirm that when you send your messages, they go to LevelDB and
are stored?
Also, you've never said whether this is queues or t
I did make sure of persistence both in XML and while sending message
[producer.setDeliveryMode(DeliveryMode.PERSISTENT)].
Its still getting lost after fail-over.
And I observed one more thing, after the fail-over, if I stop the active
broker it does not connect back to reinstated broker.
Flow:
B
Only persistent messages are stored in the persistence store;
non-persistent messages will be lost after a restart no matter what
persistence store you choose. Are you sure your messages are persistent?
If you turn off broker B and repeat your test, what's the behavior?
Tim
On Jan 29, 2016 3:14
Just wanted to add some info:
When it works:
1. I run a publisher java class [master A and slave B are up]
2. Sends messages through master broker A.
3. I run consumer java class to receive the messages which works fine.
When it doesn't:
1. I run a publisher java class [master A and slave B are up
