Nathan,

There is pretty good documentation both on the website and contained within
the distributions in the doc/ directory. There is no "John Q's Chronicle of
Setting Up Tomcat 3.3.1" to the best of my knowledge. However, I think that
something like that would be a great thing to write and submit to the
developer list. If I only had the time... ;)

This is for 4.0:
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/index.html

http://jakarta.apache.org/tomcat/tomcat-4.0-doc/appdev/index.html

and for 3.3.1
http://jakarta.apache.org/tomcat/tomcat-3.3-doc/index.html

The source code is another good place, at least to understand the
architecture or finer points of performance.

The performance of your Servlets hitting the database is pretty much up to
the developers of your Servlets and the database machine.

Making Tomcat 3.3.1 bulletproof probably means stripping out the
non-essential items (examples/ test/ admin/), making sure your webapps are
performance demons, creating a proper set of workers/connectors to your
load, and making sure you have enough memory. You might also have to play
with the Session manager params too. Taking down your log levels is a
possible performance gain too. If you define any Context entries in
server.xml, set reloadable="false". Having a webserver like Apache handle
static content is a plus.

A search of the mailing list for similar topics might yield some fruit, as
well as a general call for folks to write up their ten best tips and tricks,
and submit it to the list. Maybe we can put together a document between us.

Regards,
Michael

----- Original Message -----
From: "Nathan Smith" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Sunday, July 28, 2002 11:38 PM
Subject: Tomcat developer or user documentation.


    Is their anywhere some really solid indepth documentation for setting up
and maintaining tomcat for production or development environments.
I need to tweak Tomcat 3.3.1 so that it is basically bulletproof and will
not fall over under strenuous use, or basically when many users are querying
a database and waiting for results concurrently.

The more advanced information the better, thanks.

Nathan.



----------------------------------------------------------------------------
----


> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to