TestRequest (35=1)
The Test Request (1) message forces a heartbeat from the opposing application. The Test Request (1) message checks sequence numbers or verifies communication line status. The opposite application responds to the Test Request (1) with a Heartbeat (0) containing the TestReqID (112).The TestReqID (112) verifies that the opposite application is generating the heartbeat as the result of Test Request (1) and not a normal timeout. The opposite application includes the TestReqID (112) in the resulting Heartbeat (0). Any string can be used as the TestReqID (112) (one suggestion is to use a timestamp string).
Request
Body
required
StandardHeader objectrequired
Must be "FIX.4.4"
Length of the message body in bytes
Message Type
Integer message sequence number
Indicates possible retransmission of message with this sequence number. If a message with this sequence number has been previously received, ignore message; if not, process normally.
See FIX Endpoints for details
See FIX Endpoints for details
Time when the message is being sent out from FIX Gateway
Indicates that message may contain information sent under another sequence number. Forward message to application and determine if previously received (i.e. verify order id and parameters).
Identifier included in Test Request (1) message to be returned in resulting Heartbeat (0)
StandardTrailer objectrequired
Three bytes, simple checksum. Always last field in message
Schema
StandardHeader objectrequired
Must be "FIX.4.4"
Length of the message body in bytes
Message Type
Integer message sequence number
Indicates possible retransmission of message with this sequence number. If a message with this sequence number has been previously received, ignore message; if not, process normally.
See FIX Endpoints for details
See FIX Endpoints for details
Time when the message is being sent out from FIX Gateway
Indicates that message may contain information sent under another sequence number. Forward message to application and determine if previously received (i.e. verify order id and parameters).
Identifier included in Test Request (1) message to be returned in resulting Heartbeat (0)
StandardTrailer objectrequired
Three bytes, simple checksum. Always last field in message