[
https://issues.apache.org/jira/browse/DIRMINA-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859236#action_12859236
]
Emmanuel Lecharny commented on DIRMINA-778:
-------------------------------------------
It's only used when initializing the TextLine decoder, as it stores the
delimiter, something not likely to change once initialized.
I gonna check if we can protect this initialization (I'm not sure this is done
only once or if there is a potential race condition where 2 threads can set up
this value).
Thanks for your insight.
> TextLineDecoder not thread safe?
> --------------------------------
>
> Key: DIRMINA-778
> URL: https://issues.apache.org/jira/browse/DIRMINA-778
> Project: MINA
> Issue Type: Bug
> Components: Filter
> Affects Versions: 2.0.0-RC1
> Reporter: Jacklondon Chen
>
> in sample code "reverser", there is code like this:
> acceptor.getFilterChain().addLast(
> "codec",
> new ProtocolCodecFilter(new TextLineCodecFactory(Charset
> .forName("UTF-8"))));
> and that means there is only one instance of TextLineCodecFactory, which
> holds one instance of TextLineEncoder, and TextLineDecoder has a member var
> named as "IoBuffer delimBuf".
> Is it thread safe to call decode() using this delimBuf?
> I think it's a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
