On Tuesday, September 19, 2017 at 5:00:21 AM UTC-4, Matthew Wild wrote:
>
> Hi,
>
> On 18 September 2017 at 19:33, Harsha Bellur <[email protected]
> <javascript:>> wrote:
> > 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.
>
> How are you sending this HTTP request? and where? Did you modify Prosody's
> code?
>
I am using the request method in net/http.lua to post HTTPS/HTTP requests
to an external http server. I did modify the method to handle POST as well
as PUT - that's about it.
>
> > --------------------------------------------------------
> > 15:16:50.130413 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
> > si_addr=0x10} ---
> > 15:16:50.238181 +++ killed by SIGSEGV +++
> > ---------------------------------------------------------
>
> A segmentation fault is a very different thing to just a slow server.
> Is this reproducible?
>
At my end, it is intermittent but reproducible. The way I do it is setup
say 40 thousand WS connections and stop nginx. Basically, I am simulating a
use case where the web socket server has lost connectivity to all clients.
>
> 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.
