qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Rudyy (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-4441) [Java broker] queue declare arguments are lost during v6 schema update for the optional bdbstore
Date Wed, 21 Nov 2012 17:35:58 GMT

     [ https://issues.apache.org/jira/browse/QPID-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alex Rudyy resolved QPID-4441.

    Resolution: Fixed

I reviewed all the changes and Robbie and I worked together on improving the BDB store upgrade
tests to cover the upgrade cases affected by the issue.

The changes to the tests have been committed in the revision http://svn.apache.org/viewvc?view=revision&revision=1412203
> [Java broker] queue declare arguments are lost during v6 schema update for the optional
> ------------------------------------------------------------------------------------------------
>                 Key: QPID-4441
>                 URL: https://issues.apache.org/jira/browse/QPID-4441
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.18
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Blocker
>             Fix For: 0.19
> The queue declare arguments are lost during v5 -> v6 store schema update for the optional
bdbstore. This will present itself in a variety of ways, such as a DLQ losing the marker argument
used to prevent chained DLQ creation, and also in Priority and Sorted queues becoming regular
> As part of the schema update, the old FieldTable binary encoding for the queue arguments
is transitioned to a property within the larger JSON ConfiguredObject encoding. This process
makes use of an intermediate FieldTable to which it does an addAll() based copy of the original
FieldTable and then potentially adds a new description argument. This addAll() fails to copy
the previous properties due to a defect in the method, wherby the source FieldTables lack
of use after creation from encoded bytes means they have yet to be decoded and this is in
effect mistaken as it being an empty FieldTable.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message