Date: Fri, 17 Feb 2006 10:54:11 -0500 From: Kurt Miller <lists@intricatesoftware.com> To: freebsd-java@freebsd.org Subject: Re: SO_REUSEADDR should not also mean SO_REUSEPORT Message-ID: <200602171054.11632.lists@intricatesoftware.com> In-Reply-To: <43F4F22F.1060402@europe.yahoo-inc.com> References: <43F4F22F.1060402@europe.yahoo-inc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 16 February 2006 4:44 pm, Arne Juul wrote: > Description by H=E5vard Pettersen=20 > (Havard.Pettersen@europe.yahoo-inc.com) > Ticket Opened: 2006-02-02=20 > 13:37 PST > > > > In the FreeBSD Java port, setting the reuse_address feature on a > > server socket also sets the reuse_port feature, which is not a good > > thing, since it allows multiple server sockets to bind to the same > > local port. > > > > A possible work-around is to also disable reuse_address, but this > > will disallow listening to an unused local port if a connection > > established against that port is still active, which is not good > > either. >=20 >=20 > I don't know why this code was put into the bsd jdk patches, it just > seems plain wrong to me. It makes java subtly non-portable in a very > strange manner; I suggest this code is removed. Below is the patch > I'm currently using :-) Linux and Solaris don't have SO_REUSEPORT. I believe their SO_REUSEADDR is equivalent to SO_REUSEADDR + SO_REUSEPORT on bsd. =2DKurt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602171054.11632.lists>