Your message dated Fri, 13 Jun 2003 12:21:53 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#195353: java.net.SocketException: SO_REUSEADDR: not valid
for TCP
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 30 May 2003 04:33:31 +0000
>From [EMAIL PROTECTED] Thu May 29 23:33:30 2003
Return-path: <[EMAIL PROTECTED]>
Received: from 12-238-57-17.client.attbi.com (yakko.doogie.org) [12.238.57.17]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19Lba6-0008Gv-00; Thu, 29 May 2003 23:33:30 -0500
Received: from localhost [127.0.0.1] (uucp)
by yakko.doogie.org with esmtp (Exim 3.36 1 (Debian))
id 19Lba5-0005CE-00; Thu, 29 May 2003 23:33:29 -0500
Date: Thu, 29 May 2003 23:33:29 -0500 (CDT)
From: Adam Heath <[EMAIL PROTECTED]>
X-X-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: java.net.SocketException: SO_REUSEADDR: not valid for TCP
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-11.7 required=4.0
tests=BAYES_01,HAS_PACKAGE,USER_AGENT_PINE
autolearn=ham version=2.53-bugs.debian.org_2003_05_24
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_05_24
(1.174.2.15-2003-03-30-exp)
package: libgcj4
version: 1:3.3-2
java.net.SocketException: SO_REUSEADDR: not valid for TCP
at java.net.PlainSocketImpl.setOption(int, java.lang.Object)
(/usr/lib/libgcj.so.4.0.0)
at java.net.ServerSocket.setReuseAddress(boolean) (/usr/lib/libgcj.so.4.0.0)
at
org.doogie.net.SuperServer.processServerSocket(java.net.InetSocketAddress,
org.doogie.net.SuperServer$ServerSocketAdapter) (Unknown Source)
at org.doogie.net.SuperServer.register(int,
org.doogie.net.SuperServer$ServerSocketAdapter) (Unknown Source)
at org.doogie.net.http.Server.main(java.lang.String[]) (Unknown Source)
It is perfectly fine to set that option for a tcp socket. Setting it for
udp makes no sense.
---------------------------------------
Received: (at 195353-done) by bugs.debian.org; 13 Jun 2003 10:26:12 +0000
>From [EMAIL PROTECTED] Fri Jun 13 05:26:11 2003
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19Qll5-0004zy-00; Fri, 13 Jun 2003 05:26:11 -0500
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id MAA28302
for <[EMAIL PROTECTED]>; Fri, 13 Jun 2003 12:21:54 +0200 (MET DST)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.11.6+Sun/8.9.3) id h5DALsi18726;
Fri, 13 Jun 2003 12:21:54 +0200 (MEST)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Fri, 13 Jun 2003 12:21:53 +0200
To: [EMAIL PROTECTED]
Subject: Re: Bug#195353: java.net.SocketException: SO_REUSEADDR: not valid for
TCP
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-20.2 required=4.0
tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
REPLY_WITH_QUOTES,USER_AGENT_VM
autolearn=ham version=2.53-bugs.debian.org_2003_06_10
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_06_10
(1.174.2.15-2003-03-30-exp)
Martin v. =?iso-8859-15?q?L=F6wis?= writes:
> Adam Heath <[EMAIL PROTECTED]> writes:
>
> > java.net.SocketException: SO_REUSEADDR: not valid for TCP
> [...]
> > It is perfectly fine to set that option for a tcp socket. Setting it for
> > udp makes no sense.
>
> Hmm.
> http://java.sun.com/j2se/1.4.1/docs/api/java/net/SocketOptions.html#SO_REUSEADDR
> says
>
> Sets SO_REUSEADDR for a socket. This is used only for MulticastSockets
> in java, and it is set by default for MulticastSockets.
>
> Valid for: DatagramSocketImpl
Closing the report.
