You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Bob Scheifler (JIRA)" <ji...@apache.org> on 2007/08/10 20:57:42 UTC

[jira] Created: (RIVER-215) LookupDiscovery throws NullPointerException on terminate

LookupDiscovery throws NullPointerException on terminate
--------------------------------------------------------

                 Key: RIVER-215
                 URL: https://issues.apache.org/jira/browse/RIVER-215
             Project: River
          Issue Type: Bug
          Components: net_jini_discovery
    Affects Versions: jtsk_2.0
            Reporter: Bob Scheifler
            Priority: Minor


Bugtraq ID [6319534|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6319534]

There is a race condition in LookupDiscovery which leads to a null pointer exception on terminate. This is caused due to the fact that the run method nulls out its socket, which in turn is referenced in the interrupt method that terminate invokes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (RIVER-215) LookupDiscovery throws NullPointerException on terminate

Posted by "Thomas Vinod Johnson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RIVER-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Vinod Johnson resolved RIVER-215.
----------------------------------------

    Resolution: Fixed

Assuming lack of comments means the change is OK.

> LookupDiscovery throws NullPointerException on terminate
> --------------------------------------------------------
>
>                 Key: RIVER-215
>                 URL: https://issues.apache.org/jira/browse/RIVER-215
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_discovery
>    Affects Versions: jtsk_2.0
>            Reporter: Bob Scheifler
>            Assignee: Thomas Vinod Johnson
>            Priority: Minor
>             Fix For: AR2
>
>
> Bugtraq ID [6319534|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6319534]
> There is a race condition in LookupDiscovery which leads to a null pointer exception on terminate. This is caused due to the fact that the run method nulls out its socket, which in turn is referenced in the interrupt method that terminate invokes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (RIVER-215) LookupDiscovery throws NullPointerException on terminate

Posted by "Thomas Vinod Johnson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RIVER-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Vinod Johnson reassigned RIVER-215:
------------------------------------------

    Assignee: Thomas Vinod Johnson

> LookupDiscovery throws NullPointerException on terminate
> --------------------------------------------------------
>
>                 Key: RIVER-215
>                 URL: https://issues.apache.org/jira/browse/RIVER-215
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_discovery
>    Affects Versions: jtsk_2.0
>            Reporter: Bob Scheifler
>            Assignee: Thomas Vinod Johnson
>            Priority: Minor
>             Fix For: AR2
>
>
> Bugtraq ID [6319534|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6319534]
> There is a race condition in LookupDiscovery which leads to a null pointer exception on terminate. This is caused due to the fact that the run method nulls out its socket, which in turn is referenced in the interrupt method that terminate invokes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (RIVER-215) LookupDiscovery throws NullPointerException on terminate

Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RIVER-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Firmstone closed RIVER-215.
---------------------------------


> LookupDiscovery throws NullPointerException on terminate
> --------------------------------------------------------
>
>                 Key: RIVER-215
>                 URL: https://issues.apache.org/jira/browse/RIVER-215
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_discovery
>    Affects Versions: jtsk_2.0
>            Reporter: Bob Scheifler
>            Assignee: Thomas Vinod Johnson
>            Priority: Minor
>             Fix For: AR2
>
>
> Bugtraq ID [6319534|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6319534]
> There is a race condition in LookupDiscovery which leads to a null pointer exception on terminate. This is caused due to the fact that the run method nulls out its socket, which in turn is referenced in the interrupt method that terminate invokes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Work started: (RIVER-215) LookupDiscovery throws NullPointerException on terminate

Posted by "Thomas Vinod Johnson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RIVER-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on RIVER-215 started by Thomas Vinod Johnson.

> LookupDiscovery throws NullPointerException on terminate
> --------------------------------------------------------
>
>                 Key: RIVER-215
>                 URL: https://issues.apache.org/jira/browse/RIVER-215
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_discovery
>    Affects Versions: jtsk_2.0
>            Reporter: Bob Scheifler
>            Assignee: Thomas Vinod Johnson
>            Priority: Minor
>             Fix For: AR2
>
>
> Bugtraq ID [6319534|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6319534]
> There is a race condition in LookupDiscovery which leads to a null pointer exception on terminate. This is caused due to the fact that the run method nulls out its socket, which in turn is referenced in the interrupt method that terminate invokes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (RIVER-215) LookupDiscovery throws NullPointerException on terminate

Posted by "Bob Scheifler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RIVER-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bob Scheifler updated RIVER-215:
--------------------------------

    Bugtraq ID: 6319534

> LookupDiscovery throws NullPointerException on terminate
> --------------------------------------------------------
>
>                 Key: RIVER-215
>                 URL: https://issues.apache.org/jira/browse/RIVER-215
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_discovery
>    Affects Versions: jtsk_2.0
>            Reporter: Bob Scheifler
>            Priority: Minor
>
> Bugtraq ID [6319534|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6319534]
> There is a race condition in LookupDiscovery which leads to a null pointer exception on terminate. This is caused due to the fact that the run method nulls out its socket, which in turn is referenced in the interrupt method that terminate invokes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (RIVER-215) LookupDiscovery throws NullPointerException on terminate

Posted by "Thomas Vinod Johnson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RIVER-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Vinod Johnson resolved RIVER-215.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: AR2

> LookupDiscovery throws NullPointerException on terminate
> --------------------------------------------------------
>
>                 Key: RIVER-215
>                 URL: https://issues.apache.org/jira/browse/RIVER-215
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_discovery
>    Affects Versions: jtsk_2.0
>            Reporter: Bob Scheifler
>            Assignee: Thomas Vinod Johnson
>            Priority: Minor
>             Fix For: AR2
>
>
> Bugtraq ID [6319534|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6319534]
> There is a race condition in LookupDiscovery which leads to a null pointer exception on terminate. This is caused due to the fact that the run method nulls out its socket, which in turn is referenced in the interrupt method that terminate invokes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Reopened: (RIVER-215) LookupDiscovery throws NullPointerException on terminate

Posted by "Thomas Vinod Johnson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RIVER-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Vinod Johnson reopened RIVER-215:
----------------------------------------


Shouldn't have 'resolved', just set the Fix version to AR2.

> LookupDiscovery throws NullPointerException on terminate
> --------------------------------------------------------
>
>                 Key: RIVER-215
>                 URL: https://issues.apache.org/jira/browse/RIVER-215
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_discovery
>    Affects Versions: jtsk_2.0
>            Reporter: Bob Scheifler
>            Assignee: Thomas Vinod Johnson
>            Priority: Minor
>             Fix For: AR2
>
>
> Bugtraq ID [6319534|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6319534]
> There is a race condition in LookupDiscovery which leads to a null pointer exception on terminate. This is caused due to the fact that the run method nulls out its socket, which in turn is referenced in the interrupt method that terminate invokes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.