Yogi
September 6, 2022, 11:54am
4
TomF:
Hi @Yogi ,
It sounds like what you want here is a synchronous reply - the replier replies as soon as it can, and the requester waits a specified amount of time before deciding that the replier is dead and taking some business logic decision based on that.
To do that, you’d use the request/reply pattern without the queues that you have in the interaction above. So you’d produce to a topic, add a correlation ID to the message headers. The replier replies on a response topic, with the correlation ID in the response. No queues are involved: the producer needs to keep track of which requests it has issued and which have been responded to.
Hi @TomF thank you for the reply , this functionality is working fine except for 1 day report for rest other day it is working fine hence is there any solution without doing any changes?