You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2007/08/03 08:27:52 UTC
[jira] Created: (DIRMINA-416) Possible visibility problem against
Selector access
Possible visibility problem against Selector access
---------------------------------------------------
Key: DIRMINA-416
URL: https://issues.apache.org/jira/browse/DIRMINA-416
Project: MINA
Issue Type: Bug
Components: Transport
Affects Versions: 1.1.1, 1.0.4, 1.1.0, 1.0.3, 1.0.2, 1.0.1, 1.0.0
Reporter: Trustin Lee
Assignee: Trustin Lee
Priority: Minor
Fix For: 1.0.5, 1.1.2
selector member variable of various NIO transport services is not declared as 'volatile', so it can possibly lead to a visibility problem, as discussed like the following:
http://www.nabble.com/Unsafe-concurrency-issue-in-SocketIoProcessor---tf4162935s16868.html
In 1.1, we could simply use volatile keyword for the member variables, but will need explicit synchronization block in 1.0 because most Java 1.4 VMs doesn't support volatile keyword.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRMINA-416) Possible visibility problem against
Selector access
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trustin Lee resolved DIRMINA-416.
---------------------------------
Resolution: Fixed
Changed as following:
http://svn.apache.org/viewvc?view=rev&revision=562355
> Possible visibility problem against Selector access
> ---------------------------------------------------
>
> Key: DIRMINA-416
> URL: https://issues.apache.org/jira/browse/DIRMINA-416
> Project: MINA
> Issue Type: Bug
> Components: Transport
> Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.1.0, 1.0.4, 1.1.1
> Reporter: Trustin Lee
> Assignee: Trustin Lee
> Priority: Minor
> Fix For: 1.0.5, 1.1.2
>
>
> selector member variable of various NIO transport services is not declared as 'volatile', so it can possibly lead to a visibility problem, as discussed like the following:
> http://www.nabble.com/Unsafe-concurrency-issue-in-SocketIoProcessor---tf4162935s16868.html
> In 1.1, we could simply use volatile keyword for the member variables, but will need explicit synchronization block in 1.0 because most Java 1.4 VMs doesn't support volatile keyword.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRMINA-416) Possible visibility problem against
Selector access
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRMINA-416.
-------------------------------------
> Possible visibility problem against Selector access
> ---------------------------------------------------
>
> Key: DIRMINA-416
> URL: https://issues.apache.org/jira/browse/DIRMINA-416
> Project: MINA
> Issue Type: Bug
> Components: Transport
> Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.1.0, 1.0.4, 1.1.1
> Reporter: Trustin Lee
> Assignee: Trustin Lee
> Priority: Minor
> Fix For: 1.0.5, 1.1.2
>
>
> selector member variable of various NIO transport services is not declared as 'volatile', so it can possibly lead to a visibility problem, as discussed like the following:
> http://www.nabble.com/Unsafe-concurrency-issue-in-SocketIoProcessor---tf4162935s16868.html
> In 1.1, we could simply use volatile keyword for the member variables, but will need explicit synchronization block in 1.0 because most Java 1.4 VMs doesn't support volatile keyword.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.