[
https://issues.apache.org/jira/browse/THRIFT-4962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Geyer resolved THRIFT-4962.
--------------------------------
Fix Version/s: 0.13.0
Resolution: Fixed
> Deadlock in TimerManager::stop
> ------------------------------
>
> Key: THRIFT-4962
> URL: https://issues.apache.org/jira/browse/THRIFT-4962
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.12.0
> Reporter: Guillaume Blanc
> Assignee: Guillaume Blanc
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.13.0
>
> Attachments: test.cpp
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If multiple threads call TimerManager::stop, they will all be waiting on
> monitor for state to go to STOPPED.
> As Dispatcher use monitor_.notify, only one of the thread will be awakened,
> other will stay waiting forever.
> See attached test code to reproduce the issue (timing dependent).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
