epics/pvAccess
0
0
Fork 0
Code Issues Pull Requests Projects Wiki Activity

Don't clear client _outgoingIR on beacon anomaly

Browse Source 
No reason to do this, especially w/o locking.  Outgoing used by
a TCP send thread, beacon anomaly handling on UDP receive thread.

Probably means that anomaly handling never happens...
This commit is contained in:
Michael Davidsaver
2019-05-20 22:37:15 -07:00
parent a6e7d7f5fc
commit 9e05b29f35
1 changed files with 0 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
src/remote/codec.cpp
View File

@@ -1819,7 +1819,6 @@ void BlockingClientTCPTransportCodec::release(pvAccessID clientID) {
}
void BlockingClientTCPTransportCodec::changedTransport() {
_outgoingIR.reset();
}
void BlockingClientTCPTransportCodec::send(ByteBuffer* buffer,