[jira] [Resolved] (THRIFT-4729) Crash: ForceClose expired task with Exception uncaught

["James E. King III (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/THRIFT-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James E. King III resolved THRIFT-4729.
---------------------------------------
       Resolution: Fixed
         Assignee: James E. King III
    Fix Version/s: 0.10.0

Recommend trying at least version 0.10.0 and see if you still get that problem, as 0.8.0 is quite old and there have been a number of changes.  There were significant stabilization changes to the concurrency area of the C++ code in 0.10.0 (see THRIFT-3932).

> Crash: ForceClose expired task with Exception uncaught
> ------------------------------------------------------
>
>                 Key: THRIFT-4729
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4729
>             Project: Thrift
>          Issue Type: Bug
>          Components: C++ - Library
>    Affects Versions: 0.8
>            Reporter: KG.Xu
>            Assignee: James E. King III
>            Priority: Major
>             Fix For: 0.10.0
>
>
> Context is: I've employed NonblockingServer & ThreadManager, with setTaskExpireTime() used in my app. Under heavy load, it crashed. Crash point is *forceClose()::throw TException* (to be specific, send(NotificationSocketFD) failed).
>  I went through the code, noted that during *removeExpiredTasks*() there is no try-catch involved. On the contrary, Task::run() is enclosed by try-catch.
> Is it by design, or just a bug ? Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)