Timeout watchdog using a standby thread
http://codereview.stackexchange.com/questions/84697/timeout-watchdog-using-a-standby-thread
he simple but generic timeout class to be used watching for network connections, user input, filesystem events, and is intended to have a very simple interface specific to only our use cases (i.e. no satisfy-all attitude).
Intended steps to use:
- Construct
- Activate
- Potentially react to a timeout, deactivates itself
- Re-activate
- Destruct cleanly
After triggering the alarm the guard is expected to be inactive until explicitly activated. The code expected to be reasonably tested (that is one of the issues).
This posted code as a testable Visual Studio 2013 project lives on the GitHub.
Besides a general feedback on the code quality - or if, please, please, please, you see a bug, I would love to hear about these areas:
Destruction. Although I did my best to tell the guard thread to end, I am still concerned about having to
join()in the destructor. Generally I love my destructors short and sweet for emergency landings - is it possible here? Is there an STL way to brutally kill that thread?Tests. Existing ones test for intended simple scenarios. I am not sure this is enough to claim that the code works as intended. Is it? I did not find a better way to test timing edge cases. Also, as tests are time-dependant, they occasionally spuriously fail when run on slow VMs. Or are they? Is it sufficient for code like this to know that if tests run somewhere consistently? If I increase timeouts the spurious fails go away, but that lengthens the overall project test run.
Below are the current header, implementation, and tests files to save the GitHub trip.
Header:
#pragma once
namespace utility
{
/**
The `clock` alias is for easy switching to `steady_clock` once Microsoft fixes it
*/
typedef std::chrono::system_clock clock;
/**
The `TimeoutGuard` class triggers the `alarm` callback from the `guard_thread`
if `touch` was not called for at least the `timeout` duration.
Because of the way the `guard_thread` sleeps, the actual detection may happen
as late as after `timeout` + `naptime` duration. Hence it is possible that the alarm
will not be called if the `TimeoutGuard` instance is touched within the
'timeout` and `timeout` + `naptime` timeframe.
If not provided, by default the `naptime` is same as `timeout`.
The `TimeoutGuard` is not active after construction, whicn means, that the
`guard_thread` will block until it is activated by calling the `watch` method.
The `TimeoutGuard` class is not copyable and not moveable.
*/
class TimeoutGuard
{
public:
TimeoutGuard(
clock::duration timeout,
std::function<void( void )> alarm,
clock::duration naptime
);
TimeoutGuard(
clock::duration timeout,
std::function<void( void )> alarm
);
~TimeoutGuard();
TimeoutGuard( const TimeoutGuard & ) = delete;
TimeoutGuard & operator=(const TimeoutGuard & ) = delete;
TimeoutGuard( TimeoutGuard && ) = delete;
TimeoutGuard & operator=( TimeoutGuard && ) = delete;
void watch();
void touch();
private:
void guard();
clock::duration timeout;
clock::duration naptime;
std::function<void( void )> alarm;
std::atomic_bool idle;
std::atomic_bool live;
std::atomic<clock::time_point> touched;
std::thread guard_thread;
std::mutex guard_mutex;
std::condition_variable wakeup;
};
}
Here is the implementation:
#include "stdafx.h"
#include "TimeoutGuard.h"
namespace utility
{
TimeoutGuard::TimeoutGuard(
clock::duration timeout,
std::function<void( void )> alarm,
clock::duration naptime
)
: timeout( timeout )
, alarm( alarm )
, naptime( naptime )
{
idle.store( true );
live.store( true );
guard_thread = std::thread( std::bind( &TimeoutGuard::guard, this ) );
}
TimeoutGuard::TimeoutGuard(
clock::duration timeout,
std::function<void( void )> alarm
)
: TimeoutGuard( timeout, alarm, timeout )
{};
TimeoutGuard::~TimeoutGuard()
{
live.store( false );
wakeup.notify_all();
guard_thread.join();
}
void TimeoutGuard::guard()
{
while ( live.load() )
{
if ( idle.load() )
{
// Sleep indefinitely until either told to become active or destruct
std::unique_lock<std::mutex> live_lock( guard_mutex );
wakeup.wait( live_lock, [this]() { return ! this->idle.load() || ! this->live.load(); } );
};
// quit the loop if destructing
if ( ! live.load() ) break;
// the actual timeout checking
auto now = clock::now();
if ( ( now - touched.load() ) > timeout )
{
idle.store( true );
alarm();
continue; // skip waiting for next timeout
}
{
// sleep until next timeout check or destruction
std::unique_lock<std::mutex> live_lock( guard_mutex );
wakeup.wait_for( live_lock, naptime, [this](){ return ! this->live.load(); } );
}
};
}
void TimeoutGuard::watch()
{
touch();
idle.store( false );
wakeup.notify_all();
}
void TimeoutGuard::touch()
{
touched.store( clock::now() );
}
}
And, finally, existing tests:
#include "stdafx.h"
#include "CppUnitTest.h"
#include "TimeoutGuard.h"
using namespace Microsoft::VisualStudio::CppUnitTestFramework;
namespace utility
{
TEST_CLASS( TimeoutGuardTest )
{
public:
bool triggered = false;
void shoud_trigger()
{
triggered = true;
}
TEST_METHOD( TimeoutGuardExpiration )
{
TimeoutGuard tg{
std::chrono::milliseconds{ 5 },
std::bind( &TimeoutGuardTest::shoud_trigger, this )
};
triggered = false;
tg.watch();
std::this_thread::sleep_for( std::chrono::milliseconds{ 10 } );
Assert::IsTrue( triggered, L"Failed to call the timeout alarm on the first run", LINE_INFO() );
triggered = false;
tg.watch();
std::this_thread::sleep_for( std::chrono::milliseconds{ 10 } );
Assert::IsTrue( triggered, L"Failed to call the timeout alarm on the second run", LINE_INFO() );
}
TEST_METHOD( TimeoutGuardNoAlarm )
{
TimeoutGuard tg{
std::chrono::milliseconds{ 5 },
std::bind( &TimeoutGuardTest::shoud_trigger, this )
};
triggered = false;
tg.watch();
std::this_thread::sleep_for( std::chrono::milliseconds{ 1 } );
Assert::IsFalse( triggered, L"Wrongly called the timeout alarm on the first run", LINE_INFO() );
triggered = false;
tg.watch();
for (auto i = 0; i < 10; ++i)
{
std::this_thread::sleep_for( std::chrono::milliseconds{ 1 } );
tg.touch();
}
Assert::IsFalse( triggered, L"Wrongly called the timeout alarm on the second run", LINE_INFO() );
}
};
}
Timeout watchdog using a standby thread的更多相关文章
- Concurrent.Thread.js
(function(){ if ( !this.Data || (typeof this.Data != 'object' && typeof this.Data != 'functi ...
- 多线程爬坑之路-Thread和Runable源码解析
多线程:(百度百科借一波定义) 多线程(英语:multithreading),是指从软件或者硬件上实现多个线程并发执行的技术.具有多线程能力的计算机因有硬件支持而能够在同一时间执行多于一个线程,进而提 ...
- java中多线程中Runnable接口和Thread类介绍
java中的线程时通过调用操作系统底层的线程来实现线程的功能的. 先看如下代码,并写出输出结果. // 请问输出结果是什么? public static void main(String[] args ...
- Thread的run()与start()的区别
Java的线程是通过java.lang.Thread类来实现的.VM启动时会有一个由主方法所定义的线程.可以通过创建Thread的实例来创建新的线程.每个线程都是通过某个特定Thread对象所对应的方 ...
- Thread类源码剖析
目录 1.引子 2.JVM线程状态 3.Thread常用方法 4.拓展点 一.引子 说来也有些汗颜,搞了几年java,忽然发现竟然没拜读过java.lang.Thread类源码,这次特地拿出来晒一晒. ...
- 从源码解读线程(Thread)和线程池(ThreadPoolExecutor)的状态
线程是比进程更加轻量级的调度执行单位,理解线程是理解并发编程的不可或缺的一部分:而生产过程中不可能永远使用裸线程,需要线程池技术,线程池是管理和调度线程的资源池.因为前不久遇到了一个关于线程状态的问题 ...
- HttpClient throws TaskCanceledException on timeout
error msg: HttpClient throws TaskCanceledException on timeout HttpClient is throwing a TaskCanceledE ...
- java Thread 类的源码阅读(oracle jdk1.8)
java线程类的源码分析阅读技巧: 首先阅读thread类重点关注一下几个问题: 1.start() ,启动一个线程是如何实现的? 2.java线程状态机的变化过程以及如何实现的? 3. 1.star ...
- [Java多线程]-Thread和Runable源码解析
多线程:(百度百科借一波定义) 多线程(英语:multithreading),是指从软件或者硬件上实现多个线程并发执行的技术.具有多线程能力的计算机因有硬件支持而能够在同一时间执行多于一个线程,进而提 ...
随机推荐
- sql server备份
完全备份 declare @device varchar(255),@path varchar(255),@dbname varchar(255)set @dbname='MIS_TEMP'set @ ...
- mybatis sql转义符号
第一种写法:通过<![CDATA[ ]]>符号来写 大于等于:<![CDATA[ >= ]]> 小于等于:<![CDATA[ <= ]]> 例如:sql ...
- sql2008查看备份进度
SELECT session_id, request_id, start_time, status, command, sql_handle --,statement_start_offset, st ...
- MFC之HTTP文件上传
BOOL UploadFile(LPCTSTR strURL, LPCTSTR strLocalFileName) { // 如果URL为空或者文件不存在,直接返回 if (strURL == NUL ...
- 【转】Unity摄像机的使用二:摄像机的切换
http://blog.csdn.net/liujunjie612/article/details/45847877 我们接着上一篇博文继续研究摄像机,这篇我们说下Unity中摄像机的切换,说到切换, ...
- PHP中create_function的用法总结
在php中,函数create_function主要用来创建匿名函数,有时候匿名函数可以发挥它的作用. 1.测试一 测试一主要用来循环替换数组中多个值的<与>,我们用array_map加上c ...
- Mysql实战之主从复制的读写分离
author:JevonWei 版权声明:原创作品 ProxySQL构建主从复制的读写分离 ProxySQL官网及下载地址 http://www.proxysql.com/ 架构角色 mysql-sl ...
- U盘用FAT32还是用NTFS格式好
U盘用FAT32还是用NTFS格式好 ● FAT32文件系统 FAT32使用4个字节(也就是32位)的空间来表示每个扇区(Sector)配置文件的情形,故称之为FAT32.FAT16的分区容量上限是2 ...
- 模块(二)——简单的log日志
简单的log日志 鉴于任何功能模块或系统在调试时都需要日志打印,这里随便写了一下,作为以后代码调试之用,只实现了不同等级的日志输出功能,其他的调试功能以后再行添加:使用方法简单,只需要在头文件里事先按 ...
- CCC2019游记
好吧其实是清华游记,$CCC2019$ 在中国只有北京和天津举办,要选去加拿大的人很少,估计是最近两国关系有点紧张的缘故吧 但实际上是某些已经被清华钦点的人去预览一下他们未来的栖息所 $13:30$ ...