Home/ Questions/Q 220481
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T18:56:35+00:00

I am currently experiencing a strange problem with the open-source QuickFix engine. Our broker

  • 0

I am currently experiencing a strange problem with the open-source QuickFix engine. Our broker is sending some test trades with MsgType = 8 (Execution Report), and our QuickFix engine immediately replies with an exception saying “Unsupported Message Type”. All of the tags in the broker’s message appear to be legitimate.

Why is this happening and how can I resolve the issue?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I can’t read minds, but it sounds like you may have implemented your application as a MessageCracker but forgotten to override the appropriate onMessage function. Note there is a separate onMessage overload for each FIX version of a message type, e.g. there are:

    onMessage (const FIX40::ExecutionReport&, const FIX::SessionID&) 
onMessage (const FIX41::ExecutionReport&, const FIX::SessionID&) 
onMessage (const FIX42::ExecutionReport&, const FIX::SessionID&) 
onMessage (const FIX43::ExecutionReport&, const FIX::SessionID&) 
onMessage (const FIX44::ExecutionReport&, const FIX::SessionID&)

    The default implementation of all of these methods throws an UnsupportedMessageType exception, which sounds like what you are seeing.

    • 0