However things start to break when I do 3) which is putting Nginx in
front of Glassfish Gem.
There appears to be some redundant stuffing of HTTP Headers, which
breaks all Ajax requests. The regular HTTP Get request work fine though.
But, when I remove Nginx to access Glassfish directly, then things are
fine.
At this point, 3) is my preferred deployment because Glassfish appears
to not suffer from the memory leak that Mongrel (Jruby) does, and I
need Nginx to service all other requests on this machine.
I am suspecting that it’s not a BUG but rather a feature.
Glassfish uses:
Transfer-Encoding: chunked
Which is not use by Mongrel or anything else.
And NGINX does not handle it very well.
I guess I can either switch to Apache or try to disable this in
Glassfish. I would rather stick to the lightweightness of NGINX however.
Would you know how to turn off Transfer-Encoding: chunked?
On Aug 20, 2008, at 5:45 AM, Arun G. wrote:
Mongrel/Glassfish to service rails with the following config
But, when I remove Nginx to access Glassfish directly, then things
Blog: http://blogs.sun.com/arungupta
I tried following the instruction by modifying domain.xml in the gem
folder. It did not work.
Is there a way to do this for the Glassfish Gem?
This would be very important to many Ruby on Rails users, as NGINX is
a historically popular front end for them, as opposed to Apache. Many
of Rails users still use NGINX + Mongrel or NGINX + Thin, as Apache is
sometime too thick for them.
Thanks
On Aug 21, 2008, at 4:01 AM, Arun G. wrote:
I am suspecting that it’s not a BUG but rather a feature.
Mongrel/Glassfish to service rails with the following config
But, when I remove Nginx to access Glassfish directly, then things
Blog: http://blogs.sun.com/arungupta