Confirmed Message Ack in JetStream
A confirmed message ack means that the client waits for an ack from the server to ensure that the ack was received and processed. The functionality can be found in various clients under the following:
Name | Clients |
---|---|
ack ack | Javascript |
double ack | Rust, C# .NET V2 |
ack sync | Go, Python, Java, C |
Code
package example;
import io.nats.client.*;
import io.nats.client.api.ConsumerConfiguration;
import io.nats.client.api.ConsumerInfo;
import io.nats.client.api.StorageType;
import io.nats.client.api.StreamConfiguration;
import java.io.IOException;
import java.time.Duration;
import java.util.concurrent.TimeoutException;
public class Main {
public static void main(String[] args) {
String natsURL = System.getenv("NATS_URL");
if (natsURL == null) {
natsURL = "nats://127.0.0.1:4222";
}
try (Connection nc = Nats.connect(natsURL)) {
JetStreamManagement jsm = nc.jetStreamManagement();
JetStream js = jsm.jetStream();
Create a stream (remove the stream first so we have a clean starting point)
try { jsm.deleteStream("verifyAckStream"); } catch (JetStreamApiException e) {}
jsm.addStream(StreamConfiguration.builder()
.name("verifyAckStream")
.subjects("verifyAckSubject")
.storageType(StorageType.Memory)
.build());
Publish a couple messages so we can look at the state
js.publish("verifyAckSubject", "A".getBytes());
js.publish("verifyAckSubject", "B".getBytes());
Consume a message with 2 different consumers The first consumer will (regular) ack without confirmation The second consumer will ackSync which confirms that ack was handled.
StreamContext sc = nc.getStreamContext("verifyAckStream");
ConsumerContext cc1 = sc.createOrUpdateConsumer(ConsumerConfiguration.builder().filterSubject("verifyAckSubject").build());
ConsumerContext cc2 = sc.createOrUpdateConsumer(ConsumerConfiguration.builder().filterSubject("verifyAckSubject").build());
Consumer 1, regular ack
ConsumerInfo ci = cc1.getConsumerInfo();
System.out.println("Consumer 1");
System.out.println(" Start\n # pending messages: " + ci.getNumPending() + "\n # messages with ack pending: " + ci.getNumAckPending());
Message m = cc1.next();
ci = cc1.getConsumerInfo();
System.out.println(" After received but before ack\n # pending messages: " + ci.getNumPending() + "\n # messages with ack pending: " + ci.getNumAckPending());
m.ack();
Thread.sleep(100); // to give time for the ack to be completed on the server
ci = cc1.getConsumerInfo();
System.out.println(" After ack\n # pending messages: " + ci.getNumPending() + "\n # messages with ack pending: " + ci.getNumAckPending());
Consumer 2, ackAck
ci = cc2.getConsumerInfo();
System.out.println("Consumer 2");
System.out.println(" Start\n # pending messages: " + ci.getNumPending() + "\n # messages with ack pending: " + ci.getNumAckPending());
m = cc2.next();
ci = cc2.getConsumerInfo();
System.out.println(" After received but before ack\n # pending messages: " + ci.getNumPending() + "\n # messages with ack pending: " + ci.getNumAckPending());
m.ackSync(Duration.ofMillis(500));
ci = cc2.getConsumerInfo();
System.out.println(" After ack\n # pending messages: " + ci.getNumPending() + "\n # messages with ack pending: " + ci.getNumAckPending());
}
catch (InterruptedException | IOException | JetStreamApiException | JetStreamStatusCheckedException | TimeoutException e) {
e.printStackTrace();
}
}
}
Output
Consumer 1 Start # pending messages: 2 # messages with ack pending: 0 After received but before ack # pending messages: 1 # messages with ack pending: 1 After ack # pending messages: 1 # messages with ack pending: 0 Consumer 2 Start # pending messages: 2 # messages with ack pending: 0 After received but before ack # pending messages: 1 # messages with ack pending: 1 After ack # pending messages: 1 # messages with ack pending: 0
Recording
Note, playback is half speed to make it a bit easier to follow.