Home/ Questions/Q 8908083
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T03:05:21+00:00

Given that the boost::asio::ip::tcp::acceptor and boost::asio::ip::tcp::socket are both marked as non-thread safe as of

  • 0

Given that the boost::asio::ip::tcp::acceptor and boost::asio::ip::tcp::socket are both marked as non-thread safe as of Boost 1.52.0, is it possible to shutdown a tcp::acceptor currently blocking on accept() from a separate thread?

I’ve looked at calling boost::asio::io_service::stop() and this looks possible as io_service is thread safe. Would this leave the io_service event loop running until any processing being done on the socket are complete?

I am operating synchronously as this is as simple event loop as part of a bigger program and don’t want to create additional threads without good reason which I understand async will do.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Having spent some time looking into this there is only 1 thread safe manner in which this can be achieved: by sending a message to the socket (on a thread not waiting on accept()) telling the thread to close the socket and the acceptor. By doing this the socket and acceptor can be wholly owned by a single thread.

    As pointed out separately, io_service is only of use for asynchronous operations.

    • 0