Imported from previous forum
[ original email was from gdavidsohn@aol.com - ]
We have a problem here.
While our client was temporarily down,
an execution report was sent from the exchange
to our FIX engine.
We tried to send the message to our client but
message was rejected because he was down.
Is it compliant with FIX protocol 3.0?
When he subsequently logged back on, the next message he received had the same sequence number as the message which was rejected. How is the client to know that he missed this message?
Does the FIX protocol specify what should be done?
[ original email was from blamoureux@bridge.com - ]
Shouldn’t you have saved the message in your persistent store even if you failed to transmit it and then incremented your sequence number ???
> We have a problem here.
> While our client was temporarily down,
> an execution report was sent from the exchange
> to our FIX engine.
> We tried to send the message to our client but
> message was rejected because he was down.
> Is it compliant with FIX protocol 3.0?
> When he subsequently logged back on, the next message he received had the same sequence number as the message which was rejected. How is the client to know that he missed this message?
> Does the FIX protocol specify what should be done?
>
>
>