Is it possible to use InterApp communication on a replicated element?
Currently, we see the following error on the staging system:
2022/04/13 14:30:22.402|SLManagedScripting.exe|ManagedInterop|ERR|0|120|QA4|4|Run|Exception thrown: System.TimeoutException: Timeout while waiting on responses: 851338dc-c6fc-4613-bf36-56dd81c6dfa5 at Skyline.DataMiner.Library.Common.Subscription.Waiters.InterApp.MessageWaiter.<WaitNext>d__5.MoveNext() at Skyline.DataMiner.Library.Common.InterAppCalls.CallBulk.InterAppCall.<Send>d__30.MoveNext() at Skyline.Protocol.Generic.RequestEventsInformation(SLProtocol protocol, ElementInfoEventMessage element) at Skyline.Protocol.Generic.GetEventsFromElement(SLProtocolExt protocol, String elementName) at QAction.Run(SLProtocolExt protocol)
On the internal test system, we receive an empty response. When switched to the original element everything seems to work fine.
Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 14th July 2023
InterApp Calls were never tested using Replicated Elements.
InterApp calls in the background use two technologies:
- SLNet remote parameter sets
- SLNet Subscriptions.
If one of those doesn’t function correctly with replicated elements then InterApp Calls won’t work.
I’ve created a task internally to look into adding replicated elements as part of our testing suite and see if we can get it working.
Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 14th July 2023