...
- Logon/Logout: Every time that a FIX Messaging Client is invoked, it will always send a Logon request before sending the specified request, then send a Logout request when the connection is closed.
- Response not received: If the FIX Messaging Client fails to receive a response, it is most likely for one of the following reasons:
- The message sequence number is out of sync with the AUT: In this case, one fix is to ensure the sequence is reset to start from the beginning on both the FIX Messaging Client and on the AUT.
- The FIX client actually receives a response, but it is invalid according to the FIX data dictionary: If the response is indeed legitimate, you can prevent the FIX Messaging Client from rejecting the response by setting the following in the initiator cfg file:
ValidateIncomingMessage=NRejectInvalidMessage=N
Change Log
1.1
- Use FIX as the default transport for FIX clients (in SOAtest 2026.1 and later)
1.0
- Initial release
Third-Party Content
This extension includes items that have been sourced from third parties as outlined below.
- QuickFIX/J (QuickFIX License)
- Apache Mina (Apache License)
- SLF4J (MIT License)
Additional license details are available in this plugin's licenses folder.