View Issue Details

IDProjectCategoryView StatusLast Update
0009002CTT UA Scripts1 - Script Issuepublic2023-10-26 15:51
ReporterMartin Herberg Assigned ToMichael Fehler  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Fixed in Version1.03.505 
Summary0009002: Monitor Value Change 014 - Create too many monitored items
Description

The test script tries to send all possible monitored items requests as fast as possible, and does not wait, or remove monitored items.

I think this leads from
CreateMonitoredItemsHelper.Execute

My settings are as follows:
Settings.ServerTest.Capabilities.MaxSupportedMonitoredItems = 2
Settings.ServerTest.NodeIds.Static.AllProfiles.Arrays.Settings has 4 entries.

During debugging
"Settings.ServerTest.NodeIds.Static.AllProfiles.Arrays.Settings"
is equal to 19 at the start of the script, and changes to 4 later - leading to even more monitore item requests.

CreateMonitoredItemsHelper.Execute seems to try to create all 19 monitored items withput any break. (See Wireshark trace).

Is this a known issue?

TagsNo tags attached.
Attached Files
Files Affected

/maintree/Monitored Item Services/Monitor Value Change/Test Cases/014.js

Activities

Martin Herberg

2023-06-09 14:58

reporter   ~0019476

Update:
CTT version is 1.04.09.401.

Paul Hunkar

2023-07-21 14:43

administrator   ~0019699

The script should take into account what is configured for items (so not 19 but the 4)
The second part is that the maximum monitored items should be honored (i.e. if they have less then the number of datatype then the list should just be a sub set of the datatypes)

Alexander Allmendinger

2023-10-26 15:51

developer   ~0020247

Replaced .GetRequiredNodes with .fromSettings, to esnsure that items will only receive existing nodes from Settings once.

Added MaxItemsPerCall gServerCapabilities.OperationLimits.MaxMonitoredItemsPerCall to CreateMonitoredItemsHelper, so that Max Supported MonitoredItems is respected.

Paul Hunkar

2023-10-26 15:51

administrator   ~0020248

reviewed changes in call , agreed and closed issue

Issue History

Date Modified Username Field Change
2023-06-09 14:39 Martin Herberg New Issue
2023-06-09 14:39 Martin Herberg File Added: 20230609_monitoredValueChange_014_02.JPG
2023-06-09 14:58 Martin Herberg Note Added: 0019476
2023-07-21 14:40 Paul Hunkar Assigned To => Alexander Allmendinger
2023-07-21 14:40 Paul Hunkar Status new => assigned
2023-07-21 14:43 Paul Hunkar Note Added: 0019699
2023-10-19 13:47 Michael Fehler Assigned To Alexander Allmendinger => Michael Fehler
2023-10-19 13:49 Michael Fehler Files Affected => /maintree/Monitored Item Services/Monitor Value Change/Test Cases/014.js
2023-10-26 15:51 Alexander Allmendinger Status assigned => resolved
2023-10-26 15:51 Alexander Allmendinger Resolution open => fixed
2023-10-26 15:51 Alexander Allmendinger Note Added: 0020247
2023-10-26 15:51 Paul Hunkar Status resolved => closed
2023-10-26 15:51 Paul Hunkar Fixed in Version => 1.03.505
2023-10-26 15:51 Paul Hunkar Note Added: 0020248