[reSIProcate] DUM DumShutdownHandler does not get triggered

[Scott Godin]

I'm shutting down using dum->shutdown(&shutdownhandler) and it is working
fine.  There was problems with this a few weeks ago - but it has since been
fixed.  

 

  _____  

From: Nash Tsai [mailto:nash.teltel at gmail.com] 
Sent: Tuesday, May 03, 2005 12:14 AM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] DUM DumShutdownHandler does not get triggered

 

Hi,

 

After call DialogUsageManager.shutdown and passing a DumShutdownHandler, the
DUM seem to be shutting down without calling
DumShutdownHandler.onDumCanBeDeleted, some how when shutting down the DUM
the following part of codes never gets executed:

 

      TransactionUserMessage* tuMsg =
dynamic_cast<TransactionUserMessage*>(msg.get());

      if (tuMsg)

      {

         InfoLog (<< "TU unregistered ");

         assert(mShutdownState == RemovingTransactionUser);

         assert(tuMsg->type() ==
TransactionUserMessage::TransactionUserRemoved);

         mShutdownState = Shutdown;

         if (mDumShutdownHandler)

         {

            mDumShutdownHandler->onDumCanBeDeleted();

            mDumShutdownHandler = 0;

         }

         return;

      }

 

Is this a bug of DUM ?

 

Thanks,

Nash

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050503/1e9470f2/attachment.htm>