You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example using UA Expert, when creating a new subscription with more than 10k of items, some of the tags start to fail saying that the StatusCode is Bad.
Expected Behavior
All the tags/items should be Good no matter the number.
Steps To Reproduce
Configure the XML to use the DA Server with the tags/items
Run the Com Server Wrapper
Connect with UA Expert or other tool
Create a new subscription and add a couple of tags/items
Keep adding tags/items
At some point (around 10k but not always), we start to see Bad tags for working ones
If we delete some of the tags/items and decrease the total amount in the same subscription, we can see that everything returns to the normal with Good tags
NOTE: This happens globally, what do I mean by this, if we have two or more subscriptions, I can get BAD tags when the total amount of tags/items in all of the subscriptions are higher than the 10k, I can get BAD tags in one of the subscription that has for instance 1k.
Environment
- OS: Windows 11
- Environment: n/a
- Runtime: .NET4.8
- Nuget Version: 1.5.374.78
- Component: ???
- Server: UA Com Server
- Client: UA Expert
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Type of issue
Current Behavior
For example using UA Expert, when creating a new subscription with more than 10k of items, some of the tags start to fail saying that the StatusCode is Bad.
Expected Behavior
All the tags/items should be Good no matter the number.
Steps To Reproduce
NOTE: This happens globally, what do I mean by this, if we have two or more subscriptions, I can get BAD tags when the total amount of tags/items in all of the subscriptions are higher than the 10k, I can get BAD tags in one of the subscription that has for instance 1k.
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: