[This message was posted by Mahesh Kumaraguru of <[email protected]> to the
"Certification" discussion forum at http://fixprotocol.org/discuss/9. You can
reply to it on-line at http://fixprotocol.org/discuss/read/45b35647 - PLEASE DO
NOT REPLY BY MAIL.]
Your FIX Engine and the broker's FIX Engine must be "in Session" for FIX
Messages to flow. In disconnected condition, messages being sent by your FIX
Engine are ending up in void and not reaching the broker. Neither would ur FIX
Engine receive any messages from broker till the session is reestablished.
To give you a non-FIX example :- I am fast asleep and you are trying to ask me
something without realizing I am asleep, the words come out of your mouth, but
my ear is not listening and since I am asleep, you would not get any reply.
Your FIX Engine monitor / trading application GUI should show you an error
message like "Unable to send message to <broker>, connection is down". Also
check the logs, somewhere an error should be logged unless your FIX Engine is
doing catch(Exception e){ /* Do nothing */ }
> am testing with both the engines broker and initiator... if broker
> engine is turned off initiator is sending messages from MSMQ then how
> the broker simulator will reply for initiator simulator messages..
[You can unsubscribe from this discussion group by sending a message to
mailto:[email protected]]
--
You received this message because you are subscribed to the Google Groups
"Financial Information eXchange" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/fix-protocol?hl=en.
