Tomcat doesn't do what weblogic does. Weblogic is a J2EE container; Tomcat
is a servlet container. J2EE is more than servlets.

You might also consider Orion (www.orionserver.com) - it's also a J2EE
container, runs much faster than WebLogic (although BEA won't allow anyone
to publish benchmarks - I wonder why?) and has a price tag of $1500,
compared to BEA's open pricing.

---------------------------------------------------
Joseph B. Ottinger               [EMAIL PROTECTED]
http://adjacency.org                  IT Consultant



>From: Daniel Jaffa <[EMAIL PROTECTED]>
>Reply-To: A mailing list about Java Server Pages specification and
>reference <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Platform choice advice for deploying a website
>Date: Wed, 24 Oct 2001 04:11:58 +0000
>
>Getting a little off topic here: Can tomcat handle load of up to 70k - 120k
>hits an hour.  Or would i have to go to a product like WebLogic.
>
>The reason i ask is that i have been building with weblogic and when it
>comes time for the client to pay the bill they always gag at the price.
>And
>if TomCat + apache can fit the bill for free well then of TomCat i will go.
>
>
>
>
>----Original Message Follows----
>specification and reference <[EMAIL PROTECTED]>
>
>This is actually a current topic of discussion on the
>[EMAIL PROTECTED] mailing list.
>
>What I mentioned is more of a rule of thumb since I don't know of any
>Tomcat+Apache benchmarks. You would need to look into your own business
>needs and performance criteria. When you look at volume you don't just need
>to look at the number of hits. You have to look at the information that you
>are serving. What is it? Is it a set of static pages or a set of dynamic?
>How many requests of that content do you really need to handle per second?
>
>As for security, Tomcat 4.0 has container-managed security that you can
>install on a per webapp basis. Among other things, you also can setup
>access
>logging and ssi.
>
>Justy
>
>----- Original Message -----
>From: "Haseltine, Celeste" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Tuesday, October 23, 2001 12:52 PM
>Subject: Re: Platform choice advice for deploying a website
>
>
> > Justyna,
> >
> > This addresses an issue we have been discussing up here at work.  Is the
> > "rule of thumb" always "the number of static pages vs the number of
>dynamic
> > pages" in determining whether you need to run a JSP/Servlet server as a
> > stand alone server, or in conjunction with an HTML server, such as
>Apache
>or
> > IIS?  What weight in the decision process do you give the "volume" or
> > "number of hits" you expect your web site to generate in making your
> > decision regarding servers?  And where do security considerations play
>into
> > the decision making process regarding using a stand alone JSP server vs
>an
> > HTML and JSP server together (such as Apache + Tomcat), or do they play
>in
> > at all?
> >
> > My thanks in advance to anyone with additional advice on this topic.
>Also,
> > if anyone has any good references/sites that discuss this topic in
>general,
> > I would be interested in them.
> >
> > Celeste
> >
> > -----Original Message-----
> > From: horwat [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, October 23, 2001 1:51 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Platform choice advice for deploying a website
> >
> >
> > You can minimize your pain threshold by analyzing what type of server
>you
> > need. Is it going to be large volume with many static pages and a couple
>of
> > dynamic pages? Then you should use Apache + Tomcat.
> >
> > Now, if your server isn't going to be large volume or has mostly dynamic
> > pages then you should really consider running Tomcat standalone. You
>dynamic
> > pages would not be relayed through Apache but be served directly by
>Tomcat.
> > It is much easier to configure Tomcat standalone than configure two
>servers
> > and the connector between them.
> >
> > As for documentation, I would look at the apache site for both products:
> >
> > http://www.apache.org
> > http://jakarta.apache.org/tomcat
> >
> > Justy
> >
> >
> > ----- Original Message -----
> > From: "Paul Idusogie" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Monday, October 22, 2001 3:06 PM
> > Subject: Platform choice advice for deploying a website
> >
> >
> > > Hello Folks:
> > >
> > > I need your advice on the best approach due to budgetry constraints.
> > > I'm considering learning Linux to deploy my website using apache as my
> > > web server and tomcat as the servlet container. Could any one provide
> > > suggestions on books, linux version and the pain threshold.
> > >
> > > I can not afford Windows 2000 server software.
> > >
> > >
>
>
>
>_________________________________________________________________
>Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
>===========================================================================
>To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
>JSP-INTEREST".
>For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
>DIGEST".
>Some relevant FAQs on JSP/Servlets can be found at:
>
>http://archives.java.sun.com/jsp-interest.html
>http://java.sun.com/products/jsp/faq.html
>http://www.esperanto.org.nz/jsp/jspfaq.jsp
>http://www.jguru.com/faq/index.jsp
>http://www.jspinsider.com


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:

 http://archives.java.sun.com/jsp-interest.html
 http://java.sun.com/products/jsp/faq.html
 http://www.esperanto.org.nz/jsp/jspfaq.jsp
 http://www.jguru.com/faq/index.jsp
 http://www.jspinsider.com

Reply via email to