Unsubscribed topic, repeatedly kicked out using client connection only.

Open
#990 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
networking

Research direction

No source file, test, or entry point is named. Start by reproducing the two reported steps with the MQTT client connection and inspect the broker-connection-loss behavior shown in the screenshots. Done means the client no longer gets repeatedly disconnected for an unsubscribed topic, with the expected behavior covered by a regression test.

Written by the indexing model from the issue text.

Description

step1: Mop service built using MQTT client connection.
step2: The client waits for 2 seconds and prompts Broker connection loss: Resting client.
1686728247220
1686728266288

Dominant language
Java
Stars
190
Forks
56
Avg merge
27m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from streamnative/mop

All issues in streamnative/mop

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.