You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Tassilo Pilati <tp...@informationsdesign.de> on 2001/04/18 14:47:11 UTC

worker.properties

Hello,

i did not edit my worker.properties file at all. I`m using Tomcat 3.2.1. It
is working with Apache and in standalone mode (besides that session
tracking, using URL rewritting is not working, which is another issue).
Anyway, I was wondering if I have to edit this file. For example I see in
the file that the workers.tomcat_home and the workers.java_home is not set
correclty, as it is configured for the windows plattform. Nevertheless,
tomcat is starting up and working, so I was just wondering if that is normal
? Here is my workers file...

# ... skipped header comments ...
#
# workers.tomcat_home should point to the location where you
# installed tomcat. This is where you have your conf, webapps and lib
# directories.
#
workers.tomcat_home=c:\jakarta-tomcat

#
# workers.java_home should point to your Java installation. Normally
# you should have a bin and lib directories beneath it.
#
workers.java_home=c:\jdk1.2.2

#
# You should configure your environment slash... ps=\ on NT and / on UNIX
# and maybe something different elsewhere.
#
ps=\
# ps=/

#
#------ ADVANCED MODE ------------------------------------------------
#---------------------------------------------------------------------
#

#
#------ DEFAULT worket list ------------------------------------------
#---------------------------------------------------------------------
#
#
# The workers that your plugins should create and work with
#
worker.list=ajp12, ajp13

#
#------ DEFAULT ajp12 WORKER DEFINITION ------------------------------
#---------------------------------------------------------------------
#

#
# Defining a worker named ajp12 and of type ajp12
# Note that the name and the type do not have to match.
#
worker.ajp12.port=8007
worker.ajp12.host=localhost
worker.ajp12.type=ajp12
#
# Specifies the load balance factor when used with
# a load balancing worker.
# Note:
#  ----> lbfactor must be > 0
#  ----> Low lbfactor means less work done by the worker.
worker.ajp12.lbfactor=1

#
#------ DEFAULT ajp13 WORKER DEFINITION ------------------------------
#---------------------------------------------------------------------
#

#
# Defining a worker named ajp13 and of type ajp13
# Note that the name and the type do not have to match.
#
worker.ajp13.port=8009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13
#
# Specifies the load balance factor when used with
# a load balancing worker.
# Note:
#  ----> lbfactor must be > 0
#  ----> Low lbfactor means less work done by the worker.
worker.ajp13.lbfactor=1

#
# Specify the size of the open connection cache.
#worker.ajp13.cachesize

#
#------ DEFAULT LOAD BALANCER WORKER DEFINITION ----------------------
#---------------------------------------------------------------------
#

#
# The loadbalancer (type lb) workers perform wighted round-robin
# load balancing with sticky sessions.
# Note:
#  ----> If a worker dies, the load balancer will check its state
#        once in a while. Until then all work is redirected to peer
#        workers.
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers=ajp12, ajp13


#
#------ DEFAULT JNI WORKER DEFINITION---------------------------------
#---------------------------------------------------------------------
#

#
# Defining a worker named inprocess and of type jni
# Note that the name and the type do not have to match.
#
worker.inprocess.type=jni

#
#------ CLASSPATH DEFINITION -----------------------------------------
#---------------------------------------------------------------------
#

#
# Additional class path components.
#
worker.inprocess.class_path=$(workers.tomcat_home)$(ps)classes

#
# The XML parser provided with Tomcat
#
worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)jaxp.jar
worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)parser.jar

#
# Tomcat's implementation
#
worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)jasper.jar
worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)servlet.jar
worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)webserver.jar

#
# Javac as available from Java2SE
#
worker.inprocess.class_path=$(workers.java_home)$(ps)lib$(ps)tools.jar

#
# Setting the command line for tomcat
# Note: The cmd_line string may not contain spaces.
#
worker.inprocess.cmd_line=-config
worker.inprocess.cmd_line=$(workers.tomcat_home)/conf/jni_server.xml
worker.inprocess.cmd_line=-home
worker.inprocess.cmd_line=$(workers.tomcat_home)

#
# The JVM that we are about to use
#
# This is for Java2
#
worker.inprocess.jvm_lib=$(workers.java_home)$(ps)jre$(ps)bin$(ps)classic$(p
s)jvm.dll

#
# And this is for jdk1.1.X
#
#worker.inprocess.jvm_lib=$(workers.java_home)$(ps)bin$(ps)javai.dll
#

#
# Setting the place for the stdout and stderr of tomcat
#
worker.inprocess.stdout=$(workers.tomcat_home)$(ps)inprocess.stdout
worker.inprocess.stderr=$(workers.tomcat_home)$(ps)inprocess.stderr

#
# Setting the tomcat.home Java property
#
worker.inprocess.sysprops=tomcat.home=$(workers.tomcat_home)

#
# Java system properties
#
# worker.inprocess.sysprops=java.compiler=NONE
# worker.inprocess.sysprops=myprop=mypropvalue

#
# Additional path components.
#
# worker.inprocess.ld_path=d:$(ps)SQLLIB$(ps)bin
#


AW: worker.properties

Posted by Tassilo Pilati <tp...@weboperations.com>.
Well, this file is in the conf directory of my tomcat installation. But I
don`t get an error message ....

