MassTransit.RequestTimeoutExceptioncaused while using Request-Response pattern

[Giorgobiani-G]

I have two api. I am using MassTransit.RabbitMQ" Version="8.1.3 for communication. Problem is that when i send get request From api A , i get MassTransit.RequestTimeoutExceptioncaused , but not always. This happens only when the api B connection in rabbitMq is down.. when connection of api B is runnung its not the problem. The api B Connection is down after some time itself, i get it , but i think it should be reactivated itself when i send request from api A, that uses request/response to get data from api B.
I have this type of configuration here for api A:

here is Request Client in api A:

here Consumer from Api B :

Tell me please, Should i add some additional configuration or how to fix this problem?

i think i need rabbitMQ connection to configure so that it wtill automatically be actived when i send IRequestClient requst from service A, but how to achieve that.

[lukebakken]

Hello, thanks for using RabbitMQ.

I suggest asking your question in the MassTransit GitHub discussions - https://github.com/MassTransit/MassTransit/discussions

[lukebakken]

MassTransit/MassTransit#5084 (reply in thread)

If you think RabbitMQ is terminating your connection to save resources, you are mistaken.

At this point, you MUST investigate your RabbitMQ logs to see what is logged at the same time as your connection stops. If you find something, ATTACH the log file to your comment here. If you paste a large amount of text, or do not provide enough of a log file to determine the issue, I can't help you.

[Giorgobiani-G]

ok but i found nothing special in logs just opeinig and closing connecions:

2024-04-10 19:26:46.735000+04:00 [info] <0.271821.0> accepting AMQP connection <0.271821.0> (192.168.1.40:57861 -> 192.168.1.40:5672)
2024-04-10 19:26:46.756000+04:00 [info] <0.271821.0> connection <0.271821.0> (192.168.1.40:57861 -> 192.168.1.40:5672) has a client-provided name: w3wp
2024-04-10 19:26:46.759000+04:00 [info] <0.271821.0> connection <0.271821.0> (192.168.1.40:57861 -> 192.168.1.40:5672 - w3wp): user 'Syllogia' authenticated and granted access to vhost '/'
2024-04-10 19:27:02.413000+04:00 [info] <0.271855.0> accepting AMQP connection <0.271855.0> (192.168.1.40:57872 -> 192.168.1.40:5672)
2024-04-10 19:27:02.432000+04:00 [info] <0.271855.0> connection <0.271855.0> (192.168.1.40:57872 -> 192.168.1.40:5672) has a client-provided name: w3wp
2024-04-10 19:27:02.436000+04:00 [info] <0.271855.0> connection <0.271855.0> (192.168.1.40:57872 -> 192.168.1.40:5672 - w3wp): user 'Syllogia' authenticated and granted access to vhost '/'
2024-04-10 19:44:17.426000+04:00 [info] <0.272260.0> accepting AMQP connection <0.272260.0> (192.168.1.40:58112 -> 192.168.1.40:5672)
2024-04-10 19:44:17.449000+04:00 [info] <0.272260.0> connection <0.272260.0> (192.168.1.40:58112 -> 192.168.1.40:5672) has a client-provided name: w3wp
2024-04-10 19:44:17.454000+04:00 [info] <0.272260.0> connection <0.272260.0> (192.168.1.40:58112 -> 192.168.1.40:5672 - w3wp): user 'Syllogia' authenticated and granted access to vhost '/'
2024-04-10 19:47:44.238000+04:00 [info] <0.271821.0> closing AMQP connection <0.271821.0> (192.168.1.40:57861 -> 192.168.1.40:5672 - w3wp, vhost: '/', user: 'Syllogia')
2024-04-10 19:48:01.518000+04:00 [info] <0.271855.0> closing AMQP connection <0.271855.0> (192.168.1.40:57872 -> 192.168.1.40:5672 - w3wp, vhost: '/', user: 'Syllogia')
2024-04-10 20:05:15.227000+04:00 [info] <0.272260.0> closing AMQP connection <0.272260.0> (192.168.1.40:58112 -> 192.168.1.40:5672 - w3wp, vhost: '/', user: 'Syllogia')

[lukebakken]

That shows that there are no unexpected connection "terminations" or closures.

The only way we can assist you at this point is a way to reproduce this issue.

[Giorgobiani-G]

ok , u just tell is there a way to keep connection alive until api is down.

[lukebakken]

Probably, but I've never used MassTransit. I need code that I can clone, compile and run to give you any more assistance.

More than likely there is a bug in how you are using MassTransit.