Details
-
Type: Bug
-
Status: Open
-
Priority: Default
-
Resolution: Unresolved
-
Affects Version/s: 1.5.0
-
Fix Version/s: None
-
Component/s: Engine
-
Labels:None
-
Environment:Windows & Linux.
Description
We set the "ForceResync" to true and "PersistMessages" to false. Attempting connect to a target with a different sequence number, we get a logout message with the expected sequence number and the following is called:
(in Session.java):
private void forceStoreResync(int nextTargetMsgSeqNum, int nextSenderMsgSeqNum )
in that method, a heartbeat message is created for each missing sequence number and it's stored in the Message Store without checking if persisteMessage is true.
Is there a reason for this or this a bug? If it's a bug, I'd suggest this fix:
Line 1601:
- if (actualSenderMsgSeqNum < nextSenderMsgSeqNum) {
+ if (actualSenderMsgSeqNum < nextSenderMsgSeqNum && persistMessages ) {
Thank you.