7.0 not returning Rpc request the 2nd time

Hi

I’m trying out version 7 (currently on RC 2) in a small project, as I wish to use the new non-generic version of the PubSub.Subscribe. All that seems to work correctly.

I am however experiencing an issue on an Rpc.Request, where the first execution of the request works as expected, however, any subsequent requests will not come through. The specific code being run is this: var data = await bus.Rpc.RequestAsync<UserDataRequest, UserDataResponse>(new UserDataRequest() { UserId = authId });

I have verified that there are no exceptions being thrown by the responder to this request. It runs and returns both times as intended.

Debug log:

(First time)
[11:33:49 Debug] Declared queue easynetq.response.92896953-8791-400a-97df-6842c3914491: durable=False, exclusive=True, autoDelete=True, arguments=
[11:33:49 Debug] Bound queue easynetq.response.92896953-8791-400a-97df-6842c3914491 to exchange easy_net_q_rpc with routingKey=easynetq.response.92896953-8791-400a-97df-6842c3914491 and arguments=
[11:33:49 Info] Declared consumer with consumerTag easynetq.response.92896953-8791-400a-97df-6842c3914491 on queue  and configuration EasyNetQ.Consumer.ConsumerConfiguration
[11:33:49 Debug] Published to exchange easy_net_q_rpc with routingKey=Messages.Read.Users.UserDataRequest, Messages and correlationId=972dcb8f-05f9-4a3b-ac2b-9cee4350e2e4
[11:33:50 Debug] Message delivered to consumer amq.ctag-4IF8xm2fHdTzBdYb0JjrBg with deliveryTag 1
[11:33:50 Debug] Received message with receivedInfo=[ConsumerTag=amq.ctag-4IF8xm2fHdTzBdYb0JjrBg, DeliveryTag=1, Redelivered=False, Exchange=easy_net_q_rpc, RoutingKey=easynetq.response.92896953-8791-400a-97df-6842c3914491, Queue=easynetq.response.92896953-8791-400a-97df-6842c3914491]

(2nd time)
[11:34:04 Debug] Published to exchange easy_net_q_rpc with routingKey=Messages.Read.Users.UserDataRequest, Messages and correlationId=e1e43365-0c5d-46a4-89af-8183d8f6d6cd

(3rd time)
[11:35:21 Debug] Published to exchange easy_net_q_rpc with routingKey=Messages.Read.Users.UserDataRequest, Messages and correlationId=554ed798-e805-4e0f-a930-a6ec0d88b945

Eventually, it reaches the timeout.

If I revert to the latest stable version 6, everything (except obvs. the non-generic subscribe) works as intended.

The Service receiving and handling the message is running EasyNetQ v5.

Any suggestions?

[joamla96]

Everything seems to work wonderfully. Thank you again 😃

[Pliner]

I’ve found the issue. The fix is in progress.