Gecko [ edgpens.lpkmn.gov.my ]

Name	Size	Permission
.mad-root	0 B	-rw-rw-rw-
ajp.html	53.52 KB	-rw-rw-rw-
automatic-deployment.html	78.04 KB	-rw-rw-rw-
cluster-channel.html	12.05 KB	-rw-rw-rw-
cluster-deployer.html	10.31 KB	-rw-rw-rw-
cluster-interceptor.html	32.31 KB	-rw-rw-rw-
cluster-listener.html	8.6 KB	-rw-rw-rw-
cluster-manager.html	26.82 KB	-rw-rw-rw-
cluster-membership.html	14.12 KB	-rw-rw-rw-
cluster-receiver.html	16.68 KB	-rw-rw-rw-
cluster-sender.html	18 KB	-rw-rw-rw-
cluster-valve.html	16.63 KB	-rw-rw-rw-
cluster.html	16.29 KB	-rw-rw-rw-
context.html	96.03 KB	-rw-rw-rw-
engine.html	18.48 KB	-rw-rw-rw-
executor.html	11.98 KB	-rw-rw-rw-
filter.html	114.75 KB	-rw-rw-rw-
globalresources.html	18.98 KB	-rw-rw-rw-
host.html	41.36 KB	-rw-rw-rw-
http.html	95.74 KB	-rw-rw-rw-
index.html	8.73 KB	-rw-rw-rw-
jar-scanner.html	11.84 KB	-rw-rw-rw-
listeners.html	45.44 KB	-rw-rw-rw-
loader.html	15.9 KB	-rw-rw-rw-
manager.html	39.54 KB	-rw-rw-rw-
realm.html	75.08 KB	-rw-rw-rw-
resources.html	12.17 KB	-rw-rw-rw-
server.html	10.82 KB	-rw-rw-rw-
service.html	9.92 KB	-rw-rw-rw-
sessionidgenerator.html	10.85 KB	-rw-rw-rw-
systemprops.html	50.22 KB	-rw-rw-rw-
valve.html	129.69 KB	-rw-rw-rw-

Code Editor : manager.html

<html><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>Apache Tomcat 7 Configuration Reference (7.0.107) - The Manager Component</title><meta name="author" content="Craig R. McClanahan"><meta name="author" content="Yoav Shapira"><style type="text/css" media="print">
 .noPrint {display: none;}
 td#mainBody {width: 100%;}
</style><style type="text/css">
code {background-color:rgb(224,255,255);padding:0 0.1em;}
code.attributeName, code.propertyName {background-color:transparent;}

table {
 border-collapse: collapse;
 text-align: left;
}
table *:not(table) {
 /* Prevent border-collapsing for table child elements like <div> */
 border-collapse: separate;
}

th {
  text-align: left;
}

div.codeBox pre code, code.attributeName, code.propertyName, code.noHighlight, .noHighlight code {
 background-color: transparent;
}
div.codeBox {
 overflow: auto;
 margin: 1em 0;
}
div.codeBox pre {
 margin: 0;
 padding: 4px;
 border: 1px solid #999;
 border-radius: 5px;
 background-color: #eff8ff;
 display: table; /* To prevent <pre>s from taking the complete available width. */
 /*
 When it is officially supported, use the following CSS instead of display: table
 to prevent big <pre>s from exceeding the browser window:
 max-width: available;
 width: min-content;
 */
}

div.codeBox pre.wrap {
  white-space: pre-wrap;
}

table.defaultTable tr, table.detail-table tr {
    border: 1px solid #CCC;
}

table.defaultTable tr:nth-child(even), table.detail-table tr:nth-child(even) {
    background-color: #FAFBFF;
}

table.defaultTable tr:nth-child(odd), table.detail-table tr:nth-child(odd) {
    background-color: #EEEFFF;
}

table.defaultTable th, table.detail-table th {
  background-color: #88b;
  color: #fff;
}

table.defaultTable th, table.defaultTable td, table.detail-table th, table.detail-table td {
  padding: 5px 8px;
}

