head	1.7;
access;
symbols
	JSERV_0_10_PREVIEW:1.2.0.2
	JSERV_0_9_11:1.1.0.2;
locks; strict;
comment	@# @;


1.7
date	99.02.02.05.19.07;	author ed;	state Exp;
branches;
next	1.6;

1.6
date	98.12.21.15.54.35;	author ed;	state Exp;
branches;
next	1.5;

1.5
date	98.12.21.14.49.27;	author ed;	state Exp;
branches;
next	1.4;

1.4
date	98.12.21.14.42.00;	author ed;	state Exp;
branches;
next	1.3;

1.3
date	98.12.21.05.23.20;	author ed;	state Exp;
branches;
next	1.2;

1.2
date	98.05.10.18.59.20;	author ed;	state Exp;
branches;
next	1.1;

1.1
date	98.05.10.16.59.26;	author ed;	state Exp;
branches
	1.1.2.1;
next	;

1.1.2.1
date	98.05.19.12.01.37;	author ed;	state Exp;
branches;
next	;


desc
@@


1.7
log
@update classname for JServServlet
@
text
@
INSTALL file for JServ 0.9.12-dev
Authors: Ed Korthof and James Cooper

Table Of Contents

	Road Map
	Installing the JServ Module
	Automatic Mode
	Manual Mode
        Testing JServ
	Available Apache Directives
	General Properties File
	Servlets Properties Files


---------------------------------------------------------------------------
		Road Map

You should follow one of the two paths shown below.  First time users are
highly encouraged to try Automatic Mode first since fewer things can go wrong.

For Automatic Mode:
  1.) Recompile Apache (Installing the JServ Module)
  2.) Set up the Apache Configuration file(s) for Automatic Mode
      (Automatic Mode)
  3.) Set up the JServ Configuration file(s)

For Manual Mode:
  1.) Recompile Apache (Installing the JServ Module)
  2.) Set up Manual Mode (Manual Mode)
  3.) Set up the Apache Configuration file(s) for Manual Mode
      (Manual Mode)
  4.) Set up the JServ Configuration file(s)

When you've followed one of these paths, see the "Testing JServ" section
for a brief test you can do to make sure your installation was successful.

Note that in the text which follows, it has been assumed that JServ
was placed in /local/jserv.  That string should generally be replaced
with the directory in which you wish to place jserv.  You should start by
untarring the distribution, and copying it into that directory.

---------------------------------------------------------------------------
		Installing the JServ Module

First you need to compile mod_jserv.c into Apache.

Apache 1.2.x:

  1) Copy apache/mod_jserv.c into the src directory of your Apache tree
  2) Add this to your Configuration file in the src directory:
       Module jserv_module mod_jserv.o
  3) Type ./Configure while in the src directory
  4) Type make to recompile Apache

Apache 1.3.x:

  1) Copy apache/mod_jserv.c into the src/modules/extra directory of
     your Apache tree
  2) Add this to your Configuration file in the src directory:
       AddModule modules/extra/mod_jserv.o
  3) Type ./Configure while in the src directory
  4) Type make to recompile Apache

   ** Note that there are multiple ways to build Apache 1.3 binaries, the
      method above works, but if you have a different prefered method,
      feel free to use it.  the important thing in any case is to get
      mod_jserv compiled into the binary


When you're done building the binary, double check that mod_jserv made it in.

 in the src directory, type:

  ./httpd -l | grep jserv

 you should see:

  mod_jserv.c

If you don't see that, then double check the above steps and recompile Apache.


---------------------------------------------------------------------------
		Automatic Mode

I. Overview
-----------

In this mode, JServ is started and stopped by Apache.  If the JVM dies 
unexpectedly, Apache will respawn another.

