Re: [reSIProcate] dum leaks dialogs and dialogsets on shutdown

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

Assuming the notify has a terminated event state in it - sounds like a bug in DUM.  

Scott

On Wed, Mar 5, 2014 at 4:50 AM, Daniel Tacalau <dtacalau@xxxxxxxxx> wrote:

Hi,

In the scenario below, when dum is shutdown gracefully with dum.shutdown(&_shutdownHandler), it waits indefinitely in shutdown - from logs there are some AppDialog and AppDialogSet which are not destroyed. Not sure what's the problem. Shutdown does not block if I use forced method _dum.forceShutdown(&_shutdownHandler);

Here's the scenario:

I use DUM as a subscribe client to fetch state from phones by sending SUBSCRIBE requests with Expires 0. Phone replies back with 200 OK and NOTIFY, but proxy reverse the sequence and sends to DUM the NOTIFY followed by 200OK. The leaked Dialogs and DialogSets are created by DUM when it receives the 200OK.

I've attached logs.

2014-03-04T14:34:28.747357Z:6273:SIP:DEBUG:dtacalau-laptop.dev-ezuce.ro::7f658e604700:sipxsss:DEBUG | 20140304-163428.747 |  | RESIP:DUM | 140074157098752 | HandleManager.cxx:51 | 14 -> AppDialog 14

2014-03-04T14:34:28.747493Z:6275:SIP:DEBUG:dtacalau-laptop.dev-ezuce.ro::7f658e604700:sipxsss:DEBUG | 20140304-163428.747 |  | RESIP:DUM | 140074157098752 | HandleManager.cxx:51 | 3 -> AppDialogSet 3

2014-03-04T14:34:28.747589Z:6277:SIP:DEBUG:dtacalau-laptop.dev-ezuce.ro::7f658e604700:sipxsss:DEBUG | 20140304-163428.747 |  | RESIP:DUM | 140074157098752 | HandleManager.cxx:51 | 4 -> AppDialogSet 4

Could there be anything wrong on my end or could be a bug in DUM? I'd prefer to shutdown gracefully.

Thanks,

Daniel

_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel