Problem
The listener currently only listens once and can only receive a single message, instead of remaining active to receive subsequent messages.
Expected Behavior
The listener should continuously listen and receive multiple messages as they are published without stopping after the first one.
Steps to Reproduce
- Set up a listener in the pubsub framework.
- Publish multiple messages.
- Observe the listener only processes the first message, then stops.
Additional Context
This behavior limits the usability of pubsub in persistent or streaming message scenarios. Continuous listening is required for many real-world applications.
Suggestions
- Investigate the subscription or message handling logic that could cause the listener to exit after the first message.
- Refactor so the listener maintains an active state and catches all messages until explicitly stopped.
Problem
The listener currently only listens once and can only receive a single message, instead of remaining active to receive subsequent messages.
Expected Behavior
The listener should continuously listen and receive multiple messages as they are published without stopping after the first one.
Steps to Reproduce
Additional Context
This behavior limits the usability of pubsub in persistent or streaming message scenarios. Continuous listening is required for many real-world applications.
Suggestions