# Responding to Logon conflicts?

**URL:** <https://forum.fixtrading.org/t/responding-to-logon-conflicts/4986>\
**Category:** General Q&A\
**Tags:** general-qa, xid\_167935, imported\
**Created:** [January 14, 2010, 7:31pm UTC](https://forum.fixtrading.org/t/responding-to-logon-conflicts/4986 "2010-01-14T19:31:25Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![russellcurry\_x](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@russellcurry\_x](https://forum.fixtrading.org/u/russellcurry_x)\
**Post date:** [January 14, 2010, 7:31pm UTC](https://forum.fixtrading.org/t/responding-to-logon-conflicts/4986/1 "2010-01-14T19:31:25Z")

</div>

Imported from previous forum

---

<div class="post-metadata">

**Author:** ![russellcurry\_x](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@russellcurry\_x](https://forum.fixtrading.org/u/russellcurry_x)\
**Post date:** [January 14, 2010, 7:31pm UTC](https://forum.fixtrading.org/t/responding-to-logon-conflicts/4986/2 "2010-01-14T19:31:25Z")

</div>

Hi All,

I’m curious as to the correct way a FIX engine should respond to the receipt of a logon from a peer that collides with a session that is already active from a different peer - should the engine send a response message (with a default sequence number) or should the engine simply disconnect with no response to the offending client?

Thanks,

Russ

---

<div class="post-metadata">

**Author:** ![paulraskin\_x](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@paulraskin\_x](https://forum.fixtrading.org/u/paulraskin_x)\
**Post date:** [January 14, 2010, 7:49pm UTC](https://forum.fixtrading.org/t/responding-to-logon-conflicts/4986/3 "2010-01-14T19:49:29Z")

</div>

Hi Russ,

The following is from the FIX.4.4 spec ([http://fixprotocol.org/specifications/FIX.4.4](http://fixprotocol.org/specifications/FIX.4.4), volume 2, page 29):

“If during a Logon one receives a second connection attempt while a valid FIX session is already underway for that same SenderCompID, it is  
recommended that the session acceptor immediately terminate the second connection attempt and not send a Logout message. Sending a Logout  
message runs the risk of interfering with and possibly adversely affecting the current active FIX connection. For example, in some FIX system implementations, sending a Logout message might consume a sequence number that would cause an out of sequence condition for the established FIX session.”

- Paul

> Hi All,
> 
> I’m curious as to the correct way a FIX engine should respond to the  
> receipt of a logon from a peer that collides with a session that is  
> already active from a different peer - should the engine send a response  
> message (with a default sequence number) or should the engine simply  
> disconnect with no response to the offending client?
> 
> Thanks,
> 
> Russ

---

<div class="post-metadata">

**Author:** ![russellcurry\_x](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@russellcurry\_x](https://forum.fixtrading.org/u/russellcurry_x)\
**Post date:** [January 14, 2010, 8:00pm UTC](https://forum.fixtrading.org/t/responding-to-logon-conflicts/4986/4 "2010-01-14T20:00:36Z")

</div>

> Hi Russ,
> 
> The following is from the FIX.4.4 spec  
> ([http://fixprotocol.org/specifications/FIX.4.4](http://fixprotocol.org/specifications/FIX.4.4), volume 2, page 29):
> 
> "If during a Logon one receives a second connection attempt while a  
> valid FIX session is already underway for that same SenderCompID, it is  
> recommended that the session acceptor immediately terminate the second  
> connection attempt and not send a Logout message.

Hi Paul,

Thanks - that’s pretty much what I thought, but I had received an email from someone who wasn’t happy with QuickFix doing that so I was wondering if other engines were doing something different.

It would be nice if FIX included an informational message type that could be used in these situations, e.g. one where the sequencer number was not relevant. It seems there are several situations where receiving a response message would be beneficial to the connecting system.

Cheers,

Russ

---

<div class="post-metadata">

**Author:** ![paulraskin\_x](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@paulraskin\_x](https://forum.fixtrading.org/u/paulraskin_x)\
**Post date:** [January 14, 2010, 8:13pm UTC](https://forum.fixtrading.org/t/responding-to-logon-conflicts/4986/5 "2010-01-14T20:13:50Z")

</div>

> > Hi Russ,
> > 
> > The following is from the FIX.4.4 spec  
> > ([http://fixprotocol.org/specifications/FIX.4.4](http://fixprotocol.org/specifications/FIX.4.4), volume 2, page 29):
> > 
> > "If during a Logon one receives a second connection attempt while a  
> > valid FIX session is already underway for that same SenderCompID, it  
> > is recommended that the session acceptor immediately terminate the  
> > second connection attempt and not send a Logout message.
> 
> Hi Paul,
> 
> Thanks - that’s pretty much what I thought, but I had received an email  
> from someone who wasn’t happy with QuickFix doing that so I was  
> wondering if other engines were doing something different.
> 
> It would be nice if FIX included an informational message type that  
> could be used in these situations, e.g. one where the sequencer number  
> was not relevant. It seems there are several situations where receiving  
> a response message would be beneficial to the connecting system.
> 
> Cheers,
> 
> Russ

I agree wholeheartedly, Russ. It is completely unclear to the third party in this scenario as to why logon messages sent are unanswered. It would be much more helpful in diagnosing the root cause for that party if at least some message were sent, even if it were just an admin-level reject versus a logout message. If the FIX engine were smart enough, it wouldn’t up the sequence number for that session if it were already active when it received another logon request and it decided to send a notification to the third party. Just my two cents.

- Paul

---

<div class="post-metadata">

**Author:** ![chiragpatel29\_x](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@chiragpatel29\_x](https://forum.fixtrading.org/u/chiragpatel29_x)\
**Post date:** [January 14, 2010, 8:22pm UTC](https://forum.fixtrading.org/t/responding-to-logon-conflicts/4986/6 "2010-01-14T20:22:55Z")

</div>

> > > Hi Russ,
> > > 
> > > The following is from the FIX.4.4 spec  
> > > ([http://fixprotocol.org/specifications/FIX.4.4](http://fixprotocol.org/specifications/FIX.4.4), volume 2, page 29):
> > > 
> > > "If during a Logon one receives a second connection attempt while a  
> > > valid FIX session is already underway for that same SenderCompID, it  
> > > is recommended that the session acceptor immediately terminate the  
> > > second connection attempt and not send a Logout message.
> > 
> > Hi Paul,
> > 
> > Thanks - that’s pretty much what I thought, but I had received an  
> > email from someone who wasn’t happy with QuickFix doing that so I was  
> > wondering if other engines were doing something different.
> > 
> > It would be nice if FIX included an informational message type that  
> > could be used in these situations, e.g. one where the sequencer  
> > number was not relevant. It seems there are several situations  
> > where receiving a response message would be beneficial to the  
> > connecting system.
> > 
> > Cheers,
> > 
> > Russ
> 
> I agree wholeheartedly, Russ. It is completely unclear to the third  
> party in this scenario as to why logon messages sent are unanswered. It  
> would be much more helpful in diagnosing the root cause for that party  
> if at least some message were sent, even if it were just an admin-level  
> reject versus a logout message. If the FIX engine were smart enough, it  
> wouldn’t up the sequence number for that session if it were already  
> active when it received another logon request and it decided to send a  
> notification to the third party. Just my two cents.
> 
> - Paul

FIX connectivity may not always be on private lines. If it is an anonymous user/hacker who is trying to connect, it is worth not sending anything back but simply drop the connection request. My 2 cents.

-Chirag

---

<div class="post-metadata">

**Author:** ![jim.northey](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/jim.northey/32/37_2.png) [@jim.northey](https://forum.fixtrading.org/u/jim.northey)\
**Post date:** [January 14, 2010, 8:29pm UTC](https://forum.fixtrading.org/t/responding-to-logon-conflicts/4986/7 "2010-01-14T20:29:56Z")

</div>

> > > > Hi Russ,
> > > > 
> > > > The following is from the FIX.4.4 spec  
> > > > ([http://fixprotocol.org/specifications/FIX.4.4](http://fixprotocol.org/specifications/FIX.4.4), volume 2, page  
> > > > 29):
> > > > 
> > > > "If during a Logon one receives a second connection attempt while  
> > > > a valid FIX session is already underway for that same  
> > > > SenderCompID, it is recommended that the session acceptor  
> > > > immediately terminate the second connection attempt and not send a  
> > > > Logout message.
> > > 
> > > Hi Paul,
> > > 
> > > Thanks - that’s pretty much what I thought, but I had received an  
> > > email from someone who wasn’t happy with QuickFix doing that so I  
> > > was wondering if other engines were doing something different.
> > > 
> > > It would be nice if FIX included an informational message type that  
> > > could be used in these situations, e.g. one where the sequencer  
> > > number was not relevant. It seems there are several situations where  
> > > receiving a response message would be beneficial to the connecting  
> > > system.
> > > 
> > > Cheers,
> > > 
> > > Russ
> > 
> > I agree wholeheartedly, Russ. It is completely unclear to the third  
> > party in this scenario as to why logon messages sent are unanswered.  
> > It would be much more helpful in diagnosing the root cause for that  
> > party if at least some message were sent, even if it were just an admin-  
> > level reject versus a logout message. If the FIX engine were smart  
> > enough, it wouldn’t up the sequence number for that session if it were  
> > already active when it received another logon request and it decided  
> > to send a notification to the third party. Just my two cents.
> > 
> > - Paul
> 
> FIX connectivity may not always be on private lines. If it is an  
> anonymous user/hacker who is trying to connect, it is worth not sending  
> anything back but simply drop the connection request. My 2 cents.
> 
> -Chirag

Chirag- correct we were concerned about denial of service attacks. Modifying to provide a response without consuming a sequence number would be an amelioration to the denial of service impact but is a fairly large change to the protocol.

---

<div class="post-metadata">

**Author:** ![paulraskin\_x](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@paulraskin\_x](https://forum.fixtrading.org/u/paulraskin_x)\
**Post date:** [January 14, 2010, 8:30pm UTC](https://forum.fixtrading.org/t/responding-to-logon-conflicts/4986/8 "2010-01-14T20:30:55Z")

</div>

> > > > Hi Russ,
> > > > 
> > > > The following is from the FIX.4.4 spec  
> > > > ([http://fixprotocol.org/specifications/FIX.4.4](http://fixprotocol.org/specifications/FIX.4.4), volume 2, page  
> > > > 29):
> > > > 
> > > > "If during a Logon one receives a second connection attempt while  
> > > > a valid FIX session is already underway for that same  
> > > > SenderCompID, it is recommended that the session acceptor  
> > > > immediately terminate the second connection attempt and not send a  
> > > > Logout message.
> > > 
> > > Hi Paul,
> > > 
> > > Thanks - that’s pretty much what I thought, but I had received an  
> > > email from someone who wasn’t happy with QuickFix doing that so I  
> > > was wondering if other engines were doing something different.
> > > 
> > > It would be nice if FIX included an informational message type that  
> > > could be used in these situations, e.g. one where the sequencer  
> > > number was not relevant. It seems there are several situations where  
> > > receiving a response message would be beneficial to the connecting  
> > > system.
> > > 
> > > Cheers,
> > > 
> > > Russ
> > 
> > I agree wholeheartedly, Russ. It is completely unclear to the third  
> > party in this scenario as to why logon messages sent are unanswered.  
> > It would be much more helpful in diagnosing the root cause for that  
> > party if at least some message were sent, even if it were just an admin-  
> > level reject versus a logout message. If the FIX engine were smart  
> > enough, it wouldn’t up the sequence number for that session if it were  
> > already active when it received another logon request and it decided  
> > to send a notification to the third party. Just my two cents.
> > 
> > - Paul
> 
> FIX connectivity may not always be on private lines. If it is an  
> anonymous user/hacker who is trying to connect, it is worth not sending  
> anything back but simply drop the connection request. My 2 cents.
> 
> -Chirag

I agree, but if the connection is over a public line, you should probably be using encryption anyway. Otherwise, all the traffic is in plain text. A net-to-net VPN is always nice, but as you said, not always available or practical. I hate to use the ‘C’ word, but this would be great to have as a configurable option so that if you know you’re on a private line you could configure the engine to send a message in response, but if it’s public you could simply drop the connection attempt with no reply. Again, there are plenty of ways to manage privacy, and I certainly don’t have experience with each and every one.

- Paul

---

<div class="post-metadata">

**Author:** ![chiragpatel29\_x](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@chiragpatel29\_x](https://forum.fixtrading.org/u/chiragpatel29_x)\
**Post date:** [January 14, 2010, 8:03pm UTC](https://forum.fixtrading.org/t/responding-to-logon-conflicts/4986/9 "2010-01-14T20:03:01Z")

</div>

I agree with Paul. In my experience with Appia, the acceptor does not respond back to the second initiator but simply disconnects it.

> Hi Russ,
> 
> The following is from the FIX.4.4 spec  
> ([http://fixprotocol.org/specifications/FIX.4.4](http://fixprotocol.org/specifications/FIX.4.4), volume 2, page 29):
> 
> “If during a Logon one receives a second connection attempt while a  
> valid FIX session is already underway for that same SenderCompID, it is  
> recommended that the session acceptor immediately terminate the second  
> connection attempt and not send a Logout message. Sending a Logout  
> message runs the risk of interfering with and possibly adversely  
> affecting the current active FIX connection. For example, in some FIX  
> system implementations, sending a Logout message might consume a  
> sequence number that would cause an out of sequence condition for the  
> established FIX session.”
> 
> - Paul
> 
> > Hi All,
> > 
> > I’m curious as to the correct way a FIX engine should respond to the  
> > receipt of a logon from a peer that collides with a session that is  
> > already active from a different peer - should the engine send a  
> > response message (with a default sequence number) or should the engine  
> > simply disconnect with no response to the offending client?
> > 
> > Thanks,
> > 
> > Russ