II. Configuration
-----------------

  A. Add Apache directives in srm.conf:

    You need to set the following Apache directives to use this mode:

      ServletPort, ServletAlias, ServletClassPath, ServletBinary,
      ServletProperties

    It is strongly recommended that you use the following directive:

      ServletErrorLog

    This will trap STDERR from the JVM to a file, which is where untrapped
    exceptions will end up.

    The meanings of these directives are shown below, in the section
    "Available Apache Directives"; a sample set of them is shown below.  These
    are typically added to Apache's srm.conf file.

    Example:

	ServletPort 8007
	ServletAlias /servlets /local/jserv/servlets
        ServletAlias /jserv    /local/jserv/jserv-0.9.12.jar
	ServletClassPath /usr/local/java/lib/classes.zip
        ServletClassPath /local/jserv/servclasses.zip
        ServletClassPath /local/jserv/jserv-0.9.12.jar
        ServletClassPath /local/jserv/servlets
	ServletBinary /usr/local/java/bin/java
	ServletProperties /local/jserv/conf/servlet.properties
	ServletErrorLog logs/jserv_errors.log

  B. Create a "Servlet Properties" file

    in the above example, /local/jserv/conf/servlet.properties is the
    Servlet Properties file.  See the "Servlet Properties File" section
    below for a description of the valid properties for this file.

    if you're not sure what to put in this file, simply create an empty
    file with this name.  The servlet you will test below does not require
    any configuration properties.  But be sure to read the "Servlet
    Properties File" section to familiarize yourself with the valid options
    you can place in this file when you write your own servlets.

After you've added these directives, restart Apache.  See the "Testing JServ"
section for an explanation of how to determine if things are working.

---------------------------------------------------------------------------
		Manual Mode

I. Overview
-----------

In this mode, JServ runs as a separate process, requiring its own
initialization and shutdown at system startup and shutdown.  There are
scripts in the manual directory which may be helpful for this.

To use this mode, compile jserv.c (in the manual directory).  You may
need to edit the Makefile options for your system (Linux and Solaris
are shown; options for other systems would be welcome).

II. Configuration
-----------------

  A. Add Apache directives in srm.conf:

       ServletManual On
       ServletPort   8007
       ServletAlias /servlets /local/jserv/servlets
  
     (see the "Available Apache Directives" section below for additional
      directives)

  B. Create "General Properties" file (jserv.properties)

   See the "General Properties File" section below for an explanation of how 
   to write a General Properties file.  This is required in manual mode, and
   enables you to have separate ClassLoaders for different virtual hosts on
   your machine (so each virtual host can have a different CLASSPATH, and
   run separate copies of servlets).

  C. Create a "Servlet Properties" file for each host in jserv.proprties

   See the "Servlet Properties File" section below for an explanation of
   how to write a Servlet Properties file.  an example file is included in
   the distribution in conf/servlet.properties

  D. Create a shell script to start/stop the JServ Java process:

   Edit the jserv.init script, setting the appropriate values for
   several paths, the jserv.properties file, the port, and any other
   available options.

   This shell script also sets your CLASSPATH for Java process.  Make sure
   that servclasses.zip and jserv-0.9.12.jar appear there, or JServ will
   not work.  Note, if you want to turn on tracing (for debugging purposes),
   use jserv-0.9.12-tracing.jar.


After you've added these directives, restart Apache, and run the JServ
start script you created in section D.

---------------------------------------------------------------------------
                Testing JServ

Once you have successfully compiled mod_jserv into Apache, edited your
Apache configuration files, and created a Servlet Properties file, you are
ready to test your configuration.

Automatic Mode:

   Make sure that this appears in you srm.conf (or other Apache .conf file):

   ServletAlias     /jserv  /local/jserv/jserv-0.9.12.jar
   ServletClassPath /local/jserv/jserv-0.9.12.jar

Manual Mode:

   1) Make sure that this appears in you srm.conf (or other Apache .conf file):

   ServletAlias /jserv /local/jserv/jserv-0.9.12.jar 

   2) Make sure jserv-0.9.12.jar is in your CLASSPATH, and that 

