Modification responses cannot be cached, as their sequence
number is changing -- which leads to cached responses being
dropped.
Change-Id: I3c4037e3a29cff3cdd193865cd98f5df152286f4
Signed-off-by: Robert Varga <rovarga@cisco.com>
private long expectedSequence;
private ReadWriteShardDataTreeTransaction openTransaction;
private long expectedSequence;
private ReadWriteShardDataTreeTransaction openTransaction;
- private ModifyTransactionSuccess cachedModifySuccess;
private DataTreeModification sealedModification;
private ShardDataTreeCohort readyCohort;
private DataTreeModification sealedModification;
private ShardDataTreeCohort readyCohort;
}
private ModifyTransactionSuccess replyModifySuccess(final long sequence) {
}
private ModifyTransactionSuccess replyModifySuccess(final long sequence) {
- if (cachedModifySuccess == null) {
- cachedModifySuccess = new ModifyTransactionSuccess(id, sequence);
- }
-
- return recordSuccess(sequence, cachedModifySuccess);
+ return recordSuccess(sequence, new ModifyTransactionSuccess(id, sequence));
}
private @Nullable TransactionSuccess<?> handleModifyTransaction(final ModifyTransactionRequest request,
}
private @Nullable TransactionSuccess<?> handleModifyTransaction(final ModifyTransactionRequest request,