Re: [Quickfixj-users] QuickfixJ Initiator reconnection policy & SeqNumResets

[t.s. <tru...@cb...>]

Sorry for late reply,

>> There were mentions about 'ReconnectInterval' parameter in the config
>> file; does it mean that the initiator will retry to reconnect
>> indefinitely? Is the mechanism reliable ?
> Yes, it will reconnect indefinitely. And it's reliable as far as I 
> know. What problems were you experiencing?
The first version that i deployed on the remote machine uses only a 
single thread/instance of the initiator. There were complaints from the 
users that the initiator failed to reconnect to third party server in 
several scenarios :
1. connection is broken by the remote server on purpose. (maintenance)
2. internet connection problem (we have a rather spotty infrastructure)
3. unplugging the network cable from the machine. (a bit extreme, i 
know...:)

Because of time constraints, i ended up with the approach i mentioned 
earlier: dropping the whole thread/instance and creating another one 
from scratch as soon as any problem's detected. It's been running OK for 
several weeks now, but it does seem a bit overkill...

> I strongly recommend using the built-in reconnection capabilities instead
> of this approach. It might work to some extent, but the initiators are not
> designed to be used this way.
I see. I will try going back to the single instance approach. Thanks for 
the suggestion. I'll let you know how it goes.

Concerning the sequence number reset thingy, i just got confirmation 
that i'm supposed to send a tag 141=Y value in the logon message via the 
toAdmin() method.
...
   message.setField(new ResetSeqNumFlag(true) );
...

Do i have to do anything else for quickfix/j to negotiate the sequence 
number reset ?

Thanks in advance,
regards,
t.s.