View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000631010000-004: ServicesSpecpublic2020-12-10 17:272021-03-01 18:52
ReporterAlexander Allmendinger Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0006310: Clarify expected behavior when ModifySubscription is called on a durable subscription
Description

In order to describe the expected behavior for a ModifySubscription service call on a durable subscription, the specification needs to be updated to describe the correlation of the parameter lifetimeInHours of the SetSubscriptionDurable method call and the LifetimeCount of a Subscription.
It is expected that the ModifySubscription call is being executed as requested by the client and the server tries to honor the requested parameter. The Subscription in this case will stay in durable mode and the server may revise the parameters accordingly.

Additional Information

See:
Part 4 - 6.8 Durable Subscriptions
Part 4 - 5.13.3 ModifySubscription

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0006312 closedAlexander Allmendinger Compliance Test Tool (CTT) Unified Architecture Clarify expected behavior when ModifySubscription is called on a durable subscription 

Activities

Matthias Damm

2020-12-11 15:27

developer   ~0013462

Added clarification to 6.8 Durable Subscriptions

The revisedLifeTimeInHours is used to set the LifeTimeCount of the Subscription.
ModifySubscription can be used to change the parameters of the durable Subscription. If the Client would like to keep the previous life time setting, the Client needs to calculate the LifeTimeCount based on the revisedLifeTimeInHours and the PublishingInterval. ModifySubscription does not change the durable mode of the Subscription.

Jim Luth

2020-12-11 15:29

administrator   ~0013464

Agreed to text in 1.05 text in Virtual F2F.
Needs 1.04 Errata to close.

Jim Luth

2021-03-01 18:52

administrator   ~0013860

Agreed to 1.04 Errata in Virtual F2F.

Issue History

Date Modified Username Field Change
2020-12-10 17:27 Alexander Allmendinger New Issue
2020-12-11 15:27 Matthias Damm Assigned To => Matthias Damm
2020-12-11 15:27 Matthias Damm Status new => resolved
2020-12-11 15:27 Matthias Damm Resolution open => fixed
2020-12-11 15:27 Matthias Damm Note Added: 0013462
2020-12-11 15:27 Jim Luth Issue cloned: 0006312
2020-12-11 15:27 Jim Luth Relationship added related to 0006312
2020-12-11 15:29 Jim Luth Note Added: 0013464
2021-03-01 18:52 Jim Luth Status resolved => closed
2021-03-01 18:52 Jim Luth Fixed in Version => 1.05
2021-03-01 18:52 Jim Luth Note Added: 0013860