Restart Apache and JServ (if you're in manual mode), then request this URL
with your web browser:

http://your.host.com/jserv/org.apache.jserv.JServServlet

You should get a "Hello JServ" message.  If you do not, check your logs
(Apache's error_log, the file specified in ServletErrorLog in Automatic Mode,
or STDERR in Manual Mode).

Troubleshooting:

  1) Double check that the JVM is listening on the ServletPort you specified
     telnet to localhost 8007 and see if you get an answer.  If not, then the
     VM isn't starting up.  Double check your CLASSPATH to make sure that
     jserv-0.9.12.jar and servclasses.zip are both present.

  2) Double check that the user the web server and JServ run as can read all
     the relevant files (classes, .jar/.zip files, properties files)

  3) Consult the JServ log specified in the ServletErrorLog directive (or
     whatever file you're redirecting STDERR/STDOUT to if you're running in
     manual mode).  Any exceptions thrown when the JVM starts will appear here.

  4) Consult Apache's error_log to see if there are any JServ related messages

---------------------------------------------------------------------------
		Available Apache Directives

Unless otherwise stated, all directives are optional.

name:			value:			Manual/Automatic/Both

ServletAlias		(alias) (dir)		B

	the alias is used to map requests to mod_jserv; any URI which begins
	with this string will be handled by mod_jserv.  dir is actually a
	directory, zip, or jar file; it (as well as possibly other paths
	or files) will be searched for servlets when a request matches
	the alias.  ServletAlias is required.

ServletAuthExport	(on|off)		A

	whether or not to allow other modules to have access to JServ's
	authorization information.  not relevant in Manual mode because
	in Manual mode, there is currently no authorization information
	required to talk to the JServ process.

ServletBinary		(executable file)	A

	the full path for the executabe file to use to start the JVM
	when in automatic mode.  ServletBinary is required in
	automatic mode.

ServletClassPath	(path specification)	A

	the classpath for JServ, which the webservers initiates in
	automatic mode.  This is a colon separated list of files,
	directories, zip files, and jar files; it should contain
	the general Java libraries, the 'servclasses.zip' file which
	comes with the JServ distribution, and the JServ class
	files.  For example, it might be the following:
	ServletClassPath /usr/local/java/lib/classes.zip:/local/jserv/servclasses.zip:/local/jserv/jserv-0.9.12.jar
	ServletClassPath is required in automatic mode.

ServletEnvironment	(list of variables)	A

	a space separated list of variable names; these environmental
	variables will be passed on to the JServ processes created in
	automatic mode.  If you use Oracle, eg., you will need to pass
	along ORACLE_HOME and LD_LIBRARY_PATH (which will also need to
	be set in the script whichs starts the webserver).

ServletGeneralProperties (filename)		A

	this is the general properties file given to JServ during
	initialization in automatic mode.

ServletBinaryArgument	(raw arguments)		A

	the arguments to be passed along to the ServletBinary (which
	starts the JVM), when it is launched in automatic mode.
	Here are two examples: -J-mx64m (which sets the maximum heap
	size to 64 MB) and -J-ms16m (which sets the minimum heap
	size to 16 MB).  These numbers are only examples; you should
	use numbers appropriate to your applications, if necessary.

ServletArgument		(raw arguments)		A

	the arguments to be passed to the JServ process, when it is
	launched during the automatic startup process.

ServletErrorLog		(abs or rel file)	A

	the absolute or relative (to the httpd ServerRoot) file will
	be used for logging in Automatic mode.  STDERR and STDOUT from
        the JVM will appear in this file.

ServletManual		(on|off)		B

	this directive determines whether manual mode will be on or
	off; it defaults to off.

ServletPort		(number)		B

	the port is used to connect to JServ.  in manual mode, it
	should correspond to the port used in the script which starts
	JServ.  this directive is required, and should appear before
        any ServletVMHost directives.

ServletVMHost		(host name or ip)	M

	the name (which the server will attempt to resolve to an ip)
	or ip will be used to connect to JServ (the JServ process
	should be running on that machine).

        In JServ 0.9.12, you can include multiple ServletVMHost entries.
        If you do so, JServ will distribute requests between all of these
        entries.  Although Session objects will not be replicated across the
        different VMs, JServ will route requests from a given browser to the
        same VM each time.

        JServ will also attempt to do some basic fault tolerance (if one of the
        VMs is down, requests get re-routed to another VM).
        The format of the directive in this case is: <hostname>:<port>
        For example:

              ServletVMHost  jserv1.apache.org:8007
              ServletVMHost  jserv2.apache.org:8007
              ServletVMHost  jserv3.apache.org:8007

        If no port is given, the port in ServletPort will be used, but the
        ServletPort directive *must* appear before any ServletVMHost 
        directives.

ServletManagerHostName	(arbitrary string)	M

	the string will be used to identify this host when talking to
	JServ; it should correspond to one entry in the jserv.hosts line.


---------------------------------------------------------------------------
		General Properties File

I. Overview
-----------

This file is the general properties is optional in automatic mode, but
required in manual mode.  The directives are as follows:

The General Properties file will be refered to as jserv.properties.  

There are three types of lines that appear in the General Properties file:

 jserv.hosts
    * Occurs only once per file
    * Colon separated list of virtual hosts will be using the JServ.  

 For each host in jserv.hosts you need two additional lines:

   jserv.<hostname>.repository
       * Colon separated list of directories which contain servlets for
         that host.  
       * Also refered to as the "reloadable classpath"
         because JServ will reload servlets that are recompiled in these
         directories without you having to restart the JVM
   jserv.<hostname>.properties
       * Path to the "Servlet Properties" file for this host.
       * See the "Servlet Properties" section below for a list of valid
         properties that can be placed in this file

II. Example
-----------

Here is an example jserv.properties file:

    jserv.hosts=_default_:foo.bar.com
    jserv.foo.bar.com.repository=/home/foo/lib/classes:/www/foo/lib/classes
    jserv.foo.bar.com.properties=/home/foo/conf/servlet.properties
    jserv._default_.repository=/local/apache/lib/classes
    jserv._default_.properties=/local/apache/conf/servlet-default.properties

