We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When trying to read a workqueue stream, I get the following error:
nats: error: multiple non-filtered consumers not allowed on workqueue stream (10099)
The command I used:
nats stream view EVENTS # events is the name of the queue
Reference discussion: nats-io/nats-server#4778
Expected to read the messages in the stream
CLI client version: v0.1.1 NATS server version nats-server: v2.10.4
v0.1.1
nats-server: v2.10.4
Mac OS 14.1.1
Create a stream with the following config
cfg := jetstream.StreamConfig{ Name: "EVENTS", Subjects: []string{"events.>"}, Storage: jetstream.FileStorage, Retention: jetstream.WorkQueuePolicy, AllowDirect: true, }
Create a consumer using the following config
cons1, err := stream.CreateOrUpdateConsumer(ctx, jetstream.ConsumerConfig{ Name: "durable-1", Durable: "durable-1", AckPolicy: jetstream.AckExplicitPolicy, DeliverPolicy: jetstream.DeliverAllPolicy, FilterSubject: "events.>", })
Now try to read the messages using the cli.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Observed behavior
When trying to read a workqueue stream, I get the following error:
The command I used:
Reference discussion: nats-io/nats-server#4778
Expected behavior
Expected to read the messages in the stream
Server and client version
CLI client version:
v0.1.1
NATS server version
nats-server: v2.10.4
Host environment
Mac OS 14.1.1
Steps to reproduce
Create a stream with the following config
Create a consumer using the following config
Now try to read the messages using the cli.
The text was updated successfully, but these errors were encountered: