shouldStoreAndForwardMessagesSentWhilstOfflineis exactly the scenario I am trying to reproduce. I have an acceptor and initiator setup a connection and upon successfully connection, the initiator immediately requests a logout. Once that happens my acceptor will request the session again (this time an offline session) and I send a sample execution report to that session. I then reconnect the initiator and the engine will request a replay for me. The sequence numbers up to this point all look right. However, I am running into a "position not aligned to data header" error. It looks like the indexRecord provided has a position that is equivalent to the end of the stream. Any ideas as to what I could be missing? Thanks in advance!
ReplayQueryis able to access the
ReplayIndexRecordthat contains the necessary replay sequence number, but
image.isEndOfStream()being true. Because of this, though the initiator does not receive the replay messages, I can still continue to send new messages with persistent sequence numbers.
We tried upgrading to 0.75 and found a change of behaviour introduced by
There are venues which occasionally put non-numeric data into numeric fields because of poorly setup data, and we were handling this by catching AsciiNumberFormatException and sending 35=3 back
Now it seems there's no way of doing this
If the change can't be reverted - is it possible to introduce another validation flag to allow original behaviour, i.e. throw when trying to parse non-numerical string? Happy to submit patch for that.
MISSING_INTif the length is 0, thus covering that scenario and throwing in other cases.