[
https://issues.apache.org/jira/browse/DIRMINA-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531301
]
Trustin Lee commented on DIRMINA-249:
-------------------------------------
Another problem with introducing WriteException is that WriteException has to
be thrown for each subsequent write request to notify all write failures. It
is because WriteException is raised by I/O error and will lead to connection
close. For now, all WriteFutures are notified in the same manner. We should
probably do the same for WriteExceptions in exceptionCaught. WDYT?
> exceptionCaught() should provide more information
> -------------------------------------------------
>
> Key: DIRMINA-249
> URL: https://issues.apache.org/jira/browse/DIRMINA-249
> Project: MINA
> Issue Type: Improvement
> Environment: All
> Reporter: Vinod Panicker
> Fix For: 2.0.0-M1
>
>
> Currently if the application calls a write() on MINA, it will get notified of
> any exceptions via the exceptionCaught() method. The problem is that the
> application does not have any information as to what data could not be
> written on the session. To figure that out, it either has to wait on the
> WriteFuture or implement some state mechanism within the IoSession.
> Trustin recommended that a WriteException could be created, which could
> provide the necessary information. It should have the ByteBuffer for which
> the write() failed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
