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 2014/09/06 08:52:28 UTC
[jira] [Commented] (DIRMINA-585) Visibility issue in various
configuration properties and a few critical counters.
[ https://issues.apache.org/jira/browse/DIRMINA-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124359#comment-14124359 ]
Emmanuel Lecharny commented on DIRMINA-585:
-------------------------------------------
Postponed to 3.0, where we will be able to think about the better way to handle those elements.
> Visibility issue in various configuration properties and a few critical counters.
> ---------------------------------------------------------------------------------
>
> Key: DIRMINA-585
> URL: https://issues.apache.org/jira/browse/DIRMINA-585
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.10, 1.1.7, 2.0.0-M1
> Reporter: Trustin Lee
> Priority: Minor
> Fix For: 3.0.0-M3
>
>
> Configuration properties such as idleTimeForRead, readBufferSize and useReadOperation have visibility issue because they are mutable and non-volatile. All configuration propeties should be declared as volatile and some critical counter properties such as idleCount should be an AtomicInteger or something similar. Detailed discussion is here:
> http://markmail.org/message/h4rcitkfit4bdcpl
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)