You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
var response = await (_client.ExecuteSequence(p => p.PublishAsync(new HelloWorld()).Complete<HelloWorldResponse>())).Task;
However, if you add a generic wrapping the response class, the message on the queue doesn't get consumed and the sequence times out:
var response = await (_client.ExecuteSequence(p => p.PublishAsync(new HelloWorld()).Complete<Response<HelloWorldResponse>>())).Task;
If you don't use message sequences (instead, setting up a publisher and subscriber independently) it works fine, which leads me to believe there's a problem in the message sequence extension in how it sets up the subscriber for the response, although when I glanced at the logs it looked like it was subscribing to the correct queue.
The text was updated successfully, but these errors were encountered:
You are absolutely right. The reason for this is that I took a shortcut when setting the routing key in the message sequence. It should use naming convention, but it doesn't.
In v2, the following works fine:
However, if you add a generic wrapping the response class, the message on the queue doesn't get consumed and the sequence times out:
If you don't use message sequences (instead, setting up a publisher and subscriber independently) it works fine, which leads me to believe there's a problem in the message sequence extension in how it sets up the subscriber for the response, although when I glanced at the logs it looked like it was subscribing to the correct queue.
The text was updated successfully, but these errors were encountered: