You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Andrew Zhang (JIRA)" <ji...@apache.org> on 2006/08/15 09:17:15 UTC

[jira] Commented: (HARMONY-1162) [classlib][luni] java.net.MulticastSocket constructor doesn't call DatagramSocket.setReuseAddress(boolean) as spec requires.

    [ http://issues.apache.org/jira/browse/HARMONY-1162?page=comments#action_12428050 ] 
            
Andrew Zhang commented on HARMONY-1162:
---------------------------------------

Hi Paulex,

The fix looks good, many thanks!

Best regards,
Andrew

> [classlib][luni] java.net.MulticastSocket constructor doesn't call  DatagramSocket.setReuseAddress(boolean)  as spec requires.
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-1162
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1162
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>            Reporter: Andrew Zhang
>         Assigned To: Paulex Yang
>         Attachments: Harmony-1162.diff
>
>
> java.net.MulticastSocket constructor doesn't call  DatagramSocket.setReuseAddress(boolean)  as spec requires. MulticastSocket constructor spec says "When the socket is created the DatagramSocket.setReuseAddress(boolean) method is called to enable the SO_REUSEADDR socket option.".
> Following test reproduces the bug:
>     public void test_MulticastSocket() throws Exception {
>         InetSocketAddress addr = new InetSocketAddress("0.0.0.0", 0);
>         MulticastSocket s = new MulticastSocket(addr);
>         try {
>             assertTrue(s.getReuseAddress());
>         } finally {
>             s.close();
>         }
>     }
> The test passes against RI while fails against Harmony. 
> I'll upload a patch to fix this problem soon.Thanks!
> Best regards,
> Andrew

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira