camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Charles Moulliard <>
Subject Re: Quickfix send/receive messages in both directions
Date Fri, 12 Mar 2010 08:46:02 GMT

Communication with FIX engine is different from a pure client - server
communication. AS mentioned in the documentation the quickfix engine that we
use behind the camel-quickfix endpoint will establish a communication with a
FIX Server and FIX messages will be exchanged regularly (=hearbeat, logon,
logout) to keep the communication alive. So this is not a true socket
channel created between the two partners but a communication channel. To
send messages to FIX server you must use the quickfix-client even if FIX
will provide you feedback on the messages exchanged and to receive from a
FIX server messages (as a client), you to use the other endpoint.

So you can use from(quickfixserver).to(quickfixclient) otherwise you will
resend messages receive through a FIX session to another FIX server with
same sesssion id.

Kind regards
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

blog :
twitter :
Linkedlin :

Apache Camel Group :

On Wed, Mar 10, 2010 at 9:24 PM, grabiarz <> wrote:

> I wanted to use camel and Quickfix combo in my project and I noticed this
> warning (on :
> Warning: You cannot use a quickfix engine to send or receive messages in
> both direction as the FIX protocol handle logon/logout sessions with
> heartbeat messages which are send to verify if the server or client is
> still
> alive in only one direction.
> I'm not quite sure how to understand it as I managed to get camel to
> forward
> a message from one endpoint to another like this:
> from("quickfix-server:server.cfg").to("quickfix-client:client.cfg");
> (Listen for incoming fix messages and then forward them to a different
> system)
> Does the warning mean I would not be able to return an "ACK" type message
> to
> whoever sent a message to my 'server' unless I configured another endpoint
> to point back to them and an endpoint to target system I want to forward
> to?
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message