You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openmeetings.apache.org by "seba.wagner@gmail.com" <se...@gmail.com> on 2020/09/24 02:19:32 UTC
WebSockets idle connection 30sec ping
The current ping keep alive in main.js is set to 30sec:
self.ping = *function*() {
setTimeout(() => OmUtil.sendMessage({type: 'ping'}), 30000);
};
Which happens to be the exact same default connection timeout on AWS ELB's.
So the connection actually timeout after 60 sec (on the 2nd ping).
I'm relatively certain just increasing the default would work. But should
we maybe make this value configurable in OpenMeetings?
I can imagine a lot of load balancers will have the same issue or a need to
configure the ping timeout.
Thanks,
Seb
Sebastian Wagner
Director Arrakeen Solutions
http://arrakeen-solutions.co.nz/
<https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
<https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
Re: WebSockets idle connection 30sec ping
Posted by Maxim Solodovnik <so...@gmail.com>.
this is weird
both should miss ...
On Thu, 24 Sep 2020 at 09:24, seba.wagner@gmail.com
<se...@gmail.com> wrote:
>
> The first ping resets it, but the second one times out as it missed the
> 30sec window.
>
>
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
>
>
> On Thu, 24 Sep 2020 at 14:22, Maxim Solodovnik <so...@gmail.com> wrote:
>
> > OK with me :)
> >
> > still unclear why timeout happens after 60sec< and not 30 .....
> >
> > On Thu, 24 Sep 2020 at 09:19, seba.wagner@gmail.com
> > <se...@gmail.com> wrote:
> > >
> > > The current ping keep alive in main.js is set to 30sec:
> > >
> > > self.ping = *function*() {
> > >
> > > setTimeout(() => OmUtil.sendMessage({type: 'ping'}), 30000);
> > >
> > > };
> > >
> > > Which happens to be the exact same default connection timeout on AWS
> > ELB's.
> > >
> > > So the connection actually timeout after 60 sec (on the 2nd ping).
> > >
> > > I'm relatively certain just increasing the default would work. But should
> > > we maybe make this value configurable in OpenMeetings?
> > > I can imagine a lot of load balancers will have the same issue or a need
> > to
> > > configure the ping timeout.
> > >
> > > Thanks,
> > > Seb
> > >
> > > Sebastian Wagner
> > > Director Arrakeen Solutions
> > > http://arrakeen-solutions.co.nz/
> > > <
> > https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url
> > >
> > > <
> > https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url
> > >
> >
> >
> >
> > --
> > Best regards,
> > Maxim
> >
--
Best regards,
Maxim
Re: WebSockets idle connection 30sec ping
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
The first ping resets it, but the second one times out as it missed the
30sec window.
Sebastian Wagner
Director Arrakeen Solutions
http://arrakeen-solutions.co.nz/
<https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
<https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
On Thu, 24 Sep 2020 at 14:22, Maxim Solodovnik <so...@gmail.com> wrote:
> OK with me :)
>
> still unclear why timeout happens after 60sec< and not 30 .....
>
> On Thu, 24 Sep 2020 at 09:19, seba.wagner@gmail.com
> <se...@gmail.com> wrote:
> >
> > The current ping keep alive in main.js is set to 30sec:
> >
> > self.ping = *function*() {
> >
> > setTimeout(() => OmUtil.sendMessage({type: 'ping'}), 30000);
> >
> > };
> >
> > Which happens to be the exact same default connection timeout on AWS
> ELB's.
> >
> > So the connection actually timeout after 60 sec (on the 2nd ping).
> >
> > I'm relatively certain just increasing the default would work. But should
> > we maybe make this value configurable in OpenMeetings?
> > I can imagine a lot of load balancers will have the same issue or a need
> to
> > configure the ping timeout.
> >
> > Thanks,
> > Seb
> >
> > Sebastian Wagner
> > Director Arrakeen Solutions
> > http://arrakeen-solutions.co.nz/
> > <
> https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url
> >
> > <
> https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url
> >
>
>
>
> --
> Best regards,
> Maxim
>
Re: WebSockets idle connection 30sec ping
Posted by Maxim Solodovnik <so...@gmail.com>.
OK with me :)
still unclear why timeout happens after 60sec< and not 30 .....
On Thu, 24 Sep 2020 at 09:19, seba.wagner@gmail.com
<se...@gmail.com> wrote:
>
> The current ping keep alive in main.js is set to 30sec:
>
> self.ping = *function*() {
>
> setTimeout(() => OmUtil.sendMessage({type: 'ping'}), 30000);
>
> };
>
> Which happens to be the exact same default connection timeout on AWS ELB's.
>
> So the connection actually timeout after 60 sec (on the 2nd ping).
>
> I'm relatively certain just increasing the default would work. But should
> we maybe make this value configurable in OpenMeetings?
> I can imagine a lot of load balancers will have the same issue or a need to
> configure the ping timeout.
>
> Thanks,
> Seb
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
--
Best regards,
Maxim