Thanks Emile for the response and help.<br>We really want to have a function for terminating rpc server, when clients still sending msg to that, I mean, that function will make rpc server stop to recieve new msg from que, and we can stop rpc server easyly and gracefully.<br>
<br>or any suggestion/best practices for stopping rpc server will be very appreciated!<br><br><div class="gmail_quote">2012/10/4 Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
On 04/10/12 04:10, Hongtao wrote:<br>
> but, for shtutting down rpc server, how can we make sure all<br>
> messages have been dealt with, and no msg lost. we want a graceful<br>
> shutdown process, seems no document talking about that.<br>
><br>
> if we call: execService.shutdown();<br>
><br>
> Consumer.handleDelivery will not be triggerred then?<br>
<br>
If you make sure not to acknowledge RPC requests until after sending the<br>
RPC reply then message will not be lost, even if you shut down the RPC<br>
server. Your clients must be prepared to handle duplicates though, as<br>
replies might be sent more than once.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
-Emile<br>
<br>
</font></span></blockquote></div><br>