You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Nigel Daley (JIRA)" <ji...@apache.org> on 2007/05/15 00:36:16 UTC
[jira] Created: (HADOOP-1366) Inconsistent synchronization of
Server$Listener.acceptChannel; locked 50% of time
Inconsistent synchronization of Server$Listener.acceptChannel; locked 50% of time
---------------------------------------------------------------------------------
Key: HADOOP-1366
URL: https://issues.apache.org/jira/browse/HADOOP-1366
Project: Hadoop
Issue Type: Bug
Components: ipc
Affects Versions: 0.12.3
Reporter: Nigel Daley
Priority: Blocker
Fix For: 0.13.0
Server.java line 290
The acceptChannel field of this class appears to be accessed inconsistently with respect to synchronization.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HADOOP-1366) Inconsistent synchronization of
Server$Listener.acceptChannel; locked 50% of time
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko resolved HADOOP-1366.
-----------------------------------------
Resolution: Duplicate
> Inconsistent synchronization of Server$Listener.acceptChannel; locked 50% of time
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-1366
> URL: https://issues.apache.org/jira/browse/HADOOP-1366
> Project: Hadoop
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.12.3
> Reporter: Nigel Daley
> Assignee: Konstantin Shvachko
> Fix For: 0.14.0
>
>
> Server.java line 290
> The acceptChannel field of this class appears to be accessed inconsistently with respect to synchronization.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-1366) Inconsistent synchronization of
Server$Listener.acceptChannel; locked 50% of time
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur reassigned HADOOP-1366:
----------------------------------------
Assignee: Konstantin Shvachko
> Inconsistent synchronization of Server$Listener.acceptChannel; locked 50% of time
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-1366
> URL: https://issues.apache.org/jira/browse/HADOOP-1366
> Project: Hadoop
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.12.3
> Reporter: Nigel Daley
> Assigned To: Konstantin Shvachko
> Fix For: 0.14.0
>
>
> Server.java line 290
> The acceptChannel field of this class appears to be accessed inconsistently with respect to synchronization.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1366) Inconsistent synchronization of
Server$Listener.acceptChannel; locked 50% of time
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1366:
-------------------------------------
Fix Version/s: (was: 0.13.0)
0.14.0
Priority: Major (was: Blocker)
Could occur only when server is shutdown. Deferring to 0.14
> Inconsistent synchronization of Server$Listener.acceptChannel; locked 50% of time
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-1366
> URL: https://issues.apache.org/jira/browse/HADOOP-1366
> Project: Hadoop
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.12.3
> Reporter: Nigel Daley
> Fix For: 0.14.0
>
>
> Server.java line 290
> The acceptChannel field of this class appears to be accessed inconsistently with respect to synchronization.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.