You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2012/11/26 04:56:57 UTC

[jira] [Created] (CXF-4651) AsyncBaseLifeCycle should be able to return Error MessageExchange if provider threadpool is run out

Freeman Fang created CXF-4651:
---------------------------------

             Summary: AsyncBaseLifeCycle should be able to return Error MessageExchange if provider threadpool is run out 
                 Key: CXF-4651
                 URL: https://issues.apache.org/jira/browse/CXF-4651
             Project: CXF
          Issue Type: Bug
            Reporter: Freeman Fang


currently it just print out an error message and do nothing else, so the consumer side hang to wait and can't know what exactly happen.
Should return an error MessageExchage instead which can inform the client/consumer need adjust the threadpool to get a better throughtput

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CXF-4651) AsyncBaseLifeCycle should be able to return Error MessageExchange if provider threadpool is run out

Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Freeman Fang reassigned CXF-4651:
---------------------------------

    Assignee: Freeman Fang
    
> AsyncBaseLifeCycle should be able to return Error MessageExchange if provider threadpool is run out 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CXF-4651
>                 URL: https://issues.apache.org/jira/browse/CXF-4651
>             Project: CXF
>          Issue Type: Bug
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>
> currently it just print out an error message and do nothing else, so the consumer side hang to wait and can't know what exactly happen.
> Should return an error MessageExchage instead which can inform the client/consumer need adjust the threadpool to get a better throughtput

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira