NATS Logo by Example

Work-queue Stream in JetStream

A work-queue retention policy satisfies a very common use case of queuing up messages that are intended to be processed once and only once.

This retention policy supports queuing up messages from publishers independent of consummption. Since each message is intended to be processed only once, this retention type allows for a set of consumers that have non-overlapping interest on subjects. In other words, if multiple consumers are bound to a work-queue stream, they must have disjoint filter subjects. This is in constrast to a standard limits-based or interest-based stream which supports multiple consumers with overlapping interest.

Like the interest policy this retention policy is additive to any limits set on the stream. As a contrived example, if max-msgs is set to one with old messages being discarded, every new message that is received by the stream will result in the prior message being deleted regardless if any subscriptions were available to process the message.

In this example, we will walk through the work-queue retention setup and behavior. If you are new to streams, it is recommended to read the limits-based stream example prior to reading this one.

CLI Go Python JavaScript Rust C# C#2 Java Ruby Elixir Crystal C
Jump to the output or the recording
$ nbe run jetstream/workqueue-stream/java
View the source code or learn how to run this example yourself


package example;

import io.nats.client.*;
import io.nats.client.api.StreamConfiguration;
import io.nats.client.api.ConsumerConfiguration;
import io.nats.client.api.StreamInfo;
import io.nats.client.api.StreamState;
import io.nats.client.api.RetentionPolicy;
import io.nats.client.api.AckPolicy;

import java.time.Duration;
import java.nio.charset.StandardCharsets;

public class Main {
  public static void main(String[] args) {
    String natsURL = System.getenv("NATS_URL");
    if (natsURL == null) {
        natsURL = "nats://";

Initialize a connection to the server. The connection is AutoCloseable on exit.

    try (Connection nc = Nats.connect(natsURL)) {

Creating the stream

Initialize the JetStreamManagement context for managing JetStream assets.

      JetStreamManagement jsm = nc.jetStreamManagement();

Define the stream configuration, specifying the retention policy as WorkQueue and create it.

      StreamConfiguration sc = StreamConfiguration.builder()


      StreamInfo si = jsm.addStream(sc);
      System.out.printf("Created stream %s\n\n", si.getConfiguration().getName());


Create a JetStream context for publishing and subscribing.

      JetStream js = nc.jetStream();

      js.publish("", "time_ms: 120".getBytes(StandardCharsets.UTF_8));
      js.publish("", "x: 510, y: 1039".getBytes(StandardCharsets.UTF_8));
      js.publish("", "id: username".getBytes(StandardCharsets.UTF_8));
      System.out.println("Published 3 messages");

      StreamInfo info = jsm.getStreamInfo("EVENTS");
      long msgCount = info.getStreamState().getMsgCount();
      System.out.printf("msgs in stream: %s\n\n", msgCount);

Adding a consumer

Now let’s add a consumer. It can be a push or pull consumer, however for this example we will use pull. The first pull consumer will be bound to all subjects in the stream, since we did not specify filterSubject(...).

      ConsumerConfiguration c1 = ConsumerConfiguration.builder()

      jsm.addOrUpdateConsumer("EVENTS", c1);

Now we bind the subscription. Note that null or empty string for the subject tells the subscription to use exactly the filter subject provided by the consumer.

      PullSubscribeOptions o1 = PullSubscribeOptions.bind("EVENTS", "processor-1");
      JetStreamSubscription s1 = js.subscribe(null, o1);

Now we can get all three messages in the stream. Note, we are requesting more messages than we know exist in the stream simply to demonstrate that the pull consumer will only get the messages that are available and return null when there are no more messages.

      for (int i = 0; i < 5; i++) {
        Message msg = s1.nextMessage(Duration.ofSeconds(1));
        if (msg == null) {
        System.out.printf("Received event: %s\n", msg.getSubject());

We can confirm by checking the stream state again.

      info = jsm.getStreamInfo("EVENTS");
      msgCount = info.getStreamState().getMsgCount();
      System.out.printf("msgs in stream: %s\n\n", msgCount);

Exclusive non-filtered consumer

As noted in the description above, work-queue streams can only have at most one consumer with interest on a subject at any given time. Since this first pull consumer is not filtered, if we try to create another consumer, it will fail.

      ConsumerConfiguration c2 = ConsumerConfiguration.builder()

      try {
        jsm.addOrUpdateConsumer("EVENTS", c2);
      } catch (JetStreamApiException e) {
        System.out.printf("Failed to create an overlapping consumer:\n%s\n\n", e.getMessage());

However if we delete the first consumer, this will remove the interest and allow us to create a new consumer.

      jsm.deleteConsumer("EVENTS", "processor-1");
      System.out.println("Deleting the first consumer");

      jsm.addOrUpdateConsumer("EVENTS", c2);
      System.out.println("Succeeded to create a new consumer");
      jsm.deleteConsumer("EVENTS", "processor-2");
      System.out.println("Deleting the new consumer\n");

Multiple filtered consumers

To create multiple consumers, we need to filter the subjects. For example, we can create a consumer that only receives subjects that start with and another that only receives subjects that start with

      ConsumerConfiguration c3 = ConsumerConfiguration.builder()

      jsm.addOrUpdateConsumer("EVENTS", c3);

      PullSubscribeOptions o3 = PullSubscribeOptions.bind("EVENTS", "processor-3");

      JetStreamSubscription s3 = js.subscribe(null, o3);

      ConsumerConfiguration c4 = ConsumerConfiguration.builder()

      jsm.addOrUpdateConsumer("EVENTS", c4);

      PullSubscribeOptions o4 = PullSubscribeOptions.bind("EVENTS", "processor-4");

      JetStreamSubscription s4 = js.subscribe(null, o4);
      System.out.println("Created two filtered consumers");

      js.publish("", "time_ms: 103".getBytes(StandardCharsets.UTF_8));
      js.publish("", "x: 1040, y: 39".getBytes(StandardCharsets.UTF_8));
      js.publish("", "id: password".getBytes(StandardCharsets.UTF_8));
      System.out.println("Published 3 more messages");

      for (int i = 0; i < 2; i++) {
        Message msg = s3.nextMessage(Duration.ofSeconds(1));
        System.out.printf("Received event via 'processor-us': %s\n", msg.getSubject());

      Message msg = s4.nextMessage(Duration.ofSeconds(1));
      System.out.printf("Received event via 'processor-eu': %s\n", msg.getSubject());

      jsm.deleteConsumer("EVENTS", "processor-3");

      jsm.deleteConsumer("EVENTS", "processor-4");

    } catch (Exception e) {


Created stream EVENTS

Published 3 messages
msgs in stream: 3

Received event:
Received event:
Received event:
msgs in stream: 0

Failed to create an overlapping consumer:
multiple non-filtered consumers not allowed on workqueue stream [10099]

Deleting the first consumer
Succeeded to create a new consumer
Deleting the new consumer

Created two filtered consumers
Published 3 more messages
Received event via 'processor-us':
Received event via 'processor-us':
Received event via 'processor-eu':


Note, playback is half speed to make it a bit easier to follow.