(_default_ will match any hostname not listed in jserv.hosts.  Use this if you
don't plan to have multiple virtual hosts)

III. Properties Reference
-------------------------

name:			value:			Automatic/Manual/Both

jserv.hosts		host1[:host2:...:hostn]	M

	this directive sets up the virtual hosts which will be handled
	by this JServ.  note that "_default_" is a special value which
	will match any otherwise unmatched request.  also note that
	the name a request gives (which is ordinarily the virtual host
	name) can be overriden with the Apache directive
	ServletManagerHostName.  if there is no host named "_default_"
	then requests whose hostname doesn't match a configured host
	will be rejected.  this directive is required; and for
	each host, jserv.{host}.repository and jserv.{host}.properties
	are required.

jserv.hostX.repository	(classpath spec)	M

	the classpath spec is a colon separated list consisting of
	directories, zip files, and jars.  it will be used to
	extend the classpath of this host.  hostX represents one of
	the hosts configured in the jserv.hosts line.  this directive
	is required in manual mode.  furthermore, each of the listed
	resources *must* exist, or JServ will not work.  the
	value may be empty.

jserv.hostX.properties	(properties file)	M

	the properties file will be the Servlet Properties File,
	documented below.  this directive is required, but the file
	does not need to exist.

jserv.security.localhostonly	(true|false)	M

	this should be set to true if webservers on other machines
	will be talking to this JServ.  otherwise, it should be
	false for security reasons.

jserv.threads (integer)                         B

        as of 0.9.12, JServ supports thread pooling.  if this directive
        is present, JServ will spawn x number of threads, and reuse them
        between requests.

        if this directive is not present, a new Thread will be created per
        request, as in 0.9.11.

        NOTE: this feature is experimental.  Do not set this directive in a
        production environment unless you have conducted your own tests first
        and are happy with the results.

jserv.tracing		(list of numbers)	B

        if you wish to use tracing, make sure that the 
        jserv-0.9.12-tracing.jar file is in the CLASSPATH (instead of
        jserv-0.9.12.jar).  If you forget to this, all the tracing 
        directives will be ignored.

	this directive sets tracing true for each of the specified
	numbers (which may be a bit-wise-OR combination of other
	values).  the list is colon separated.
	this (and the following tracing directives) are valid in
	either mode.

jserv.tracing.Init		(true|false)	B
jserv.tracing.ServiceRequest	(true|false)	B
jserv.tracing.RequestData	(true|false)	B
jserv.tracing.ResponseHeaders	(true|false)	B
jserv.tracing.Signal		(true|false)	B
jserv.tracing.ExceptionTracing	(true|false)	B
jserv.tracing.ServletManager	(true|false)	B
jserv.tracing.Classloader	(true|false)	B
jserv.tracing.ClassloaderVerbose (true|false)	B

	each of these directives turns on (or off -- this will override
	the jserv.tracing line) tracing for the specified type of
	tracing.


---------------------------------------------------------------------------
		Servlet Properties Files

There is one servlet properties file for each host or virtual host,
as configured.  

In Automatic mode, you can specify a separate Servlet Properties file per
virtual host by including a separate ServletProprties directive in each
<VirtualHost> block.

In Manual mode, you specify the Servlet Properties file on each
jserv.<hostname>.properties line.

Each Servlet Properties file may contain any of the following directives, all 
of which are relevant in both Automatic and Manual mode:

name:				value:

servlets.startup		(servlets list)

	comma/space separated list of servlets to started when this
	host/virtual host is initialized.  each can be either an
	absolute name or an alias

servlets.default.initArgs	(raw string)

	this, if present and not empty, will be used as the
	initialization argument to any servlets which don't have their
	own configured initArgs.  when used, it is passed to the init
	function.

servlet.(name).code		(fully qualifed classname)

	this resolves an alias (name) to a class (the value).  if
	aliases are used, you should refer to the servlets by their
	aliases throughout.

servlet.(name).initArgs		(raw string)

	this is the initialization arguments for the class or
	alias "name".  it will be passed in to the init funciton.

        these arguments should be comma separated.  use \, to escape a comma.
        use \= to escape = in a value.  For example:

        servlet.myservlet.initArgs=arg1=value1,arg2=value2,arg3=value3

jserv.timeout		(integer timeout in milliseconds)

	this, if present, is the time a servlet which has been
	told to initialize or destroy itself will be allowed to work before
	being considered a failure.

jserv.autoreload.file		(true|false)

	if true, this will cause the host/virtual host to be
	reloaded (including class files) if the servlets property
	file for that host changes.

jserv.autoreload.classes	(true|false)

	if true, this will cause the host/virtual host to be
	reloaded if any of the class files change).

jserv.cookie.domain

       if set, the JServSessionID cookie set when sessions are created will
       contain a domain="" attribute set to the value of this property.
       for example:

         # set domain mask for all .apache.org servers:
         jserv.cookie.domain=.apache.org

       if this value is not set, the cookie will only be sent back to the 
       hostname that created the cookie.  Be careful to set this value to
       a valid domain.  Netscape Navigator is known to ignore the cookie
       completely if the domain mask is invalid.

jserv.cookie.lifetime  (int[s|m|h|d])

        if set, the JServSessionID cookie set when sessions are created will
        be persistant for the lifetime specified.  example values:

         # persistant for 10 seconds:
         jserv.cookie.lifetime=10s

         # persistant for 1 year:
         jserv.cookie.lifetime=365d

         if this property is not set, the cookie will be transient (ie. will
         go away when the browser exits).

