> I believe that Jaybird 2.1.3 does not have a read timeout configured, so it will block indefinitely if it does not receive a reply. Roman could probably tell you more.

My assumption is that it has something to do with a deadlock...

As to the socket timeout configuration, this is very experimental stuff
done on request of one of the company, but so far no experience about
how the whole system would behave when a read timeout occurs (there is
no specific error handling for this case there). The good thing about
this is that by default it is switched off and it does not influence
normal work of the driver.

Roman