You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2010/02/17 16:19:27 UTC

[jira] Commented: (DIRMINA-765) Calling write(...) sometimes ends up in messageReceived when using SSL filter

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

Emmanuel Lecharny commented on DIRMINA-765:
-------------------------------------------

Can you test with the latest trunk ?

Many problems have been fixed since 2.0.0-RC1.

If you can't build trunk, just push a comment there, I can provide a jar on my home page .

> Calling write(...) sometimes ends up in messageReceived when using SSL filter
> -----------------------------------------------------------------------------
>
>                 Key: DIRMINA-765
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-765
>             Project: MINA
>          Issue Type: Bug
>          Components: Filter
>    Affects Versions: 2.0.0-RC1
>         Environment: Ubuntu 9.10, Sun java 1.6.0
>            Reporter: Linus Zetterlund
>            Priority: Minor
>
> When using the SSL filter, the write(...) call on IoSession will sometimes end up in messageReceived(...) on the IoHandler, before returning from write(...). This behavior was unexpected for us and triggered a deadlock. Is the ExecutorFilter intended to be used to avoid situations like this?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.