[RIVER-225] NullPointerException in Reggie during destroy

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: jtsk_2.1
• Fix Version/s: River_2.1.2
• Component/s: com_sun_jini_reggie
• Bugtraq ID: 6377953
• Assignee: Juan Ramirez
• Reporter: Thomas Vinod Johnson
• Created: 10/Aug/07 19:42
• Updated: 06/Jan/10 06:04
• Resolved: 20/Mar/08 17:00

Description

Bugtraq 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.