From owner-freebsd-java@FreeBSD.ORG Tue Dec 16 12:25:16 2008 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E4551065675 for ; Tue, 16 Dec 2008 12:25:16 +0000 (UTC) (envelope-from "cyb."@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id DAA658FC22 for ; Tue, 16 Dec 2008 12:25:15 +0000 (UTC) (envelope-from "cyb."@gmx.net) Received: (qmail invoked by alias); 16 Dec 2008 11:58:33 -0000 Received: from pD952E4A4.dip0.t-ipconnect.de (EHLO core2duo.local) [217.82.228.164] by mail.gmx.net (mp001) with SMTP; 16 Dec 2008 12:58:33 +0100 X-Authenticated: #4870692 X-Provags-ID: V01U2FsdGVkX1/2NqwvnKv2tjzfCh/+1ntwaUzILg2SuTPglSHzz1 j1hztRg4QRk+8J Date: Tue, 16 Dec 2008 12:58:30 +0100 From: Andreas Rudisch To: alvaro rosales Message-Id: <20081216125830.384a9b6f.cyb.@gmx.net> In-Reply-To: <958977.77379.qm@web24105.mail.ird.yahoo.com> References: <958977.77379.qm@web24105.mail.ird.yahoo.com> X-Mailer: Sylpheed 2.5.0 (GTK+ 2.12.11; i386-portbld-freebsd6.3) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Tue__16_Dec_2008_12_58_30_+0100_P4KY2WJtwHuzR8du" X-Y-GMX-Trusted: 0 X-FuHaFi: 0.6 Cc: freebsd-questions@freebsd.org, freebsd-java@freebsd.org Subject: Re: Limewire 4.18 problem X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2008 12:25:16 -0000 --Signature=_Tue__16_Dec_2008_12_58_30_+0100_P4KY2WJtwHuzR8du Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 16 Dec 2008 10:44:14 +0000 (GMT) alvaro rosales wrote: > I have a freebsd 7 Release #0 box, it works as a marble, > unfortunately I have a problem with limewire 4.18. I can connect with > any other p2p network client, (firewall is ok and set up to allow > connections on limewire port and upnp is enable) but limewire wont > connect. Sounds like the same problem Vuze/Azureus has when running on FreeBSD 7. > I have made a search on the net and found a thread that fixed > it by modifying the file /etc/libmap.conf as follows:=20 > [/usr/local/diablo-jre1.5.0/]=20 > libpthread.so libc_r.so=20 > libpthread.so.2 libc_r.so.6=20 That work-around only works on FreeBSD 6 (probably because of the change to libthr in FreeBSD 7). When I was testing Vuze again on FreeBSD 7.1-RC1 a few days ago, I noticed that data transfer was happening when using UDP. But normal TCP connections to other peers would time out, hanging during/after the handshake. The connections seemed to be established though. A Vuze developer told me, that transfers via UDP and TCP are using different sets of native java APIs. TCP is non-blocking IO, so there could be a problem in the FreeBSD Java code. Andreas -- GnuPG key : 0x2A573565 | http://www.gnupg.org/howtos/de/ Fingerprint: 925D 2089 0BF9 8DE5 9166 33BB F0FD CD37 2A57 3565 --Signature=_Tue__16_Dec_2008_12_58_30_+0100_P4KY2WJtwHuzR8du Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklHl+gACgkQ8P3NNypXNWVFMACdHV8P7ObnG39NV+HygyadAVfR 840An3RhlcMvCTbmzjgA6zpIQfB42F/1 =dDwA -----END PGP SIGNATURE----- --Signature=_Tue__16_Dec_2008_12_58_30_+0100_P4KY2WJtwHuzR8du--