Bug 4230 - Invalid DatagramSocket option
Invalid DatagramSocket option
Product: Red Hat Linux
Classification: Retired
Component: netscape (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-07-27 17:54 EDT by gailizhao
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-08-24 12:38:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description gailizhao 1999-07-27 17:54:01 EDT

I have an applet that performs a multicast function on a
Linux machine.  The browser is Netscape communicator 4.51.
The applet is a signed applet and has passed
the "Multicast" privilege checking when the applet is
executed. Right after the privilege checking, the applet
attempts to instantiate a multicastSocket with the
following code: DatagramSocket socket = new MulticastSocket
(6666); At this point, a SocketException occurrs.

The Stack traces are:
invalid DatagramSocket option
at java.net.PlainDatagramSocketImpl.setOption
at java.net.MulticastCreate (MulticastSocket.java:111)
at java.net.DatagramSocket. (DatagramSocket.java:115)
at java.net.DatagramSocket. (DatagramSocket.java:101)
at java.net.MulticastSocket. (MulticastSocket.java:92)
at inria.net.MulticastSession.run
(MulticastSession.java:205)  applet code
at java.lang.Thread.run (Thread.java:504)

Note: The same applet running with Netscape communicator
4.51 under Windows is OK.

Can someone tell me what's the cause of this problem?


Larry Hsiao
Foresyte Technologies, Inc.
Comment 1 Bill Nottingham 1999-07-29 12:42:59 EDT
Do you have multicast support compiled into your kernel?
Comment 2 Bill Nottingham 1999-08-24 12:38:59 EDT
Corfirmed and reported to Netscape. Unfortunately, since we
don't control the netscape source code, we can't really
fix this.

Note You need to log in before you can comment on or make changes to this bug.