Date: Thu, 30 Nov 2006 23:20:13 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Tim Clewlow <tim1timau@yahoo.com> Cc: freebsd-java@freebsd.org Subject: Re: Something is really not right with azureus 2.5 / diablo-jdk 1.5 Message-ID: <20061130212013.GQ69556@deviant.kiev.zoral.com.ua> In-Reply-To: <816020.25749.qm@web50303.mail.yahoo.com> References: <816020.25749.qm@web50303.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--451BZW+OUuJBCAYj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 30, 2006 at 01:07:47PM -0800, Tim Clewlow wrote: > > > FYI - I discovered the internet connection was constantly at 100% u/l= due > > to a > > > number of people on the LAN doing p2p, so I shaped the external link = to > > only > > > allow 80% of the real uplink capacity (which creates a 20% buffer to > > attempt to > > > mininize collisions on the uplink) and azureus suddenly came back to = life. > > Note > > > that azureus on the windows box was happy before I shaped the link, b= ut the > > BSD > > > version was not. This makes me think the BSD version of azureus gets = into > > > trouble when outgoing packets get lost due to packet collision. > > >=20 > > > Tim. > >=20 > > Does this thing use nio ? > >=20 >=20 > It uses the following ports from "java" to build - I dont know if nio is = in > these versions or not: >=20 > -0003 jakarta-commons-cli-1.0,1 /java/jakarta-commons-cli > -0004 junit-3.8.2 /java/junit > -0007 diablo-jdk-1.5.0.07.01_1 /java/diablo-jdk15 > -0010 jakarta-commons-lang-2.1 /java/jakarta-commons-lang > -0037 javavmwrapper-2.3 /java/javavmwrapper >=20 > It also uses the following ports from "net" to build: >=20 > -0006 seda-3.0 /net/seda > -0034 linc-1.0.3_6 /net/linc > -0058 samba-libsmbclient-3.0.23c /net/samba-libsmbclient > -0059 avahi+libdns-0.6.14_3 /net/avahi Nio is a feature supplied by jdk itself. There is a bug in freebsd port of jdk in the nio support, see PR java/105482. What you described could be caused by this bug. --451BZW+OUuJBCAYj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFb0sNC3+MBN1Mb4gRAsfNAJ4rNR3H0w+z2BdWmcLJyIv5/W+HMwCfRNUd lEqYWmd1T1VWTFT1tF4gHFI= =d4dR -----END PGP SIGNATURE----- --451BZW+OUuJBCAYj--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061130212013.GQ69556>