Skip to content
This repository has been archived by the owner on Nov 18, 2020. It is now read-only.

Correctly handle errors with duplicate subscription ids provided by client #5

Closed
michaelklishin opened this issue Mar 12, 2015 · 2 comments
Closed

Correctly handle errors with duplicate subscription ids provided by client #5

michaelklishin opened this issue Mar 12, 2015 · 2 comments
Assignees
@priviterag
Labels
bug effort-low
Milestone
3.5.5

Comments

@michaelklishin
Copy link
Member

Reported on the list.
Looks like a race condition.
@michaelklishin michaelklishin self-assigned this Mar 12, 2015
@michaelklishin michaelklishin added this to the 3.6.0 milestone Mar 12, 2015
@michaelklishin michaelklishin modified the milestones: n/a, 3.6.0 Sep 10, 2015
@michaelklishin
Copy link
Member Author

Clearing milestone because we couldn't reproduce this so far.

@michaelklishin michaelklishin removed this from the n/a milestone Sep 10, 2015
This was referenced Sep 14, 2015
Closed
Merged
@michaelklishin
Copy link
Member Author

We believe this is fixed by #35, will be in 3.5.5.

@michaelklishin michaelklishin added this to the 3.5.5 milestone Sep 16, 2015
@michaelklishin michaelklishin mentioned this issue Sep 16, 2015
Closed
@michaelklishin michaelklishin changed the title Client reconnection fail with a duplicate consumer tag Correctly handle errors with duplicate subscription ids provided by client Sep 16, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@priviterag priviterag

Labels
bug effort-low
Projects
None yet
Milestone
3.5.5
Development

No branches or pull requests
2 participants
@michaelklishin @priviterag