I have been attempting to mug on Glassfish and something factor that keeps approaching may be the "how-to" on fronting Glassfish with Apache. Regrettably, I haven't yet look for a description of why you would like to do that!

From the experimentation, Glassfish appears just like a pretty fully featured web server-type service however i may be missing a great deal. So, may be the perception of front-ending Glassfish much more of a strategy to integrate it by having an existing architecture, or does front-ending (inside a pure Java atmosphere) provide extra benefits?

Additionally, there are another valid use situation why we front Glassfish with Apache. Apache in cases like this would be the reverse proxy for elevated security of the Glassfish. The RP is set up to permit only certain Web addresses to become passed right through to the applying server. For e.g., you might have application contexts /myApp and /myPrivApp used in Glassfish. Within the RP server, you simply configure /myApp to become passed to Glassfish. Anybody asking for for /myPrivApp would visit a 404 'cos the request stops right in the RP level.

In a single of my deployments, I've got a couple of WARs used, some for customers from the internet, some for intranet only. I've 2 RPs running, one for internet customers and also the other for intranet. I configure the web RP to simply allow Web addresses for approved internet programs to feed while intranet customers see everything.

Hope that can help.

It is almost always accustomed to quicken things. Since apache is an extremely fast web server it's accustomed to deliver static content. Like images, CSS files and so forth. Glassfish serves the dynamic content (servlets, JSPs) within this scenario.

One more reason for implementing Apache like a frontend to Glassfish may be the possible ways to provide load balancing across a Glassfish cluster. See http://tiainen.sertik.net/2011/03/load-balancing-with-glassfish-31-and.html for particulars.