JQ.
Reputation: 688
udp (boost::asio) read error after async_receive_from
The handler sometimes gives an error after the remote UDP socket closes, the error is --> "No connection could be made because the target machine actively refused it".
My question is: isn't UDP connection-less ? does it care whatever on the remote side ?
btw, I got this on Windows 7.
Upvotes: 1
Views: 569
Answers (1)
Tanner Sansbury
Reputation: 51871
UDP is a connectionless protocol.
The confusing error message is the result of asio having to provide portable errors. Some context is loss when having to go from platform specific errors to portable errors. In this case, asio receives ERROR_PORT_UNREACHABLE and maps it to boost::asio::error::connection_refused.
Upvotes: 3
Related Questions
- boost::asio udp socket read and write
- Boost asio UDP client not receiving data
- boost asio async_receive_from() missing udp frames data retrieval when frames sent consecutive
- boost::asio::udp async response is not entirely received
- Asio UDP socket receive failed
- Boost::Asio Async UDP Server - Unhandled Exception Message
- Boost UDP async_receive_from doesn't wait for timeout or receive
- Boost.Asio UDP async_read_from segmentation fault
- boost asio udp socket async_receive_from does not call the handler
- boost::asio error for UDP async_receive