From owner-freebsd-java@FreeBSD.ORG  Thu Sep 16 09:40:36 2004
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
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 9B13716A4CE
	for <freebsd-java@freebsd.org>; Thu, 16 Sep 2004 09:40:36 +0000 (GMT)
Received: from web14126.mail.yahoo.com (web14126.mail.yahoo.com
	[66.163.171.117])
	by mx1.FreeBSD.org (Postfix) with SMTP id 73ADB43D41
	for <freebsd-java@freebsd.org>; Thu, 16 Sep 2004 09:40:36 +0000 (GMT)
	(envelope-from colbyt@yahoo.com)
Message-ID: <20040916094036.13482.qmail@web14126.mail.yahoo.com>
Received: from [129.93.191.22] by web14126.mail.yahoo.com via HTTP;
	Thu, 16 Sep 2004 02:40:36 PDT
Date: Thu, 16 Sep 2004 02:40:36 -0700 (PDT)
From: Colby Thomson <colbyt@yahoo.com>
To: freebsd-java@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Native JDK random # seed (Corrected plain-text email hopefully)
X-BeenThere: freebsd-java@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting Java to FreeBSD <freebsd-java.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-java>,
	<mailto:freebsd-java-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-java>
List-Post: <mailto:freebsd-java@freebsd.org>
List-Help: <mailto:freebsd-java-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-java>,
	<mailto:freebsd-java-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2004 09:40:36 -0000

I'm running FreeBSD 4.10 with jdk 1.4.2p6. 

Summary: The native JDK should provide the same stack
trace error as the linux-sun-jdk when it suffers from
a lack of entropy while generating random numbers..
rather than simply locking with no output. 

I had a number of apps that locked solid with no debug
output or stack trace.  I ran these apps using the
linux-sun-jdk and recieved an error relating to
seeding random numbers (I can recreate and paste the
stack trace if needed).  I then switched back to the
native jdk and seeded /dev/random with 'rndcontrol -s
10' . Now the native JDK gets past the lock-up.  


P.S. My solution to this is to set rndcontrol in a
startup script -- let me know if there is a better
suggestion.

Thanks, 

- C. Colby Thomson 
J.D. Edwards Design Studio 
cthomson@unlnotes.unl.edu 


		
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail