From c0b7206652b2852bc574694e7ba07ba1c2acdc00 Mon Sep 17 00:00:00 2001 From: hongbotian Date: Mon, 30 Nov 2015 03:10:21 -0500 Subject: delete app Change-Id: Id4c572809969ebe89e946e88063eaed262cff3f2 Signed-off-by: hongbotian --- .../conf/workers.properties | 165 --------------------- 1 file changed, 165 deletions(-) delete mode 100644 rubbos/app/tomcat-connectors-1.2.32-src/conf/workers.properties (limited to 'rubbos/app/tomcat-connectors-1.2.32-src/conf/workers.properties') diff --git a/rubbos/app/tomcat-connectors-1.2.32-src/conf/workers.properties b/rubbos/app/tomcat-connectors-1.2.32-src/conf/workers.properties deleted file mode 100644 index cd374285..00000000 --- a/rubbos/app/tomcat-connectors-1.2.32-src/conf/workers.properties +++ /dev/null @@ -1,165 +0,0 @@ -# Licensed to the Apache Software Foundation (ASF) under one or more -# contributor license agreements. See the NOTICE file distributed with -# this work for additional information regarding copyright ownership. -# The ASF licenses this file to You under the Apache License, Version 2.0 -# (the "License"); you may not use this file except in compliance with -# the License. You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -# See the License for the specific language governing permissions and -# limitations under the License. - -# Note that the distributed version of this file requires modification -# before it is usable. -# -# Reference documentation: http://tomcat.apache.org/connectors-doc/reference/workers.html -# -# As a general note, the characters $( and ) are used internally to define -# macros. Do not use them in your own configuration!!! -# -# Whenever you see a set of lines such as: -# x=value -# y=$(x)\something -# -# the final value for y will be value\something - -# Define two status worker: -# - jk-status for read-only use -# - jk-manager for read/write use -worker.list=jk-status -worker.jk-status.type=status -worker.jk-status.read_only=true - -worker.list=jk-manager -worker.jk-manager.type=status - -# We define a load balancer worker -# with name "balancer" -worker.list=balancer -worker.balancer.type=lb -# error_escalation_time: seconds, default = recover_time/2 (=30) -# Determines, how fast a detected error should switch from -# local error state to global error state -# Since: 1.2.28 -worker.balancer.error_escalation_time=0 - -# - max_reply_timeouts: number, default=0 -# If there are to many reply timeouts, a worker -# is put into the error state, i.e. it will become -# unavailable for all sessions residing on the respective -# Tomcat. The number of tolerated reply timeouts is -# configured with max_reply_timeouts. The number of -# timeouts occuring is divided by 2 once a minute and the -# resulting counter is compared against max_reply_timeouts. -# If you set max_reply_timeouts to N and the errors are -# occuring equally distributed over time, you will -# tolerate N/2 errors per minute. If they occur in a burst -# you will tolerate N errors. -# Since: 1.2.24 -worker.balancer.max_reply_timeouts=10 - - - -# Now we add members to the load balancer -# First member is "node1", most -# attributes are inherited from the -# template "worker.template". -worker.balancer.balance_workers=node1 -worker.node1.reference=worker.template -worker.node1.host=localhost -worker.node1.port=8109 -# Activation allows to configure -# whether this node should actually be used -# A: active (use node fully) -# D: disabled (only use, if sticky session needs this node) -# S: stopped (do not use) -# Since: 1.2.19 -worker.node1.activation=A - -# Second member is "node2", most -# attributes are inherited from the -# template "worker.template". -worker.balancer.balance_workers=node2 -worker.node2.reference=worker.template -worker.node2.host=localhost -worker.node2.port=8209 -# Activation allows to configure -# whether this node should actually be used -# A: active (use node fully) -# D: disabled (only use, if sticky session needs this node) -# S: stopped (do not use) -# Since: 1.2.19 -worker.node2.activation=A - -# Finally we put the parameters -# which should apply to all our ajp13 -# workers into the referenced template -# - Type is ajp13 -worker.template.type=ajp13 - -# - socket_connect_timeout: milliseconds, default=0 -# Since: 1.2.27 -worker.template.socket_connect_timeout=5000 - -# - socket_keepalive: boolean, default=false -# Should we send TCP keepalive packets -# when connection is idle (socket option)? -worker.template.socket_keepalive=true - -# - ping_mode: Character, default=none -# When should we use cping/cpong connection probing? -# C = directly after establishing a new connection -# P = directly before sending each request -# I = in regular intervals for idle connections -# using the watchdog thread -# A = all of the above -# Since: 1.2.27 -worker.template.ping_mode=A - -# - ping_timeout: milliseconds, default=10000 -# Wait timeout for cpong after cping -# Can be overwritten for modes C and P -# Using connect_timeout and prepost_timeout. -# Since: 1.2.27 -worker.template.ping_timeout=10000 - -# - connection_pool_minsize: number, default=connection_pool_size -# Lower pool size when shrinking pool due -# to idle connections -# We want all connections to be closed when -# idle for a long time in order to prevent -# firewall problems. -# Since: 1.2.16 -worker.template.connection_pool_minsize=0 - -# - connection_pool_timeout: seconds, default=0 -# Idle time, before a connection is eligible -# for being closed (pool shrinking). -# This should be the same value as connectionTimeout -# in the Tomcat AJP connector, but there it is -# milliseconds, here seconds. -worker.template.connection_pool_timeout=600 - -# - reply_timeout: milliseconds, default=0 -# Any pause longer than this timeout during waiting -# for a part of the reply will abort handling the request -# in mod_jk. The request will proceed running in -# Tomcat, but the web server resources will be freed -# and an error is send to the client. -# For individual requests, the timeout can be overwritten -# by the Apache environment variable JK_REPLY_TIMEOUT. -# JK_REPLY_TIMEOUT since: 1.2.27 -worker.template.reply_timeout=300000 - -# - recovery_options: number, default=0 -# Bit mask to configure, if a request, which was send -# to a backend successfully, should be retried on another backend -# in case there's a problem with the response. -# Value "3" disables retries, whenever a part of the request was -# successfully send to the backend. -worker.template.recovery_options=3 - -- cgit 1.2.3-korg