View Issue Details

IDProjectCategoryView StatusLast Update
000806510000-007: ProfilesSpecpublic2022-08-23 15:36
ReporterJim Luth Assigned ToKarl Deiretsbacher  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Target Version1.05.02Fixed in Version1.05.02 RC1 
Summary0008065: Add MaxMonitoredItemsQueueSize to capabilities
Description

This was raised in the UA meeting on Dec 14, 2021.

Such a queue may reduce the frequency of publish requests but is particularly relevant for durable subsciptions.

Additional Information

When implemented, the issue needs to be cloned to Part 7 to add an appropriate capability CU.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0007474 closedJeff Harding 10000-005: Information Model Add MaxMonitoredItemsQueueSize to capabilities 

Activities

Jeff Harding

2022-06-21 15:13

developer   ~0016953

The description suggests this is useful for durable subscriptions but it isn't clear if the writer intended it to only be for the in memory queue or also the lifetime of non-volatile queues.
Do we want to define 2 Properties here?

  • MaxMonitoredItemsQueueSize - This would describe the normal maximum size of a monitored item.
  • MaxDurableSubscriptionLifetime - This would describe the normal maximum lifetime, in hours, of a durable subscription.

Jeff Harding

2022-06-21 15:13

developer   ~0016954

Comments from Karl,

We have not talked about the lifetime but for me it makes sense to add this property also.

I wonder if we also need two queueSize properties. One for "normal" subscriptions (there it will be a handful as it is kept in memory) and one for durable subscriptions. Servers will often use disk space for queues of durable subscriptions and may support large queue sizes.

Jeff Harding

2022-06-21 15:13

developer   ~0016955

Add MaxMonitoredItemsQueueSize to ServerCapabilitiesType

Jim Luth

2022-06-21 15:14

administrator   ~0016956

Need to add a CU for MaxMonitoredItemsQueueSize

Karl Deiretsbacher

2022-06-22 10:44

developer   ~0016975

Created a new CU in the profile database (https://profiles.opcfoundation.org/conformanceunit/4055).
Added this CU to Embedded DataChange Subscription 2022 Server Facet (https://profiles.opcfoundation.org/profile/1323) and to Standard Event Subscription 2022 Server Facet (https://profiles.opcfoundation.org/profile/1483).

Jim Luth

2022-08-23 15:36

administrator   ~0017366

Agreed to changes in the database.

Issue History

Date Modified Username Field Change
2022-06-21 15:13 Jim Luth New Issue
2022-06-21 15:13 Jim Luth Status new => assigned
2022-06-21 15:13 Jim Luth Assigned To => Karl Deiretsbacher
2022-06-21 15:13 Jim Luth Issue generated from: 0007474
2022-06-21 15:13 Jim Luth Note Added: 0016953
2022-06-21 15:13 Jim Luth Note Added: 0016954
2022-06-21 15:13 Jim Luth Note Added: 0016955
2022-06-21 15:13 Jim Luth Relationship added related to 0007474
2022-06-21 15:14 Jim Luth Project 10000-005: Information Model => 10000-007: Profiles
2022-06-21 15:14 Jim Luth Note Added: 0016956
2022-06-22 10:44 Karl Deiretsbacher Status assigned => resolved
2022-06-22 10:44 Karl Deiretsbacher Resolution open => fixed
2022-06-22 10:44 Karl Deiretsbacher Note Added: 0016975
2022-08-23 15:36 Jim Luth Status resolved => closed
2022-08-23 15:36 Jim Luth Fixed in Version => 1.05.02 RC1
2022-08-23 15:36 Jim Luth Note Added: 0017366