InterApp Return Message Timeout

Solved603 views
3
0 Comments

Hi,

I developed a protocol that receives a message from an automation script and returns a list of data. I'm using the InterApp resource to perform this task and I see that the automation sends the request and the protocol returns the response perfectly, but, for some reason, the script goes into timeout. I am displaying the request and response parameters and I see that communication between them is correct.

MAXIMILIANO FILHO [DevOps Enabler] Selected answer as best 6th November 2023

4 Answers

0
762 1 Comment

Hi Robin,

As I said in the comment, the UUID is the same.

This is the CreateReturnMessage code in the executor:
var dateTimeInterval = IncidentLibrary.Common.IncidentHelper.GetRoundedIntervalDates(1, 10);
var alarms = PreCompiled.Methods.FetchAlarms(Message.CorrelatorElementList, dateTimeInterval);
var returnMessage = new AlarmFetcherResponseMessage()
{
     Guid = Message.Guid,
     Source = Message.Source,
     ReturnAddress = Message.ReturnAddress,
     Alarms = alarms,
};

return returnMessage;

Robin Meurisse [SLC] [DevOps Advocate] Posted new comment 6th November 2023
Robin Meurisse [SLC] [DevOps Advocate] commented

Hi Maximiliano,
The source property seems to be empty in the return message (agentId and elementId set to default value 0).
Would it be possible to give it a try with the Source filled in for the returnMessage?
E.G.

var returnMessage = new AlarmFetcherResponseMessage()
{
Guid = Message.Guid,
Source = new Source(“Connector Name”, protocol.DataMinerID, protocol.ElementId),
Alarms = alarms,
};

And if possible verify where the return messsage is send, the code is using the original returnAddress.
E.G.
returnMessage.Send(
protocol.SLNet.RawConnection,
message.ReturnAddress.AgentId,
message.ReturnAddress.ElementId,
message.ReturnAddress.ParameterId,
KnownTypes);

Let us know if this works for you.
Kind regards.
You are viewing 1 out of 4 answers, click here to view all answers.