NGINX module reporting 0 time to access.log

[chase.holland]

Valentin V. Bartenev Wrote:
-------------------------------------------------------
> On Monday 01 December 2014 22:09:14 chase.holland wrote:
> > Hey all,
> > 
> > We've written a module to connect NGINX / OpenResty with ZMQ
> endpoints
> > (https://github.com/neloe/ngx_zmq), but all requests through the
> module
> > report a 0.000 time back to access.log, making it impossible to
> determine
> > which of our subsystems is the problem area in terms of latency. Is
> there a
> > flag or callback somewhere that needs to be implemented in order to
> report
> > this time properly?
> [..]
> 
> The whole code is one big problem.  It just blocks a worker process on
> network 
> IO and endless loops.  You should never write code this way in nginx.
> 
>   wbr, Valentin V. Bartenev
> 
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

Hi Valentine,

Thank you for your quick response! Could you be more specific on what is
blocking the worker process? Does an instance of an nginx module only get
one context per process (thus we need to do our own threading), or is each
instance of the module thread-based to match nginx's threads?

Thanks!

- Chase Holland

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,255254,255276#msg-255276