Page History
...
- On each failed logon attempt the Gateway will:
- First issue an ErrorReport(Subject= VenueLogonError, Text="Venue Logon failed, waiting <RetryInterval>s before retry."), then
- wait RetryInterval seconds (> 0), and repeat.
- Once MaxAttempts (> 0) failed logons occur in a row, the Gateway will:
- First issue an ErrorReport(Subject= VenueLogonError, Text="Venue Logon failed, waiting <BackoffInterval>s before retry."), then
- wait BackoffInterval seconds (>= 0) and restart the cycle.
MarketFactory will apply appropriate values to each of these three properties, based on individual Venue requirements. No Customer involvement is required.
This behaviour applies across all Gateways, irrespective of line protocol, Maker/Taker perspective, or trading model.MarketFactory will apply appropriate values to each of these three properties, based on individual Venue requirements. No Customer involvement is required.
Unless otherwise specified by the venue, the values outlined above will be preset to the following:
Preset | Value |
|---|---|
RetryInterval | 15s |
MaxAttempts | 3 |
BackoffInterval | 30s |
| Tip |
|---|
Should the Client User wish to instruct the Gateway to cease attempting to connect to the Venue at any time during this cycle, then it may issue a UserRequest (UserRequestType=LogOffUser) message. |
...
| Tip |
|---|
| In this event, the Customer should contact MF Support Contact in order to confirm any necessary corrective action. |
...
| Tip |
|---|
| In this event, the Customer should contact MF Support Contact in order to confirm any necessary corrective action. |
...
Whatever the reason, once logged off, it is the Client's responsibility to initiate a new connection via UserRequest (UserRequestType=LogOnUser).
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
...
Prior to the establishment of the venue session, or after it is terminated, any business messages sent by the client will be rejected with an ErrorReport.
| Gliffy Diagram | ||||
|---|---|---|---|---|
|