boost::asio-async_connect不可取消
boost::asio async_connect is not cancellable?
小故事：socket.async_connect(...)之后的调用socket.cancel()工作良好，即调用完成处理程序；然而，对于CCD_ 4之后的CCD_ 3，从不调用完成处理程序。
长话短说，这里有一个完整的源代码：
#include <iostream>
#include <vector>
#include <chrono>
#include <ctime>
#include <boost/asio.hpp>
namespace sys = boost::system;
namespace asio = boost::asio;
using tcp = asio::ip::tcp;
static const int count = 10;
struct client_t {
using sock_ptr_t = std::unique_ptr<tcp::socket>;
using resolve_results_t = tcp::resolver::results_type;
client_t(asio::io_context& io_context_): io_context{io_context_}, resolver{io_context}{
}
void start() {
tcp::endpoint endpoint(asio::ip::address::from_string("93.184.216.34"), 80);
resolver.async_resolve("www.example.com", "80", [&](auto ec, auto results){
this->on_resolve(ec, results);
});
}
void on_resolve(const sys::error_code& ec, resolve_results_t results) {
auto now = std::chrono::system_clock::now();
time_t tt = std::chrono::system_clock::to_time_t(now);
std::cerr << "on_resolve " << this << " " << ec.message() << ", at " << ctime(&tt);
if (!ec) {
sock = std::make_unique<tcp::socket>(io_context);
/*
sock->async_connect(*results.begin(), [this](auto& ec){
this->on_connect(ec);
});
*/
asio::async_connect(*sock, results.begin(), results.end(), [this](auto& ec, auto it){
this->on_connect(ec);
});
}
}
void on_connect(const sys::error_code& ec) {
auto now = std::chrono::system_clock::now();
time_t tt = std::chrono::system_clock::to_time_t(now);
std::cerr << "on_connect " << this << " " << ec.message() << ", at " << ctime(&tt);
}
void cancel() {
std::cout << "cancellation attempt for " << this << "n";
if (sock) {
sys::error_code ec;
sock->cancel(ec);
std::cout << "cancellation result: " << ec.message() << "n";
}
}
asio::io_context& io_context;
sock_ptr_t sock;
tcp::resolver resolver;
};
using client_ptr_t = std::unique_ptr<client_t>;
using container_t = std::vector<client_ptr_t>;
int main() {
asio::io_context io_context;
std::cerr << "startingn";
container_t container;
for(int i = 0; i < count; ++i) {
auto client = std::make_unique<client_t>(io_context);
client->start();
container.emplace_back(std::move(client));
}
boost::asio::deadline_timer timer(io_context);
timer.expires_from_now(boost::posix_time::milliseconds(5));
timer.async_wait([&](auto& ec){
for(auto& it : container) {
it->cancel();
}
auto now = std::chrono::system_clock::now();
time_t tt = std::chrono::system_clock::to_time_t(now);
std::cout << "cancelled at " << ctime(&tt);
});
io_context.run();
std::cerr << "finishedn";
return 0;
}
输出样本为：
starting
on_resolve 0x985000 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x9854c0 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985600 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985730 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985830 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985700 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985a90 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985bb0 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985cd0 Success, at Sat Oct 26 22:59:22 2019
on_resolve 0x985e80 Success, at Sat Oct 26 22:59:22 2019
cancellation attempt for 0x985000
cancellation result: Success
cancellation attempt for 0x9854c0
cancellation result: Success
cancellation attempt for 0x985600
cancellation result: Success
cancellation attempt for 0x985730
cancellation result: Success
cancellation attempt for 0x985830
cancellation result: Success
cancellation attempt for 0x985700
cancellation result: Success
cancellation attempt for 0x985a90
cancellation result: Success
cancellation attempt for 0x985bb0
cancellation result: Success
cancellation attempt for 0x985cd0
cancellation result: Success
cancellation attempt for 0x985e80
cancellation result: Success
cancelled at Sat Oct 26 22:59:22 2019
(我必须按ctrl+c键才能停止程序(。
然而，如果我使用sock->async_connect(...)(上面代码中注释的部分(，一切都很好，即
starting
on_resolve 0x6d6000 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d64c0 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6600 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6730 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6830 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6700 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6a90 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6bb0 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6cd0 Success, at Sat Oct 26 22:59:03 2019
on_resolve 0x6d6e80 Success, at Sat Oct 26 22:59:03 2019
cancellation attempt for 0x6d6000
cancellation result: Success
cancellation attempt for 0x6d64c0
cancellation result: Success
cancellation attempt for 0x6d6600
cancellation result: Success
cancellation attempt for 0x6d6730
cancellation result: Success
cancellation attempt for 0x6d6830
cancellation result: Success
cancellation attempt for 0x6d6700
cancellation result: Success
cancellation attempt for 0x6d6a90
cancellation result: Success
cancellation attempt for 0x6d6bb0
cancellation result: Success
cancellation attempt for 0x6d6cd0
cancellation result: Success
cancellation attempt for 0x6d6e80
cancellation result: Success
cancelled at Sat Oct 26 22:59:03 2019
on_connect 0x6d6000 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d64c0 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6600 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6730 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6830 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6700 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6a90 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6bb0 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6cd0 Operation canceled, at Sat Oct 26 22:59:03 2019
on_connect 0x6d6e80 Operation canceled, at Sat Oct 26 22:59:03 2019
finished
为什么会这样？我已经阅读了文档，没有发现任何迹象表明我做错了什么。
如文档中所述，asio::async_connect
。。。尝试将套接字连接到一系列端点中的一个。。。为序列中的每个端点一次，直到成功建立连接。
如果提供了多个端点，取消一次未完成的连接尝试将导致asio::async_connect从后续端点重试(这是循环(。
取消后尝试close套接字。这将阻止asio::async_connect重试。
sock->cancel(ec);
sock->close(ec);
相关文章：
- CMake:我们可以为一组不形成可执行文件或库的特定文件指定包含目录吗?
- 在清除 istream 之前，我不应该需要取消获取它吗？
- 命名空间 std:: 不包含可选
- 为什么结构化绑定不支持可变数组?
- std::remove(） 按预期处理文字，但不能与取消引用的迭代器一起工作
- RXCPP：创建一个不关心可观察量输入类型的扩展
- 对于实际指针类型，用于检测类似指针(可取消引用）类型的模板函数失败
- 在 Spirit X3 中使用布尔属性而不是可选属性
- 防御性地应用 std::move 到平凡可复制的类型是否不可取
- 使命令不产生可执行文件
- 我可以定义一个(键入的）常数，该常数确定不占据可执行文件中的空间
- GDB错误不以可执行格式:未识别的文件格式
- 为什么*_leastN_t和*_fastN_t类型是必需的，而不是可选的
- "make"的输出是一个共享对象，而不是可执行文件
- 运算符重载：简单添加...错误 C2677：二进制"+"：未找到采用类型 ___ 的全局运算符(或者不存在可接受的转换)
- 在 Visual C++ 系统调用的路径中找不到可执行文件
- Eclipse Ubuntu 中的“程序不是可识别的可执行文件”错误
- 数组迭代器不是可取消引用的错误
- 迭代器不是可取消引用的堆栈(表达式树)和循环无法正常工作
- 列出迭代器而不是可取消引用的运行时
