camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Handling unsuccessful Session.send in Quickfix component
Date Thu, 03 May 2012 04:05:13 GMT
On Thu, May 3, 2012 at 12:14 AM, Hadrian Zbarcea <> wrote:
> Is there some code you wanted to show that's missing?
> Hadrian

Ah looks like he posted a html mail from Nabble, where the code was
filtered out on our mailing list.

If you click the nabble link you can see the code

I think your proposal makes sense. Please fell free to log a JIRA. And
as we love contributions you are welcome to work on a patch.

And there is a CamelExchangeException that could make sense to use. Or
if quickfix got some better suited exceptions for this scenario.

> On 05/02/2012 11:18 AM, Marek Strejczek wrote:
>> My use case requires to know whether the FIX message was sent successfully
>> to
>> the counterparty or not.
>> Camel-Quickfix doesn't allow me to obtain this information, as it ignores
>> the result of the Session.send invocation.
>> I think about the following solution:
>> replace in QuickfixjConsumer.sendOutMessage:
>> with
>> Of course, QuickFIX/J configuration should include
>> SocketSynchronousWrites=Y
>> in this case, which may decrease throughput but makes the flag returned by
>> Session.send actually mean something.
>> Please let me know if my short analysis above is correct and if the
>> proposed
>> solution is viable. I can work on the patch then.
>> --
>> View this message in context:
>> Sent from the Camel - Users mailing list archive at
> --
> Hadrian Zbarcea
> Principal Software Architect
> Talend, Inc

Claus Ibsen
CamelOne 2012 Conference, May 15-16, 2012:
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message