Re: KahabDB compatibility issue between ActiveMQ 5.10 and ActiveMQ 5.11

2015-05-18 Thread xabhi
I took some more time out and found that this inconsistency was not because of any change in KahaDB but because of change in physicalName of AnyDestination from 0 to !0. The commit refers to this JIRA issue: https://issues.apache.org/jira/browse/AMQ-5450

Re: KahabDB compatibility issue between ActiveMQ 5.10 and ActiveMQ 5.11

2015-05-15 Thread xabhi
Hi Tim, Did you got a chance to look at this? Thanks, Abhi -- View this message in context: http://activemq.2283324.n4.nabble.com/KahabDB-compatibility-issue-between-ActiveMQ-5-10-and-ActiveMQ-5-11-tp4692008p4696555.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: KahabDB compatibility issue between ActiveMQ 5.10 and ActiveMQ 5.11

2015-05-15 Thread Tim Bain
I haven't, but what I would have done is grabbed the 5.11 code, walked through it from the starting point you referenced till I figured out where the value of 210 came from, then found that code in GitHub and looked at the commit history to see who changed it, when, and why. You're completely

Re: KahabDB compatibility issue between ActiveMQ 5.10 and ActiveMQ 5.11

2015-05-07 Thread xabhi
Hi Tim, I don't have any specific idea as to what changed between the versions but i can point you to the part of code that does it. In my mulitKahaDB adapater configuration I have this entry: amq:filteredKahaDB

Re: KahabDB compatibility issue between ActiveMQ 5.10 and ActiveMQ 5.11

2015-05-06 Thread Tim Bain
I just looked through all the 5.11.x JIRA issues and don't see any that describe this change outright nor any that I would have expected to require making the change. Abhi, did you find the code change that causes the change you describe? If so, can you see if the commit includes the number of

Re: KahabDB compatibility issue between ActiveMQ 5.10 and ActiveMQ 5.11

2015-05-05 Thread Tom_Z
Hi Abhi, thanks for sharing your findings. Did you find any documentation on this problem? Is this change accidental or is there a reason? Tom -- View this message in context:

Re: KahabDB compatibility issue between ActiveMQ 5.10 and ActiveMQ 5.11

2015-04-27 Thread xabhi
ActiveMQ has changed the name of the default persistent adapter from 0 to #210 in ActiveMQ 5.11.1. ActiveMQ v5.11.1 will not read messages from 0 directory as there is no persistence adapter defined for that and hence they are kind of lost. Thanks, Abhi -- View this message in context:

Re: KahabDB compatibility issue between ActiveMQ 5.10 and ActiveMQ 5.11

2015-04-25 Thread Tom_Z
Hi Ahbi, what is the result of your research? Tom -- View this message in context: http://activemq.2283324.n4.nabble.com/KahabDB-compatibility-issue-between-ActiveMQ-5-10-and-ActiveMQ-5-11-tp4692008p4695628.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: KahabDB compatibility issue between ActiveMQ 5.10 and ActiveMQ 5.11

2015-03-02 Thread xabhi
Ping. Can some one please explain any changes in kahadb when moving from ActiveMQ 5.10 to ActiveMQ 5.11? -- View this message in context: http://activemq.2283324.n4.nabble.com/KahabDB-compatibility-issue-between-ActiveMQ-5-10-and-ActiveMQ-5-11-tp4692008p4692323.html Sent from the ActiveMQ -