interrupt-alarms in jtreg are using the wrong Alarm API

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • jtreg4.2
    • Affects Version/s: None
    • Component/s: tools
    • None
    • b04

      (I think this is a remnant from when I refactored the Alarm class.)

      There are some calls to:

      alarm = Alarm.schedule(timeout, TimeUnit.SECONDS, alarmOut, Thread.currentThread());

      which should really be:

      alarm = Alarm.schedulePeriodicInterrupt(timeout, TimeUnit.SECONDS, alarmOut, Thread.currentThread());

      The first call will actually send Thread.currentThread() as a Runnable to the Alarm to be executed when the Alarm triggers. I'm guessing this can lead to some very interesting scenarios...

            Assignee:
            Staffan Larsen (Inactive)
            Reporter:
            Staffan Larsen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: