Boost C++ Libraries: Ticket #7392: boost::asio::ip::tcp::socket::is_open returns true even if socket is unusable

anonymous — Sat, 27 Oct 2012 09:17:07 GMT

I also see that behaviour with boost 1.49.0.1 (stock Debian package), but in my case the error from the call to connect failed with error 111: Connection refused

Subsequent call to is_open returns != 0

1902561 [0x7ffff7fc3760] ERROR inverter.Shared_Comms_Inverter1 null - Error while connecting: (111) Connection refused 1902561 [0x7ffff7fc3760] DEBUG inverter.Shared_Comms_Inverter1 null - new state: CMD_DISCONNECTED 1902561 [0x7ffff4d3b700] DEBUG inverter.Shared_Comms_Inverter1.Comms_SharedConnection..Comms_TCP_ASIO null - Already connected

anonymous — Sat, 27 Oct 2012 09:54:59 GMT

Note: In reactive_socket_service_base.hpp Determine whether the socket is open.

bool is_open(const base_implementation_type& impl) const {

return impl.socket_ != invalid_socket;

}

impl.socket_ is "8" in my case

The issue is also present in 1.50 (the latest one in debian)

version changed

anonymous — Sat, 27 Oct 2012 09:56:03 GMT

version Boost 1.51.0 → Boost 1.49.0

status changed; resolution set

chris_kohlhoff — Sat, 29 Dec 2012 10:03:07 GMT

status new → closed
resolution → invalid

A socket is not automatically closed when the connect fails, hence is_open still returns true. This is the intended (and documented) behaviour. You need to check the error code produced by the operation and act on it accordingly.