View Issue Details

IDProjectCategoryView StatusLast Update
000283010000-004: ServicesSpecpublic2014-12-19 18:49
ReporterHenning Mersch Assigned ToMatthias Damm  
PrioritynormalSeveritytweakReproducibilitysometimes
Status closedResolutionfixed 
Product Version1.02 
Fixed in Version1.03 
Summary0002830: BadWaitingForInitialData sould 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.
Commit Version
Fix Due Date

Relationships

related to 0002920 closedAlexander Allmendinger Compliance Test Tool (CTT) Unified Architecture BadWaitingForInitialData should be valid for reenabling subscriptions 

Activities

Matthias Damm

2014-11-18 09:36

developer   ~0005620

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-16 13:14

developer   ~0005689

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',

Jim Luth

2014-12-19 18:49

administrator   ~0005700

Reviewed in Tuesday telecon and agreed to close.

Issue History

Date Modified Username Field Change
2014-08-25 10:26 Henning Mersch New Issue
2014-11-17 20:57 Matthias Damm Assigned To => Matthias Damm
2014-11-17 20:57 Matthias Damm Status new => assigned
2014-11-18 09:36 Matthias Damm Note Added: 0005620
2014-12-16 13:14 Matthias Damm Note Added: 0005689
2014-12-16 13:14 Matthias Damm Status assigned => resolved
2014-12-16 13:14 Matthias Damm Resolution open => fixed
2014-12-19 18:46 Jim Luth Issue cloned: 0002920
2014-12-19 18:46 Jim Luth Relationship added related to 0002920
2014-12-19 18:49 Jim Luth Note Added: 0005700
2014-12-19 18:49 Jim Luth Status resolved => closed
2014-12-19 18:49 Jim Luth Fixed in Version => 1.03