You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Thomas Vinod Johnson (JIRA)" <ji...@apache.org> on 2007/08/10 21:43:42 UTC
[jira] Created: (RIVER-225) NullPointerException in Reggie during
destroy
NullPointerException in Reggie during destroy
---------------------------------------------
Key: RIVER-225
URL: https://issues.apache.org/jira/browse/RIVER-225
Project: River
Issue Type: Bug
Components: com_sun_jini_reggie
Affects Versions: jtsk_2.1
Reporter: Thomas Vinod Johnson
Priority: Minor
Bugtraq ID [6377953|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6377953]
Reggie has a workaround for Thread.interrrupt() not interrupting MulticastSocket.receive() on all paltforms. The workaround is to attempt to close the socket in the interrupt() method of MuticastThread. If Reggie is configured with DiscoveryManagement.NO_GROUPS, the MulticastThread will be created and started, but it won't set a socket, so when interrupt() is called on this thread at destroy time, a NullPointerException will be thrown. Whether the workaround is still necesarry or not should be investigated as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-225) NullPointerException in Reggie during
destroy
Posted by "Juan Ramirez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juan Ramirez updated RIVER-225:
-------------------------------
Attachment: RIVER-225_RIVER-246.patch
Added missing patch file.
> NullPointerException in Reggie during destroy
> ---------------------------------------------
>
> Key: RIVER-225
> URL: https://issues.apache.org/jira/browse/RIVER-225
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_reggie
> Affects Versions: jtsk_2.1
> Reporter: Thomas Vinod Johnson
> Assignee: Juan Ramirez
> Priority: Minor
> Fix For: AR2
>
> Attachments: RIVER-225_RIVER-246.patch
>
>
> Bugtraq ID [6377953|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6377953]
> Reggie has a workaround for Thread.interrrupt() not interrupting MulticastSocket.receive() on all paltforms. The workaround is to attempt to close the socket in the interrupt() method of MuticastThread. If Reggie is configured with DiscoveryManagement.NO_GROUPS, the MulticastThread will be created and started, but it won't set a socket, so when interrupt() is called on this thread at destroy time, a NullPointerException will be thrown. Whether the workaround is still necesarry or not should be investigated as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-225) NullPointerException in Reggie during
destroy
Posted by "Juan Ramirez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juan Ramirez updated RIVER-225:
-------------------------------
Fix Version/s: AR2
Assignee: Juan Ramirez
> NullPointerException in Reggie during destroy
> ---------------------------------------------
>
> Key: RIVER-225
> URL: https://issues.apache.org/jira/browse/RIVER-225
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_reggie
> Affects Versions: jtsk_2.1
> Reporter: Thomas Vinod Johnson
> Assignee: Juan Ramirez
> Priority: Minor
> Fix For: AR2
>
>
> Bugtraq ID [6377953|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6377953]
> Reggie has a workaround for Thread.interrrupt() not interrupting MulticastSocket.receive() on all paltforms. The workaround is to attempt to close the socket in the interrupt() method of MuticastThread. If Reggie is configured with DiscoveryManagement.NO_GROUPS, the MulticastThread will be created and started, but it won't set a socket, so when interrupt() is called on this thread at destroy time, a NullPointerException will be thrown. Whether the workaround is still necesarry or not should be investigated as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (RIVER-225) NullPointerException in Reggie during
destroy
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone closed RIVER-225.
---------------------------------
> NullPointerException in Reggie during destroy
> ---------------------------------------------
>
> Key: RIVER-225
> URL: https://issues.apache.org/jira/browse/RIVER-225
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_reggie
> Affects Versions: jtsk_2.1
> Reporter: Thomas Vinod Johnson
> Assignee: Juan Ramirez
> Priority: Minor
> Fix For: AR2
>
> Attachments: RIVER-225_RIVER-246.patch
>
>
> Bugtraq ID [6377953|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6377953]
> Reggie has a workaround for Thread.interrrupt() not interrupting MulticastSocket.receive() on all paltforms. The workaround is to attempt to close the socket in the interrupt() method of MuticastThread. If Reggie is configured with DiscoveryManagement.NO_GROUPS, the MulticastThread will be created and started, but it won't set a socket, so when interrupt() is called on this thread at destroy time, a NullPointerException will be thrown. Whether the workaround is still necesarry or not should be investigated as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (RIVER-225) NullPointerException in Reggie during
destroy
Posted by "Juan Ramirez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juan Ramirez resolved RIVER-225.
--------------------------------
Resolution: Fixed
> NullPointerException in Reggie during destroy
> ---------------------------------------------
>
> Key: RIVER-225
> URL: https://issues.apache.org/jira/browse/RIVER-225
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_reggie
> Affects Versions: jtsk_2.1
> Reporter: Thomas Vinod Johnson
> Assignee: Juan Ramirez
> Priority: Minor
> Fix For: AR2
>
>
> Bugtraq ID [6377953|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6377953]
> Reggie has a workaround for Thread.interrrupt() not interrupting MulticastSocket.receive() on all paltforms. The workaround is to attempt to close the socket in the interrupt() method of MuticastThread. If Reggie is configured with DiscoveryManagement.NO_GROUPS, the MulticastThread will be created and started, but it won't set a socket, so when interrupt() is called on this thread at destroy time, a NullPointerException will be thrown. Whether the workaround is still necesarry or not should be investigated as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.