is issue is serious : duplicate message or lost message is grave.
> >
> >
>
> ---
> Gary Tully said : Can you try your test scenario with the 5.3 snapshot, I
> think it should
> behave better. There was an issue with the queue cache, i think this
> related
> to https://issues.apache.org/activemq/browse/AMQ-2020
>
> OK, this issue seems resolved with apache-activemq-5.3-SNAPSHOT. I can't
> reproduce it after five tests with the same conditions.
> Thanks
> --
> View this message in context:
> http://www.nabble.com/Duplicate-message-when-HashIndex-table-is-resized-tp23872984p2389.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com
t;
---
Gary Tully said : Can you try your test scenario with the 5.3 snapshot, I
think it should
behave better. There was an issue with the queue cache, i think this related
to https://issues.apache.org/activemq/browse/AMQ-2020
OK, this issue seems resolved w
queue, I can't reproduce the issue.
> and the resized HashIndex is different
> INFO HashIndex - Resize hash bins queue-data_queue#3a#2f#2fM1 from
> 1024 to 2048
> INFO HashIndex - Resize hash bins queue-data_queue#3a#2f#2fM1 from
> 2048 to 4096
>
> Th
HashIndex - Resize hash bins queue-data_queue#3a#2f#2fM1 from
2048 to 4096
This issue is serious : duplicate message or lost message is grave.
--
View this message in context:
http://www.nabble.com/Duplicate-message-when-HashIndex-table-is-resized-tp23872984p23872984.html
Sent from the Ac
