[
https://issues.apache.org/jira/browse/ASYNCWEB-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee closed ASYNCWEB-32.
-------------------------------
Resolution: Fixed
Fixed. If there is any unexpected exception in the FutureListener, it is
propagated to the waiting response future.
> any unexpected exception in FutureListener.operationComplete() is silently
> swallowed
> ------------------------------------------------------------------------------------
>
> Key: ASYNCWEB-32
> URL: https://issues.apache.org/jira/browse/ASYNCWEB-32
> Project: Asyncweb
> Issue Type: Bug
> Components: Client
> Affects Versions: client-1.0.0
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
>
> Occasionally we see unexpected exceptions happening in
> AsyncHttpClient$FutureListener.operationComplete(). For example,
> Socket.setIntOption() may fail unexpectedly occasionally.
> When they do, the exception from operationComplete() gets caught by Mina's
> default exception monitor. The behavior of this default monitor is to log a
> warning and eat up the exception. As a result, the particular request is
> aborted.
> This has a particularly serious consequence if the caller uses a future to
> wait for the response. Although the request is aborted, the future is never
> completed by anyone. If there is an unexpected exception, the future should
> be immediately completed with the exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
