RE: [reSIProcate] Unable to shutdown DUM during retransmission ofMESSAGE requests

[Dmitry Semyonov <dsemyonov@xxxxxxx>]

Scott,

If I call end() inside onFailure() DUM shuts down indeed. But when 
end() is called during MESSAGE retransmissions, the retransmissions 
continue, (they even continue after shutdown()) and after that I 
can see in the trace that there is no "Destroying usage" line for 
MESSAGE DialogSet after retransmissions timeout.

See attached logs with two cases described above.


On Tue, 9 Aug 2005, Scott Godin wrote:

> I can understand why it would not shutdown if you don't call end() -
> since nothing would destroy the usage.  
> 
> But if you call end() before shutdown, then it SHOULD shutdown OK.  To
> figure this one out - you will likely need to walk through a trace to
> find out what usages/handles are still around.
> 
> Scott
> 
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Dmitry Semyonov
> Sent: Tuesday, August 09, 2005 1:00 PM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] Unable to shutdown DUM during retransmission
> ofMESSAGE requests
> 
> Hello.
> 
> Consider the following scenario.
>  * Send MESSAGE to nowhere.
>  * DUM starts the series of retransmissions.
>  * Shutdown DUM before onFailure() is called due to retransmissions 
> timeout.
> 
> In this case DUM never exits.
> 
> I even tried to call ClientPagerMsgHandle->end() before shutting DUM 
> down with no luck. (I.e. I was not able to force transaction end.)

-- 
...Bye..Dmitry.

Attachment: shutdown_hangup.zip
Description: Zip archive