Type of issue

• Bug
• Enhancement
• Compliance
• Question
• Help wanted

Current Behavior

The $SDK\Server\NodeManager\SamplingGroup class from V1.04 or above Opc.Ua.Server library spawns a sperate new thread for each monitoredItem being added to the same sampling group.

Expected Behavior

The SamplingGroup is expected to sample all MonitoredItems with same sampling interval on the same thread. It should not spawn separate thread in each call for ApplyChanges.

The $SDK\Server\NodeManager\SamplingGroup class from V1.02 had correct behavior.

Root cause of the issue:
The SamplingGroup::ApplyChanges starts the group even if the group is already running.

Description of fix:
File: $SDK\Server\NodeManager\SamplingGroup
Ad a new member variable to hold the task that is created in Startup function. Set the default value to null.

Function: Startup

• Store the task returned by Task.Factory.StartNew in the member variable.

Function: ApplyChanges

• Call Startup if (m_items.Count > 0 && null == m_task)

Steps To Reproduce

No response

Environment

- OS:
- Environment:
- Runtime:
- Nuget Version:
- Component:
- Server:
- Client:

Anything else?

No response