before an upgrade, take a copy/backup of the data directory that can
be used as a fallback.
On 6 July 2014 12:18, khandelwalanuj wrote:
> But ideally it should be supported.
>
> It may be possible that after switching broker to 5.10, broker or clients
> can face some issues. In such scenerios, we
Patches happily accepted.
Sent from my pressure cooker.
> On Jul 6, 2014, at 5:18, khandelwalanuj wrote:
>
> But ideally it should be supported.
>
> It may be possible that after switching broker to 5.10, broker or clients
> can face some issues. In such scenerios, we revert broker back to 5.8
On 07/06/2014 07:18 AM, khandelwalanuj wrote:
But ideally it should be supported.
It may be possible that after switching broker to 5.10, broker or clients
can face some issues. In such scenerios, we revert broker back to 5.8. It
should be backward compatible.
Thanks,
Anuj
--
View this messa
But ideally it should be supported.
It may be possible that after switching broker to 5.10, broker or clients
can face some issues. In such scenerios, we revert broker back to 5.8. It
should be backward compatible.
Thanks,
Anuj
--
View this message in context:
http://activemq.2283324.n4.nab
On 07/05/2014 07:54 AM, khandelwalanuj wrote:
Hi Gary,
When i switch my broker from 5.8 to 5.10, everything seems to be normal and
works fine. But when I switch back from 5.10 to 5.8, I am seeing issues.
Below are the details of my configuration:
1. Using MultikahaDB.
Configuration:
*
Hi Gary,
When i switch my broker from 5.8 to 5.10, everything seems to be normal and
works fine. But when I switch back from 5.10 to 5.8, I am seeing issues.
Below are the details of my configuration:
1. Using MultikahaDB.
Configuration:
*
That is not good. We try and do auto updates - the test is at
https://github.com/apache/activemq/blob/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/store/kahadb/KahaDBVersionTest.java
I wonder what is different in your store?
You could just rebuild the index, use forceRecoverIndex o
Hi,
I am using ActiveMQ 5.8 and trying to switch to ActiveMQ 5.10. The problem
here is that I have to clear the kahaDB before switch otherwise I get error.
This also happens if I want to switch back from 5.10 to 5.8.
Everytime we need to clear the kahaDB
Error:
"java.io.IOException: Could no
