Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of b.unckel@gmx.net designates
 213.165.64.21 as permitted sender)
Date: Thu, 15 Dec 2005 18:54:58 +0100 (MET)
From: "Boris Unckel" <b.unckel@gmx.net>
To: commons-dev@jakarta.apache.org
MIME-Version: 1.0
Subject: Re: [POLL] System.currentTimeMillis()
Message-ID: <7321.1134669298@www76.gmx.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Joerg,

this is an absolutely "normal" behaviour. It does not depend
on the operating system, but more on system speed.
Your CPU has enough power to calculate n-thousand additions
in one milli second.
It is not predictable, since it depends on the machine in use.

I have found this in an other context:
Random  r1 = new Random(); //depends on System.currentMillis()

If you have the need to randomize more than one number (and cannot
rely on the same random object) you need one random for the seed,
and one random for the number generating:

private static final Random RANDOM_FOR_SEED = new Random();
//....
public int generateRandomInt(){
 Random localRandom = new Random(RANDOM_FOR_SEED.nextLong());
 return localRandom.nextInt(100);
}

Regards
Boris

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org