From owner-freebsd-java Fri Aug 23 14:33:13 2002 Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CBD337B400 for ; Fri, 23 Aug 2002 14:33:11 -0700 (PDT) Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DBE343E4A for ; Fri, 23 Aug 2002 14:33:11 -0700 (PDT) (envelope-from absinthe@pobox.com) Received: from dhcp068-64-151-24.nt01-c4.cpe.charter-ne.com ([24.151.64.68] helo=laredo.retrovertigo.com) by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17iM3F-00009a-00; Fri, 23 Aug 2002 14:33:05 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Dylan Carlson Reply-To: absinthe@pobox.com To: , Subject: Re: /lib/libpthread.so.0: No such file or directory. Errors with Linux Jdk1.4.0.1 & Resin or Tomcat Date: Fri, 23 Aug 2002 17:33:16 -0400 User-Agent: KMail/1.4.2 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200208231733.16012.absinthe@pobox.com> Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Friday 23 August 2002 05:15pm, Jeremy Suo-Anttila wrote: > so i am going to try and > link all of the missing files to from the /usr/lib/foo > > /usr/compat/linux/usr/lib/foo to see if that will solve the problem. Hopefully that won't cause you problems with your FreeBSD binaries, but I guess it's worth a shot. Let us know how it goes. > Anyone on the list happen to know a easier way to accomplish this? I can > see this not being the best way to handle this since it can be easily > broken by a makeworld or other upgrades. Do i need to maybe add the path to > the linux libs to a hint file somewhere?? Also this only happens when i run > the MS Application Web stress tester against my server with a 100+ threads > and the server is under ALOT of load. The threading under 1.4 is an known, open problem. Until we have a native-build port of the 1.4.x SDK I personally wouldn't expect a fix. Green threads are gone, and I doubt the Linuxulator will ever handle that well going forward. (someone correct me if I'm wrong) However, Alexey Zelkin recently bootstrapped a native build of 1.4.0 and that's great news -- which means that we should see a native-build port emerge sometime. It's a first step, anyway. But none of this information will solve your problem today. It sounds to me that you didn't use FreeBSD as your development platform when you wrote your app; you are in turn using FreeBSD as your QA/production platform. 1.4.0 is bleeding edge (IMO) ... if I were you, I would bend the code backwards to 1.3.1. If your 1.4.0 VM isn't predictable, I don't know what choice you have -- apart from making a (pragmatic, undesireable) decision to run it on another platform. Cheers, -- Dylan Carlson [absinthe@pobox.com] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message