In which scenarios are the request re-routed when a Load Balancing configuration is setup for Target Operations in TIBCO API Exchange Gateway(APIX-G)?

In which scenarios are the request re-routed when a Load Balancing configuration is setup for Target Operations in TIBCO API Exchange Gateway(APIX-G)?

book

Article ID: KB0093749

calendar_today

Updated On:

Products Versions
TIBCO API Exchange -
Not Applicable -

Description

Resolution:

Attached is a sample log for a Round Robin with Failover Target Operation Group: RR_Failover_testing.txt.


- The 1st and 2nd requests were sent to t520(line#1426) and win2k8(line#1679) hosts respectively.

- The 3rd request should have gone to t520, as per RoundRobin logic, but as it was down it was routed to win2k8(line#1942-1964).
- All the subsequent requests were routed to win2k8, as t520 was DOWN.
- At the next health-check interval, line#3620, t520 was UP.
- The next request was routed to t520.

In the sample log RR_Failover_testing_2.txt:


- At line#1426, t520 timed out but the request was not replayed.

- The 2nd request was sent to win2k8 and processed.
- For the 3rd request, the service on t520 was stopped while the request was being processed and the request was rerouted.

Issue/Introduction

In which scenarios are the request re-routed when a Load Balancing configuration is setup for Target Operations in TIBCO API Exchange Gateway(APIX-G)?

Additional Information

Documentation --> User's Guide --> Project Configuration --> Routing --> Target Operation Groups for more information.

Attachments

In which scenarios are the request re-routed when a Load Balancing configuration is setup for Target Operations in TIBCO API Exchange Gateway(APIX-G)? get_app
In which scenarios are the request re-routed when a Load Balancing configuration is setup for Target Operations in TIBCO API Exchange Gateway(APIX-G)? get_app