Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Labels:
-
Story Points:3
-
Epic Link:
-
Team:Telescope and Site
-
Urgent?:No
Description
Because TCP/IP module can not run multiple instances I need to separate this wrong behavior into several steps before trying to solve them in one single ticket. After this, I will create other tickets to solve the bug step by step.
We would like to have the following test cases:
(a) Two servers can construct the connections at the same time.
(b) Two servers can have multiple times of connections at the same time.
(c) User can stop two servers without the problem at the same time.
(d) Two clients can write commands to two servers at the same time.
(e) Two clients can write events to two servers at the same time.
(f) Two clients can write telemetry to two servers at the same time.
(g) Two servers can write command status to two clients at the same time.
(h) Two servers can write events to two clients at the same time.
Two servers can write telemetry to two clients at the same time.
(j) Two servers can report the connection status at the same time.
(k) Two servers can report the log messages at the same time.
Attachments
Issue Links
Activity
Reviewed in GitHub. As the discussion, there would be another ticker of phase 2 to finish the untested use cases (please list the finished and unfinished use cases in the ticket description.).
Create ticket DM-39591 as Phase 2.
I created different test cases to understand why TCP/IP module can not run multiple instances. There are VI execution options that we have to evaluate (shared or preallocated clones). In addition, I think occurrences have to be replaced with other synchronization techniques, like notifiers.