Should I Catch Exceptions Thrown by boost::asio::io_service::run()?

Catching Exceptions in boost::asio::io_service::run()

In boost::asio, the run() method of the io_service class can throw a boost::system::system_error exception in case of error. Determining whether to handle this exception is crucial for the proper functioning of your application.

Justification for Handling the Exception

The documentation states that exceptions thrown from completion handlers are propagated. Therefore, it is advisable to handle the exception thrown by run() as appropriate for your application.

Recommended Approach

A common approach is to repeatedly call run() until it exits without an error. The following code sample illustrates this approach:

static void m_asio_event_loop(boost::asio::io_service& svc, std::string name) {
    for (;;) {
        try {
            svc.run();
            break; // exited normally
        } catch (std::exception const &e) {
            logger.log(LOG_ERR) << "[eventloop] An unexpected error occurred running " << name << " task: " << e.what();
        } catch (...) {
            logger.log(LOG_ERR) << "[eventloop] An unexpected error occurred running " << name << " task";
        }
    }
}

This code snippet encapsulates the handling of the run() exception within a loop, ensuring that the event loop continues running until it exits without an error. Further documentation on the handling of exceptions in io_service can be found at:

• [Effect of Exceptions Thrown from Handlers](http://www.boost.org/doc/libs/1_61_0/doc/html/boost_asio/reference/io_service.html#boost_asio.reference.io_service.effect_of_exceptions_thrown_from_handlers)

The above is the detailed content of Should I Catch Exceptions Thrown by boost::asio::io_service::run()?. For more information, please follow other related articles on the PHP Chinese website!