From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15769 invoked by alias); 8 Apr 2004 16:46:47 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 15625 invoked by uid 48); 8 Apr 2004 16:46:46 -0000 Date: Thu, 08 Apr 2004 16:46:00 -0000 From: "verigoth at maug dot wireless dot mnsu dot edu" To: gcc-bugs@gcc.gnu.org Message-ID: <20040408164645.14892.verigoth@maug.wireless.mnsu.edu> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug java/14892] New: Issues with TimerTask/Calendar X-Bugzilla-Reason: CC X-SW-Source: 2004-04/txt/msg00731.txt.bz2 List-Id: I noticed there are already bug reports for Calendar, but I don't think any of them cover this aspect: Calendar now = Calendar.getInstance(); Calendar myCal = Calendar.getInstance(); myCal.set(Calendar.HOUR_OF_DAY, 23); myCal.set(Calendar.MINUTE, 59); myCal.set(Calendar.SECOND, 59); long resetTime = myCal.getTimeInMillis() - now.getTimeInMillis(); turnTimer.scheduleAtFixedRate(new TurnTask(keeper), resetTime, 86400000); If I do a System.out.println(resetTime) and calculate milliseconds to hours it is always >25. Then if I subtract 86400000 it will display correctly but it doesn't run the task. Other Java compilers do this correctly so it's not my poor code causing the issue. ;) I have another TimerTask that starts looks like this: respawnTimer.scheduleAtFixedRate(new ResetTask(keeper), 0, 35000); which works just fine. -- Summary: Issues with TimerTask/Calendar Product: gcc Version: 3.3.3 Status: UNCONFIRMED Severity: normal Priority: P2 Component: java AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: verigoth at maug dot wireless dot mnsu dot edu CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org GCC build triplet: x86 GCC host triplet: x86 GCC target triplet: x86 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14892