p.notice {
 border: 1px solid rgb(255, 0, 0);
 background-color: rgb(238, 238, 238);
 color: rgb(0, 51, 102);
 padding: 0.5em;
 margin: 1em 2em 1em 1em;
}
</style></head><body bgcolor="#ffffff" text="#000000" link="#525D76" alink="#525D76" vlink="#525D76"><table border="0" width="100%" cellspacing="0"><tr><td><a href="https://tomcat.apache.org/"><img src="../images/tomcat.gif" align="right" alt="
 The Apache Tomcat Servlet/JSP Container
 " border="0"></a></td><td><h1>Apache Tomcat 7</h1>Version 7.0.107, Nov 18 2020</td><td><a href="http://www.apache.org/"><img src="../images/asf-logo.svg" align="right" alt="Apache Logo" border="0" style="width: 266px;height: 83px;"></a></td></tr></table><table border="0" width="100%" cellspacing="4"><tr><td colspan="2"><hr noshade size="1"></td></tr><tr><td width="20%" valign="top" nowrap class="noPrint">Links<ul><li><a href="../index.html">Docs Home</a></li><li><a href="index.html">Config Ref. Home</a></li><li><a href="https://wiki.apache.org/tomcat/FAQ">FAQ</a></li><li><a href="#comments_section">User Comments</a></li></ul>Top Level Elements<ul><li><a href="server.html">Server</a></li><li><a href="service.html">Service</a></li></ul>Executors<ul><li><a href="executor.html">Executor</a></li></ul>Connectors<ul><li><a href="http.html">HTTP</a></li><li><a href="ajp.html">AJP</a></li></ul>Containers<ul><li><a href="context.html">Context</a></li><li><a href="engine.html">Engine</a></li><li><a href="host.html">Host</a></li><li><a href="cluster.html">Cluster</a></li></ul>Nested Components<ul><li><a href="globalresources.html">Global Resources</a></li><li><a href="jar-scanner.html">JarScanner</a></li><li><a href="listeners.html">Listeners</a></li><li><a href="loader.html">Loader</a></li><li><a href="manager.html">Manager</a></li><li><a href="realm.html">Realm</a></li><li><a href="resources.html">Resources</a></li><li><a href="sessionidgenerator.html">SessionIdGenerator</a></li><li><a href="valve.html">Valve</a></li></ul>Cluster Elements<ul><li><a href="cluster.html">Cluster</a></li><li><a href="cluster-manager.html">Manager</a></li><li><a href="cluster-channel.html">Channel</a></li><li><a href="cluster-membership.html">Channel/Membership</a></li><li><a href="cluster-sender.html">Channel/Sender</a></li><li><a href="cluster-receiver.html">Channel/Receiver</a></li><li><a href="cluster-interceptor.html">Channel/Interceptor</a></li><li><a href="cluster-valve.html">Valve</a></li><li><a href="cluster-deployer.html">Deployer</a></li><li><a href="cluster-listener.html">ClusterListener</a></li></ul>web.xml<ul><li><a href="filter.html">Filter</a></li></ul>Other<ul><li><a href="systemprops.html">System properties</a></li></ul></td><td width="80%" valign="top" align="left" id="mainBody"><h1>The Manager Component</h1><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><a name="Table of Contents"></a><a name="Table_of_Contents">Table of Contents</a></td></tr><tr><td><blockquote>
<ul><li><a href="#Introduction">Introduction</a></li><li><a href="#Attributes">Attributes</a><ol><li><a href="#Common_Attributes">Common Attributes</a></li><li><a href="#Standard_Implementation">Standard Implementation</a></li></ol></li><li><a href="#Nested_Components">Nested Components</a></li><li><a href="#Special_Features">Special Features</a><ol><li><a href="#Persistence_Across_Restarts">Persistence Across Restarts</a></li><li><a href="#Disable_Session_Persistence">Disable Session Persistence</a></li></ol></li></ul>
</blockquote></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><a name="Introduction">Introduction</a></td></tr><tr><td><blockquote>

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, &mdash; see
 Standard Manager Implementation below for the details
 of this configuration.

</blockquote></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><a name="Attributes">Attributes</a></td></tr><tr><td><blockquote>

