[
https://issues.apache.org/jira/browse/QPID-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499865#comment-13499865
]
Robbie Gemmell edited comment on QPID-4441 at 11/18/12 6:25 PM:
----------------------------------------------------------------
Committed a test and fix for the underlying FieldTable#addAll(..) defect:
http://svn.apache.org/viewvc?view=revision&revision=1410949
Still need to add unit tests to the bdbstore UpgradeFrom5to6Test to verify its
effectiveness (requires first updating the v4 and v5 store schema test data).
was (Author: gemmellr):
Committed a fix for the underlying FieldTable#addAll(..) defect:
http://svn.apache.org/viewvc?view=revision&revision=1410949
Still need to add unit tests to the bdbstore UpgradeFrom5to6Test to verify its
effectiveness (requires first updating the v4 and v5 store schema test data).
> [Java broker] queue declare arguments are lost during v6 schema update for
> the optional bdbstore
> ------------------------------------------------------------------------------------------------
>
> 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 queues.
> 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: [email protected]
For additional commands, e-mail: [email protected]
