[drats_users] [D-RATS] #156: D-RATS doesn't notice dropped connection on Windows until next transmit (was: Ratflector or DRats locks when there is no activity?)

[D-RATS Tracker]

#156: D-RATS doesn't notice dropped connection on Windows until next transmit
------------------------------+---------------------------------------------
 Reporter:  kb1ejh@…          |       Owner:  kk7ds   
     Type:  Bug               |      Status:  accepted
 Priority:  Stability         |   Milestone:          
Component:  General           |     Version:  0.3.1b6 
 Keywords:                    |    Platform:  Windows 
------------------------------+---------------------------------------------
Changes (by kk7ds):

  * status:  new => accepted


Comment:

 Nope, not a lock or hang.  In this case, you became disconnected from the
 ratflector at some point due to a network hiccup or something.  D-RATS
 notices and does its reconnect when it tries to transmit and notices that
 the socket is disconnected.  Your log shows that from your system:

 1830    Sending block: DDT2-: 0:1:1 KB1EJH->CQCQCQ (Ping Request...[12])
 1831    Data path IO error: Socket error: (10054, 'Connection reset by
 peer')
 1832    Attempting reconnect...

 On Linux, a dead socket is noticed immediately and the reconnect is
 triggered.  If I recall correctly, the way Windows handles its sockets
 makes this not behave in the same way.  I'll take a look and see if
 there's some way I can work around this.

-- 
Ticket URL: <http://d-rats.com/trac/ticket/156#comment:1>
D-RATS <http://www.d-rats.com/trac>
D-RATS Development