Hi Mathew,
I guess I should have mentioned this earlier - when websocket is closed, I
send a http request to a microservice. I believe I am establishing multiple
connections that is either slowing things down or causing segmentation
fault based on strace.
--------------------------------------------------------
15:16:50.130413 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
si_addr=0x10} ---
15:16:50.238181 +++ killed by SIGSEGV +++
---------------------------------------------------------
Again, this happens when a large number of websockets close at the same time
Thanks
On Saturday, September 16, 2017 at 4:16:57 AM UTC-4, Matthew Wild wrote:
>
> Hey,
>
> On 16 September 2017 at 01:27, Harsha Bellur <[email protected]
> <javascript:>> wrote:
> > Well, besides setting use_libevent to true in prosody config, is there
> > anything else to do?
> > I am using Jitsi components for audio/video conferencing - so NGINX
> proxies
> > APIs to these components as well.
> > When connected the clients send ping messages (XEP-0199) periodically -
> that
> > is about it
> > Basically, I am validating how the websocket server handles loss of
> > connectivity from all clients at once - this is where I am seeing the
> issue.
>
> Can you provide the output of `strace -Ttt -p PROSODY_PID` for the
> duration of the socket-closing operation?
>
> Regards,
> Matthew
>
--
You received this message because you are subscribed to the Google Groups
"prosody-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/prosody-dev.
For more options, visit https://groups.google.com/d/optout.
