From owner-freebsd-java Fri Aug 23 14:49: 1 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 CBD8E37B401 for ; Fri, 23 Aug 2002 14:48:57 -0700 (PDT) Received: from ns3.ideathcare.com (mail.allneo.com [216.185.96.68]) by mx1.FreeBSD.org (Postfix) with SMTP id E0AD243E75 for ; Fri, 23 Aug 2002 14:48:56 -0700 (PDT) (envelope-from jps@funeralexchange.com) Received: (qmail 99603 invoked by uid 85); 23 Aug 2002 22:01:41 -0000 Received: from jps@funeralexchange.com by ns3.ideathcare.com with qmail-scanner-1.03 (uvscan: v4.1.40/v4121. . Clean. Processed in 0.223469 secs); 23 Aug 2002 22:01:41 -0000 Received: from unknown (HELO pimpin) (216.138.114.132) by mail.allneo.com with SMTP; 23 Aug 2002 22:01:41 -0000 Reply-To: From: "Jeremy Suo-Anttila" 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 16:56:22 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <200208231733.16012.absinthe@pobox.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 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 Dylan, I will try the linking this evening when i can afford for the box to be down for a few minutes if break something. We did develop this application on FreeBSD 4.x with Jdk1.4 + Tomcat 4 and it has been running nice until now when i started with the stress testing. I am not to concerned about the JVM crashing like it has benn since i have 2 resin JVM servers running on the same box and the second is just failover server ready to take over incase the first dies for some odd reason. I just dont like to see programs up and die and dump a nice 500mb core file on my disk. I would be more then willing to be a guinea pig and test out the new 1.4 native if anyone was willing to give me the source to build. Also i will not be running this application on FreeBSD much longer since it looks like we will have to move to a Solaris 9 platform and take adavantage of its native 1.4 jdk. I was just hoping i could do this all with FreeBSD and not have to shell out the money for Sun hardware and OS. Hopefully FreeBSD will have better java support near future and i can keep on using it. I will try out the linking and let you all know how it went. Thanks Jeremy Suo-Anttila jps@funeralexchange.com From: Dylan Carlson [mailto:absinthe@pobox.com] Sent: Friday, August 23, 2002 4:33 PM 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