From owner-freebsd-java@FreeBSD.ORG Tue May 30 01:52:37 2006 Return-Path: X-Original-To: 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 6DEB016A459 for ; Tue, 30 May 2006 01:52:37 +0000 (UTC) (envelope-from classacts@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9BDE43D53 for ; Tue, 30 May 2006 01:52:36 +0000 (GMT) (envelope-from classacts@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so329094uge for ; Mon, 29 May 2006 18:52:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=alTF5nOnRENBam+Gv819oK0eHwsaGKCy8K7UVEqgUTvhh7Us0ZTrqI1F4d1Kbz/4/dwpybVRI23YsbBtzqMznp4S2SR8GI65rOpRz+PZ5PiKuJBwko2w34aZ3hovYvBrczdUdg9jx+EQ7Rv1P9iKcyuJQw19uFwQL1herOwXtqM= Received: by 10.78.45.13 with SMTP id s13mr514072hus; Mon, 29 May 2006 17:55:14 -0700 (PDT) Received: by 10.78.25.14 with HTTP; Mon, 29 May 2006 17:55:14 -0700 (PDT) Message-ID: Date: Tue, 30 May 2006 08:55:14 +0800 From: "class acts" To: freebsd-java@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Object.wait() inaccurate? X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2006 01:52:38 -0000 I'm noticing similar behavior to issue Java/94223 in diablo-jdk15 ( http://www.freebsd.org/cgi/query-pr.cgi?pr=94223) I have a java.util.Timer task that executes every second but executes every 15ms - 1015ms. I do have jdk15p2 installed on the same machine, but I have confirmed via `ps` that my application is in fact using the diablo jdk. same issue occurs on jdk15 p2 on the same box, but goes away if i try linux-sun-jdk14. machine is FreeBSD/i386 5.4 SMP dual Xeon EM64T Kind Regards,