[Recipient] The message order in request-reply is not the same as the route configuration

[Hooghof]

It is expected that messages sent via a recipient configured for request-reply to multiple routes will be processed on a per-route basis. Each route following the recipient will only start once the preceding connected route has processed the message.
This was the case in 4.14.9, see the acceptance test. In 4.17.11 routes are sometimes started before the previous one has been completed. It is expected that processing will take place in the order in which the routes are connected. In 4.17.11 that doesn't happen always.

Jira: https://dovetailworld.atlassian.net/browse/FG-2592

Test case 4.14.9
Instance: acceptance.dovetail.world
Tenant: wcg
Flow: QueuesRequestReply
Call: https://acceptance.dovetail.world/test/inbound_http/354476/QueuesRequestReply

Result
Route Start time End time
Route 1 4309577 4314645
Route 2 4314831 4319866
Route 3 4320152 4325189
Route 4 4325447 4330478
Route 5 4330669 4335699

Test case 4.17.12
Instance: development.dovetail.world
Tenant: wcg
Flow: QueuesRequestReply
Call: https://development.dovetail.world/test/inbound_http/wcg/QueuesRequestReply

Result
Route Start time End time
Route 1 5114954 5119980
Route 2 5114958 5119985
Route 4 5114960 5125005
Route 3 5114959 5125008
Route 5 5114972 5130025

[Hooghof]

This ticket on the backend will be closed and added to the frontend.

We have decided not to make any changes to the code for the following reasons:

• Previous changes made due to the transition from Camel 2 to Camel 4, to ensure that the functionality remains identical
• A workaround is available for configuring the transport type for queues in combination with the ‘request-reply’ recipient; the transport type in the flow can be set to ‘synchronous’
• In the next major version, it will no longer be possible to set the transport type to ‘queues’

To guide the user in selecting the correct setting, we intend to display a warning when the following conditions are met:

• recipient set to request-reply
• flow transport type is queues

Message in the recipient options pop-up: Strict message ordering is only possible when the transport type is set to synchronous.

The message can be displayed in red beneath the ‘request-reply’ radio button