0006173: Subscription Services/Subscription Minimum 02/003

ID	Project	Category	View Status	Date Submitted	Last Update

0006173	CTT UA Scripts	1 - Script Issue	public	2020-10-23 12:45	2022-08-25 03:09

Reporter	Frank Fischer	Assigned To	Alexander Allmendinger
Priority	normal	Severity	major	Reproducibility	sometimes
Status	assigned	Resolution	open
Platform	PC	OS	Windows	OS Version	7

Summary	0006173: Subscription Services/Subscription Minimum 02/003
Description	This testcase basically writes to subscribed values, waits until the Subscription is read to publish values and then sends a PublishRequest. This Request should not be enqueued but served immediately by the correct Subscription. However the script uses PublishHelper.WaitInterval to wait, this function waits for the highest PublishingInterval OR SamplingInterval, but to be sure the Subscription must publish immediately the script would need to wait for the SamplingInterval to expire and afterwards the PublishingInterval to expire. A server does not need to synchronize these intervals, so in the worst case this can take the SamplingInterval PLUS PublishingInterval. It should be reviewed what the intended purpose of PublishHelper.WaitInterval is and whether it is broken or if it is just the wrong function to use in this script.
Steps To Reproduce	One affected server is the HP Demoserver, run this testcase with a SamplingInterval of 50ms and a PublishingInterval of 250ms multiple times (like 20), then the testcase should succeed most of the time but fail sporadically.
Tags	No tags attached.

Files Affected

Paul Hunkar 2020-11-12 16:36 administrator ~0013189	This issue need to be discussed in a UA Meeting (the error code Bad_WaitingForInitialValue and the the paragraph in 7.20.2 DataChangeNotification parameter ) seem to be interpreted differently. Also section 5.13.1.1 - see "When a Subscription is created, the first Message is sent at the end of the first publishing cycle to inform the Client that the Subscription is operational. " also see section 5.12.1.3 Monitoring mode - "the Server shall report the first sample as soon as possible and the time of this sample becomes the starting point for the next sampling interval." This need to be discussed from the client point of view and what a client can expect

Paul Hunkar 2020-11-12 16:36 administrator ~0013190	waiting for UA group discussion

Frank Fischer 2020-11-13 09:12 reporter ~0013194	The Problem is not the initial data change as the order of the first PublishResponses is ignored (these would have the same problem if checked though), but after the the initial data changes the script uses a WriteRequest to trigger further data changes which are checked for the correct order.

Date Modified	Username	Field	Change
2020-10-23 12:45	Frank Fischer	New Issue
2020-11-12 16:36	Paul Hunkar	Note Added: 0013189
2020-11-12 16:36	Paul Hunkar	Assigned To	=> Paul Hunkar
2020-11-12 16:36	Paul Hunkar	Status	new => acknowledged
2020-11-12 16:36	Paul Hunkar	Note Added: 0013190
2020-11-13 09:12	Frank Fischer	Note Added: 0013194
2021-04-12 09:53	Sebastian Allmendinger	Relationship added	duplicate of 0004874
2022-08-05 15:15	Paul Hunkar	Assigned To	Paul Hunkar => Alexander Allmendinger
2022-08-05 15:15	Paul Hunkar	Status	acknowledged => assigned
2022-08-25 03:09	Paul Hunkar	Project	Compliance Test Tool (CTT) Unified Architecture => CTT UA Scripts