jserv.session.lifetime (int[s|m|h|d])

        if set, JServ will spawn a daemon thread to monitor session objects in
        the VM. If the session goes unused for more than the lifetime specified
        invalidate() will be called on the session, which will remove it from
        RAM.  example values are the same as above:

        # timeout after 1 hour of inactivity
        jserv.session.lifetime=1h

        # timeout after 90 minutes of inactivity
        jserv.session.lifetime=90m

        If this is not set, servlets must call invalidate() on the sessions
        manually.
@


1.6
log
@move JServServlet into the servlets/ subdirectory.
@
text
@d223 1
a223 1
http://your.host.com/jserv/org.apache.jserv.servlets.JServServlet
@


1.5
log
@correctly identify version as 0.9.12-dev pending final releas
@
text
@d223 1
a223 1
http://your.host.com/jserv/org.apache.jserv.JServServlet
@


1.4
log
@updated installation instructions
@
text
@d2 1
a2 1
INSTALL file for JServ 0.9.12
d591 1
a591 1
        manually.@


1.3
log
@set CHANGES and INSTALL back to the 0.9.11 versions; remove the contents
of the doc/ directory (they mostly concern 0.10, not 0.9.x).
@
text
@a0 10
This document briefly explains how to install JServ, for both
automatic and manual mode.  It does not provide in depth information
(README provides that in release 0.9.11), just enough information
(and references) to get you started.

-
 * Authors: 	Ed Korthof
 * Revision:	$Revision: 1.1.2.1 $ 
 * Date:		$Date: 1998/05/19 12:01:37 $
-
d2 2
a7 1
	Making JServ Classes
d11 1
d19 3
a21 1
You should follow one of the two paths shown below:
d24 2
a25 3
  1.) Make the JServ Classes (Making JServ Classes)
  2.) Recompile Apache (Installing the JServ Module)
  3.) Set up the Apache Configuration file(s) for Automatic Mode
d27 1
d30 3
a32 4
  1.) Make the JServ Classes (Making JServ Classes)
  2.) Recompile Apache (Installing the JServ Module)
  3.) Set up Manual Mode (Manual Mode)
  4.) Set up the Apache Configuration file(s) for Manual Mode
d34 4
d45 5
a49 1
		Making JServ Classes
d51 5
a55 2
On some systems, you can go to /local/jserv and run make.  This
may work -- or it may not.
d57 1
a57 6
If it fails, you can set your class path to an appropriate value.
Assuming you installed jserv in /local/jserv and java in /usr/local/java,
that could be (in csh, then sh):
setenv CLASSPATH /usr/local/java/lib/classes.zip:/local/jserv/servclasses.zip:/local/jserv/src
    or
