View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001627 | 10000-007: Profiles | public | 2011-05-03 17:45 | 2012-01-11 15:38 | |
Reporter | Randy Armstrong | Assigned To | Paul Hunkar | ||
Priority | high | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0001627: Handling of MonitoredItem changes in short network interuption scenarios | ||||
Description | The following situation is a problem in normal and in transparent server redundancy setups: It is stronly recommended by OPC UA that a client is reusing a Subscription after a short network interuption by activating the existing Session with the new SecureChannel. If a client called CreateMonitoredItems during the network interuption and the call succeeded in the server but did not return to the client, the client does not know if the call succeded. He may receive data changes for these monitored items but he is not able to remove them since he does not know the server handle for the monitored item. There is also no way for the client to detect if the create succeeded. To delete and recreate the subscription is also no option since there may be several monitored items operating normally that should not be interupted. | ||||
Additional Information | Telco March 7, 2011 Discussed resolution through a Method on the Server object getMonitoredItems( | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
child of | 0001543 | closed | Wolfgang Mahnke | 10000-005: Information Model | Handling of MonitoredItem changes in short network interuption scenarios |
|
The method GetMonitoredItems is optional in Part 5 since it is a new Method and we need to keep backward compatibility. The Standard Server Profile should make this Method mandatory. |
|
Make this conformance unit required for subscriptions |
|
Added Conformance Units for this feature, but still need decide what profile(s) will include them. |
|
Added new conformance Unit Updated description to of profile to include that the optional conformance unit is ighly recommended and that in a future revision of the profile it will become manditory, that it is optional only for backward compatability |
|
Reviewed and agreed to in Boca Meeting. |
Date Modified | Username | Field | Change |
---|---|---|---|
2011-05-03 17:45 | Randy Armstrong | New Issue | |
2011-05-03 17:45 | Randy Armstrong | Issue generated from: 0001543 | |
2011-05-03 17:45 | Randy Armstrong | Relationship added | child of 0001543 |
2011-05-03 17:45 | Randy Armstrong | Project | 10000-005: Information Model => 10000-007: Profiles |
2011-05-10 16:17 | Randy Armstrong | Status | new => assigned |
2011-05-10 16:17 | Randy Armstrong | Assigned To | => Paul Hunkar |
2011-05-23 18:17 | Matthias Damm | Note Added: 0002756 | |
2011-08-16 16:23 | Paul Hunkar | Note Added: 0002837 | |
2012-01-02 16:34 | Paul Hunkar | Note Added: 0003118 | |
2012-01-05 08:17 | Paul Hunkar | Status | assigned => resolved |
2012-01-05 08:17 | Paul Hunkar | Resolution | open => fixed |
2012-01-05 08:17 | Paul Hunkar | Note Added: 0003136 | |
2012-01-11 15:38 | Jim Luth | Status | resolved => closed |
2012-01-11 15:38 | Jim Luth | Note Added: 0003165 |