View Issue Details

IDProjectCategoryView StatusLast Update
000343710000-004: ServicesSpecpublic2016-12-15 22:28
ReporterNathan PocockAssigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.03 
Summary0003437: 5.4.6.3 RegisterServer2: How to achieve Bad_NotSupported?
Description

CMPWG May-19-2016:

In what circumstance would you receive Bad_NotSupported for RegisterServer2?

If an older LDS receives this request, it would not understand a RegisterServer2 so it would not return this code. If a newer LDS, then it came from the OPCF and presumably would have this service implemented.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2016-05-31 18:08

administrator   ~0006973

We believe that as call to an old LDS that does not implement RegisterServer2 would return Bad_NotSupported. Part 4 should specify a specific return code to be returned when a client calls an unknown or unimplemented service. (We think Part 4 is currently silent on this).

Matthias Damm

2016-12-09 17:13

developer   ~0007477

There is nothing wrong and nothing missing:

(1) Bad_ServiceUnsupported is the general service fault for not implemented. This is exactily mentioned in the description:
Servers that support RegisterServer2 shall try to register with the Discovery Server using this Service and shall fall back to RegisterServer if RegisterServer2 fails with the status Bad_ServiceUnsupported.

(2) Bad_NotSupported is an operation level result code. It is mentioned in the description of parameter discoveryConfiguration:
Discovery Servers that do not understand a configuration shall return Bad_NotSupported for this configuration.

The only thing that I enhanced was the splitting of the status code tables in service codes and operation level codes like we have it for other services.

Made changes in document version OPC UA Part 4 - Services 1.04 Specification Draft 02.docx

Jim Luth

2016-12-15 22:28

administrator   ~0007584

agreed to changes in meeting.

Issue History

Date Modified Username Field Change
2016-05-19 16:48 Nathan Pocock New Issue
2016-05-31 18:08 Jim Luth Note Added: 0006973
2016-05-31 18:08 Jim Luth Assigned To => Matthias Damm
2016-05-31 18:08 Jim Luth Status new => assigned
2016-05-31 18:09 Jim Luth Target Version => 1.04
2016-12-09 17:13 Matthias Damm Note Added: 0007477
2016-12-09 17:13 Matthias Damm Status assigned => resolved
2016-12-09 17:13 Matthias Damm Resolution open => fixed
2016-12-15 22:28 Jim Luth Note Added: 0007584
2016-12-15 22:28 Jim Luth Status resolved => closed
2016-12-15 22:28 Jim Luth Fixed in Version => 1.04