CLASSPATH=/usr/local/java/lib/classes.zip:/local/jserv/servclasses.zip:/local/jserv/src; export CLASSPATH
d59 6
a64 1
Then compile all the java files (assuming you're in /local/jserv):
d66 4
a69 1
javac src/org/apache/*/*.java src/org/apache/util/*/*.java
a70 2
Note that the directory for the JServ classes is now:
/local/jserv/src
d72 1
a72 2
The file for the JSDK classes is
/local/jserv/servclasses.zip
d74 1
a74 1
These will be needed later.
d76 1
d78 3
a80 2
---------------------------------------------------------------------------
		Installing the JServ Module
d82 1
a82 4
You may need to recompile Apache in order to use JServ.  If this is
the case, follow the directions in the README file (basically, copy
mod_jserv.c to the appropriate source directory in Apache, edit the
Configuration file and the Makefile, run Configure, and then use make).
d88 5
a92 1
In this mode, JServ is started and stopped by Apache.
d94 2
a95 1
You need to set the following Apache directives to use this mode:
d97 1
a97 2
ServletPort, ServletAlias, ServletClassPath, ServletBinary,
ServletProperties
d99 1
a99 1
It is strongly recommended that you use the following directive:
d101 2
a102 1
ServletErrorLog
d104 14
a117 3
The meanings of these directives are shown below, in the section
"Available Apache Directives"; a sample set of them is shown below:
	ServletPort 8008
d119 5
a123 1
	ServletClassPath /usr/local/java/lib/classes.zip:/local/jserv/servclasses.zip:/local/jserv/src
d125 1
a125 1
	ServletProperties /local/jserv/conf/jserv.properties
d128 14
d146 3
d157 4
a160 29
You will need to write a configuration file at this point -- this file
will be refered to as jserv.properties.  It needs to have at least three
entries: first, it needs to have a "jserv.hosts" line, indicating which
virtual hosts will be using the JServ.  For each of those hosts, there
should be two directives: "jserv.${host}.repository" and
"jserv.${host}.properties".  The following is a sample jserv.properties
file:
	jserv.hosts=_default_:foo.bar.com
	jserv.foo.bar.com.repository=/home/foo/lib/classes:/www/foo/lib/classes
	jserv.foo.bar.com.properties=/home/foo/conf/servlet.properties
	jserv._default_.repository=/local/apache/lib/classes
	jserv._default_.repository=/local/jserv/conf/jserv.properties._default_
(_default_ is a special value documented in manual/README.)

Then edit the scripts start-jserv and stop-jserv (or, if you'd rather
use a single script, jserv.init), setting the appropriate values for
several paths, the jserv.properties file, the port, and any other
available options.

The format of the properties files for each of the hosts is documented
below, in the section "Servlet Properties Files".

The last thing you need to do is to reconfigure Apache -- the following
directives (which can be in any of the conf files other than .htaccess
files) are needed:

ServletManual On
ServletPort {port}
ServletAlias /servlets /local/jserv/servlets
d162 6
a167 2
The meaning of these directives, as well as a list of all available
directives can be found below, in the section "Available Apache Directives".
d169 1
a169 1
After you've added these directives, restart Apache.
d171 73
d281 1
a281 1
	ServletClassPath /usr/local/java/lib/classes.zip:/local/jserv/servclasses.zip:/local/jserv/src
d292 1
a292 1
ServletGeneralProperties(filename)		A
d314 2
a315 1
	be used for logging in Automatic mode.
d326 2
a327 1
	JServ.  this directive is required.
d335 19
d363 3
d369 38
d444 13
d459 5
d486 4
a489 1
		Servlets Properties Files
d491 9
a499 3
There is one servlets properties file for each host or virtual host,
as configured.  That file may contain any of the following directives,
all of which are relevant in either mode:
d527 2
a528 1
jserv.init.timeout		(integer timeout in milliseconds)
d530 1
a530 3
	this, if present, is the time a servlet which has been
	told to initalize itself will be allowed to work before
	being considered a failure.
d532 1
a532 1
jserv.destroy.timeout		(integer timeout in milliseconds)
d535 1
a535 1
	told to destroy itself will be allowed to work before
d549 43
@


1.2
log
@Note change to 0.9.12-dev
@
text
@d3 1
a3 1
(README provides that in release 0.9.12-dev), just enough information
d8 2
a9 2
 * Revision:	$Revision: 1.1 $ 
 * Date:		$Date: 1998/05/10 16:59:26 $
@


1.1
log
@installation instructions (simplified from the README).
@
text
@d3 1
a3 1
(README provides that in release 0.9.11-release-canidate), just enough information
d8 2
a9 2
 * Revision:	$Revision: 1.0 $ 
 * Date:		$Date: 1998/05/09 19:46:00 $
@


1.1.2.1
log
@release 0.9.11
@
text
@d3 1
a3 1
(README provides that in release 0.9.11), just enough information
@


