romanettandClaude Opus 5 8e874d073b Revise event monitored item queueSize 0/1 per Part 4 §7.21 (fixes CTT Auditing Connections) (#4480)
## Problem

CTT **Auditing Connections** (CTT 1.05.06, scripts 1.05.513,
`ConsoleReferenceServer --ctt -a`) fails nondeterministically:

- `TestFindActualFromExpected - Unable to Find Entry for
ClientAuditEntryId <id>` (011.js, 012.js, 007.js, 020.js, varying by
run)
- `TestFindActualFromExpected - Unable to Find an Entry for
AuditEventType: i=2060` (and i=2069/i=2071), reported as Not Supported

## Root cause

The CTT audit subscription (`library/Base/auditThread.js`) monitors
`Server.EventNotifier` with the CTT's default `QueueSize = 1` and a 250
ms publishing interval. For **event** monitored items Part 4 §7.21
defines queueSize 0 as "the Server default" and 1 as "the minimum queue
size the Server requires for Event Notifications". `EventManager` only
clamped the maximum and `MonitoredItem.InitializeQueue` mapped only 0 to
1000, so 1 became a literal one-entry discard-oldest queue
(`RevisedQueueSize = 1`).

A single connect raises OpenSecureChannel, CreateSession,
ActivateSession and CloseSession audit events within milliseconds, and
in `--ctt` mode alarm events share the queue. Every event except the
last one raised between two publishes was dropped and replaced by an
`EventQueueOverflowEventType`.

The audit event content itself was correct. The events that survived
carried exactly the `ClientAuditEntryId` the CTT put in
`RequestHeader.AuditEntryId`.

## Evidence (instrumented CTT copy logging `Test.Audit.GetBuffer()`)

| Server | RevisedQueueSize | CTT buffer | Auditing group result |
| --- | --- | --- | --- |
| master | 1 | 16 events, **7 × i=3035 EventQueueOverflow**, 0 ×
OpenSecureChannel (2060), 0 × CloseSession (2069) | 18 pass, 2 Error + 1
NotSupported (007/020/001) |
| this PR | 1000 | 42 events, no overflow, every expected audit type
present | 21 pass, 0 errors (official project, uninstrumented) |

Each gap in the master buffer is followed by an overflow event. For
example, OpenSecureChannel at .553 is overwritten by CreateSession at
.617, and CloseSession at 08.307 by CloseSecureChannel at 08.312.

## Fix

- `EventManager.CalculateRevisedQueueSize`: requested queueSize 0 and 1
are revised to the new `EventManager.DefaultEventQueueSize` (1000), then
limited by `MaxEventQueueSize`/`MaxDurableEventQueueSize`. This applies
on create, modify and restore, so `RevisedQueueSize` reports the real
size.
- `MonitoredItem.InitializeQueue`/`RestoreQueue`: event items with
queueSize ≤ 1 use the same default. Previously only 0 did; data change
behaviour is unchanged.

## Tests

- New `EventManagerTests`: revision of 0/1, clamping to max, modify with
1, and a behavioural test that a 3-event burst on a `QueueSize = 1` item
publishes all 3. Before the fix it published 2: the last event plus the
overflow event.
- `Opc.Ua.Server.Tests`: 5558 passed / 0 failed (net10.0)
- `Opc.Ua.Subscriptions.Tests`: 619 passed / 0 failed / 6 skipped
(net10.0)
- `Opc.Ua.Core.Security.Tests` (Audit filter): 88 passed / 0 failed / 3
skipped

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-09-14 10:15:21 +02:00
…

OPC UA .NET Standard Stack

Release NuGet Downloads Build Tests Coverage

🆕 This is version 2.0 of the OPC UA .NET Standard Stack (current master).

Looking for the supported 1.x release? It lives on the master378 branch (last release: 1.5.378). All new feature work happens here on master; master378 continues to receive security and critical-bug fixes for the 1.x line.

The official OPC Foundation reference implementation of OPC UA for .NET — a certified, cross-platform stack with client, server, PubSub, GDS, complex types, and source-generated tooling. Used in production across industrial control, manufacturing, energy, and IoT systems.

📦 What it is

  • A full-stack OPC UA implementation — Core / Client / Server / PubSub / GDS / LDS / Complex Types / Device Integration / Positioning libraries built on .NET, with UA-TCP and HTTPS transports.
  • Cross-platform — runs on .NET 10, .NET 9, .NET 8 (LTS), .NET Framework 4.8, and .NET Standard 2.1; ships Native-AOT-friendly assemblies.
  • Certified for compliance — the reference server has been certified through an OPC Foundation Certification Test Lab and is continuously verified against the latest Compliance Test Tool (CTT).
  • Companion-spec coverage — Part 9 (Alarms & Conditions), Part 11 (Historical Access), Part 13 (Aggregates), Part 16 (State Machines), Part 17 (Alias Names), Part 18 (Role Management), Part 20 (File Transfer), Part 100 (Device Integration), Parts 210/211 (Relative Spatial Location and Global Positioning), OPC-10030 (ISA-95 Common Model) with OPC-10031-4 Job Control V1/V2, OPC 30270 / OPC UA for Asset Administration Shell V2 and V3, OPC 10100-1 (WoT Connectivity), OPC 40001-1 (Industrial Automation), OPC 40010-1 (Robotics).
  • Modern developer surface — first-class Microsoft.Extensions.DependencyInjection hosting (services.AddOpcUa()), fluent server + client builders, source-generated NodeManagers and DataTypes, and an MCP server so LLMs / Copilot can drive an OPC UA client.

For the full feature breakdown see OPC UA Profiles and Facets and the What's New in 2.0 tour.

🚀 Getting started

You need the .NET 10 SDK to build the repo. From the repository root:

dotnet restore UA.slnx
dotnet build UA.slnx

For the supported target frameworks and platform notes see the Developer Guide. The official NuGet packages are published to nuget.org under the OPCFoundation.NetStandard prefix — the meta package OPCFoundation.NetStandard.Opc.Ua pulls in everything, or reference individual packages directly, e.g. OPCFoundation.NetStandard.Opc.Ua.Client for clients or OPCFoundation.NetStandard.Opc.Ua.Server for servers. Preview builds from every successful master build are available from the GitHub Packages NuGet feed. Official public 2.0 preview releases are also on nuget.org. Enable prerelease packages and use 2.0.0-preview.* to float to the latest published 2.0.0-preview.N release.

Samples

The stack also includes a large collection of platform-independent sample applications that turn its core services and companion models into runnable client/server workflows. More applications, including platform-specific examples, are available in the companion OPC UA .NET Samples repository.

Developer tools

  • OPC UA MCP Server — installable .NET tool and container that exposes OPC UA client operations as MCP tools for LLMs and Copilot. The tools also ship as libraries (…Opc.Ua.Mcp.Core, .PubSub, .Diagnostics, .PubSub.Diagnostics) so an application can embed them next to its own MCP tools.

🔧 Migrating from 1.5.378 to 2.0

The 2.0 release introduces breaking API changes, and comes with a full prescriptive migration guide that links to per-area documentation for the migration sub-topics.

Most of the mechanical migration work is automated:

  • OPCFoundation.NetStandard.Opc.Ua.MigrationAnalyzer NuGet — install it in your project to get 26 analyzer rules through UA0030 (excluding UA0013, UA0016, UA0017, and the shim-only UA0029) plus one-click code fixes for the patterns in the guide. Setup steps are in the package's NugetREADME.md.
  • Migration agent skill — the opcua-v20-migration skill walks Copilot / Claude / any coding agent through installing the NuGet, running dotnet format analyzers to apply auto-fixes, and handling the small residual manual patterns. The skill knows which sub-doc to load for each symptom so it stays context-efficient.

Copilot CLI discovers the skill automatically inside a clone. To install it for use in any repository:

copilot plugin marketplace add OPCFoundation/UA-.NETStandard
copilot plugin install opcua-v20-migration@opcua-dotnet

If you are still on 1.x and not ready to upgrade, stay on the master378 branch — it continues to receive security and critical-bug fixes.

🤝 Contributing and license

Community contributions are welcome. Fork the repository, make your changes on a branch, and open a pull request; see CONTRIBUTING.md for the contribution workflow.

Contributors must sign the OPC Foundation Contributor License Agreement (CLA). The CLA "I AGREE" gate is presented automatically on your first PR.

The project is licensed under the OPC Foundation MIT License. Report security vulnerabilities via the process documented in SECURITY.md.

📚 Further reading

S
Description
OPC Unified Architecture .NET Standard
Readme
296 MiB
Languages
C# 99.4%
PowerShell 0.2%