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

Cloudor Pu edited comment on DIRMINA-1120 at 1/13/20 2:02 AM:
--------------------------------------------------------------

It's true I should make sure that the filters I'm using are thread-safe and I 
found the ProtocolCodecFilter was thread-safe before version 2.1.1 but some new 
designs are broken since v2.1.1. The same write request object is passed to the 
next filter with  different messages in queue by mistake in the filterWrite 
method. It makes the previous messages might be overwritten by next messages 
and the next messages' buffer might be used up when they come to the 
IoProcessor again.


was (Author: cloudor):
It's true I should make sure that the filters I'm using are thread-safe and I 
found the ProtocolCodecFilter was thread-safe before version 2.1.1 but some new 
designs are broken since v2.1.1. The same write request object are passed to 
the next filter with  different messages in queue by mistake in the filterWrite 
method. It makes the previous messages might be overwritten by next messages 
and the next messages' buffer might be used up when they come to the 
IoProcessor again.

> ProtocolCodecFilter does not support concurrent access
> ------------------------------------------------------
>
>                 Key: DIRMINA-1120
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-1120
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.1, 2.1.2, 2.1.3
>            Reporter: Cloudor Pu
>            Priority: Major
>
> In ProtocolCodecFilter#filterWrite method, the same writeRequest might be 
> written more than once and previous encoded message would be overwritten by 
> next ones and cause message lost problems.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to