Log pending messages

[andreydp]

There is a low visibility of a pending messages, e.g. when Session.sendToTarget() is invoked while FIX session is down. Message is only stored to the session storage, and not to the log.

Would like to expect the message to trigger something like onPending callback and be able to see actually assigned sequence number and sending time by the engine in this log.

It may be a major change to the current logging approach so open to discussion first :)

[chrjohn]

Hi @andreydp , I think a callback is the least intrusive way to do this so anyone could decide whether to implement it or not.
However, as a quick workaround you could extend your message store's set method to print that information. Maybe only if the session is not logged on...
Cheers
Chris

[chrjohn]

I don't know what your exact use case is. Maybe it helps to check the messages in the store, e.g. via SessionAdmin MBean, to get an overview of the messages and seqnums.

[andreydp]

The use case is - it's required by the industry to store all messages for 7 years, even not sent to the client. Imagine situation when client disconnects before session end time, but application stil has some pending messages to sent. Then EndTime comes, session is reset and on StartTime those messages are lost.

[chrjohn]

The use case is - it's required by the industry to store all messages for 7 years, even not sent to the client. Imagine situation when client disconnects before session end time, but application stil has some pending messages to sent. Then EndTime comes, session is reset and on StartTime those messages are lost.

Ok, then it has overlaps with #463