Nginx, jmeter and xml-rpc

Hello nginx users,

I’m experiencing issue testing java based xml-rpc service deployed on
tomcat 6 using jmeter 2.5.1. When the application server is fronted by
nginx 1.0.8 I’m getting http 408 error code when message being sent is
~30+ lines of indented XML, nginx doesn’t seem to get whole content of
the message jmeter is sending and keeps waiting until timeout occurs.
When message is ~10 lines of XML, it gets passed through to the tomcat
and back to the client well. When I replace nginx with apache httpd it
works well for both bigger and smaller message.

Has anyone experienced anything similar? Any thoughts where to look
for the root cause are more than welcome.

IMO it’s either a bug in nginx or configuration issue. At the moment I
can share just the output of nginx -V (see [1])

Regards,
Stevo.

[1] “nginx -V” output
[[email protected] ~]$ nginx -V
nginx: nginx version: nginx/1.0.8
nginx: built by gcc 4.1.2 20080704 (Red Hat 4.1.2-46)
nginx: TLS SNI support disabled
nginx: configure arguments: --user=nginx --group=nginx
–prefix=/usr/share/nginx --sbin-path=/usr/sbin/nginx
–conf-path=/etc/nginx/nginx.conf
–error-log-path=/var/log/nginx/error.log
–http-log-path=/var/log/nginx/access.log
–http-client-body-temp-path=/var/lib/nginx/tmp/client_body
–http-proxy-temp-path=/var/lib/nginx/tmp/proxy
–http-fastcgi-temp-path=/var/lib/nginx/tmp/fastcgi
–http-uwsgi-temp-path=/var/lib/nginx/tmp/uwsgi
–http-scgi-temp-path=/var/lib/nginx/tmp/scgi
–pid-path=/var/run/nginx.pid --lock-path=/var/lock/subsys/nginx
–with-http_ssl_module --with-http_realip_module
–with-http_addition_module --with-http_xslt_module
–with-http_sub_module --with-http_gzip_static_module
–with-http_random_index_module --with-http_secure_link_module
–with-http_stub_status_module --with-cc-opt=’-O2 -g -m64
-mtune=generic’ --with-cc-opt=’-O2 -g -m64 -mtune=generic’
–add-module=nginx_ajp_module --add-module=ngx_postgres-0.8
–add-module=agentzh-nginx-eval-module

Your issue is probably the buffer sizes:
http://wiki.nginx.org/HttpProxyModule#proxy_buffer_size

Greetings,
Joost

On Tue, Nov 1, 2011 at 6:54 AM, Stevo Slavić [email protected] wrote:

Has anyone experienced anything similar? Any thoughts where to look
for the root cause are more than welcome.

IMO it’s either a bug in nginx or configuration issue. At the moment I
can share just the output of nginx -V (see [1])

You need to provide nginx configuration, and log output at a minimum.
It is probably configuration, but no one can help you without you
providing data.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs