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

durable and persistent headers aren't always used interchangeably, leading to non-durable subscriptions #58

Closed
michaelklishin opened this issue Feb 15, 2016 · 1 comment
Closed

durable and persistent headers aren't always used interchangeably, leading to non-durable subscriptions #58

michaelklishin opened this issue Feb 15, 2016 · 1 comment
Assignees
@michaelklishin
Labels
bug effort-low usability
Milestone
3.6.1

Comments

@michaelklishin
Copy link
Member

See this rabbitmq-users thread. When durable was introduced as an alias for persistent, we didn't update UNSUBSCRIBE frame handler to support both.
@michaelklishin michaelklishin self-assigned this Feb 15, 2016
@michaelklishin michaelklishin added this to the 3.6.1 milestone Feb 15, 2016
michaelklishin added a commit that referenced this issue Feb 15, 2016
@michaelklishin
Use 'durable' and 'persistent' interchangeably in more places
849594b 
Fixes #58.
@michaelklishin michaelklishin mentioned this issue Feb 15, 2016
Merged
michaelklishin added a commit that referenced this issue Feb 15, 2016
@michaelklishin
Use 'durable' and 'persistent' interchangeably in more places
2eb3fd2 
Fixes #58.
@michaelklishin michaelklishin mentioned this issue Feb 18, 2016
Closed
@michaelklishin michaelklishin mentioned this issue Feb 20, 2016
Closed
@michaelklishin
Copy link
Member Author

I should clarify that this issue affected more than UNSUBSCRIBE frames and could result in queue name being server-generated where it shouldn't have been (depends on the destination kind used).

@michaelklishin michaelklishin changed the title Support both persistent and durable headers for UNSUBSCRIBE frames durable and persistent headers aren't always used interchangeably, leading to non-durable subscriptions Feb 20, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@michaelklishin michaelklishin

Labels
bug effort-low usability
Projects
None yet
Milestone
3.6.1
Development

No branches or pull requests
1 participant
@michaelklishin