quickfixj
quickfixj copied to clipboard
Improve disconnect reason when `ResetOnLogon` is not honoured by counter party
trafficstars
This fixes #960 by clarifying the reason for sequence number in response not being 1 when resetOnLogon is configured to true.
As far as I could tell, it isn't necessary to add/amend a unit test for this fix as the disconnect is already tested by SessionTest.testInferResetSeqNumAcceptedWithNonInitialSequenceNumber()