[jboss-cvs] JBossAS SVN: r75560 - branches/JBPAPP_4_2_0_GA_CP/server/src/resources/dtd.

[jboss-cvs-commits at lists.jboss.org]

Author: bstansberry at jboss.com
Date: 2008-07-09 13:36:52 -0400 (Wed, 09 Jul 2008)
New Revision: 75560

Modified:
   branches/JBPAPP_4_2_0_GA_CP/server/src/resources/dtd/jboss-web_4_2.dtd
Log:
[JBPAPP-944] Remove max-unreplicated-interval from DTD

Modified: branches/JBPAPP_4_2_0_GA_CP/server/src/resources/dtd/jboss-web_4_2.dtd
===================================================================
--- branches/JBPAPP_4_2_0_GA_CP/server/src/resources/dtd/jboss-web_4_2.dtd	2008-07-09 17:10:40 UTC (rev 75559)
+++ branches/JBPAPP_4_2_0_GA_CP/server/src/resources/dtd/jboss-web_4_2.dtd	2008-07-09 17:36:52 UTC (rev 75560)
@@ -297,7 +297,7 @@
 <!--
    HTTP Session clustering configuration (optional tags)
 -->
-<!ELEMENT replication-config (replication-trigger?, replication-granularity, replication-field-batch-mode?, max-unreplicated-interval?)>
+<!ELEMENT replication-config (replication-trigger?, replication-granularity, replication-field-batch-mode?)>
 
 <!--
    Clustering only: Determines when the container should consider that a session
@@ -372,38 +372,6 @@
          <replication-field-batch-mode>FALSE</replication-field-batch-mode>
 -->
 <!ELEMENT replication-field-batch-mode (true|false)>
-
-<!--
-   Clustering only: Determines the maximum interval between requests, in 
-   seconds, after which a request will trigger replication of the session's 
-   timestamp and other metadata regardless of whether the request has otherwise 
-   made the session dirty.  Such replication ensures that other nodes in the 
-   cluster are aware of the most recent value for the session's timestamp 
-   and won't incorrectly expire an unreplicated session upon failover. It also
-   results in correct values for HttpSession.getLastAccessedTime() calls 
-   following failover.
-
-   The cost of this metadata replication depends on the configured
-   replication-granularity. With <code>SESSION</code>, the session's 
-   attribute map is replicated along with the metadata, so it can be fairly 
-   costly.  With other granularities, the metadata object is replicated 
-   separately from the attributes and only contains a String, and a few longs, 
-   ints and booleans.
-   
-   A value of 0 means the metadata will be replicated whenever the session is
-   accessed.  A value of -1 means the metadata will be replicated only if some
-   other activity during the request (e.g. modifying an attribute) has
-   resulted in other replication work involving the session. A positive value
-   greater than the HttpSession.getMaxInactiveInterval() value will be treated 
-   as a likely misconfiguration and converted to 0 -- i.e. replicate the 
-   metadata on every request.
-    
-   Default value is 60 seconds.
-   
-   This element was added in releases 4.2.3.GA, EAP 4.2.0.CP04 and EAP 4.2.0.CP02.
-   In releases prior to those it has no effect.
--->
-<!ELEMENT max-unreplicated-interval (#PCDATA)>
 
 <!--
 Runtime information about a web service.