[jira] [Commented] (DIRMINA-962) Immediate session close with a SSL filter

["Emmanuel Lecharny (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DIRMINA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130777#comment-14130777 ] 

Emmanuel Lecharny commented on DIRMINA-962:
-------------------------------------------

Also note that just because the server has close the connection does not mean the enqueued messages should be discarded.

>  Immediate session close with a SSL filter
> ------------------------------------------
>
>                 Key: DIRMINA-962
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-962
>             Project: MINA
>          Issue Type: Bug
>          Components: Filter
>    Affects Versions: 2.0.7
>            Reporter: Romain Rossier
>             Fix For: 2.0.8
>
>
> In the filterClose call in the SSLFilter , we try to write a last message in the queue and we add a listener to only continue to the next filter once that message is written. So when the client is already backed up like crazy and the os buffer is full, doing this is pretty much useless as you have to wait for the entire queue of backed up messages to be consumed and the session just sit there.
> So in that case, i would think that the right behavior would be to clear the queue before to try to write that last ssl close message and even have a timer on the message and if it can not be written in x sec, screw the clean ssl termination just closed the socket.



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