August 20, 2018
Hot Topics:

Java 5's DelayQueue

  • January 18, 2007
  • By Jeff Langr
  • Send Email »
  • More Articles »

FaxServer code calls the method transmit for each object taken from the DelayQueue. Code in transmit attempts to dial the fax recipient, and if a connection is made, uses the Transmitter object to send the fax. If a connection cannot be made, the FaxTransmission object method setToResend is invoked (in which it must designate how long to wait before redialing). Code in transmit then re-adds the FaxTransmission object to the DelayQueue.

So, how does the queue know when a fax has been waiting long enough? That's the primary job of the FaxTransmission class (see Listing 4). A FaxTransmission object stores a Fax object plus the time at which the request was initially made (requestTime). Since FaxTransmission implements the Delayed interface, objects of type FaxTransmission objects can be placed in a DelayQueue. The method getDelay, declared in the Delayed interface, indicates to the DelayQueue how much longer an object must wait in order to meet the minimum delay period.

Initially, fax requests shouldn't have to wait--once taken from the queue, the FaxServer should attempt to send them. Thus FaxTransmission holds a boolean called initialTransmission to indicate whether or not a transmission has already been attempted. The first time around, then, getDelay returns a delay of 0.

Sun designed the getDelay function to be flexible, allowing for delay periods to be specified using a variety of time units--either microseconds, milliseconds, nanoseconds, or seconds. The getDelay method is passed a TimeUnit object that represents a duration. Once getDelay calculates how much time is left, it must return this amount in the same unit as the duration passed in. The convert method defined on TimeUnit accomplishes this goal, by taking as a second argument the unit from which the remaining time is to be converted:

      return timeUnit.convert(remainingMs, TimeUnit.MILLISECONDS);

In order to define the proper ordering of objects that are delayed in the queue, the FaxTransmission class also must define a compareTo method. According to Sun's javadoc, this method must provide "an ordering consistent with" the getDelay method. For FaxTransmission, a Delayed object comes before another delayed object (i.e. should be removed first from the queue) if its timeRemaining is less, or if the timeRemaining is equal and its original request time is earlier.

Listing 4. The FaxTransmission class.

import java.util.*;
import java.util.concurrent.*;

public class FaxTransmission implements Delayed {
   static final int REDIAL_PERIOD_IN_SECONDS = 10;
   private long endOfDelay;
   private boolean initialTransmission = true;
   private final Fax fax;
   private final Date requestTime;

   public FaxTransmission(Fax fax) {
      this.fax = fax;
      this.requestTime = new Date();

   public long getDelay(TimeUnit timeUnit) {
      if (initialTransmission)
         return 0;
      return timeUnit.convert(endOfDelay - System.currentTimeMillis(),

   public int compareTo(Delayed delayed) {
      FaxTransmission request = (FaxTransmission)delayed;
      if (this.endOfDelay < request.endOfDelay)
         return -1;
      if (this.endOfDelay > request.endOfDelay)
         return 1;
      return this.requestTime.compareTo(request.requestTime);

   public void setToResend() {
      initialTransmission = false;
      endOfDelay = System.currentTimeMillis() + REDIAL_PERIOD_IN_SECONDS
                   * 1000L;

   public String toString() {
      return fax.toString();

   public Fax getFax() {
      return fax;

The final class, Demo (shown in Listing 5), provides a demonstration of the fax server. This driver code creates a stub implementation of the Dialer, one that connects randomly, roughly every five attempts. It also creates a stub Transmitter that pauses for about ten seconds while printing pseudo-progress information. The driver then sends four faxes, one immediately after the other. Note that the Demo application will run infinitely due to the infinite loop defined in FaxServer.

Listing 5. A demonstration driver.

import java.util.*;

import util.*;

public class Demo {
   public static void main(String[] args) {
      Fax fax1 = new Fax("1", "5555", "some message 1");
      Fax fax2 = new Fax("2", "6666", "some message 2");
      Fax fax3 = new Fax("3", "7777", "some message 3");
      Fax fax4 = new Fax("4", "8888", "some message 4");

      Dialer dialer = new Dialer() {
         private Random random = new Random();
         public boolean connect(String number) {
            return random.nextInt(5) == 0;

      Transmitter transmitter = new Transmitter()  {
         public void send(Fax fax) {
            for (int i = 0; i < 10; i++) {

      FaxServer server = new FaxServer(dialer, transmitter);

The power of the Java 5 queue implementations, including DelayQueue, is that they define constructs for common queueing needs in a thread-safe manner. It would be reasonably easy to build the logic for your own DelayQueue, but getting the thread safety correct is not so easy. The other benefit of using the Java 5 queues is that they help separate concerns (and thus help your system adhere to the Single Responsibility Principle): The semantics of how items have to wait on the queue is defined separately from the code that defines how the queue is used by the fax server.

About the Author

Jeff Langr is a veteran software developer with a score and more years of experience. He's authored two books and dozens of published articles on software development, including Agile Java: Crafting Code With Test-Driven Development (Prentice Hall) in 2005. You can find out more about Jeff at his site, http://langrsoft.com, or you can contact him directly at jeff@langrsoft.com.

Page 2 of 2

Comment and Contribute


(Maximum characters: 1200). You have characters left.



Enterprise Development Update

Don't miss an article. Subscribe to our newsletter below.

By submitting your information, you agree that developer.com may send you developer offers via email, phone and text message, as well as email offers about other products and services that developer believes may be of interest to you. developer will process your information in accordance with the Quinstreet Privacy Policy.


Thanks for your registration, follow us on our social networks to keep up-to-date