From owner-freebsd-java Wed Mar 12 10:26:15 2003 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 E5CBA37B404 for ; Wed, 12 Mar 2003 10:26:13 -0800 (PST) Received: from mgr3.xmission.com (mgr3.xmission.com [198.60.22.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF70B43FA3 for ; Wed, 12 Mar 2003 10:26:12 -0800 (PST) (envelope-from glewis@eyesbeyond.com) Received: from mail by mgr3.xmission.com with spam-scanned (Exim 3.35 #1) id 18tAvc-0000Um-03; Wed, 12 Mar 2003 11:26:12 -0700 Received: from [207.135.128.145] (helo=misty.eyesbeyond.com) by mgr3.xmission.com with esmtp (Exim 3.35 #1) id 18tAva-0000TN-03; Wed, 12 Mar 2003 11:26:11 -0700 Received: (from glewis@localhost) by misty.eyesbeyond.com (8.11.6/8.11.6) id h2CIQ6780737; Thu, 13 Mar 2003 04:56:06 +1030 (CST) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Thu, 13 Mar 2003 04:56:06 +1030 From: Greg Lewis To: Guerry Semones Cc: freebsd-java@freebsd.org Subject: Re: FreeBSD JDK 1.3.1_p8 HotSpot not loading from jre/lib/ext??? Message-ID: <20030313045606.A80657@misty.eyesbeyond.com> References: <200303120835.AA1746731258@mail.mstar2.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200303120835.AA1746731258@mail.mstar2.net>; from gsemones@treenleaf.com on Wed, Mar 12, 2003 at 08:35:15AM -0800 X-Spam-Status: No, hits=-3.8 required=8.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, SIGNATURE_SHORT_DENSE,SPAM_PHRASE_01_02,USER_AGENT, USER_AGENT_MUTT,X_AUTH_WARNING version=2.43 X-Spam-Level: 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 Wed, Mar 12, 2003 at 08:35:15AM -0800, Guerry Semones wrote: > Thanks much for the responses, and for the patch. I'm taking > advantage of them, but I still have an open issue: > > Will this patch or a similar fix make its way into a 1.3.1_p9 in > the future. Unfortunately, my concern here is from a customer > support standpoint. If one of our customer's tries to use our > product with with the 1.3.1_p8 (the "latest" and the version that > passed compatibility tests, they will have this problem if using SSL. > > I could force the fix by using Antony's approach in my JNI code, > or point customer's to the problem in the source code, or even > share Haro's patch, but ideally for customer support, it'd be > better to just have them get a patch 9. Or you could just use the green threads + Classic VM combination which is what passed the compatibility tests. This error is _only_ for HotSpot which is clearly stated to be experimental for 1.3.1. To be more specific, if you want a compliant JDK, you will compile 1.3.1p8 without native threads or HotSpot and without optimisation. You will not use a JIT. That is the only setup which has tested as compliant so far. To answer your question about the patch being included in patchset 9, the answer is yes. I've got it in my local tree and will check it in to the repo soon and add a patch to the port after ports freeze is done. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message