archive-es.com » ES » E » EPPA.ES

Total: 100

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Apache Tomcat 7 Configuration Reference (7.0.22) - The LifeCycle Listener Component
    loading of JDBNC Driver in the the current class loader The web application level memory leak protection can take care of this in most cases but triggering the loading here has fewer side effects The default is true gcDaemonProtection Enables protection so that calls to sun misc GC requestLatency long triggered by a web application do not result in a memory leak Use of RMI is likely to trigger a call to this method A side effect of enabling this protection is the creation of a thread named GC Daemon The protection uses reflection to access internal Sun classes and may generate errors on startup on non Sun JVMs The default is true java2DDisposerProtection Enables protection so that loading the sun java2d Disposer class by a web application does not result in a memory leak Defaults to false because a thread is launched ldapPoolProtection Enables protection so that the PoolCleaner thread started by com sun jndi ldap LdapPoolManager does not result in a memory leak The thread is started the first time the LdapPoolManager class is used if the system property com sun jndi ldap connect pool timeout is set to a value greater than 0 Without this protection if a web application uses this class the PoolCleaner thread will be configured with the thread s context class loader set to the web application class loader which in turn will trigger a memory leak on reload Defaults to true securityLoginConfigurationProtection Enables protection so that usage of the javax security auth login Configuration class by a web application does not provoke a memory leak The first access of this class will trigger the initializer that will retain a static reference to the context class loader The protection loads the class with the system class loader to ensure that the static initializer is not triggered by a web application Defaults to true securityPolicyProtection Enables protection so that usage of the deprecated javax security auth Policy class by a web application does not result in a memory leak The first access of this class will trigger the static initializer that will retain a static reference to the context class loader The protection calls the getPolicy method of this class to ensure that the static initializer is not triggered by a web application Defaults to true tokenPollerProtection Enables protection so that any token poller thread initialized by sun security pkcs11 SunPKCS11 initToken does not result in a memory leak The thread is started depending on various conditions as part of the initialization of the Java Cryptography Architecture Without the protection this can happen during Webapp deployment when the MessageDigest for generating session IDs is initialized As a result the thread has the Webapp class loader as its thread context class loader Enabling the protection initializes JCA early during Tomcat startup Defaults to true urlCacheProtection Enables protection so that reading resources from JAR files using java net URLConnection s does not result in the JAR file being locked Note that enabling this protection disables caching

    Original URL path: http://ticket.eppa.es/docs/config/listeners.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Loader Component
    in depth description of the class loader hierarchy that is implemented by Catalina see the ClassLoader HowTo The description below uses the variable name CATALINA BASE to refer the base directory against which most relative paths are resolved If you have not configured Tomcat for multiple instances by setting a CATALINA BASE directory then CATALINA BASE will be set to the value of CATALINA HOME the directory into which you have installed Tomcat Attributes Common Attributes All implementations of Loader support the following attributes Attribute Description className Java class name of the implementation to use This class must implement the org apache catalina Loader interface If not specified the standard value defined below will be used delegate Set to true if you want the class loader to follow the standard Java2 delegation model and attempt to load classes from parent class loaders before looking inside the web application Set to false the default to have the class loader look inside the web application first before asking parent class loaders to find requested classes or resources reloadable Set to true if you want Catalina to monitor classes in WEB INF classes and WEB INF lib for changes and automatically reload the web application if a change is detected This feature is very useful during application development but it requires significant runtime overhead and is not recommended for use on deployed production applications You can use the Manager web application however to trigger reloads of deployed applications on demand NOTE The value for this property will be inherited from the reloadable attribute you set on the surrounding Context component and any value you explicitly set here will be replaced Standard Implementation The standard implementation of Loader is org apache catalina loader WebappLoader It supports the following additional attributes in addition to the

    Original URL path: http://ticket.eppa.es/docs/config/loader.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Manager Component
    across a normal restart of Tomcat The actual persistent storage mechanism used is selected by your choice of a Store element nested inside the Manager element this is required for use of PersistentManager This implementation of Manager supports the following attributes in addition to the Common Attributes described earlier Attribute Description className It has the same meaning as described in the Common Attributes above You must specify org apache catalina session PersistentManager to use this manager implementation maxIdleBackup The time interval in seconds since the last access to a session before it is eligible for being persisted to the session store or 1 to disable this feature By default this feature is disabled maxIdleSwap The time interval in seconds since the last access to a session before it should be persisted to the session store and passivated out of the server s memory or 1 to disable this feature If this feature is enabled the time interval specified here should be equal to or longer than the value specified for maxIdleBackup By default this feature is disabled minIdleSwap The time interval in seconds since the last access to a session before it will be eligible to be persisted to the session store and passivated out of the server s memory or 1 for this swapping to be available at any time If specified this value should be less than that specified by maxIdleSwap By default this value is set to 1 processExpiresFrequency It is the same as described above for the org apache catalina session StandardManager class saveOnRestart Should all sessions be persisted and reloaded when Tomcat is shut down and restarted or when this application is reloaded By default this attribute is set to true secureRandomClass It is the same as described above for the org apache catalina session StandardManager class secureRandomProvider It is the same as described above for the org apache catalina session StandardManager class secureRandomAlgorithm It is the same as described above for the org apache catalina session StandardManager class In order to successfully use a PersistentManager you must nest inside it a Store element as described below Nested Components Standard Manager Implementation If you are using the Standard Manager Implementation as described above no elements may be nested inside your Manager element Persistent Manager Implementation If you are using the Persistent Manager Implementation as described above you MUST nest a Store element inside which defines the characteristics of the persistent data storage Two implementations of the Store element are currently available with different characteristics as described below File Based Store The File Based Store implementation saves swapped out sessions in individual files named based on the session identifier in a configurable directory Therefore you are likely to encounter scalability problems as the number of active sessions increases and this should primarily be considered a means to easily experiment To configure this add a Store nested inside your Manager element with the following attributes Attribute Description checkInterval The interval in seconds between checks for expired sessions

    Original URL path: http://ticket.eppa.es/docs/config/manager.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Realm Component
    can not be made to the provider at the connectionURL an attempt will be made to use the alternateURL authentication A string specifying the type of authentication to use none simple strong or a provider specific definition can be used If no value is given the providers default is used commonRole A role name assigned to each successfully authenticated user in addition to the roles retrieved from LDAP If not specified only the roles retrieved via LDAP are used connectionName The directory username to use when establishing a connection to the directory for LDAP search operations If not specified an anonymous connection is made which is often sufficient unless you specify the userPassword property connectionPassword The directory password to use when establishing a connection to the directory for LDAP search operations If not specified an anonymous connection is made which is often sufficient unless you specify the userPassword property connectionTimeout The timeout in milliseconds to use when establishing the connection to the LDAP directory If not specified a value of 5000 5 seconds is used connectionURL The connection URL to be passed to the JNDI driver when establishing a connection to the directory contextFactory Fully qualified Java class name of the factory class used to acquire our JNDI InitialContext By default assumes that the standard JNDI LDAP provider will be utilized derefAliases A string specifying how aliases are to be dereferenced during search operations The allowed values are always never finding and searching If not specified always is used digest The digest algorithm to apply to the plaintext password offered by the user before comparing it with the value retrieved from the directory Valid values are those accepted for the algorithm name by the java security MessageDigest class If not specified the plaintext password is assumed to be retrieved Not required unless userPassword is specified protocol A string specifying the security protocol to use If not given the providers default is used referrals How do we handle JNDI referrals Allowed values are ignore follow or throw see javax naming Context REFERRAL for more information Microsoft Active Directory often returns referrals If you need to follow them set referrals to follow Caution if your DNS is not part of AD the LDAP client lib might try to resolve your domain name in DNS to find another LDAP server roleBase The base directory entry for performing role searches If not specified the top level element in the directory context will be used If specified it may optionally include pattern replacements 0 n corrosponding to the name parts of the user s distinguished name as returned by javax naming Name get roleName The name of the attribute that contains role names in the directory entries found by a role search In addition you can use the userRoleName property to specify the name of an attribute in the user s entry containing additional role names If roleName is not specified a role search does not take place and roles are taken only from the user s entry roleSearch The LDAP filter expression used for performing role searches Use 0 to substitute the distinguished name DN of the user and or 1 to substitute the username If not specified a role search does not take place and roles are taken only from the attribute in the user s entry specified by the userRoleName property roleSearchAsUser When searching for user roles should the search be performed as the user currently being authenticated If false connectionName and connectionPassword will be used if specified else an anonymous If not specified the default value of false is used Note that when accessing the directory using delegated credentials this attribute is always ignored and the search is performed using the delegated credentials roleSubtree Set to true if you want to search the entire subtree of the element specified by the roleBase property for role entries associated with the user The default value of false causes only the top level to be searched sizeLimit Specifies the maximum number of records to return when using the userSearch attribute If not specified the default of 0 is used which indicates no limit stripRealmForGss When processing users authenticated via the GSS API this attribute controls if any is removed from the end of the user name If not specified the default is true timeLimit Specifies the time in milliseconds to wait for records to be returned when using the userSearch attribute If not specified the default of 0 is used which indicates no limit useDelegatedCredential When the JNIRealm is used with the SPNEGO authenticator delegated credentials for the user may be available If such credentials are present this attribute controls whether are not they are used to connect to the directory If not specified the default value of true is used userBase The base element for user searches performed using the userSearch expression Not used if you are using the userPattern expression userPassword Name of the attribute in the user s entry containing the user s password If you specify this value JNDIRealm will bind to the directory using the values specified by connectionName and connectionPassword properties and retrieve the corresponding attribute for comparison to the value specified by the user being authenticated If you do not specify this value JNDIRealm will attempt a simple bind to the directory using the DN of the user s entry and the password presented by the user with a successful bind being interpreted as an authenticated user userPattern Pattern for the distinguished name DN of the user s directory entry with 0 marking where the actual username should be inserted You can use this property instead of userSearch userSubtree and userBase when the distinguished name contains the username and is otherwise the same for all users Note that when accessing the directory using delegated credentials this attribute is always ignored and userSearch userSubtree and userBase are always used instead userRoleName The name of an attribute in the user s directory entry containing zero or more values for

    Original URL path: http://ticket.eppa.es/docs/config/realm.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Resources Component
    which classes will be loaded HTML JSP and the other static files will be served This allows the webapp to reside on various mediums other than the filesystem like compressed in a WAR file in a JDBC database or in a more advanced versioning repository A unified caching engine is provided for all accesses to the webapp resources made by the servlet container and web applications which use the container provided mechanisms to access such resources such as classloader access access through the ServletContext interface or native access through the DirectoryContext interface Note Running a webapp with non filesystem based Resources implementations is only possible when the webapp does not rely on direct filesystem access to its own resources and uses the methods in the ServletContext interface to access them A Resources element MAY be nested inside a Context component If it is not included a default filesystem based Resources will be created automatically which is sufficient for most requirements Attributes Common Attributes All implementations of Resources support the following attributes Attribute Description className Java class name of the implementation to use This class must implement the javax naming directory DirContext interface It is recommended for optimal functionality and performance

    Original URL path: http://ticket.eppa.es/docs/config/resources.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Valve Component
    logged if ServletRequest getAttribute junk null The use of Filters is an easy way to set unset the attribute in the ServletRequest on many different requests condition The same as conditionUnless This attribute is provided for backwards compatibility fileDateFormat Allows a customized date format in the access log file name The date format also decides how often the file is rotated If you wish to rotate every hour then set this value to yyyy MM dd HH The default value is yyyy MM dd The date format will always be localized using the locale en US buffered Flag to determine if logging will be buffered If set to false then access logging will be written after each request Default value true Values for the pattern attribute are made up of format tokens Some of the tokens need an additional prefix Possible prefixes are c for client s for server cs for client to server sc for server to client or x for application specific Furthermore some tokens are completed by an additional selector See the W3C specification for more information about the format The following format tokens are supported bytes Bytes sent excluding HTTP headers or if zero c dns Remote host name or IP address if enableLookups for the connector is false c ip Remote IP address cs method Request method GET POST etc cs uri Request URI cs uri query Query string prepended with a if it exists cs uri stem Requested URL path date The date in yyyy mm dd format for GMT s dns Local host name s ip Local IP address sc status HTTP status code of the response time Time the request was served in HH mm ss format for GMT time taken Time in seconds as floating point taken to serve the request x threadname Current request thread name can compare later with stacktraces For any of the x H XXX the following method will be called from the HttpServletRequest object x H authType getAuthType x H characterEncoding getCharacterEncoding x H contentLength getContentLength x H locale getLocale x H protocol getProtocol x H remoteUser getRemoteUser x H requestedSessionId getRequestedSessionId x H requestedSessionIdFromCookie isRequestedSessionIdFromCookie x H requestedSessionIdValid isRequestedSessionIdValid x H scheme getScheme x H secure isSecure There is also support to write information about headers cookies context request or session attributes and request parameters cs XXX for incoming request headers with name XXX sc XXX for outgoing response headers with name XXX x A XXX for the servlet context attribute with name XXX x C XXX for the first cookie with name XXX x O XXX for a concatenation of all outgoing response headers with name XXX x P XXX for the URL encoded request parameter with name XXX x R XXX for the request attribute with name XXX x S XXX for the session attribute with name XXX Remote Address Filter Introduction The Remote Address Filter allows you to compare the IP address of the client that submitted this request against one or more regular expressions and either allow the request to continue or refuse to process the request from this client A Remote Address Filter can be associated with any Catalina container Engine Host or Context and must accept any request presented to this container for processing before it will be passed on The syntax for regular expressions is different than that for standard wildcard matching Tomcat uses the java util regex package Please consult the Java documentation for details of the expressions supported Note There is a caveat when using this valve with IPv6 addresses Format of the IP address that this valve is processing depends on the API that was used to obtain it If the address was obtained from Java socket using Inet6Address class its format will be x x x x x x x x That is the IP address for localhost will be 0 0 0 0 0 0 0 1 instead of the more widely used 1 Consult your access logs for the actual value See also Remote Host Filter Remote IP Valve Attributes The Remote Address Filter supports the following configuration attributes Attribute Description className Java class name of the implementation to use This MUST be set to org apache catalina valves RemoteAddrValve allow A regular expression using java util regex that the remote client s IP address is compared to If this attribute is specified the remote address MUST match for this request to be accepted If this attribute is not specified all requests will be accepted UNLESS the remote address matches a deny pattern deny A regular expression using java util regex that the remote client s IP address is compared to If this attribute is specified the remote address MUST NOT match for this request to be accepted If this attribute is not specified request acceptance is governed solely by the accept attribute Example To allow access only for the clients connecting from localhost Valve className org apache catalina valves RemoteAddrValve allow 127 d d d 1 0 0 0 0 0 0 0 1 Remote Host Filter Introduction The Remote Host Filter allows you to compare the hostname of the client that submitted this request against one or more regular expressions and either allow the request to continue or refuse to process the request from this client A Remote Host Filter can be associated with any Catalina container Engine Host or Context and must accept any request presented to this container for processing before it will be passed on The syntax for regular expressions is different than that for standard wildcard matching Tomcat uses the java util regex package Please consult the Java documentation for details of the expressions supported See also Remote Address Filter Attributes The Remote Host Filter supports the following configuration attributes Attribute Description className Java class name of the implementation to use This MUST be set to org apache catalina valves RemoteHostValve allow A regular expression using java util regex that the remote client s hostname is compared to If this attribute is specified the remote hostname MUST match for this request to be accepted If this attribute is not specified all requests will be accepted UNLESS the remote hostname matches a deny pattern deny A regular expression using java util regex that the remote client s hostname is compared to If this attribute is specified the remote hostname MUST NOT match for this request to be accepted If this attribute is not specified request acceptance is governed solely by the accept attribute Single Sign On Valve Introduction The Single Sign On Vale is utilized when you wish to give users the ability to sign on to any one of the web applications associated with your virtual host and then have their identity recognized by all other web applications on the same virtual host See the Single Sign On special feature on the Host element for more information Attributes The Single Sign On Valve supports the following configuration attributes Attribute Description className Java class name of the implementation to use This MUST be set to org apache catalina authenticator SingleSignOn requireReauthentication Default false Flag to determine whether each request needs to be reauthenticated to the security Realm If true this Valve uses cached security credentials username and password to reauthenticate to the Realm each request associated with an SSO session If false the Valve can itself authenticate requests based on the presence of a valid SSO cookie without rechecking with the Realm cookieDomain Sets the host domain to be used for sso cookies Basic Authenticator Valve Introduction The Basic Authenticator Valve is automatically added to any Context that is configured to use BASIC authentication If any non default settings are required the valve may be configured within Context element with the required values Attributes The Basic Authenticator Valve supports the following configuration attributes Attribute Description alwaysUseSession Should a session always be used once a user is authenticated This may offer some performance benefits since the session can then be used to cache the authenticated Principal hence removing the need to authenticate the user via the Realm on every request This may be of help for combinations such as BASIC authentication used with the JNDIRealm or DataSourceRealms However there will also be the performance cost of creating and GC ing the session If not set the default value of false will be used cache Should we cache authenticated Principals if the request is part of an HTTP session If not specified the default value of true will be used changeSessionIdOnAuthentication Controls if the session ID is changed if a session exists at the point where users are authenticated This is to prevent session fixation attacks If not set the default value of true will be used className Java class name of the implementation to use This MUST be set to org apache catalina authenticator BasicAuthenticator disableProxyCaching Controls the caching of pages that are protected by security constraints Setting this to false may help work around caching issues in some browsers but will also cause secured pages to be cached by proxies which will almost certainly be a security issue securePagesWithPragma offers an alternative secure workaround for browser caching issues If not set the default value of true will be used securePagesWithPragma Controls the caching of pages that are protected by security constraints Setting this to false may help work around caching issues in some browsers by using Cache Control private rather than the default of Pragma No cache and Cache control No cache If not set the default value of false will be used secureRandomAlgorithm Name of the algorithm to use to create the java security SecureRandom instances that generate session IDs If an invalid algorithm and or provider is specified the platform default provider and the default algorithm will be used If not specified the default algorithm of SHA1PRNG will be used If the default algorithm is not supported the platform default will be used To specify that the platform default should be used do not set the secureRandomProvider attribute and set this attribute to the empty string secureRandomClass Name of the Java class that extends java security SecureRandom to use to generate SSO session IDs If not specified the default value is java security SecureRandom secureRandomProvider Name of the provider to use to create the java security SecureRandom instances that generate SSO session IDs If an invalid algorithm and or provider is specified the platform default provider and the default algorithm will be used If not specified the platform default provider will be used Digest Authenticator Valve Introduction The Digest Authenticator Valve is automatically added to any Context that is configured to use DIGEST authentication If any non default settings are required the valve may be configured within Context element with the required values Attributes The Digest Authenticator Valve supports the following configuration attributes Attribute Description alwaysUseSession Should a session always be used once a user is authenticated This may offer some performance benefits since the session can then be used to cache the authenticated Principal hence removing the need to authenticate the user via the Realm on every request This may be of help for combinations such as BASIC authentication used with the JNDIRealm or DataSourceRealms However there will also be the performance cost of creating and GC ing the session If not set the default value of false will be used cache Should we cache authenticated Principals if the request is part of an HTTP session If not specified the default value of true will be used changeSessionIdOnAuthentication Controls if the session ID is changed if a session exists at the point where users are authenticated This is to prevent session fixation attacks If not set the default value of true will be used className Java class name of the implementation to use This MUST be set to org apache catalina authenticator DigestAuthenticator cnonceCacheSize To protect against replay attacks the DIGEST authenticator tracks client nonce and nonce count values This attribute controls the size of that cache If not specified the default value of 1000 is used disableProxyCaching Controls the caching of pages that are protected by security constraints Setting this to false may help work around caching issues in some browsers but will also cause secured pages to be cached by proxies which will almost certainly be a security issue securePagesWithPragma offers an alternative secure workaround for browser caching issues If not set the default value of true will be used key The secret key used by digest authentication If not set a secure random value is generated This should normally only be set when it is necessary to keep key values constant either across server restarts and or across a cluster nonceValidity The time in milliseconds that a server generated nonce will be considered valid for use in authentication If not specified the default value of 300000 5 minutes will be used opaque The opaque server string used by digest authentication If not set a random value is generated This should normally only be set when it is necessary to keep opaque values constant either across server restarts and or across a cluster securePagesWithPragma Controls the caching of pages that are protected by security constraints Setting this to false may help work around caching issues in some browsers by using Cache Control private rather than the default of Pragma No cache and Cache control No cache If not set the default value of false will be used secureRandomAlgorithm Name of the algorithm to use to create the java security SecureRandom instances that generate session IDs If an invalid algorithm and or provider is specified the platform default provider and the default algorithm will be used If not specified the default algorithm of SHA1PRNG will be used If the default algorithm is not supported the platform default will be used To specify that the platform default should be used do not set the secureRandomProvider attribute and set this attribute to the empty string secureRandomClass Name of the Java class that extends java security SecureRandom to use to generate SSO session IDs If not specified the default value is java security SecureRandom secureRandomProvider Name of the provider to use to create the java security SecureRandom instances that generate SSO session IDs If an invalid algorithm and or provider is specified the platform default provider and the default algorithm will be used If not specified the platform default provider will be used validateUri Should the URI be validated as required by RFC2617 If not specified the default value of true will be used This should normally only be set when Tomcat is located behind a reverse proxy and the proxy is modifying the URI passed to Tomcat such that DIGEST authentication always fails Form Authenticator Valve Introduction The Form Authenticator Valve is automatically added to any Context that is configured to use FORM authentication If any non default settings are required the valve may be configured within Context element with the required values Attributes The Form Authenticator Valve supports the following configuration attributes Attribute Description changeSessionIdOnAuthentication Controls if the session ID is changed if a session exists at the point where users are authenticated This is to prevent session fixation attacks If not set the default value of true will be used characterEncoding Character encoding to use to read the username and password parameters from the request If not set the encoding of the request body will be used className Java class name of the implementation to use This MUST be set to org apache catalina authenticator FormAuthenticator disableProxyCaching Controls the caching of pages that are protected by security constraints Setting this to false may help work around caching issues in some browsers but will also cause secured pages to be cached by proxies which will almost certainly be a security issue securePagesWithPragma offers an alternative secure workaround for browser caching issues If not set the default value of true will be used landingPage Controls the behavior of the FORM authentication process if the process is misused for example by directly requesting the login page or delaying logging in for so long that the session expires If this attribute is set rather than returning an error response code Tomcat will redirect the user to the specified landing page if the login form is submitted with valid credentials For the login to be processed the landing page must be a protected resource i e one that requires authentication If the landing page does not require authentication then the user will not be logged in and will be prompted for their credentials again when they access a protected page securePagesWithPragma Controls the caching of pages that are protected by security constraints Setting this to false may help work around caching issues in some browsers by using Cache Control private rather than the default of Pragma No cache and Cache control No cache If not set the default value of false will be used secureRandomAlgorithm Name of the algorithm to use to create the java security SecureRandom instances that generate session IDs If an invalid algorithm and or provider is specified the platform default provider and the default algorithm will be used If not specified the default algorithm of SHA1PRNG will be used If the default algorithm is not supported the platform default will be used To specify that the platform default should be used do not set the secureRandomProvider attribute and set this attribute to the empty string secureRandomClass Name of the Java class that extends java security SecureRandom to use to generate SSO session IDs If not specified the default value is java security SecureRandom secureRandomProvider Name of the provider to use to create the java security SecureRandom instances that generate SSO session IDs If an invalid algorithm and or provider is specified the platform default provider and the default algorithm will be used If not specified the platform default provider will be used SSL Authenticator Valve Introduction The SSL Authenticator Valve is automatically added to

    Original URL path: http://ticket.eppa.es/docs/config/valve.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The ClusterManager object
    Cluster element is the template defined for all web applications that are marked distributable in their web xml file However you can still override the manager implementation on a per web application basis by putting the Manager inside the Context element either in the context xml file or the server xml file Attributes Common Attributes Attribute Description className name The name of this cluster manager the name is used to identify a session manager on a node The name might get modified by the Cluster element to make it unique in the container notifyListenersOnReplication Set to true if you wish to have session listeners notified when session attributes are being replicated or removed across Tomcat nodes in the cluster expireSessionsOnShutdown When a web application is being shutdown Tomcat issues an expire call to each session to notify all the listeners If you wish for all sessions to expire on all nodes when a shutdown occurs on one node set this value to true Default value is false sessionAttributeFilter A regular expression used to filter which session attributes will be replicated An attribute will only be replicated if its name matches this pattern If the pattern is not set default all attributes are eligible for replication As an example the value userName sessionHistory will only replicate the two session attributes named userName and sessionHistory org apache catalina ha session DeltaManager Attributes Attribute Description expireSessionsOnShutdown When a web application is being shutdown Tomcat issues an expire call to each session to notify all the listeners If you wish for all sessions to expire on all nodes when a shutdown occurs on one node set this value to true Default value is false maxActiveSessions The maximum number of active sessions that will be created by this Manager or 1 the default for no

    Original URL path: http://ticket.eppa.es/docs/config/cluster-manager.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Cluster Channel object
    messages between different Tomcat instances A few examples of these components would be the SimpleTcpCluster that does the messaging for the DeltaManager or the BackupManager that uses a different replication strategy The ReplicatedContext object does also use the channel object to communicate context attribute changes Nested Components Channel Membership The Membership component is responsible for auto discovering new nodes in the cluster and also to provide for notifications for any nodes that have not responded with a heartbeat The default implementation uses multicast In the membership component you configure how your nodes aka members are to be discovered and or divided up You can always find out more about Apache Tribes Channel Sender The Sender component manages all outbound connections and data messages that are sent over the network from one node to another This component allows messages to be sent in parallel The default implementation uses TCP client sockets and socket tuning for outgoing messages are configured here You can always find out more about Apache Tribes Channel Sender Transport The Transport component is the bottom IO layer for the sender component The default implementation uses non blocking TCP client sockets You can always find out more about Apache

    Original URL path: http://ticket.eppa.es/docs/config/cluster-channel.html (2015-09-25)
    Open archived version from archive