activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <>
Subject [jira] [Commented] (AMQ-6099) Allow broker to read any OpenWire version from KahaDB
Date Tue, 22 Dec 2015 15:31:46 GMT


Christopher L. Shannon commented on AMQ-6099:

Something like this might work since the assumption is that it is just done until the old
messages are converted and that eventually all messages would be the same version again.

Having to store the version in the index for each type would be necessary for it to handle
different versions indefinitely without there being a performance penalty, but I don't think
there would ever be a need for that.

> Allow broker to read any OpenWire version from KahaDB
> -----------------------------------------------------
>                 Key: AMQ-6099
>                 URL:
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: KahaDB
>    Affects Versions: 5.x
>            Reporter: Tim Bain
> The current KahaDB implementation only allows a single OpenWire version to be read from
the store.  This works fine during normal operations, but when a user upgrades to a version
of ActiveMQ that uses a different OpenWire version, the new broker is unable to read any persisted
messages from the store because of the version mismatch, as described in AMQ-5995.
> Broker upgrades are going to happen, and the requirement that they be done with an empty
message store, or that the user apply temporary workarounds like running the old broker in
a networked configuration that's not the standard config for the cluster, leads to a less-than-satisfactory
experience during the upgrade. As much as possible, broker upgrades should be seamless; sometimes
that's not possible, but in this case it seems like code that would be able to read any version
of OpenWire but only write the current one (and that could be less-efficient with older versions
if necessary) wouldn't be all that hard and would eliminate this problem.

This message was sent by Atlassian JIRA

View raw message