[
https://issues.apache.org/jira/browse/DIRMINA-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRMINA-585:
--------------------------------------
Fix Version/s: (was: 2.0.0-M4)
3.0.0-M1
We don't have any list of configuration variable which need to be protected.
Moreover, we didn't reached a consensus on what we should do about them. last,
not least, the way those properties are handled is most certainly wrong : even
if you don't care about the number of written or read bytes (which is certainly
the case, assuming that the throttling filter has been removed from the core,
due to serious issues), you still have to manipulate those elements, which is
ridiculous.
I suggest we postpone this issue to 3.0, have another discussion, and state
what we should do.
> 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-M1
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