-----Ursprüngliche Nachricht-----
Von: Sam Newman [mailto:sam.newman@stamplets.com]
Gesendet: Mittwoch, 18. April 2001 15:36
An: tomcat-user@jakarta.apache.org
Betreff: Re: worker.properties


The workers.properties file configures the worker threads that take requests
for servlets/jsp's from apache and processes them appropirately. As such,
when running Tomcat without Apache it will have no effect. You only need to
edit this file when you run Apache and Tomcat together. Infact you'll get a
syntax error on a non-PC platform if you forget to edit this file and try
and include it in the Apache directives. See the workers.properties howto
for more information (its in the Tomcat docs somewhere).

sam
----- Original Message -----
From: "Tassilo Pilati" <tp...@informationsdesign.de>
To: <to...@jakarta.apache.org>
Sent: Wednesday, April 18, 2001 1:47 PM
Subject: worker.properties


> Hello,
>
> i did not edit my worker.properties file at all. I`m using Tomcat 3.2.1.
It
> is working with Apache and in standalone mode (besides that session
> tracking, using URL rewritting is not working, which is another issue).
> Anyway, I was wondering if I have to edit this file. For example I see in
> the file that the workers.tomcat_home and the workers.java_home is not set
> correclty, as it is configured for the windows plattform. Nevertheless,
> tomcat is starting up and working, so I was just wondering if that is
normal



Re: worker.properties

Posted by Sam Newman <sa...@stamplets.com>.
The workers.properties file configures the worker threads that take requests
for servlets/jsp's from apache and processes them appropirately. As such,
when running Tomcat without Apache it will have no effect. You only need to
edit this file when you run Apache and Tomcat together. Infact you'll get a
syntax error on a non-PC platform if you forget to edit this file and try
and include it in the Apache directives. See the workers.properties howto
for more information (its in the Tomcat docs somewhere).

sam
----- Original Message -----
From: "Tassilo Pilati" <tp...@informationsdesign.de>
To: <to...@jakarta.apache.org>
Sent: Wednesday, April 18, 2001 1:47 PM
Subject: worker.properties


> Hello,
>
> i did not edit my worker.properties file at all. I`m using Tomcat 3.2.1.
It
> is working with Apache and in standalone mode (besides that session
> tracking, using URL rewritting is not working, which is another issue).
> Anyway, I was wondering if I have to edit this file. For example I see in
> the file that the workers.tomcat_home and the workers.java_home is not set
> correclty, as it is configured for the windows plattform. Nevertheless,
> tomcat is starting up and working, so I was just wondering if that is
normal