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
OPC Wrapper goes into a bad state(BadTooManyOperations) when left running for long.
Steps To Reproduce
We are running the wrapper sample with a HDA server. We are reading about 20 nodes at regular intervals and when left to run over for long goes into a bad state. The History Read starts failing with BadTooManyOperations. Once this happens the server fails with the same error when another client tries to connect to the server. Disconnecting the HDA client also does not help. The only way to recover is to restart the Wrapper.
@vinaybr this error (BadTooManyOperations) is hit when the server local thread pool which processes the service requests runs out of threads, which means there might be threads consumed and waiting which never return, or too few threads are configured. How long does it take until it goes to a bad state?
Please check also the latest Nuget bits, this error was changed to return BadServerTooBusy.
To change the max number of threads in use, here are the settings:
Type of issue
Current Behavior
OPC Wrapper goes into a bad state(BadTooManyOperations) when left running for long.
Steps To Reproduce
We are running the wrapper sample with a HDA server. We are reading about 20 nodes at regular intervals and when left to run over for long goes into a bad state. The History Read starts failing with BadTooManyOperations. Once this happens the server fails with the same error when another client tries to connect to the server. Disconnecting the HDA client also does not help. The only way to recover is to restart the Wrapper.
Environment
The text was updated successfully, but these errors were encountered: