The ErrorReport is a custom, user-defined, message used by the Whisperer Feed Handler to notify the Client of any erroneous scenarios that are encountered during operation. In some circumstances these may be regarded as informational, but usually they will require some action by the Client so must not be ignored.
Since there are scenarios where ErrorReport messages may not be delivered (e.g. during session abort sequences), these messages are persisted and will be delivered on re connection.
ErrorReports may be triggered as a result of Client-side or Venue-side issues.
From Client
- At an invalid lifecycle phase (e.g. QuoteRequest sent before the connection to the Maker Venue is established, or after the Whisperer Feed Handler has disconnected from the Venue).
- Message is not supported by the Venue (e.g. sending a Quote to a Maker Venue).
- Message contains invalid data.
From Venue
- A FIX Reject or BusinessMessageReject message
Client
Venue
Client Message Validation
Whisperer performs message validation in order to ensure that is is always able to construct a well-formed Venue message. Should the client omit the population of a required field, or populate it with an unsupported value, then Whisperer cannot translate the message correctly, and it will not be sent to the Venue.
Validation Errors should never occur in Production
In the event that a Client message fails Whisperer validation checks, it is entirely the Client's responsibility to ensure that Venue state is managed correctly as a result of this error. For Production systems, MarketFactory recommends that the Client disconnect immediately, so that the necessary corrective action may be taken.
Venue
Venue Message Validation
It is sometimes possible that a Venue may send unsupported messages to the Client once connected. For example, an ECN end-user may make a request for an unsupported product type. Whisperer ensure that the Client is always informed of these events by emitting an ErrorReport containing the full message details.
Overview
Content Tools