vmassol     01/09/25 02:12:15

  Modified:    conf/sample/build/servlet22 build-tests-enhydra-31.xml
               conf/sample/conf/test/servlet22/enhydra31 multiserver.conf
  Log:
  some tweakings but does not work better, I still get the exception upon start ...
  
  Revision  Changes    Path
  1.4       +2 -2      
jakarta-cactus/conf/sample/build/servlet22/build-tests-enhydra-31.xml
  
  Index: build-tests-enhydra-31.xml
  ===================================================================
  RCS file: 
/home/cvs/jakarta-cactus/conf/sample/build/servlet22/build-tests-enhydra-31.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- build-tests-enhydra-31.xml        2001/09/15 12:40:41     1.3
  +++ build-tests-enhydra-31.xml        2001/09/25 09:12:15     1.4
  @@ -107,7 +107,7 @@
           <!-- Create work and conf directories and copy configuration files -->
           <mkdir dir="${out.enhydra31.dir}/conf"/>
           <mkdir dir="${out.enhydra31.dir}/work"/>
  -        <mkdir dir="${out.enhydra31.dir}/webapps"/>
  +        <mkdir dir="${out.enhydra31.dir}/webapps/test"/>
   
           <!-- Copy the configuration file -->
           <copy file="${conf.enhydra31.dir}/multiserver.conf"
  @@ -116,6 +116,6 @@
           <!-- This is needed here because Enhydra 3.1 does not support
                automatic war deployment  -->
           <unwar src="${out.test.dir}/test.war"
  -            dest="${out.enhydra31.dir}/webapps/"/>
  +            dest="${out.enhydra31.dir}/webapps/test"/>
   
       </target>
  
  
  
  1.4       +15 -367   
jakarta-cactus/conf/sample/conf/test/servlet22/enhydra31/multiserver.conf
  
  Index: multiserver.conf
  ===================================================================
  RCS file: 