<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><a name="Common Attributes"></a><a name="Common_Attributes">Common Attributes</a></td></tr><tr><td><blockquote>

All implementations of Manager
 support the following attributes:

NOTE - The value for this property is inherited
 automatically based on the presence or absence of the
 <code>&lt;distributable&gt;</code> element in the web application
 deployment descriptor (<code>/WEB-INF/web.xml</code>).
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">maxActiveSessions</code></td><td align="left" valign="center">
 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>.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">maxInactiveInterval</code></td><td align="left" valign="center">
 Deprecated: This should be configured via the
 Context.
 The initial maximum time interval, in seconds,
 between client requests before a session is invalidated. A negative value
 will result in sessions never timing out. If the attribute is not provided,
 a default of 1800 seconds (30 minutes) is used.

This attribute provides the initial value whenever a
 new session is created, but the interval may be dynamically
 varied by a servlet via the
 <code>setMaxInactiveInterval</code> method of the <code>HttpSession</code> object.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">sessionIdLength</code></td><td align="left" valign="center">
 The length of session ids created by this Manager, measured in bytes,
 excluding subsequent conversion to a hexadecimal string and
 excluding any JVM route information used for load balancing.
 The default is 16. You should set the length on a nested
 SessionIdGenerator element instead.
 </td></tr></table>

</blockquote></td></tr></table>

<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><a name="Standard Implementation"></a><a name="Standard_Implementation">Standard Implementation</a></td></tr><tr><td><blockquote>

Tomcat provides two standard implementations of Manager
 for use &mdash; 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):

Please note that the session's <code>Principal</code> 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.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">processExpiresFrequency</code></td><td align="left" valign="center">
 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.
 
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">secureRandomClass</code></td><td align="left" valign="center">
 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>.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">secureRandomProvider</code></td><td align="left" valign="center">
 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.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">secureRandomAlgorithm</code></td><td align="left" valign="center">
 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.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">sessionAttributeNameFilter</code></td><td align="left" valign="center">
 A regular expression used to filter which session attributes will be
 distributed. An attribute will only be distributed 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.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">sessionAttributeValueClassNameFilter</code></td><td align="left" valign="center">
 A regular expression used to filter which session attributes will be
 distributed. An attribute will only be distributed 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>.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">warnOnSessionAttributeFilterFailure</code></td><td align="left" valign="center">
 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>.
 </td></tr></table>

<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.

Please note that the session's <code>Principal</code> 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.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">processExpiresFrequency</code></td><td align="left" valign="center">
 It is the same as described above for the
 <code>org.apache.catalina.session.StandardManager</code> class.
 
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">saveOnRestart</code></td><td align="left" valign="center">
 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>.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">secureRandomClass</code></td><td align="left" valign="center">
 It is the same as described above for the
 <code>org.apache.catalina.session.StandardManager</code> class.
 
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">secureRandomProvider</code></td><td align="left" valign="center">
 It is the same as described above for the
 <code>org.apache.catalina.session.StandardManager</code> class.
 
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">secureRandomAlgorithm</code></td><td align="left" valign="center">
 It is the same as described above for the
 <code>org.apache.catalina.session.StandardManager</code> class.
 
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">sessionAttributeNameFilter</code></td><td align="left" valign="center">
 A regular expression used to filter which session attributes will be
 distributed. An attribute will only be distributed 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.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">sessionAttributeValueClassNameFilter</code></td><td align="left" valign="center">
 A regular expression used to filter which session attributes will be
 distributed. An attribute will only be distributed 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>.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">warnOnSessionAttributeFilterFailure</code></td><td align="left" valign="center">
 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>.
 </td></tr></table>

In order to successfully use a PersistentManager, you must nest inside
 it a &lt;Store&gt; element, as described below.

</blockquote></td></tr></table>

</blockquote></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><a name="Nested Components"></a><a name="Nested_Components">Nested Components</a></td></tr><tr><td><blockquote>

<h3>All Manager Implementations</h3>

All Manager implementations bundled with Tomcat or extending
 <code>ManagerBase</code> allow nesting of a
 &lt;SessionIdGenerator&gt; element. It defines
 the behavior of session id generation. All implementations
 of the <a href="sessionidgenerator.html">SessionIdGenerator</a> allow the
 following attributes:

<h3>Persistent Manager Implementation</h3>

If you are using the Persistent Manager Implementation
 as described above, you MUST nest a
 &lt;Store&gt; element inside, which defines the
 characteristics of the persistent data storage. Two implementations
 of the <code>&lt;Store&gt;</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>&lt;Store&gt;</code> nested inside
 your <code>&lt;Manager&gt;</code> element with the following attributes:

<h5>JDBC Based Store</h5>

The JDBC Based Store implementation saves swapped out
 sessions in individual rows of a preconfigured table in a database
 that is accessed via a JDBC driver. 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>&lt;Store&gt;</code> nested inside
 your <code>&lt;Manager&gt;</code> element with the following attributes:

<table border="1" cellpadding="5"><tr><th width="15%" bgcolor="#023264">Attribute</th><th width="85%" bgcolor="#023264">Description</th></tr><tr><td align="left" valign="center"><code class="attributeName">checkInterval</code></td><td align="left" valign="center">
 The interval (in seconds) between checks for expired sessions
 among those sessions that are currently swapped out. By default,
 this interval is set to 60 seconds (one minute).
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">className</code></td><td align="left" valign="center">
 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.JDBCStore</code>
 to use this implementation.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">connectionURL</code></td><td align="left" valign="center">
 The connection URL that will be handed to the configured JDBC
 driver to establish a connection to the database containing our
 session table.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">dataSourceName</code></td><td align="left" valign="center">
 Name of the JNDI resource for a JDBC DataSource-factory. If this option
 is given and a valid JDBC resource can be found, it will be used and any
 direct configuration of a JDBC connection via <code>connectionURL</code>
 and <code>driverName</code> will be ignored. 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>.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">driverName</code></td><td align="left" valign="center">
 Java class name of the JDBC driver to be used.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">sessionAppCol</code></td><td align="left" valign="center">
 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>.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">sessionDataCol</code></td><td align="left" valign="center">
 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).
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">sessionIdCol</code></td><td align="left" valign="center">
 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).
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">sessionLastAccessedCol</code></td><td align="left" valign="center">
 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).
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">sessionMaxInactiveCol</code></td><td align="left" valign="center">
 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).
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">sessionTable</code></td><td align="left" valign="center">
 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.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">sessionValidCol</code></td><td align="left" valign="center">
 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.
 </td></tr></table>

Before attempting to use the JDBC Based 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:

<div class="codeBox"><pre><code>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)
);</code></pre></div>

In order for the JDBC Based Store to successfully connect to your
 database, the JDBC driver you configure must be visible to Tomcat's
 internal class loader. Generally, that means you must place the JAR
 file containing this driver into the <code>$CATALINA_HOME/lib</code>
 directory.

</blockquote></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><a name="Special Features"></a><a name="Special_Features">Special Features</a></td></tr><tr><td><blockquote>

<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><a name="Persistence Across Restarts"></a><a name="Persistence_Across_Restarts">Persistence Across Restarts</a></td></tr><tr><td><blockquote>

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>&lt;distributable&gt;</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.

</blockquote></td></tr></table>

<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><a name="Disable Session Persistence"></a><a name="Disable_Session_Persistence">Disable Session Persistence</a></td></tr><tr><td><blockquote>

As documented above, every web application by default has
 standard manager implementation configured, and it performs session
 persistence across restarts. To disable this persistence feature, create
 a <a href="context.html">Context</a> configuration file for your web
 application and add the following element there:

<div class="codeBox"><pre><code>&lt;Manager pathname="" /&gt;</code></pre></div>
 </blockquote></td></tr></table>

</blockquote></td></tr></table></td></tr><tr><td colspan="2"><hr noshade size="1"></td></tr><tr><td colspan="2"><div align="center">
 Copyright &copy; 1999-2020, Apache Software Foundation
 </div></td></tr></table></body></html>

${this.title}

Code Editor : manager.html