cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml configwebcom.xml
costin 2003/03/06 11:45:27
Modified:jk/xdocs/jk2 configweb.xml configwebcom.xml
Log:
Updated the documentations.
Revision ChangesPath
1.17 +119 -68 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml
Index: configweb.xml
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- configweb.xml 11 Dec 2002 20:56:42 - 1.16
+++ configweb.xml 6 Mar 2003 19:45:27 - 1.17
@@ -7,94 +7,145 @@
date$Date$/date
/properties
section name=Intro
-pJk2 uses a config file ( workers2.properties ) in the style of a
.properties or ini
- file. It can be configured to use any other backend that provides similar
- capabilities.
- /p
-p
- This document describes the format of this configuration file. Its default name
is ${serverRoot}/conf/workers2.properties,
- where ${serverRoot} is something like /opt/apache.
-/p
+
+pJk2 uses an architecture and configuration mechanism modeled after JMX.
It consist of
+jk_bean components, with a registry and API that attempts to mirror JMX./p
+
+pAs in JMX, multiple config formats and stores are possible. The default
is a neutral .INI-style
+file, and Apache2 also supports configuration in httpd.conf. Other formats and
repositories can be
+easily implemented, but the general concept is the same./p
+
+pEach component has a name, a type and a set of attributes. Reasonable
defaults are provided, and
+some components are created automatically using the defaults if not explicitely
configured.
+You need to specify the config only where you want to override the defaults./p
+
/section
-section name=Config file
-p The default config file is user editable, but mod_jk may persist
-changes requested by protocol. If you manually change the file while jk2 is
-working and make changes using jkstatus or a jmx proxy, your changes will be lost.
- /p
-
-pJk2 is modeled after JMX. It consist of a number of named components, each having
-certain management attributes. In order to configure jk2 you need to create
-the components and set the desired attributes. /p
-
-pThe format of the default config file. Each setting consists of an
object
-name and a property, with the associated value. The property name is a simple
- string, with no '.' in it. The name has 2 parts, separated by :. The first part
-is the component type, and the second is the local part of the name.
- /p
-p2 formats are supported:
+
+section name=Config file format
+
+pThe config file is named workers2.properties, located by default in
${serverRoot}/conf,
+where ${serverRoot} is the web server dir, like /usr/local/apache. It is possible
to modify the location
+of the file using server-specific directives./p
+
+pSettings are grouped in sections - one section for each object. The
section head is the component
+name, and must include the type and local name of the component, separated by :.
Inside each section
+you must define the attributes of the component. The attribute name is a simple
string, with no '.' or
+special characters. The value is a string - no quoting is currently supported. It
should be noted that
+the component name is processed to compute default for the component attributes -
for example
+[channel.socket:localhost:8009] name will create a socket channel object with
host=locahost and
+port=8009. You don't need to provide this information twice. It is highly
recommended to use
+this naming scheme for consistency, even if you could use any name and then specify
the properties
+explicitely./p
+
+pThe general syntax is:
source
-TYPE:NAME.PROPERTY=VALUE
+[TYPE:NAME]
+PROPERTY=VALUE
/source
/p
-pand
+
+pIt is also possible to use an alternate format, mostly for backward
compatibility:
source
-[TYPE:NAME]
-PROPERTY=VALUE
+TYPE:NAME.PROPERTY=VALUE
/source
/p
/section
-section name=Advanced: reconfiguration
-pOne of the features ok jk2 is support for (partial) reconfiguration at
runtime, without a restart. The main
-use is to add/remove/change workers and uris. This allows smooth updates, without
server restarts, where each
-worker is upgraded while the other workers server content. /p
-
-pThe jk2 architecture is modeled after JMX, and in future it'll have a JMX proxy
that will make most
-reconfiguration transparent. This section describes the mechanisms used for
reconfiguration./p
-
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
costin 2002/12/11 10:37:56 Modified:jk/xdocs/jk2 configweb.xml Log: Added a section on runtime reconfiguration. Revision ChangesPath 1.13 +37 -1 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml Index: configweb.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- configweb.xml 3 Oct 2002 15:34:10 - 1.12 +++ configweb.xml 11 Dec 2002 18:37:56 - 1.13 @@ -38,4 +38,40 @@ /source /p /section + +section name=Advanced: reconfiguration +pOne of the features ok jk2 is support for (partial) reconfiguration at runtime, without a restart. The main +use is to add/remove/change workers and uris. This allows smooth updates, without server restarts, where each +worker is upgraded while the other workers server content. /p + +pThe jk2 architecture is modeled after JMX, and in future it'll have a JMX proxy that will make most +reconfiguration transparent. This section describes the mechanisms used for reconfiguration./p + +pEach Jk2 component has a name and a number of attributes. The config is abstracted - but for simplicity +we'll discuss the default ( ini-file ) format. Some of the attributes and components support run time +changes. The most important is disabled, that allows a component to be included or excluded from +the runtime. /p + +pThe easiest way to reconfigure jk2 is by making modifications to the config file. Jk will +process the file again and call the setters for attributes - including disabled, etc. Only +components and attributes that include support for reloading will be affected. +/p + +pThe reconfig is enabled by using a flag in the scoreboard. The flag can be set programmatically, +or it'll be set automatically every time the jk_status page is displayed if a change is +detected in the config file /p + +pA more advanced ( and less tested ) reconfiguration mechanism uses the jk_config API, called +programmatically using messages from server or using jk_status web interfaces. Every time +a change is made, the config file will be written ( for persistence and to allow other processes to +get the same change ). The scoreboard will be changed, and then all other server processes will +act just like in the case of a file change./p + +pA typical user will just edit the config file, add more workers or URIs or change disabled flag +of existing workers/uris. Then it'll access the jk_status page, which will detect the config +file changes and reload the config in the current server process, and use the scoreboard to +inform other server processes of the change. /p + + + /document -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
costin 2002/12/11 10:53:16 Modified:jk/xdocs/jk2 configweb.xml Log: Added a section on server-specific config ( httpd.conf ). Added a small note on the config generator (I'll expand it later, I hope ). I'm very bad with writing docs - if someone can translate this stuff in english I would apreciate it :-) Revision ChangesPath 1.14 +36 -1 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml Index: configweb.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- configweb.xml 11 Dec 2002 18:37:56 - 1.13 +++ configweb.xml 11 Dec 2002 18:53:16 - 1.14 @@ -72,6 +72,41 @@ file changes and reload the config in the current server process, and use the scoreboard to inform other server processes of the change. /p +section name=Server-specific configuration + +pSince the config is abstracted, some servers ( Apache2 only at this moment ) may support a +server-specific configuration mode. This configuration mode is less tested - but provides some +unique advantages (and disadvantages )/p + +pI'll describe the apache2 specifics, since this is the only one implemented. In this mode the +config will be included in httpd.conf. The JkSet top-level directive is used to set global +config options, and JkUriSet is used to set options for Location sections/p + +pYou can mix workers2.properties and JkUriSet - for example workers and global options +can be set in worker2.properties, but all uri properties in httpd.conf. Some people +might preffer to have only one config file and use httpd.conf for all configuration./p + +pEach Location that has a JkUriSet will automatically create a jk2 [uri] object, +using the Location path and the vhost. All JkUriSet directives will set attributes +in this [uri] object, exactly like properties in a ini file section/p + +pThe biggest benefit is that Apache2 mapping is used instead of jk2 to detect the +requests that need to be sent to tomcat. Apache2 has been optimized and tuned to +server huge number of servers and uris - if you have only few the diference may be +hard to notice. Some people preffer to use the httpd.conf format and some tools +could be better used in this mode./p + +pOne major problem is that reconfiguration is not supported if httpd.conf is used. +You can still enable/disable/add workers if you use workers2.properties, and +you could add or change uri properties in that file. /p + + +section name=Config generators +pThere is work in progress to support automatic generation of the config file. The code is +included in org.apache.jk.config and consist of a number of ant tasks ( that work from CLI as well) + that process web.xml files and generate worker2.properties or server-specific config files/p + + /document -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
costin 2002/12/11 11:01:36 Modified:jk/xdocs/jk2 configweb.xml Log: Revision ChangesPath 1.15 +12 -7 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml Index: configweb.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- configweb.xml 11 Dec 2002 18:53:16 - 1.14 +++ configweb.xml 11 Dec 2002 19:01:36 - 1.15 @@ -17,14 +17,19 @@ /p /section section name=Config file -p The default config file is user editable, but mod_jk will persist the -changes requested by protocol( not implemented). If you manually change the file while jk2 is -working, your changes will be lost. +p The default config file is user editable, but mod_jk may persist +changes requested by protocol. If you manually change the file while jk2 is +working and make changes using jkstatus or a jmx proxy, your changes will be lost. /p -pThe default configuration format . . Each setting consists of an object + +pJk2 is modeled after JMX. It consist of a number of named components, each having +certain management attributes. In order to configure jk2 you need to create +the components and set the desired attributes. /p + +pThe format of the default config file. Each setting consists of an object name and a property, with the associated value. The property name is a simple - string, with no '.' in it. The name can be anything, but it must have a -known 'type' as prefix. + string, with no '.' in it. The name has 2 parts, separated by :. The first part +is the component type, and the second is the local part of the name. /p p2 formats are supported: source -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
costin 2002/12/11 12:56:43 Modified:jk/xdocs/jk2 configweb.xml Log: Added /section, thanks Mark. Revision ChangesPath 1.16 +4 -2 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml Index: configweb.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- configweb.xml 11 Dec 2002 19:01:36 - 1.15 +++ configweb.xml 11 Dec 2002 20:56:42 - 1.16 @@ -77,6 +77,7 @@ file changes and reload the config in the current server process, and use the scoreboard to inform other server processes of the change. /p +/section section name=Server-specific configuration pSince the config is abstracted, some servers ( Apache2 only at this moment ) may support a @@ -105,13 +106,14 @@ You can still enable/disable/add workers if you use workers2.properties, and you could add or change uri properties in that file. /p - +/section section name=Config generators pThere is work in progress to support automatic generation of the config file. The code is included in org.apache.jk.config and consist of a number of ant tasks ( that work from CLI as well) that process web.xml files and generate worker2.properties or server-specific config files/p +/section /document -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
mturk 2002/10/02 23:58:24 Modified:jk/xdocs/jk2 configweb.xml Log: Add the channel.apr and explain new options for the load balancer. Revision ChangesPath 1.10 +87 -3 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml Index: configweb.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- configweb.xml 26 Sep 2002 07:37:21 - 1.9 +++ configweb.xml 3 Oct 2002 06:58:24 - 1.10 @@ -287,6 +287,66 @@ /table /p /subsection +subsection name=channel.apr +p +A communication transport to a remote Engine using APR library +bMagic:/b The local part of the name will be the Engine name, +to use when defining the uri mappings. For example +channel.apr.local_9009 will automatically define an engine named +local_9009, and if no other setting is set ajp13 will be used for +communication. +bMagic:/b If no channel is defined in the config, a default channel +will be constructed with port=8009, engine=DEFAULT, worker=ajp13 - +named 'channel.apr.DEFAULT' +/p +p +table +tr +thProperty name/th +thDefault/th +thDescription/th +/tr +tr +tdport/td +td8009/td +tdPort where Tomcat is listening/td +/tr +tr +tdhost/td +tdlocalhost/td +tdRemote host/td +/tr +tr +tdkeepalive/td +td0 (disabled)/td +tdIf set to 1 then it enables the use of keep-alive packets on TCP connection /td +/tr +tr +tdtimeout/td +td0 (infinite)/td +tdSocket timeout for sending and receiving/td +/tr +tr +tdndelay/td +td0/td +tdIf set to 1 Disables the Nagle algorithm for send coalescing/td +/tr +tr +tdlbfactor/td +td1/td +td +Load balancing factor to use. At this moment, it'll be set on the worker, +but in future it should be possible to use lb on a channel level. + /td +/tr +tr +tdgroup/td +tdlb:0/td +tdloadbalanced groups to which this channel and the associated worker will be added, multivalued/td +/tr +/table +/p +/subsection subsection name=channel.jni pThe jni channel, used if tomcat is started inprocess/p /subsection @@ -296,9 +356,9 @@ For the moment 4 worker types are supported: worker.jni,ajp13,status,lb. /p subsection name=worker.jni -pworker used in inprocess, holds the details of the Tomcat class to startup, and paramters to pass/p +pworker used in inprocess, holds the details of the Tomcat class to startup, and parameters to pass/p pThere are two predefined jni workers bonStartup/b and bonShutdown/b. Those two workers are executed -during sturtup and shutdown phase of the connector. Both must exsist in the configuration to be able to start +during startup and shutdown phase of the connector. Both must exists in the configuration to be able to start and shutdown Tomcat. /p p @@ -409,6 +469,30 @@ td/ td/ /tr +tr +tdtimeout/td +td0 (disabled)/td +tdIf all the workers are in the error state, probably by Tomcat +refusing any new connections due to the overload, you can set the timeout forcing lb to wait that some +worker becomes available, instead of immediately returning error to the
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
mturk 2002/10/03 03:52:16 Modified:jk/xdocs/jk2 configweb.xml Log: Add the explanation about uri:*:port scheme. Revision ChangesPath 1.11 +8 -1 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml Index: configweb.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- configweb.xml 3 Oct 2002 06:58:24 - 1.10 +++ configweb.xml 3 Oct 2002 10:52:16 - 1.11 @@ -151,7 +151,14 @@ p Special case is a default server named as b[uri:*]/b that is used when the virtual host cannot be found inside the configuration. All the uri directives not containing -host name belongs to this default server making global mappings.br / +host name belongs to this default server making global mappings. +/p +p +Addition wild char scheme id b[uri:*:port]/b that is used when you wish to +match any virtual host having specified (non-default) port number, like [uri:*:443]. +This will map all the virtual hosts no mather what is their name but that have port number 443. +/p +p The order how the host names are resolved is : ul liExact host name and optional non default port number/li -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml configtc.xml
mturk 2002/10/03 08:34:10
Modified:jk/xdocs/jk2 configweb.xml configtc.xml
Log:
Add new splitted documents
Revision ChangesPath
1.12 +1 -592jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml
Index: configweb.xml
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- configweb.xml 3 Oct 2002 10:52:16 - 1.11
+++ configweb.xml 3 Oct 2002 15:34:10 - 1.12
@@ -1,7 +1,7 @@
?xml version=1.0?
document
properties
-titleConfiguration in the Web Server/title
+titleConfiguration file/title
author email=[EMAIL PROTECTED]Costin Manolache/author
author email=[EMAIL PROTECTED]Jean-Frederic Clere/author
date$Date$/date
@@ -37,596 +37,5 @@
PROPERTY=VALUE
/source
/p
-/section
-section name=ComponentspEach component instance has a name, that is used
for configuration and at runtime. Each component has a number of configurable
properties. The following rules are used:
-ulliThe name is composed from the type and a local part, separated with a ':' (
example: channel.unixsocket:/tmp/jk.socket ) /li
-liThe 'type' consist of '.' and ascii characters. It is mapped to a JMX
'domain'. /li
-liThe local part consists of ascii characters and .:/;
-pNote that '=,' are not currently allowed - a future version may support the jmx
syntax by using quotes to separate the local part from the property and value ( in
.properties mode we must use '=' to separate the value from type, local name and
property name ). /p/li
-liThe property is a simple name, with no dots. /li
-liA simple form of substitution is used in values, where $(property) will be
replaced with a previously defined setting. If the property has ':' in it, it'll take
the value from the object, if not it'll take the value from a global map./li/ul/p
-subsection name=Common properties
-pCommon properties for all components/p
-p
-table
-tr
-thProperty name/th
-thDefault/th
-thDescription/th
-/tr
-tr
-tddisabled/td
-td0 (false)/td
-tddisabled state for the component, 1=true 0=false/td
-/tr
-tr
-tddebug/td
-td0 (false)/td
-tddebug state for the component, 1=true 0=false/td
-/tr
-/table
-/p
-/subsection
-subsection name=workerEnv
-pThis component represent the core jk2, it has the default logger for
all other components. Is the central controller, it controls global properties
-and provides access to all other objects/p
-p
-table
-tr
-thProperty name/th
-thDefault/th
-thDescription/th
-/tr
-tr
-tdlogger/td
-tdlogger/td
-tdDefault loger used by jk2 components, can be changed in
the config file, normally it defaults to logger the Alias for the default logger for
the Server/platform./td
-/tr
-tr
-tdtiming/td
-td0/td
-tdWill jk2 get request timing (needs APR?)/td
-/tr
-/table
-/p
-/subsection
-subsection name=config
-pThe config component, hold the detail of the conifg system, such
config file name, create global defines/p
-p
-table
-tr
- thProperty name/th
- thDefault/th
- thDescription/th
-/tr
-tr
-tdfile/td
-td${serverRoot}/conf/workers2.properties/td
-tdLocation of the workers2.properties file/td
-/tr
-tr
-tddebug/td
-td0/td
-tdSet the debug level of the config component/td
-/tr
-tr
-tddebugEnv/td
-td0/td
-tdSet the debug level of the hidden env component /td
-/tr
-/table
-
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
remm2002/09/26 00:37:21
Modified:jk/xdocs/jk2 configweb.xml
Log:
- Add missing start element.
Revision ChangesPath
1.9 +3 -2 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml
Index: configweb.xml
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- configweb.xml 26 Sep 2002 06:22:06 - 1.8
+++ configweb.xml 26 Sep 2002 07:37:21 - 1.9
@@ -98,7 +98,8 @@
thProperty name/th
thDefault/th
thDescription/th
- /tr
+/tr
+tr
tdfile/td
td${serverRoot}/conf/workers2.properties/td
tdLocation of the workers2.properties file/td
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
mturk 2002/09/25 09:47:14 Modified:jk/xdocs/jk2 configweb.xml Log: Add more desription to the uri section. Please check the english used :) Revision ChangesPath 1.7 +26 -7 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml Index: configweb.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- configweb.xml 20 Sep 2002 21:35:31 - 1.6 +++ configweb.xml 25 Sep 2002 16:47:14 - 1.7 @@ -133,8 +133,25 @@ subsection name=uri pA uri stores a pattern that is used to match requests to workers, and asociated properties/p +pIf the uri name doesn't have a slash then it is considered as a virtual host +directive. Uri name can have a virtual host name and(or) port associated with. Format +of such a name is bhostname/b or bhostname:port/b where hostname +is virtual server name and the port is vitual server port number. The port number +is used only for the non default server ports./p p -table +Special case is a default server named as b[uri:*]/b that is used when the virtual +host cannot be found inside the configuration. All the uri directives not containing +host name belongs to this default server making global mappings.br / +The order how the host names are resolved is : +ul +liExact host name and optional non default port number/li +liAlias matching host name and port number/li +li*:port if the port is other then default/li +liDefault server/li +/ul +/p +p +table tr thProperty name/th thDefault/th @@ -151,11 +168,9 @@ tdthe context that will be served by this uri component (webapp style)/td /tr tr -tdreverse/td -td0/td -tdIf set to 1 all satisfied matches will be rejected. -This is usefull for the situations when you wish to map the entire application, but still wish that -paticular context is not served through Tomcat./td +tdalias/td +td/ +tdserver name alias/td /tr /table /p @@ -272,6 +287,10 @@ /p subsection name=worker.jni pworker used in inprocess, holds the details of the Tomcat class to startup, and paramters to pass/p +pThere are two predefined jni workers bonStartup/b and bonShutdown/b. Those two workers are executed +during sturtup and shutdown phase of the connector. Both must exsist in the configuration to be able to start +and shutdown Tomcat. +/p p table tr -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
mturk 2002/09/25 23:22:06
Modified:jk/xdocs/jk2 configweb.xml
Log:
Just some additional installation info from Eugene Gluzberg.
Revision ChangesPath
1.8 +13 -4 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml
Index: configweb.xml
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- configweb.xml 25 Sep 2002 16:47:14 - 1.7
+++ configweb.xml 26 Sep 2002 06:22:06 - 1.8
@@ -95,9 +95,18 @@
p
table
tr
-thProperty name/th
-thDefault/th
-thDescription/th
+ thProperty name/th
+ thDefault/th
+ thDescription/th
+ /tr
+tdfile/td
+td${serverRoot}/conf/workers2.properties/td
+tdLocation of the workers2.properties file/td
+/tr
+tr
+tddebug/td
+td0/td
+tdSet the debug level of the config component/td
/tr
tr
tddebugEnv/td
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
jfclere 2002/09/12 05:59:33 Modified:jk/xdocs/jk2 configweb.xml Log: Add a line to list the possible worker types. Revision ChangesPath 1.3 +3 -0 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml Index: configweb.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- configweb.xml 12 Sep 2002 12:39:12 - 1.2 +++ configweb.xml 12 Sep 2002 12:59:33 - 1.3 @@ -259,6 +259,9 @@ /subsection /subsection subsection name=workers +p + For the moment 4 worker types are supported: jni,ajp13,status,lb. +/p subsection name=jni pworker used in inprocess, holds the details of the Tomcat class to startup, and paramters to pass/p p -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
What about creating style(s) for the nested subsections? This document is not very readable for the moment and I am looking for ideas to improve it. [EMAIL PROTECTED] wrote: jfclere 2002/09/12 05:59:33 Modified:jk/xdocs/jk2 configweb.xml Log: Add a line to list the possible worker types. Revision ChangesPath 1.3 +3 -0 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml Index: configweb.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- configweb.xml 12 Sep 2002 12:39:12 - 1.2 +++ configweb.xml 12 Sep 2002 12:59:33 - 1.3 @@ -259,6 +259,9 @@ /subsection /subsection subsection name=workers +p + For the moment 4 worker types are supported: jni,ajp13,status,lb. +/p subsection name=jni pworker used in inprocess, holds the details of the Tomcat class to startup, and paramters to pass/p p -- 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]
Re: cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
jean-frederic clere wrote: What about creating style(s) for the nested subsections? This document is not very readable for the moment and I am looking for ideas to improve it. It seems fine to me. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk2 configweb.xml
mturk 2002/09/12 09:15:25 Modified:jk/xdocs/jk2 configweb.xml Log: added a 'reverse' uri decription. Please do a syntax and grammar check. Revision ChangesPath 1.4 +7 -0 jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml Index: configweb.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configweb.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- configweb.xml 12 Sep 2002 12:59:33 - 1.3 +++ configweb.xml 12 Sep 2002 16:15:25 - 1.4 @@ -149,6 +149,13 @@ td/ tdthe context that will be served by this uri component (webapp style)/td /tr +tr +tdreverse/td +td0/td +tdIf set to 1 all satisfied matches will be rejected. +This is usefull for the situations when you wish to map the entire application, but still wish that +paticular context is not served through Tomcat./td +/tr /table /p /subsection -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
