Re: apache vs. tomcat (or glassfish)
Re: apache vs. tomcat (or glassfish)
- Subject: Re: apache vs. tomcat (or glassfish)
- From: Farrukh Ijaz <email@hidden>
- Date: Wed, 8 Sep 2010 10:59:15 +0300
Hi Mike,
I would advise not to go to GlassFish (or even J2EE) path if you are not gonna utilize any J2EE features which must run on a servlet container. Trust me it's a Pain ... to setup and maintain.
Pros:
Can work with other J2EE enabled applications
No more "No instance available" messages, you'll eventually get a response even if your queries take time
GlassFish built-in caching improves application performance
True multi threaded
Cons:
Wrestling with Apache Rewrite Rules and AJP module
Pain to setup GlassFish to support load balancing. If you handle with Apache, you need to setup multiple GlassFish instances (think about in terms of setup, system resources, ports etc.)
WOResponse.contentStream() does not work on Servlet based deployments so you can't stream large content
There are other pain areas which I don't remember now
In simple, for load balancing and to run on Windows, just use traditional WO setup.
Farrukh
On 2010-09-08, at 3:49 AM, Michael Gargano wrote:
> What are the different advantages/disadvantages for the differing deployment options. I'm assuming the main one is that without apache and the adaptor you lose the load balancing and monitoring capabilities. Is this accurate? What is the most common method? My main concerns are scalability and ability to run on windows. (I just made myself sad.)
>
> Thanks.
> -Mike
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden