You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "Jake Farrell (JIRA)" <ji...@apache.org> on 2016/01/06 03:04:39 UTC

[jira] [Updated] (THRIFT-3449) TBaseAsyncProcessor fb.responseReady() never called for oneway functions

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

Jake Farrell updated THRIFT-3449:
---------------------------------
    Fix Version/s:     (was: 0.9.3)
                   0.9.4

> TBaseAsyncProcessor fb.responseReady() never called for oneway functions
> ------------------------------------------------------------------------
>
>                 Key: THRIFT-3449
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3449
>             Project: Thrift
>          Issue Type: Bug
>          Components: Java - Library
>    Affects Versions: 0.9.3
>         Environment: java libthrift-0.9.3
>            Reporter: Jan Sileny
>              Labels: newbie, patch
>             Fix For: 0.9.4
>
>         Attachments: responseReadyPatch.patch
>
>
> For regular service functions, fb.responseReady() is called from generated AsyncProcessFunction's sendResponse(...). Precisely in its result handler's AsyncMethodCallback onComplete or onError implementations. Because oneway methods have void result handler's onComplete and onError implementations, responseReady is not called and frame buffer never goes back to reading state. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)