View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002920Compliance Test Tool (CTT) Unified Architecture3 - Feature Requestpublic2014-12-19 18:462019-07-25 14:50
ReporterJim Luth Assigned ToAlexander Allmendinger  
PrioritynormalSeveritytweakReproducibilitysometimes
Status closedResolutionfixed 
Target Version1.03.341.384Fixed in Version1.03.341.384 
Summary0002920: BadWaitingForInitialData should be valid for reenabling subscriptions
Description

While BadWaitingForInitialData is a valid return while creating a subscription (Part 4 Table 166) it seems that it is not valid for activating it (after subscription was suspended).

Since the underlaying system might take a while for retrieving data not only during creation time but also during suspend/reactivate, from my PointOfView it would make sense to allow BadWaitingForInitialData also for activation of subscriptions.

Steps To Reproduce

CTT tests behavior with MonitoredItemServices=>Monitor MinQueueSize_02=>005.js (and others)

Additional Information

Discussed with NathanP by mail

TagsNo tags attached.
Files Affected

Relationships

related to 0002830 closedMatthias Damm 10000-004: Services BadWaitingForInitialData sould be valid for reenabling subscriptions 

Activities

Matthias Damm

2014-12-19 18:46

reporter   ~0005698

The problem is that the monitoring mode is set to Disabled and changed back to Reporting. The initial DataValue in this case is BadWaitingForInitialData. We need to clarify if this one is delivered to the clients or if the behavior should be like when a monitored item is created. In this case BadWaitingForInitialData is the initial data value of the monitored item and it is not delivered.

Matthias Damm

2014-12-19 18:46

reporter   ~0005699

Table 166 – Common Operation Level Result Codes<br>
Bad_WaitingForInitialData<br>
In the description this status code is allowed after creating a monitored item. Added:<br>
After creating a MonitoredItem 'or after setting the MonitoringMode from DISABLED to REPORTING or SAMPLING',

Nathan Pocock

2016-02-12 18:03

viewer   ~0006719

Revised per recommendation.
Fix will be in the next release.
Will close upon validation from third party.

Paul Hunkar

2018-11-09 16:06

administrator   ~0009564

Last edited: 2018-11-09 16:06

The fix is looking for the BadWaitingForInitialData in the wrong location - it is not the service result, but the monitored item that can return BadWaitingForInitialData

Alexander Allmendinger

2019-01-04 17:53

developer   ~0009782

Changed to check the StatusCode of the MonitoredItem instead of the ServiceResult.

Paul Hunkar

2019-07-25 14:50

administrator   ~0010593

Reviewed in CMP call

Issue History

Date Modified Username Field Change
2014-12-19 18:46 Jim Luth New Issue
2014-12-19 18:46 Jim Luth Status new => assigned
2014-12-19 18:46 Jim Luth Assigned To => Matthias Damm
2014-12-19 18:46 Jim Luth Issue generated from: 0002830
2014-12-19 18:46 Jim Luth Relationship added related to 0002830
2014-12-19 18:47 Jim Luth Project 10000-004: Services => Compliance Test Tool (CTT) Unified Architecture
2014-12-19 18:47 Jim Luth Category Spec => Api Change
2014-12-19 18:48 Jim Luth Assigned To Matthias Damm =>
2014-12-19 18:48 Jim Luth Status assigned => new
2015-01-21 20:55 Nathan Pocock Assigned To => Nathan Pocock
2015-01-21 20:55 Nathan Pocock Status new => acknowledged
2015-01-21 20:55 Nathan Pocock Product Version 1.02 =>
2015-01-21 20:55 Nathan Pocock Target Version => 1.02.336.273
2015-01-21 20:55 Nathan Pocock Summary BadWaitingForInitialData sould be valid for reenabling subscriptions => BadWaitingForInitialData should be valid for reenabling subscriptions
2016-02-12 18:03 Nathan Pocock Note Added: 0006719
2016-02-12 18:03 Nathan Pocock Status acknowledged => resolved
2016-02-12 18:03 Nathan Pocock Resolution open => fixed
2018-11-09 16:04 Paul Hunkar Assigned To Nathan Pocock => Alexander Allmendinger
2018-11-09 16:04 Paul Hunkar Status resolved => assigned
2018-11-09 16:06 Paul Hunkar Note Added: 0009564
2018-11-09 16:06 Paul Hunkar Note Edited: 0009564
2019-01-04 16:08 Paul Hunkar Category Api Change => Feature Request
2019-01-04 16:08 Paul Hunkar Target Version 1.02.336.273 => 1.03.341.384
2019-01-04 17:53 Alexander Allmendinger Note Added: 0009782
2019-01-04 17:53 Alexander Allmendinger Status assigned => resolved
2019-01-04 17:53 Alexander Allmendinger Fixed in Version => 1.03.341.384
2019-01-28 14:14 Paul Hunkar Category Feature Request => 3 - Feature Request
2019-07-25 14:50 Paul Hunkar Status resolved => closed
2019-07-25 14:50 Paul Hunkar Note Added: 0010593