#182 Re-hash of bug number 1354458
Hi Victor,
I have attached both the old and new versions of the impacted files in the
attached zip.
You can make out the difference and include it in the latest code of
diameter if it is correct.
regards,
Gurpreet Singh
-----Original Message-----
From: Victor Fajardo [mailto:vfajardo@tari.toshiba.com]
Sent: Tuesday, January 30, 2007 4:48 PM
To: Gurpreet.Sandhu@alcatel-lucent.com
Cc: sanjeev.mittal@aricent.com; Rammohan Kandlakunta;
diameter-developers@lists.sourceforge.net
Subject: Re: [Diameter-developers] Regarding compliance with rfc 3539 to
detect transport disconnection.
> > Hi Victor,
> >
> > I have made the fix for the bug no. 1354458 at my end over diameter
version
> > 1.0.7e.
> > With the fix, the diameter stack initiates failover procedure on not
getting
> > DWA within watchdog timer value.
> >
> > I can provide you the fix if needed.
> >
That would be great. Thanks very much.
-- victor
> > regards,
> > Gurpreet Singh
> >
> > -----Original Message-----
> > From: Gurpreet SANDHU [mailto:gurpreet.sandhu@alcatel.com]
> > Sent: Thursday, January 18, 2007 9:49 AM
> > To: Victor Fajardo
> > Cc: diameter-developers@lists.sourceforge.net
> > Subject: RE: [Diameter-developers] Regarding compliance with rfc 3539 to
> > detect transport disconnection.
> >
> >
> > Hi Victor,
> >
> > The similar bug has already been reported by some user and its no. is
> > 1354458 and it was raised on 11th Nov. 2005.
> > You can have a look at that.
> >
> > thanks and regards,
> > Gurpreet Singh
> >
> > -----Original Message-----
> > From: Victor Fajardo [mailto:vfajardo@tari.toshiba.com]
> > Sent: Wednesday, January 17, 2007 9:31 PM
> > To: Gurpreet.Sandhu@alcatel-lucent.com
> > Cc: diameter-developers@lists.sourceforge.net
> > Subject: Re: [Diameter-developers] Regarding compliance with rfc 3539 to
> > detect transport disconnection.
> >
> >
> > Hi,
> >
> > I have'nt confirmed this behavior but you can post a bug report. We will
> > be trying to get a release out as soon as possible. The timeframe is
> > within the end of this month.
> >
> > regards,
> > victor
> >
> >
> >
>> >> Hi Guys,
>> >>
>> >> In rfc 3539, section 3.4.1, it is mentioned that "If the watchdog timer
>> >> expires and a watchdog response is pending, then failover is initiated".
>> >>
> > But
> >
>> >> the open diameter stack(version 1.0.7e) that i am using in my application
>> >> doesn't comply with that.
>> >>
>> >> It does not detect the disconnection of its diameter peer(when the
network
>> >> cable of its diameter peer is unplugged) for about 9 to 10 minutes
>> >>
> > however,
> >
>> >> i have set the watchdog timer value to be 30 seconds.
>> >>
>> >> Logically, it should move the disconnected peer to closed state on not
>> >> getting DWA after 30 seconds, and the failover procedures should be
>> >> initiated.
>> >>
>> >> I also checked the same functionality with the open diameter stack
version
>> >> 1.0.7h but it seems that this problem is still present in the latest open
>> >> diameter stack.
>> >>
>> >> Please confirm if this problem is okay or the functionality is already
>> >>
> > there
> >
>> >> in the stack.
>> >> And if this is a valid problem, when can this be fixed.
>> >>
>> >> Eagerly waiting for your response.
>> >>
>> >> thanks and regards,
>> >> Gurpreet Singh
>> >>
>> >>
>> >> -------------------------------------------------------------------------
>> >> Take Surveys. Earn Cash. Influence the Future of IT
>> >> Join SourceForge.net's Techsay panel and you'll get the chance to share
>> >>
> > your
> >
>> >> opinions on IT & business topics through brief surveys - and earn cash
>> >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> >> _______________________________________________
>> >> Diameter-developers mailing list
>> >> Diameter-developers@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/diameter-developers
>> >>
>> >>
>> >>
>> >>
> >
> >
> >
> >
Contributed fix