Re: Memory leak in nist implementation

Francisco,

A B2BUA application connects 2 Dialog objects together, one on the "UAS"=20
side (receiving a request) and one on the "UAC" side (forwarding the=20
request)
Could it be that you are referring to the "UAS" Dialog that is never=20
destroyed?

 From that Dialog's perspective, your application received the BYE but=20
never sent a 200 OK. That's different from sending out a BYE onto the=20
network, and not receiving a 200 OK.

The proper solution would be to implement logic in the BYE=20
ClientTransaction timeout handler, to still send a 200 OK for the BYE on=20
the "UAS" side. Alternatively, you can always immediately send 200 OK=20
when you receive a BYE, and generate a BYE for the second Dialog at the=20
same time.

Regards,
Jeroen

Francisco Javier Tellez Vaquero wrote:
> Hi again,
> we have an application running as a B2BUA.
>
> If we receive a BYE from an end point, we send the BYE to the other=20
> point. When we receive 200 response, we re-transmit it.
>
> We see sometimes this response is lost (because of network problems,=20
> because of terminal, ...). The question is the dialog is never=20
> destroyed until application is re-started. We have wait for garbage=20
> collection (application is running for days).
>
> Regards.
>
>
> > Date: Mon, 30 Jun 2008 14:39:30 -0400
> > From: [email protected]
> > To: [email protected]
> > Subject: Re: [nist-sip] Memory leak in nist implementation
> > CC: [email protected]
> >
> > When the tx times out delete the dialog and then you have to wait for
> > the garbage collection to run before you check for leak.
> >
> > Ranga.
> >
> > On Mon, Jun 30, 2008 at 2:32 PM, Francisco Javier Tellez Vaquero
> > <[email protected]> wrote:
> > > Hi Ranga,
> > > I agree the example case is a listener bug, but think the opposite=20
> case:
> > >
> > > - You send a BYE request but no response is received.
> > >
> > > You have no control about this point, so the idea is trying to=20
> close the
> > > dialog anyway.
> > >
> > > BR.
> > >
> > >
> > >> Date: Mon, 30 Jun 2008 14:09:05 -0400
> > >> From: [email protected]
> > >> To: [email protected]
> > >> Subject: Re: [nist-sip] Memory leak in nist implementation
> > >> CC: [email protected]
> > >>
> > >> On Mon, Jun 30, 2008 at 1:55 PM, Francisco Javier Tellez Vaquero
> > >> <[email protected]> wrote:
> > >> > Hi all,
> > >> > I see sometimes not all stack objects are destroyed.
> > >> >
> > >> > For example, if you receive BYE request but no 200 response is=20
> sent,
> > >> > dialog
> > >> > is never closed. There're a lot of different cases (ACK's lost,=20
> ...).
> > >>
> > >> Not sending a 200 OK to a BYE is an application bug. Please fix th=
at.
> > >>
> > >> Please post a specific test case (without listener bugs) and I=20
> can look
> > >> into it.
> > >>
> > >> Ranga
> > >>
> > >> >
> > >> > I have tried to free memory executing 'terminate()' and/or=20
> 'delete()'
> > >> > methods in both transaction and dialog objects but without any=20
> result.
> > >> >
> > >> > Is there any way to force to free these objects (timers, dialogs=
,
> > >> > transactions, ...) ?
> > >> >
> > >> > Regards.
> > >> >
> > >> >
> > >> >
> > >> > ________________________________
> > >> > Tecnolog=EDa, moda, motor, viajes,.suscr=EDbete a nuestros=20
> boletines para
> > >> > estar
> > >> > siempre a la =FAltima MSN Newsletters
> > >> > _______________________________________________
> > >> > nist-sip mailing list
> > >> > [email protected]
> > >> > http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
> > >> >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> M. Ranganathan
> > >
> > > ________________________________
> > > Sigue los principales acontecimientos deportivos en directo. MSN Mo=
tor
> >
> >
> >
> > --
> > M. Ranganathan
>
> -----------------------------------------------------------------------=
-
> Sigue al minuto las principales noticias de tu ciudad MSN Deportes=20
> <http://deportes.es.msn.com/>
> -----------------------------------------------------------------------=
-
>
> _______________________________________________
> nist-sip mailing list
> [email protected]
> http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
>  =20