Hi @David Bonilla
This is a message from the team on how the integration node listener works: "The listener writes the incoming message to a queue with a header indicating what flows should read it. Any flow that matches that header will read the message whenever it has a free instance available. There is no round-robin or queue type order; it is simply first come, first served."
I have tried to look for other discussions and documentation around it but haven't had much luck so far. Here is a small documentation on HTTP Listeners, though, which includes the integration node listener.
------------------------------
Gabriel Marte Blanco
Austin TX
------------------------------
Original Message:
Sent: Wed April 19, 2023 06:34 PM
From: David Bonilla
Subject: How does integration node listener work in ACE?
Hi community:
I have been trying to find documentation about how integration node listener works. I am facing an issue using this listener and this is my scenario:
URI1: /ABC (uses 5 services with the same URI)
URI2: /XYZ (uses more than 10 services with the same URI)
After requesting into URI1, and 1 services does not return a response the other 4 services are affected. Any of then works well. I use Datapower before ACE and with Latency log and I see a big gap of time from message arrives to Datapower and when Datapower send it to ACE (about 2 min acording to 120 seg of backend timeout), like a kind of queue waiting in port 7080 of ACE.
I have change to use embedded and try again the same scenario and only 1 service is affected usen URI1.
I want to know how integration node listener works because I understand that it uses MQ, is there any distributtión or logic inside MQ and ACE to handle requests?
Note: URI2 is not affected at any time.
Regards.
------------------------------
David Bonilla
------------------------------