`NATS: Subject must be supplied` when `msg.ack`
See original GitHub issueI am getting this very weird situation in which sometimes I get NATS: Subject must be supplied
when ack’ing a message. It goes away after restart. The weird part is that the connection is stable and I do receive messages on the subscription. But when this happens the instance cannot ack a message any longer, it always fail with this until I restart it.
Any idea what my be causing this?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:27 (17 by maintainers)
Top Results From Across the Web
Client Protocol - NATS Docs
The wire protocol used to communicate between the NATS server and clients is a simple, text-based publish/subscribe style protocol.
Read more >Connection (java-nats-streaming 0.2.1 API) - javadoc.io
Publishes the payload specified by data to the subject specified by subject and asynchronously processes the ACK or error state via the supplied...
Read more >Network.Nats.Message.Message - Hackage
The PUB message publishes the message payload to the given subject name. If a reply subject is supplied, it will be delivered to...
Read more >NATS Messaging - ThinkMicroservices.com
This wildcard must be the last character in the subject. ... nats bench --ack --msgs 10000 ORDERS.bench # benchmark core nats publish and ......
Read more >Modules - NATS Docs
async def subscribe_handler(msg): subject = msg.subject reply = msg.reply data = msg.data.decode() ... ack acknowledges a message delivered by JetStream.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hm… we observe this on subscriptions that were active and running for days without issues, but suddenly we starte getting those errors that do not go away unless restarting.
@nazar-pc looks like there has not been a resurgence of this issue. If you see it happening again, please reopen.