You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by ji...@apache.org on 2004/04/30 16:33:53 UTC
[jira] Created: (GERONIMO-227) non-deterministic ProtocolStressTest failure
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-227
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-227
Summary: non-deterministic ProtocolStressTest failure
Type: Bug
Status: Unassigned
Priority: Major
Project: Apache Geronimo
Assignee:
Reporter: anita kulshreshtha
Created: Fri, 30 Apr 2004 7:33 AM
Updated: Fri, 30 Apr 2004 7:33 AM
Environment: most JDK 1.4.2-0x versions running on
Win NT, 2k, XP pro, XP, Linux RH, and HP.
Description:
ProtocolStressTest is failing non-deterministically due to a
Possible race condition in selector implementation
(java.nio.channels.Selector). It is a known bug (since 2002) -
"Closing a registered SocketChannel in a different Thread
from the Thread that is doing the select will
intermittently generate a NullPointerException".
.......
java.lang.NullPointerException
at sun.nio.ch.WindowsSelectorImpl$SubSelector.processFDSet(Windo
wsSelectorImpl.java:309)
..........
Sometimes Selector.select() throws java.nio.channels.CancelledKeyException
if the closing thread is slower than the selecting one.
..............
java.nio.channels.CancelledKeyException
at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:55)
...............
It might be affecting ControlProtocolTest also.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-227) non-deterministic ProtocolStressTest failure
Posted by ji...@apache.org.
Message:
The following issue has been closed.
Resolver: Alan Cabrera
Date: Wed, 5 May 2004 8:00 AM
This has been fixed.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-227
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-227
Summary: non-deterministic ProtocolStressTest failure
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Apache Geronimo
Assignee: Alan Cabrera
Reporter: anita kulshreshtha
Created: Fri, 30 Apr 2004 7:33 AM
Updated: Wed, 5 May 2004 8:00 AM
Environment: most JDK 1.4.2-0x versions running on
Win NT, 2k, XP pro, XP, Linux RH, and HP.
Description:
ProtocolStressTest is failing non-deterministically due to a
Possible race condition in selector implementation
(java.nio.channels.Selector). It is a known bug (since 2002) -
"Closing a registered SocketChannel in a different Thread
from the Thread that is doing the select will
intermittently generate a NullPointerException".
.......
java.lang.NullPointerException
at sun.nio.ch.WindowsSelectorImpl$SubSelector.processFDSet(Windo
wsSelectorImpl.java:309)
..........
Sometimes Selector.select() throws java.nio.channels.CancelledKeyException
if the closing thread is slower than the selecting one.
..............
java.nio.channels.CancelledKeyException
at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:55)
...............
It might be affecting ControlProtocolTest also.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-227) non-deterministic ProtocolStressTest failure
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: anita kulshreshtha
Created: Fri, 30 Apr 2004 12:20 PM
Body:
Oops! It is SocketProtocolStressTest. Yes it is related to this bug.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/GERONIMO-227?page=comments#action_35342
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-227
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-227
Summary: non-deterministic ProtocolStressTest failure
Type: Bug
Status: Open
Priority: Major
Project: Apache Geronimo
Assignee: Alan Cabrera
Reporter: anita kulshreshtha
Created: Fri, 30 Apr 2004 7:33 AM
Updated: Fri, 30 Apr 2004 12:20 PM
Environment: most JDK 1.4.2-0x versions running on
Win NT, 2k, XP pro, XP, Linux RH, and HP.
Description:
ProtocolStressTest is failing non-deterministically due to a
Possible race condition in selector implementation
(java.nio.channels.Selector). It is a known bug (since 2002) -
"Closing a registered SocketChannel in a different Thread
from the Thread that is doing the select will
intermittently generate a NullPointerException".
.......
java.lang.NullPointerException
at sun.nio.ch.WindowsSelectorImpl$SubSelector.processFDSet(Windo
wsSelectorImpl.java:309)
..........
Sometimes Selector.select() throws java.nio.channels.CancelledKeyException
if the closing thread is slower than the selecting one.
..............
java.nio.channels.CancelledKeyException
at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:55)
...............
It might be affecting ControlProtocolTest also.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-227) non-deterministic ProtocolStressTest failure
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Alex Karasulu
Created: Fri, 30 Apr 2004 7:37 AM
Body:
Does this seem even remotely related:
http://developer.java.sun.com/developer/bugParade/bugs/4729342.html
Alex
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/GERONIMO-227?page=comments#action_35338
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-227
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-227
Summary: non-deterministic ProtocolStressTest failure
Type: Bug
Status: Open
Priority: Major
Project: Apache Geronimo
Assignee: Alan Cabrera
Reporter: anita kulshreshtha
Created: Fri, 30 Apr 2004 7:33 AM
Updated: Fri, 30 Apr 2004 7:37 AM
Environment: most JDK 1.4.2-0x versions running on
Win NT, 2k, XP pro, XP, Linux RH, and HP.
Description:
ProtocolStressTest is failing non-deterministically due to a
Possible race condition in selector implementation
(java.nio.channels.Selector). It is a known bug (since 2002) -
"Closing a registered SocketChannel in a different Thread
from the Thread that is doing the select will
intermittently generate a NullPointerException".
.......
java.lang.NullPointerException
at sun.nio.ch.WindowsSelectorImpl$SubSelector.processFDSet(Windo
wsSelectorImpl.java:309)
..........
Sometimes Selector.select() throws java.nio.channels.CancelledKeyException
if the closing thread is slower than the selecting one.
..............
java.nio.channels.CancelledKeyException
at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:55)
...............
It might be affecting ControlProtocolTest also.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira