View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003008 | NodeSets, XSDs and Generated Code | Api Change | public | 2015-03-24 16:26 | 2016-02-02 19:37 |
| Reporter | Jim Luth | Assigned To | Randy Armstrong | ||
| Priority | high | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0003008: Refresh on the Subscription was not a good idea | ||||
| Description | In OPC UA the events are provided by MonitoredItems and not by Subscriptions like in COM A&E. But the Refresh is on the Subscription in OPC UA. This is no problem as long there is only one event monitored item in the Subscription or there is only one event receiver on the client side. As soon as we have several event receivers working through the same Subscription, a Refresh from one event receiver will affect all event recievers in the client working through the same subscription. The only option would be to create seperate Subscriptions for every event receiver. But this may be a large number of subscriptions like in agregating servers. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
| related to | 0002029 | closed | Paul Hunkar | 10000-009: Alarms and Conditions | Refresh on the Subscription was not a good idea |
|
|
First discussion telco May 8, 2012: Two possible solutions: |
|
|
Agreed in telco that this will not be addressed in v1.02 |
|
|
Agreed to document the possibility of clients getting duplicate, unsolicited duplicate event notification. Document the "workaround" for clients is to use individual (multiple) subscriptions to prevent this. Agreed to include in 1.03 |
|
|
We should add a Method ConditionRefresh2(SubscriptionId, MonitoredItemId) to 1.03. This is the only good long term solution. Since the method is only defined on the ConditionType, this would not affect instances. An Alarm client can check for availability of this method and can call the old ConditionRefresh if the new one is not available. |
|
|
Aded text to explain expected behaviour is multiple monitored item are in the subscription. Did not add ConditionRefresh2. First we need to discuss how this will be compliance tested. It will be a 1.03 functionality and the CTT will need to be able to determine this and test accordingly. |
|
|
Added ConditionRefresh2 method that include the Monitored item |
|
|
Added ConditionRefresh2 |
|
|
Closing issues that were fixed in the past. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-03-24 16:26 | Jim Luth | New Issue | |
| 2015-03-24 16:26 | Jim Luth | Status | new => assigned |
| 2015-03-24 16:26 | Jim Luth | Assigned To | => Paul Hunkar |
| 2015-03-24 16:26 | Jim Luth | Issue generated from: 0002029 | |
| 2015-03-24 16:26 | Jim Luth | Relationship added | related to 0002029 |
| 2015-03-24 16:27 | Jim Luth | Project | 10000-009: Alarms and Conditions => NodeSets, XSDs and Generated Code |
| 2015-03-24 16:27 | Jim Luth | Category | Spec => Api Change |
| 2015-03-24 16:28 | Jim Luth | Status | assigned => new |
| 2015-03-24 16:28 | Jim Luth | Assigned To | Paul Hunkar => |
| 2015-04-02 07:06 | Randy Armstrong | Note Added: 0005995 | |
| 2015-04-02 07:06 | Randy Armstrong | Status | new => resolved |
| 2015-04-02 07:06 | Randy Armstrong | Resolution | open => fixed |
| 2015-04-02 07:06 | Randy Armstrong | Assigned To | => Randy Armstrong |
| 2016-02-02 19:37 | Jim Luth | Note Added: 0006653 | |
| 2016-02-02 19:37 | Jim Luth | Status | resolved => closed |
