Quellcode-Bibliothek

^© Kompilation durch diese Firma

[Weder Korrektheit noch Funktionsfähigkeit der Software werden zugesichert.]

Datei: Sprache: XML

Untersuchung Apache^©

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE document [
 <!ENTITY project SYSTEM "project.xml">
]>
<document url="manager.html">

 &project;

 <properties>
 <author email="[email protected]">Craig R. McClanahan</author>
 <author email="[email protected]">Yoav Shapira</author>
 <title>The Manager Component</title>
 </properties>

<body>

<section name="Table of Contents">
<toc/>
</section>

<section name="Introduction">

 The Manager element represents the session
 manager that will be used to create and maintain HTTP sessions
 as requested by the associated web application.

 A Manager element MAY be nested inside a
 <a href="context.html">Context</a> component. If it is not included,
 a default Manager configuration will be created automatically, which
 is sufficient for most requirements, — see
 Standard Manager Implementation below for the details
 of this configuration.

</section>

<section name="Attributes">

 <subsection name="Common Attributes">

 All implementations of Manager
 support the following attributes:

 <attributes>

 <attribute name="className" required="false">
 Java class name of the implementation to use. This class must
 implement the <code>org.apache.catalina.Manager</code> interface.
 If not specified, the standard value (defined below) will be used.
 </attribute>

 <attribute name="maxActiveSessions" required="false">
 The maximum number of active sessions that will be created by
 this Manager, or <code>-1</code> (the default) for no limit.

 When the limit is reached, any attempt to create a new session
 (e.g. with <code>HttpServletRequest.getSession()</code> call)
 will fail with an <code>IllegalStateException</code>.
 </attribute>

 <attribute name="notifyAttributeListenerOnUnchangedValue" required="false">
 If an attribute is added to the session and that attribute is already
 present in the session under the same name will any
 <code>HttpSessionAttributeListener</code> be notified that the attribute
 has been replaced. If not specified, the default value of
 <code>true</code> will be used.
 </attribute>

 <attribute name="notifyBindingListenerOnUnchangedValue" required="false">
 If an attribute is added to the session, that attribute is already
 present in the session under the same name and the attribute implements
 <code>HttpSessionBindingListener</code>, will the listener be notified
 that the attribute has been unbound and bound again. If not specified,
 the default value of <code>false</code> will be used.
 </attribute>

 <attribute name="sessionActivityCheck" required="false">
 If this is <code>true</code>, Tomcat will track the number of active
 requests for each session. When determining if a session is valid, any
 session with at least one active request will always be considered valid.
 If <code>org.apache.catalina.STRICT_SERVLET_COMPLIANCE</code> is set to
 <code>true</code>, the default of this setting will be <code>true</code>,
 else the default value will be <code>false</code>.
 </attribute>

 <attribute name="sessionLastAccessAtStart" required="false">
 If this is <code>true</code>, the last accessed time for sessions will
 be calculated from the beginning of the previous request. If
 <code>false</code>, the last accessed time for sessions will be calculated
 from the end of the previous request. This also affects how the idle time
 is calculated.
 If <code>org.apache.catalina.STRICT_SERVLET_COMPLIANCE</code> is set to
 <code>true</code>, the default of this setting will be <code>true</code>,
 else the default value will be <code>false</code>.
 </attribute>

 </attributes>

 </subsection>

 <subsection name="Standard Implementation">

 Tomcat provides two standard implementations of Manager
 for use — the default one stores active sessions, while the optional one
 stores active sessions that have been swapped out (in addition to saving
 sessions across a restart of Tomcat) in a storage location that is selected
 via the use of an appropriate Store nested element.

 <h3>Standard Manager Implementation</h3>

 The standard implementation of Manager is
 org.apache.catalina.session.StandardManager.
 It supports the following additional attributes (in addition to the
 common attributes listed above):

 <attributes>

 <attribute name="pathname" required="false">
 Absolute or relative (to the work directory for this Context)
 pathname of the file in which session state will be preserved
 across application restarts, if possible. The default is
 null. See
 <a href="#Persistence_Across_Restarts">Persistence Across Restarts</a>
 for more information. This persistence may be
 enabled by setting this attribute to a non empty string.
 </attribute>

 <attribute name="persistAuthentication" required="false">
 Should authentication information be included when session state is
 preserved across application restarts? If <code>true</code>, the session's
 authentication is preserved so that the session remains authenticated
 after the application has been restarted. If not specified, the default
 value of <code>false</code> will be used. See
 <a href="#Persistence_Across_Restarts">Persistence Across Restarts</a>
 for more information.

 Please note that the session's Principal class as well
 as its descendant classes are all subject to the
 sessionAttributeValueClassNameFilter. If such a filter
 is specified or a <code>SecurityManager</code> is enabled, the names of
 the <code>Principal</code> class and descendant classes must match that
 filter pattern in order to be restored.
 </attribute>

 <attribute name="processExpiresFrequency" required="false">
 Frequency of the session expiration, and related manager operations.
 Manager operations will be done once for the specified amount of
 backgroundProcess calls (i.e., the lower the amount, the more often the
 checks will occur). The minimum value is 1, and the default value is 6.
 
 </attribute>

 <attribute name="secureRandomClass" required="false">
 Name of the Java class that extends
 <code>java.security.SecureRandom</code> to use to generate session IDs.
 If not specified, the default value is
 <code>java.security.SecureRandom</code>.
 </attribute>

 <attribute name="secureRandomProvider" required="false">
 Name of the provider to use to create the
 <code>java.security.SecureRandom</code> instances that generate session
 IDs. If an invalid algorithm and/or provider is specified, the Manager
 will use the platform default provider and the default algorithm. If not
 specified, the platform default provider will be used.
 </attribute>

 <attribute name="secureRandomAlgorithm" required="false">
 Name of the algorithm to use to create the
 <code>java.security.SecureRandom</code> instances that generate session
 IDs. If an invalid algorithm and/or provider is specified, the Manager
 will use the platform default provider and the default algorithm. 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.
 </attribute>

 <attribute name="sessionAttributeNameFilter" required="false">
 A regular expression used to filter which session attributes will be
 serialized for clustering/replication, or storage to any persistent store.
 An attribute will only be serialized if its name matches
 this pattern. If the pattern is zero length or <code>null</code>, all
 attributes are eligible for distribution. The pattern is anchored so the
 session attribute name must fully match the pattern. As an example, the
 value <code>(userName|sessionHistory)</code> will only distribute the
 two session attributes named <code>userName</code> and
 <code>sessionHistory</code>. If not specified, the default value of
 <code>null</code> will be used.
 </attribute>

 <attribute name="sessionAttributeValueClassNameFilter" required="false">
 A regular expression used to filter which session attributes will be
 serialized for clustering/replication, or storage to any persistent store.
 An attribute will only be serialized if the implementation
 class name of the value matches this pattern. If the pattern is zero
 length or <code>null</code>, all attributes are eligible for
 distribution. The pattern is anchored so the fully qualified class name
 must fully match the pattern. If not specified, the default value of
 <code>null</code> will be used unless a <code>SecurityManager</code> is
 enabled in which case the default will be
 <code>java\\.lang\\.(?:Boolean|Integer|Long|Number|String)|org\\.apache\\.catalina\\.realm\\.GenericPrincipal\\$SerializablePrincipal|\\[Ljava.lang.String;</code>.
 </attribute>

 <attribute name="warnOnSessionAttributeFilterFailure" required="false">
 If sessionAttributeNameFilter or
 sessionAttributeValueClassNameFilter blocks an
 attribute, should this be logged at <code>WARN</code> level? If
 <code>WARN</code> level logging is disabled then it will be logged at
 <code>DEBUG</code>. The default value of this attribute is
 <code>false</code> unless a <code>SecurityManager</code> is enabled in
 which case the default will be <code>true</code>.
 </attribute>
 </attributes>

 <h3>Persistent Manager Implementation</h3>

 NOTE: You must set either the
 <code>org.apache.catalina.session.StandardSession.ACTIVITY_CHECK</code> or
 <code>org.apache.catalina.STRICT_SERVLET_COMPLIANCE</code>
 <a href="systemprops.html">system properties</a> to <code>true</code> for
 the persistent manager to work correctly.

 The persistent implementation of Manager is
 org.apache.catalina.session.PersistentManager. In
 addition to the usual operations of creating and deleting sessions, a
 <code>PersistentManager</code> has the capability to swap active (but
 idle) sessions out to a persistent storage mechanism, as well as to save
 all sessions 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 <code>PersistentManager</code>.

 This implementation of Manager supports the following attributes in
 addition to the <a href="#Common_Attributes">Common Attributes</a>
 described earlier.

 <attributes>

 <attribute name="className" required="true">
 It has the same meaning as described in the
 <a href="#Common_Attributes">Common Attributes</a> above.
 You must specify
 <code>org.apache.catalina.session.PersistentManager</code> to use
 this manager implementation.
 </attribute>

 <attribute name="maxIdleBackup" required="false">
 The time interval (in seconds) since the last access to a session
 before it is eligible for being persisted to the session store, or
 <code>-1</code> to disable this feature. By default, this feature is
 disabled.
 </attribute>

 <attribute name="maxIdleSwap" required="false">
 The maximum time a session may be idle before it is eligible to be
 swapped to disk due to inactivity. Setting this to <code>-1</code> means
 sessions should not be swapped out just because of inactivity. If this
 feature is enabled, the time interval specified here should be equal to
 or longer than the value specified for <code>maxIdleBackup</code>. By
 default, this feature is disabled.
 </attribute>

 <attribute name="minIdleSwap" required="false">
 The minimum time in seconds a session must be idle before it is
 eligible to be swapped to disk to keep the active session count below
 maxActiveSessions. Setting to <code>-1</code> means sessions will not be
 swapped out to keep the active session count down. If specified, this
 value should be less than that specified by <code>maxIdleSwap</code>.
 By default, this value is set to <code>-1</code>.
 </attribute>

 <attribute name="persistAuthentication" required="false">
 Should authentication information be included when sessions are
 swapped out to persistent storage? If <code>true</code>, the session's
 authentication is preserved so that the session remains authenticated
 after being reloaded (swapped in) from persistent storage. If not
 specified, the default value of <code>false</code> will be used.

 Please note that the session's Principal class as well
 as its descendant classes are all subject to the
 sessionAttributeValueClassNameFilter. If such a filter
 is specified or a <code>SecurityManager</code> is enabled, the names of
 the <code>Principal</code> class and descendant classes must match that
 filter pattern in order to be restored.
 </attribute>

 <attribute name="processExpiresFrequency" required="false">
 It is the same as described above for the
 <code>org.apache.catalina.session.StandardManager</code> class.
 
 </attribute>

 <attribute name="saveOnRestart" required="false">
 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 <code>true</code>.
 </attribute>

 <attribute name="secureRandomClass" required="false">
 It is the same as described above for the
 <code>org.apache.catalina.session.StandardManager</code> class.
 
 </attribute>

 <attribute name="secureRandomProvider" required="false">
 It is the same as described above for the
 <code>org.apache.catalina.session.StandardManager</code> class.
 
 </attribute>

 <attribute name="secureRandomAlgorithm" required="false">
 It is the same as described above for the
 <code>org.apache.catalina.session.StandardManager</code> class.
 
 </attribute>

 <attribute name="sessionAttributeNameFilter" required="false">
 A regular expression used to filter which session attributes will be
 serialized for clustering/replication, or storage to any persistent store.
 An attribute will only be serialized if its name matches
 this pattern. If the pattern is zero length or <code>null</code>, all
 attributes are eligible for distribution. The pattern is anchored so the
 session attribute name must fully match the pattern. As an example, the
 value <code>(userName|sessionHistory)</code> will only distribute the
 two session attributes named <code>userName</code> and
 <code>sessionHistory</code>. If not specified, the default value of
 <code>null</code> will be used.
 </attribute>

 <attribute name="sessionAttributeValueClassNameFilter" required="false">
 A regular expression used to filter which session attributes will be
 serialized for clustering/replication, or storage to any persistent store.
 An attribute will only be serialized if the implementation
 class name of the value matches this pattern. If the pattern is zero
 length or <code>null</code>, all attributes are eligible for
 distribution. The pattern is anchored so the fully qualified class name
 must fully match the pattern. If not specified, the default value of
 <code>null</code> will be used unless a <code>SecurityManager</code> is
 enabled in which case the default will be
 <code>java\\.lang\\.(?:Boolean|Integer|Long|Number|String)|org\\.apache\\.catalina\\.realm\\.GenericPrincipal\\$SerializablePrincipal|\\[Ljava.lang.String;</code>.
 </attribute>

 <attribute name="warnOnSessionAttributeFilterFailure" required="false">
 If sessionAttributeNameFilter or
 sessionAttributeValueClassNameFilter blocks an
 attribute, should this be logged at <code>WARN</code> level? If
 <code>WARN</code> level logging is disabled then it will be logged at
 <code>DEBUG</code>. The default value of this attribute is
 <code>false</code> unless a <code>SecurityManager</code> is enabled in
 which case the default will be <code>true</code>.
 </attribute>
 </attributes>

 In order to successfully use a PersistentManager, you must nest inside
 it a <Store> element, as described below.

 </subsection>

</section>

<section name="Nested Components">

 <h3>All Manager Implementations</h3>

 All Manager implementations allow nesting of a
 <SessionIdGenerator> element. It defines
 the behavior of session id generation. All implementations
 of the <a href="sessionidgenerator.html">SessionIdGenerator</a> allow the
 following attributes:
 

 <attributes>

 <attribute name="sessionIdLength" required="false">
 The length of the session ID may be changed with the
 sessionIdLength attribute.
 
 </attribute>

 </attributes>

 <h3>Persistent Manager Implementation</h3>

 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 <code><Store></code> element are currently available,
 with different characteristics, as described below.

 <h5>File Based Store</h5>

 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 <code><Store></code> nested inside
 your <code><Manager></code> element with the following attributes:
 

 <attributes>

 <attribute name="className" required="true">
 Java class name of the implementation to use. This class must
 implement the <code>org.apache.catalina.Store</code> interface. You
 must specify
 <code>org.apache.catalina.session.FileStore</code>
 to use this implementation.
 </attribute>

 <attribute name="directory" required="false">
 Absolute or relative (to the temporary work directory for this web
 application) pathname of the directory into which individual session
 files are written. If not specified, the temporary work directory
 assigned by the container is utilized.
 </attribute>

 </attributes>

 <h5>Data source Based Store</h5>

 The Data source Based Store implementation saves swapped out
 sessions in individual rows of a preconfigured table in a database
 that is accessed via a data sourcer. With large numbers of swapped out
 sessions, this implementation will exhibit improved performance over
 the File Based Store described above.

 To configure this, add a <code><Store></code> nested inside
 your <code><Manager></code> element with the following attributes:
 

 <attributes>

 <attribute name="className" required="true">
 Java class name of the implementation to use. This class must
 implement the <code>org.apache.catalina.Store</code> interface. You
 must specify
 <code>org.apache.catalina.session.DataSourceStore</code>
 to use this implementation.
 </attribute>

 <attribute name="dataSourceName" required="false">
 Name of the JNDI resource for a JDBC DataSource-factory. Since this
 code uses prepared statements, you might want to configure pooled
 prepared statements as shown in
 <a href="../jndi-resources-howto.html">the JNDI resources
 How-To</a>.
 </attribute>

 <attribute name="localDataSource" required="false">
 This allows the Store to use a DataSource defined for the Context
 rather than a global DataSource. If not specified, the default is
 <code>false</code>: use a global DataSource.
 </attribute>

 <attribute name="sessionAppCol" required="false">
 Name of the database column, contained in the specified session table,
 that contains the Engine, Host, and Web Application Context name in the
 format <code>/Engine/Host/Context</code>. If not specified the default
 value of <code>app</code> will be used.
 </attribute>

 <attribute name="sessionDataCol" required="false">
 Name of the database column, contained in the specified session table,
 that contains the serialized form of all session attributes for a swapped
 out session. The column type must accept a binary object (typically called
 a BLOB). If not specified the default value of <code>data</code> will be
 used.
 </attribute>

 <attribute name="sessionIdCol" required="false">
 Name of the database column, contained in the specified session table,
 that contains the session identifier of the swapped out session. The
 column type must accept character string data of at least as many
 characters as are contained in session identifiers created by Tomcat
 (typically 32). If not specified the default value of <code>id</code> will
 be used.
 </attribute>

 <attribute name="sessionLastAccessedCol" required="false">
 Name of the database column, contained in the specified session table,
 that contains the <code>lastAccessedTime</code> property of this session.
 The column type must accept a Java <code>long</code> (64 bits). If not
 specified the default value of <code>maxinactive</code> will be used.
 </attribute>

 <attribute name="sessionMaxInactiveCol" required="false">
 Name of the database column, contained in the specified session table,
 that contains the <code>maxInactiveInterval</code> property of this
 session. The column type must accept a Java <code>integer</code> (32
 bits). If not specified, the default value of <code>maxinactive</code>
 will be used.
 </attribute>

 <attribute name="sessionTable" required="false">
 Name of the database table to be used for storing swapped out sessions.
 This table must contain (at least) the database columns that are
 configured by the other attributes of this element. If not specified the
 default value of <code>tomcat$sessions</code> will be used.
 </attribute>

 <attribute name="sessionValidCol" required="false">
 Name of the database column, contained in the specified session table,
 that contains a flag indicating whether this swapped out session is still
 valid or not. The column type must accept a single character. If not
 specified the default value of <code>valid</code> will be used.
 </attribute>

 </attributes>

 Before attempting to use the data source Store for the first time,
 you must create the table that will be used to store swapped out sessions.
 Detailed SQL commands vary depending on the database you are using, but
 a script like this will generally be required:

<source>create table tomcat_sessions (
 session_id varchar(100) not null primary key,
 valid_session char(1) not null,
 max_inactive int not null,
 last_access bigint not null,
 app_name varchar(255),
 session_data mediumblob,
 KEY kapp_name(app_name)
);</source>

 Note: The SQL command above does not use the default names for either the
 table or the columns so the data source Store would need to be configured
 to reflect this.

</section>

<section name="Special Features">

 <subsection name="Persistence Across Restarts">

 Whenever Apache Tomcat is shut down normally and restarted, or when an
 application reload is triggered, the standard Manager implementation
 will attempt to serialize all currently active sessions to a disk
 file located via the <code>pathname</code> attribute. All such saved
 sessions will then be deserialized and activated (assuming they have
 not expired in the mean time) when the application reload is completed.

 In order to successfully restore the state of session attributes,
 all such attributes MUST implement the <code>java.io.Serializable</code>
 interface. You MAY cause the Manager to enforce this restriction by
 including the <code><distributable></code> element in your web
 application deployment descriptor (<code>/WEB-INF/web.xml</code>).

 Note that, if persistAuthentication is also set to
 <code>true</code>, the <code>Principal</code> class present in the session
 MUST also implement the <code>java.io.Serializable</code> interface in order
 to make authentication persistence work properly. The actual type of that
 <code>Principal</code> class is determined by the <a href="realm.html">
 Realm</a> implementation used with the application. Tomcat's standard
 <code>Principal</code> class instantiated by most of the Realms (except
 <code>JAASRealm</code>) implements <code>java.io.Serializable</code>.

 The persistence across restarts provided by the
 StandardManager is a simpler implementation than that
 provided by the PersistentManager. If robust, production
 quality persistence across restarts is required then the
 PersistentManager should be used with an appropriate
 configuration.

 </subsection>

 <subsection name="Enable Session Persistence">

 As documented above, every web application by default has
 standard manager implementation configured, which can perform session
 persistence across restarts. To enable this persistence feature, create
 a <a href="context.html">Context</a> configuration file for your web
 application and add the following element there (in this example,
 it will save sessions to files named <code>SESSIONS.ser</code>):

 <source><![CDATA[<Manager pathname="SESSIONS.ser" />]]></source>
 </subsection>

</section>

</body>

</document>

¤ Diese beiden folgenden Angebotsgruppen bietet das Unternehmen0.12Angebot Wie Sie bei der Firma Beratungs- und Dienstleistungen beauftragen können ¤

vermutete Sprache: Sekunden
vermutete Sprache: Hier finden Sie eine Liste der Produkte des Unternehmens
Mittel

Quellcode-Bibliothek

^© Kompilation durch diese Firma

[Weder Korrektheit noch Funktionsfähigkeit der Software werden zugesichert.]

Datei: Sprache: XML

Untersuchung Apache^©

¤ Diese beiden folgenden Angebotsgruppen bietet das Unternehmen0.12Angebot Wie Sie bei der Firma Beratungs- und Dienstleistungen beauftragen können ¤

Lebenszyklus

Ziele

Bot Zugriff

Quellcode-Bibliothek

© Kompilation durch diese Firma

[Weder Korrektheit noch Funktionsfähigkeit der Software werden zugesichert.]

Datei: Sprache: XML

Untersuchung Apache©

¤ Diese beiden folgenden Angebotsgruppen bietet das Unternehmen0.12Angebot Wie Sie bei der Firma Beratungs- und Dienstleistungen beauftragen können ¤

Lebenszyklus

Ziele

Bot Zugriff

^© Kompilation durch diese Firma

Untersuchung Apache^©