/home/cvs/jakarta-cactus/conf/sample/conf/test/servlet22/enhydra31/multiserver.conf,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- multiserver.conf  2001/08/02 15:02:32     1.3
  +++ multiserver.conf  2001/09/25 09:12:15     1.4
  @@ -1,373 +1,21 @@
  -# Enhydra Multiserver Config File
  -# ==================================
  -# This file contains the configuration options for the
  -# Enhydra Multiserver. Typically it is manipulated
  -# through the Multiserver Admin application, however,
  -# power users may wish to edit it by hand.
  -#
  -# Notes:
  -#  * The Multiserver only reads this file on startup.
  -#    It is thus necessary to stop and restart the server if
  -#    changes are made by hand.
  -#  * The order of the parameters in this file is not significant.
  -#  * Quotes are not required to delimit strings but are advised.
  -#  * Array parameters are specified as a comma separated list.
  -#    The parameter name is identified as an array with a "[]"
  -#    suffix.
  -#
   
  -
  -
  -# Server Section -----------------------------------------------------
  -# ==============
  -# These options configure server-wide attributes.
  -#
  -# Server.ConfDir
  -# --------------
  -# This is where the application's config files are stored.
  -# Each Enhydra application has a configuration
  -# file that must be placed in this directory in order for the
  -# application to be visible by the Multiserver and the Multiserver
  -# admin application.
  -#
  -# Server.LogFile
  -# --------------
  -# This is the file where the server log is written.
  -#
  -# Server.LogToFile[]
  -# ------------------
  -# This is a comma separated list of message types to send to the log
  -# file specified in server.logFile.
  -#
  -# Server.LogToStderr[]
  -# --------------------
  -# This is a comma separated list of message types to send to standard error.
  -#
  -# Possible logger levels:
  -# -----------------------
  -# These levels will be familiar to anyone that has used the UNIX
  -# syslog functionality:
  -#
  -#   EMERGENCY
  -#    Panic condition.
  -#   ALERT
  -#    A condition that should be corrected immediately, such as
  -#    database corruption.
  -#   CRITICAL
  -#    Critical conditions such as had device errors.
  -#   ERROR
  -#    General errors that are not usually fatal, but must be
  -#    resolved.
  -#   WARNING
  -#    Warning condition that may need attention, although the
  -#    need is not immediate.
  -#   NOTICE
  -#    Conditions that are not error conditions, but may require
  -#    special handling such as infrequent conditions.
  -#   INFO
  -#    General informational conditions, knowledge of which will
  -#    help to keep the server in good order.
  -#   DEBUG
  -#    Messages that contain information normally of use only when
  -#    debugging an application.
  -#   CLASSLOAD
  -#       Information about the loading of application classes.  Very
  -#       useful debugging class path problems.
  -#   REQUEST
  -#       The StandardLoggingFilter logs hits to this facility if
  -#       this is specified (normally it writes to it's own file).
  -#   XMLC
  -#       Information about auto-compiling XMLC pages.
  -#   XMLC_DEBUG
  -#       Debug information about auto-compiling XMLC pages.
  -#
  -#
   Server.ConfDir = "@out.enhydra31.dir@/conf"
   Server.LogFile = "@out.enhydra31.dir@/logs/multiserver.log"
   Server.LogToFile[] = EMERGENCY, ALERT, CRITICAL, ERROR, WARNING, INFO
   Server.LogToStderr[] = EMERGENCY, ALERT, CRITICAL, ERROR, WARNING, INFO
  -#
  -# The above setting is for verbose output. When running as a daemon
  -# process you may want to print out only emergencies, for example:
  -#     Server.LogToStderr[] = EMERGENCY
  -#
  -
  -
  -# Enhydra Application Section -----------------------------------------
  -# ==========================
  -# Each Enhydra application is added to the Multiserver with the
  -# following syntax. Note that multiple applications can be
  -# defined, the only restriction is that the <APPLICATION_ID> must
  -# be unique.
  -#
  -# Application.<APPLICATION_ID>.ConfFile
  -# -------------------------------------
  -# This is set to "filename.conf", which must exist in the directory
  -# defined by "Server.ConfDir".
  -#
  -# Application.<APPLICATION_ID>.Description
  -# ----------------------------------------
  -# A description of the application. This is visible in the
  -# management console.
  -#
  -# Application.<APPLICATION_ID>.Running = yes | no
  -# -----------------------------------------------
  -# This is basically the same as the start/stop buttons in the admin
  -# app. If the server has running = no, then it will not be instantiated,
  -# until the user of the admin app clicks on the "start" button.
  -#
  -
  -# Servlet Section ----------------------------------------------------
  -# ===============
  -# The Multiserver is able to run standard servlets in addition to
  -# Enhydra applications. The following syntax is
  -# used to define a servlet. Note that multiple servlets
  -# can be defined, the only restriction is that the <SERVLET_ID>
  -# must be unique.
  -#
  -# Each servlet is defined with:
  -#
  -# Servlet.<SERVLET_ID>.ClassName = entryClass
  -# Servlet.<SERVLET_ID>.DocRoot = Document root for servlet.
  -# Servlet.<SERVLET_ID>.Description = "A description of servlet"
  -# Servlet.<SERVLET_ID>.Running = yes | no
  -#
  -# where the ".classname" parameter defines the class with the
  -# service() method and ".description" defines a description used
  -# by the admin tool. The ".docRoot" is the full path to the
  -# directory used as the document root for this servlet and
  -# ".running" indicated whether to automatically start the
  -# servlet when the Multiserver is started.
  -#
  -# Optionally a servlet can be further specified with the following
  -# options:
  -#
  -# Servlet.<SERVLET_ID>.InitArgs
  -# -----------------------------
  -# This is a collection of name-value pairs that are passed to the
  -# servlet and initial arguments. Refer to the servlet documentation
  -# for more information.
  -# For example:
  -#    Servlet.<SERVLET_ID>.InitArgs.LogFile = /tmp/log
  -#    Servlet.<SERVLET_ID>.InitArgs.Max = 256
  -#    Servlet.<SERVLET_ID>.InitArgs.Names[] = "Joe Bob", "Jane Bee"
  -#
  -# Servlet.<SERVLET_ID>.ClassPath[]
  -# --------------------------------
  -# This is set to a comma-separated list of classpath elements. The
  -# class loader will be extended with these paths so that the
  -# servlet can successfully load any required classes.
  -#
  -# Application.<APPLICATION_ID>.Running
  -# ------------------------------------
  -# This is basically the same as the start/stop buttons in the admin
  -# app. If the server has running = no, then it will not be instantiated,
  -# until the user of the admin app clicks on the "start" button.
  -#
  -
  -#
  -# Example:
  -#    This shows all the data about the request available via the
  -#    servlet api. It is useful for debugging and testing.
  -#
  -#Servlet.SnoopServlet.ClassName = org.enhydra.servlet.tests.SnoopServlet
  -#Servlet.SnoopServlet.DocRoot = /tmp
  -#Servlet.SnoopServlet.Description = "The snoop servlet."
  -#Servlet.SnoopServlet.ClassPath[] = "out/test/enhydra31/lib/snoop.jar"
  -#Servlet.SnoopServlet.Running = no
  -#
  -# Example:
  -#   This servlet execs cgi-bin programs, e.g. Perl scripts.
  -#   Be sure to edit DocRoot to point to the directory containing your
  -#   scripts and/or programs.
  -# Note that an alternative mechanism for executing cgi scripts based on
  -# file extension rather than directory exists in the FileServerServlet.
  -#
  -#Servlet.CGIRunner.ClassName = org.enhydra.servlet.servlets.CGIServlet
  -#Servlet.CGIRunner.DocRoot = /usr/local/htdocs/cgi-bin
  -#Servlet.CGIRunner.Description = "Execs cgi-bin programs."
  -#Servlet.CGIRunner.Running = yes
  -#
  -# To use these examples, uncomment them and re-run the Multiserver.
  -# Then go to the admin application, select them, and add connections to
  -# whatever port and url-prefix (e.g. / or /name/) you wish.
  -# When the server is running the way you like it, remember to save your
  -# changes by clicking on the "Save State" button.
  -#
  -
  -
  -
  -# WebApp Section ----------------------------------------------------
  -# ===============
  -# The Multiserver is able to run Servlet 2.2 Web Applications.
  -# The following syntax is used to define a webapp.
  -#
  -# Each webapp is defined with:
  -#
  -# Application.<APP_ID>.DocRoot = Document root for webapp.
  -# Application.<APP_ID>.Description = "A description of webapp"
  -# Application.<APP_ID>.Running = yes | no
  -#
  -# where the ".classname" parameter defines the class with the
  -# service() method and ".description" defines a description used
  -# by the admin tool. The ".docRoot" is the full path to the
  -# directory used as the document root for this servlet and
  -# ".running" indicated whether to automatically start the
  -# servlet when the Multiserver is started.
  -#
  -# Optional parameters include the following:
  -#
  -# Application.<APP_ID>.defaultSessionTimeOut = 30
  -# Application.<APP_ID>.isInvokerEnabled = true
  -# Application.<APP_ID>.isWARExpanded = false
  -# Application.<APP_ID>.isWARValidated = false
  -# Application.<APP_ID>.isWorkDirPersistent = false
  -#
  -
  -
  -
  -# Connection Methods Section -----------------------------------------
  -# ==========================
  -# This section defines all the possible ways that the Multiserver will
  -# accept requests. Any number of connection methods are allowable
  -# so long as the <CONNECTION_ID> is unique. The <CONNECTION_ID>
  -# is used when associated with an application/servlet by defining
  -# a channel.
  -#
  -# Connection.<CONNECTION_ID>.Type
  -# -------------------------------
  -# The connection type is set to any supported connection method.
  -# Possible types are:
  -#
  -# "http"
  -# This instructs the Multiserver to directly listen for http requests on the
  -# specified port. The port is specified with:
  -#    Connection.<CONNECTION_ID>.Port = <port>
  -# The number of handler threads my be specified with:
  -#       Connection.<CONNECTION_ID>.NumThreads = <num>   (optional)
  -# The number of socket requests to queue (after accept, before processing)
  -# may be specified with:
  -#       Connection.<CONNECTION_ID>.QueueSize = <num>    (optional)
  -# The idle timeout period for a client connection, in seconds.  This is the
  -# amount of time to block without activity.
  -#       Connection.<CONNECTION_ID>.ClientTimeout = <num>   (optional)
  -# The idle timeout period for a handler thread, in seconds.  Shorter timeouts
  -# minimize the number of threads (memory) while slowing response time for
  -# bursts of activity.
  -#       Connection.<CONNECTION_ID>.ThreadTimeout = <num>   (optional)
  -#
  -# "https"
  -# This instructs the Multiserver to directly listen for secure-http requests
  -# on the specified port. The port is specified with:
  -#    Connection.<CONNECTION_ID>.Port = <port>
  -# The number of handler threads my be specified with:
  -#       Connection.<CONNECTION_ID>.NumThreads = <num>   (optional)
  -# The number of socket requests to queue (after accept, before processing)
  -# may be specified with:
  -#       Connection.<CONNECTION_ID>.QueueSize = <num>    (optional)
  -#
  -
  -
  -# Channel Section ----------------------------------------------------
  -# ===============
  -# This section defines how applications/servlets are connected with
  -# connection methods. Each channel entry represents an entry point
  -# to an application than can be individually controlled. Note that
  -# like other IDs, each <CHANNEL_ID> must by unique.
  -#
  -# Each channel is defined with:
  -#
  -# Channel.<CONNECTION_ID>.<CHANNEL_ID>.Servlet = <APPLICATION_ID>
  -#    or
  -# Channel.<CONNECTION_ID>.<CHANNEL_ID>.Servlet = <SERVLET_ID>
  -#
  -#    and
  -# Channel.<CONNECTION_ID>.<CHANNEL_ID>.Url = <url prefix>
  -#    and
  -# Channel.<CONNECTION_ID>.<CHANNEL_ID>.Filters = <FILTER_ID>,<FILTER_ID>
  -#    and
  -# Channel.<CONNECTION_ID>.<CHANNEL_ID>.Enabled = yes | no
  -#
  -#
  -# where the ".Servlet" parameter defines the application/servlet
  -# to connect to and the <CONNECTION_ID>.<CHANNEL_ID> path defines
  -# the connection method to connect to.
  -# The Url should generally begin and end with a '/'.
  -# The ".Filters" is optional and defines a
  -# list of <FILTER_ID> that a channel is subject to. Filters are
  -# executed in the order that they are defined. The most common use
  -# of a filter is for logging purposes. In general, filters are an
  -# advanced topic that is discussed in the developers guide.
  -
  -
  -
  -# Filter Section -----------------------------------------------------
  -# ==============
  -# This section is allows filters to be defined and subsequently used
  -# on a channel declaration. Note that each <FILTER_ID> must be unique.
  -#
  -# WARNING: It is the responsability of the administrator to ensure that
  -# the CLASPATH is set up prior to running the Multiserver such that the filter
  -# (and any classes it needs) will be found. The location of the filter
  -# class on disk is not specified.
  -#
  -# Each filter is defined with:
  -#
  -# Filter.<FILTER_ID>.ClassName = entryClass
  -# Filter.<FILTER_ID>.Description = "A description of filter"
  -#
  -# where the ".classname" parameter defines the class with the
  -# service() method and ".description" defines a description used
  -# by the admin tool.
  -#
  -# Optionally a filter can be further specified with the following option:
  -#
  -# Filter.<FILTER_ID>.InitArgs
  -# -----------------------
  -# This is a collection of name-value pairs that are passed to the
  -# servlet and initial arguments. Refer to the developers guide
  -# for more information.
  -# For example:
  -#    Filter.<FILTER_ID>.InitArgs.configFile = /tmp/filter_config
  -#    Filter.<FILTER_ID>.InitArgs.myParam = myValue
  -#
  -
  -
  -#
  -# This filter is used to log the requests as they are made to the server
  -# (aka "hits"). If the key REQUEST is present in Server.LogToFile or
  -# Server.LogToStderr (above), then a simple summary of the request and
  -# response will be sent to the standard logging facility. This kind of
  -# logging is usefull for quick debugging of an application. If the key
  -# REQUEST is not present, then data is not sent to the standard logging
  -# facility.
  -# If the initial argument "logFile" (optional, below) is set, then this filter
  -# will append data about the requests to the specified file, in a standard
  -# format that tools like Web Analyzer can read. If no logFile is specified,
  -# then data is not written to the file.
  -# This filter is applied to individual channels, so only the channels
  -# that need logging pay the overhead.
  -#
  -Filter.StandardLogger.ClassName = org.enhydra.servlet.filter.StandardLoggingFilter
  -Filter.StandardLogger.Description = "Standard Enhydra Logging."
  -Filter.StandardLogger.InitArgs.logFile = "@out.enhydra31.dir@/logs/access.log"
  -
  -Channel.CM_0.channel_0.Enabled = yes
  -Channel.CM_0.channel_0.Servlet = CactusSample
  -Channel.CM_0.channel_0.Url = "/test"
  -
  -Application.CactusSample.Running = yes
  -Application.CactusSample.isInvokerEnabled = true
  -Application.CactusSample.isWARValidated = true
  -Application.CactusSample.DocRoot = "@full.out.enhydra31.dir@/webapps"
  -Application.CactusSample.isWARExpanded = true
  -Application.CactusSample.Description =
  -Application.CactusSample.isWorkDirPersistent = false
  -Application.CactusSample.defaultSessionTimeOut = -1
   
  -Connection.CM_0.ThreadTimeout = 300
  -Connection.CM_0.ClientTimeout = 30
  -Connection.CM_0.NumThreads = 200
  -Connection.CM_0.Type = http
  -Connection.CM_0.QueueSize = 400
  -Connection.CM_0.Port = @test.port@
  +Application.CactusTest.Description = "Cactus Test Web Application"
  +Application.CactusTest.DocRoot = "@full.out.enhydra31.dir@/webapps/test"
  +Application.CactusTest.Running = yes
  +Application.CactusTest.defaultSessionTimeOut = 30
  +Application.CactusTest.isInvokerEnabled = true
  +Application.CactusTest.isWARExpanded = false
  +Application.CactusTest.isWARValidated = false
  +Application.CactusTest.isWorkDirPersistent = false
  +
  +Connection.HttpConn.Type = http
  +Connection.HttpConn.Port = @test.port@
  +
  +Channel.HttpConn.CactusTestChannel.Enabled = yes
  +Channel.HttpConn.CactusTestChannel.Servlet = CactusTest
  +Channel.HttpConn.CactusTestChannel.Url = "/test"
  
  
  

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

Reply via email to