Project

General

Profile

Bug #20859

TCPSocket takes a long time to reconnect after kErrorNotRequiringException

Added by Eric Flumerfelt about 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Category:
Known Issues
Target version:
Start date:
09/17/2018
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

Due to a while loop that was checking for sts != kSuccess, when the send operation returned kErrorNotRequiringException, it would continue to try and send Fragment data using the existing connection until a timeout was encountered. The loop as been updated to check sts == kTimeout, which allows the sender to reconnect promptly after a connection issue.

History

#1 Updated by Eric Flumerfelt almost 2 years ago

  • Category set to Known Issues
  • Status changed from Resolved to Closed
  • Assignee set to Eric Flumerfelt
  • Target version set to artdaq v3_03_00


Also available in: Atom PDF