You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Romain Rossier (JIRA)" <ji...@apache.org> on 2013/09/03 00:20:51 UTC

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

Romain Rossier created DIRMINA-962:
--------------------------------------

             Summary:  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


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 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