I’m preparing my slides for Rails Conf next week and the topic is “Rails
powered by GlassFish”. If you are working/aware of on any project that
is deploying Rails application on GlassFish then let me
know. I’ll be happy to give a 30-second highlight in my talk.
Here is what I need:
Title:
Public URL:
Brief Description:
Credits (icon if possible):
On Thu, Aug 28, 2008 at 10:14 AM, Albert R. [email protected] wrote:
Auktionskompaniet.com
http:://www.auktionskompaniet.com
Auction site with Live auctions and Online auctions both.
Main devs are: Me (Albert R.) and Andreas Alin. Other contracted
devs used: Teddy Zetterlund, Carl-Johan K. and jnicklas
http:://www.auktionskompaniet.com
Auction site with Live auctions and Online auctions both.
Main devs are: Me (Albert R.) and Andreas Alin. Other contracted
devs used: Teddy Zetterlund, Carl-Johan K. and jnicklas
A tip to all of you considering glassfish and rails. Dont skimp on
ram! 2GB was what we are on now, and it is really not enough. We have
the app servers running crontasks, and when the glasshfish instance
fights for ram with the runner… its not a pretty sight. We are going
for 8 GB asap.
This is a pretty small site. This is a traditional auction house, who
wanted online presence, so most of their userbase was naturally not
online-based. Today the page view count was ~125k, so the load load
wasnt an issue for us. I havent checked the number of concurrent
requests, but as previously said, the load isnt big right now.
Our setup is like this:
We have 5 boxes, 2 app servers, one nfs server, two database servers
(1 master and 1 slave, only used as backup).
The app servers run glassfish, one instance each. Jruby runtimes are
set to min 2 and max 4. The boxes are single quad core xeons.
The app servers both run a nginx web server for the static files, and
for load balancing betweeen themselves. One of the app servers
is the “main” node, and the slave will take over if the main fails. We
use heartbeat for this. I.e no BIG-IP.
The glassfish version we use is the one that is in Ubuntu 8.04. I dont
know if this is recommended, or if there are better versions out
there, but this worked out for us, after some configuration - the
initscripts are not included when installing via apt.
We might buy a support contract, but frankly I dont know what such a
contract would help us with. We could use help tuning glasshfish
maybe, but what are the main benefits from having a support contract
like that?
Albert
devs used: Teddy Zetterlund, Carl-Johan K. and jnicklas
know. I’ll be happy to give a 30-second highlight in my talk.
Your advise on the configuration is useful too. Can you provide some
more details - how many concurrent requests, app server instances, any
front-end server, BIG-IP? or other relevant stuff.
Are you using GlassFish or the corresponding production version ?
Have you considered buying support contract for GlassFish ?
Thanks for your response, this project will be now part of my talk next
week I’ll share the slides here.
See in line …
We have 5 boxes, 2 app servers, one nfs server, two database servers
(1 master and 1 slave, only used as backup).
The app servers run glassfish, one instance each. Jruby runtimes are
set to min 2 and max 4. The boxes are single quad core xeons.
The app servers both run a nginx web server for the static files, and
for load balancing betweeen themselves. One of the app servers
is the “main” node, and the slave will take over if the main fails. We
use heartbeat for this. I.e no BIG-IP.
Thanks for this configuration, I’ll include it in my talk.
The glassfish version we use is the one that is in Ubuntu 8.04. I dont
know if this is recommended, or if there are better versions out
there, but this worked out for us, after some configuration - the
initscripts are not included when installing via apt.
Can you please file a bug for this at:
We might buy a support contract, but frankly I dont know what such a
contract would help us with. We could use help tuning glasshfish
maybe, but what are the main benefits from having a support contract
like that?
There are several benefits (based upon subscription level) that are
outlined at:
The key highlights are:
Sun-branding & Indemnification
Pre-defined SLA
Access to Sun Knowledge Base, Patches Security Alerts
Email/Phone support
There are sustaining releases which are made available to paid customers
only. These are integrated in the open source version for each major
release only. The benefits on those lines are highlighted at:
I’ll share the slides here.