[jboss-cvs] JBossAS SVN: r99058 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/pt-BR.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Jan 6 01:13:48 EST 2010
Author: ldelima at redhat.com
Date: 2010-01-06 01:13:48 -0500 (Wed, 06 Jan 2010)
New Revision: 99058
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/pt-BR/Clustering_Guide_HTTP.po
Log:
translation finished
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/pt-BR/Clustering_Guide_HTTP.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/pt-BR/Clustering_Guide_HTTP.po 2010-01-06 06:10:00 UTC (rev 99057)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/pt-BR/Clustering_Guide_HTTP.po 2010-01-06 06:13:48 UTC (rev 99058)
@@ -5,7 +5,7 @@
msgstr ""
"Project-Id-Version: Clustering_Guide_HTTP\n"
"POT-Creation-Date: 2009-12-09T13:49:17\n"
-"PO-Revision-Date: 2010-01-06 16:09+1000\n"
+"PO-Revision-Date: 2010-01-06 16:13+1000\n"
"Last-Translator: \n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -65,7 +65,7 @@
#. Tag: title
#, no-c-format
msgid "Note"
-msgstr ""
+msgstr "Note"
#. Tag: para
#, no-c-format
@@ -86,11 +86,26 @@
"situations, losing a client session is not acceptable and, in this case, "
"session state replication is the price one has to pay."
msgstr ""
+"A load-balancer tracks HTTP requests and, depending on the session to which "
+"the request is linked, it dispatches the request to the appropriate node. "
+"This is called load-balancing with sticky-sessions or session affinity: once "
+"a session is created on a node, every future request will also be processed "
+"by that same node. Using a load-balancer that supports sticky-sessions but "
+"not configuring your web application for session replication allows you to "
+"scale very well by avoiding the cost of session state replication: each "
+"request for a session will always be handled by the same node. But in case a "
+"node dies, the state of all client sessions hosted by this node (the "
+"shopping carts, for example) will be lost and the clients will most probably "
+"need to login on another node and restart with a new session. In many "
+"situations, it is acceptable not to replicate HTTP sessions because all "
+"critical state is stored in a database or on the client. In other "
+"situations, losing a client session is not acceptable and, in this case, "
+"session state replication is the price one has to pay."
#. Tag: title
#, no-c-format
msgid "Configuring load balancing using Apache and mod_jk"
-msgstr ""
+msgstr "Configuring load balancing using Apache and mod_jk"
#. Tag: para
#, no-c-format
@@ -102,11 +117,17 @@
"containers while maintaining sticky sessions, which is what is most "
"interesting for us in this section."
msgstr ""
+"Apache is a well-known web server which can be extended by plugging in "
+"modules. One of these modules, mod_jk has been specifically designed to "
+"allow the forwarding of requests from Apache to a Servlet container. "
+"Furthermore, it is also able to load-balance HTTP calls to a set of Servlet "
+"containers while maintaining sticky sessions, which is what is most "
+"interesting for us in this section."
#. Tag: title
#, no-c-format
msgid "Download the software"
-msgstr ""
+msgstr "Download the software"
#. Tag: para
#, no-c-format
@@ -119,6 +140,13 @@
"sections, that you have installed Apache in the <literal>APACHE_HOME</"
"literal> directory."
msgstr ""
+"First of all, make sure that you have Apache installed. You can download "
+"Apache directly from Apache web site at <literal>http://httpd.apache.org/</"
+"literal>. Its installation is pretty straightforward and requires no "
+"specific configuration. As several versions of Apache exist, we advise you "
+"to use the latest stable 2.2.x version. We will consider, for the next "
+"sections, that you have installed Apache in the <literal>APACHE_HOME</"
+"literal> directory."
#. Tag: para
#, no-c-format
@@ -131,11 +159,18 @@
"the downloaded file to <literal>mod_jk.so</literal> and copy it under "
"<literal>APACHE_HOME/modules/</literal>."
msgstr ""
+"Next, download mod_jk binaries. Several versions of mod_jk exist as well. We "
+"strongly advise you to use mod_jk 1.2.x, as both mod_jk and mod_jk2 are "
+"deprecated, unsupported and no further development is going on in the "
+"community. The mod_jk 1.2.x binary can be downloaded from <literal>http://"
+"www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/</literal>. Rename "
+"the downloaded file to <literal>mod_jk.so</literal> and copy it under "
+"<literal>APACHE_HOME/modules/</literal>."
#. Tag: title
#, no-c-format
msgid "Configure Apache to load mod_jk"
-msgstr ""
+msgstr "Configure Apache to load mod_jk"
#. Tag: para
#, no-c-format
@@ -143,6 +178,8 @@
"Modify APACHE_HOME/conf/httpd.conf and add a single line at the end of the "
"file:"
msgstr ""
+"Modify APACHE_HOME/conf/httpd.conf and add a single line at the end of the "
+"file:"
#. Tag: para
#, no-c-format
@@ -150,11 +187,13 @@
"Next, create a new file named <literal>APACHE_HOME/conf/mod-jk.conf</"
"literal>:"
msgstr ""
+"Next, create a new file named <literal>APACHE_HOME/conf/mod-jk.conf</"
+"literal>:"
#. Tag: para
#, no-c-format
msgid "Please note that two settings are very important:"
-msgstr ""
+msgstr "Please note that two settings are very important:"
#. Tag: para
#, no-c-format
@@ -163,6 +202,9 @@
"library you have downloaded in the previous section. You must indicate the "
"exact same name with the \"modules\" file path prefix."
msgstr ""
+"The <literal>LoadModule</literal> directive must reference the mod_jk "
+"library you have downloaded in the previous section. You must indicate the "
+"exact same name with the \"modules\" file path prefix."
#. Tag: para
#, no-c-format
@@ -176,6 +218,14 @@
"loadbalancer, you can also forward all URLs (i.e., <literal>/*</literal>) to "
"mod_jk."
msgstr ""
+"The <literal>JkMount</literal> directive tells Apache which URLs it should "
+"forward to the mod_jk module (and, in turn, to the Servlet containers). In "
+"the above file, all requests with URL path <literal>/application/*</literal> "
+"are sent to the mod_jk load-balancer. This way, you can configure Apache to "
+"serve static contents (or PHP contents) directly and only use the "
+"loadbalancer for Java applications. If you only use mod_jk as a "
+"loadbalancer, you can also forward all URLs (i.e., <literal>/*</literal>) to "
+"mod_jk."
#. Tag: para
#, no-c-format
@@ -188,6 +238,13 @@
"<literal>/url=worker_name</literal>. To get things started, paste the "
"following example into the file you created:"
msgstr ""
+"In addition to the <literal>JkMount</literal> directive, you can also use "
+"the <literal>JkMountFile</literal> directive to specify a mount points "
+"configuration file, which contains multiple Tomcat forwarding URL mappings. "
+"You just need to create a <literal>uriworkermap.properties</literal> file in "
+"the <literal>APACHE_HOME/conf</literal> directory. The format of the file is "
+"<literal>/url=worker_name</literal>. To get things started, paste the "
+"following example into the file you created:"
#. Tag: para
#, no-c-format
@@ -195,6 +252,8 @@
"This will configure mod_jk to forward requests to <literal>/jmx-console</"
"literal> and <literal>/web-console</literal> to Tomcat."
msgstr ""
+"This will configure mod_jk to forward requests to <literal>/jmx-console</"
+"literal> and <literal>/web-console</literal> to Tomcat."
#. Tag: para
#, no-c-format
@@ -203,11 +262,14 @@
"conf</literal>. They are used to tell mod_jk where to put its logging file, "
"which logging level to use and so on."
msgstr ""
+"You will most probably not change the other settings in <literal>mod_jk."
+"conf</literal>. They are used to tell mod_jk where to put its logging file, "
+"which logging level to use and so on."
#. Tag: title
#, no-c-format
msgid "Configure worker nodes in mod_jk"
-msgstr ""
+msgstr "Configure worker nodeConfigure worker nodes in mod_jks in mod_jk"
#. Tag: para
#, no-c-format
@@ -219,6 +281,12 @@
"container and one global section. For a two nodes setup, the file could look "
"like this:"
msgstr ""
+"Next, you need to configure mod_jk workers file <literal>conf/workers."
+"properties</literal>. This file specifies where the different Servlet "
+"containers are located and how calls should be load-balanced across them. "
+"The configuration file contains one section for each target servlet "
+"container and one global section. For a two nodes setup, the file could look "
+"like this:"
#. Tag: para
#, no-c-format
@@ -227,6 +295,9 @@
"load balancing with sticky sessions between two servlet containers (that is, "
"JBoss AS instances) node1 and node2 listening on port 8009."
msgstr ""
+"Basically, the above file configures mod_jk to perform weighted round-robin "
+"load balancing with sticky sessions between two servlet containers (that is, "
+"JBoss AS instances) node1 and node2 listening on port 8009."
#. Tag: para
#, no-c-format
@@ -238,6 +309,12 @@
"name (or IP address) and the port number of the AJP13 connector running in "
"the Servlet container."
msgstr ""
+"In the <literal>workers.properties</literal> file, each node is defined "
+"using the <literal>worker.XXX</literal> naming convention where "
+"<literal>XXX</literal> represents an arbitrary name you choose for each of "
+"the target Servlet containers. For each worker, you must specify the host "
+"name (or IP address) and the port number of the AJP13 connector running in "
+"the Servlet container."
#. Tag: para
#, no-c-format
@@ -249,6 +326,12 @@
"receive. This setting can be used to differentiate servers with different "
"processing power."
msgstr ""
+"The <literal>lbfactor</literal> attribute is the load-balancing factor for "
+"this specific worker. It is used to define the priority (or weight) a node "
+"should have over other nodes. The higher this number is for a given worker "
+"relative to the other workers, the more HTTP requests the worker will "
+"receive. This setting can be used to differentiate servers with different "
+"processing power."
#. Tag: para
#, no-c-format
@@ -261,6 +344,13 @@
"tomcat/connectors-doc/config/workers.html</literal> for comments on "
"<literal>cachesize</literal> for Apache 1.3.x."
msgstr ""
+"The <literal>cachesize</literal> attribute defines the size of the thread "
+"pools associated to the Servlet container (i.e. the number of concurrent "
+"requests it will forward to the Servlet container). Make sure this number "
+"does not outnumber the number of threads configured on the AJP13 connector "
+"of the Servlet container. Please review <literal>http://jakarta.apache.org/"
+"tomcat/connectors-doc/config/workers.html</literal> for comments on "
+"<literal>cachesize</literal> for Apache 1.3.x."
#. Tag: para
#, no-c-format
@@ -271,6 +361,11 @@
"all workers previously defined in the same file: load-balancing will happen "
"over these workers."
msgstr ""
+"The last part of the <literal>conf/workers.properties</literal> file defines "
+"the loadbalancer worker. The only thing you must change is the "
+"<literal>worker.loadbalancer.balanced_workers</literal> line: it must list "
+"all workers previously defined in the same file: load-balancing will happen "
+"over these workers."
#. Tag: para
#, no-c-format
@@ -286,6 +381,16 @@
"To enable session stickiness, you need to set <literal>worker.loadbalancer."
"sticky_session</literal> to 1."
msgstr ""
+"The <literal>sticky_session</literal> property specifies the cluster "
+"behavior for HTTP sessions. If you specify <literal>worker.loadbalancer."
+"sticky_session=0</literal>, each request will be load balanced between node1 "
+"and node2; i.e., different requests for the same session will go to "
+"different servers. But when a user opens a session on one server, it is "
+"always necessary to always forward this user's requests to the same server, "
+"as long as that server is available. This is called a \"sticky session\", as "
+"the client is always using the same server he reached on his first request. "
+"To enable session stickiness, you need to set <literal>worker.loadbalancer."
+"sticky_session</literal> to 1."
#. Tag: para
#, no-c-format
@@ -293,11 +398,13 @@
"A non-loadbalanced setup with a single node requires a <literal>worker."
"list=node1</literal> entry."
msgstr ""
+"A non-loadbalanced setup with a single node requires a <literal>worker."
+"list=node1</literal> entry."
#. Tag: title
#, no-c-format
msgid "Configuring JBoss to work with mod_jk"
-msgstr ""
+msgstr "Configuring JBoss to work with mod_jk"
#. Tag: para
#, no-c-format
@@ -305,6 +412,8 @@
"Finally, we must configure the JBoss AS instances on all clustered nodes so "
"that they can expect requests forwarded from the mod_jk loadbalancer."
msgstr ""
+"Finally, we must configure the JBoss AS instances on all clustered nodes so "
+"that they can expect requests forwarded from the mod_jk loadbalancer."
#. Tag: para
#, no-c-format
@@ -316,6 +425,12 @@
"server name if necessary). Locate the <literal><Engine></literal> "
"element and add an attribute <literal>jvmRoute</literal>:"
msgstr ""
+"On each clustered JBoss node, we have to name the node according to the name "
+"specified in <literal>workers.properties</literal>. For instance, on JBoss "
+"instance node1, edit the <literal>JBOSS_HOME/server/all/deploy/jbossweb.sar/"
+"server.xml</literal> file (replace <literal>/all</literal> with your own "
+"server name if necessary). Locate the <literal><Engine></literal> "
+"element and add an attribute <literal>jvmRoute</literal>:"
#. Tag: para
#, no-c-format
@@ -323,6 +438,8 @@
"You also need to be sure the AJP connector in server.xml is enabled (i.e., "
"uncommented). It is enabled by default."
msgstr ""
+"You also need to be sure the AJP connector in server.xml is enabled (i.e., "
+"uncommented). It is enabled by default."
#. Tag: para
#, no-c-format
@@ -332,6 +449,10 @@
"taking care of session stickiness (clients will always use the same Servlet "
"container)."
msgstr ""
+"At this point, you have a fully working Apache+mod_jk load-balancer setup "
+"that will balance call to the Servlet containers of your cluster while "
+"taking care of session stickiness (clients will always use the same Servlet "
+"container)."
#. Tag: para
#, no-c-format
@@ -340,11 +461,14 @@
"to the JBoss wiki page at <literal>http://www.jboss.org/community/wiki/"
"UsingModjk12WithJBoss</literal>."
msgstr ""
+"For more updated information on using mod_jk 1.2 with JBoss AS, please refer "
+"to the JBoss wiki page at <literal>http://www.jboss.org/community/wiki/"
+"UsingModjk12WithJBoss</literal>."
#. Tag: title
#, no-c-format
msgid "Configuring HTTP session state replication"
-msgstr ""
+msgstr "Configuring HTTP session state replication"
#. Tag: para
#, no-c-format
@@ -354,6 +478,10 @@
"services in JBoss Enterprise Application Platform applies no matter what "
"load balancer is used."
msgstr ""
+"The preceding discussion has been focused on using mod_jk as a load "
+"balancer. The content of the remainder our discussion of clustering HTTP "
+"services in JBoss Enterprise Application Platform applies no matter what "
+"load balancer is used."
#. Tag: para
#, no-c-format
@@ -367,11 +495,19 @@
"shut down, the load balancer can fail over the next client request to any "
"server node and obtain the same session state."
msgstr ""
+"In <xref linkend=\"clustering-http-nodes\" />, we covered how to use sticky "
+"sessions to make sure that a client in a session always hits the same server "
+"node in order to maintain the session state. However, sticky sessions by "
+"themselves are not an ideal solution. If a node goes down, all its session "
+"data is lost. A better and more reliable solution is to replicate session "
+"data across the nodes in the cluster. This way, if a server node fails or is "
+"shut down, the load balancer can fail over the next client request to any "
+"server node and obtain the same session state."
#. Tag: title
#, no-c-format
msgid "Enabling session replication in your application"
-msgstr ""
+msgstr "Enabling session replication in your application"
#. Tag: para
#, no-c-format
@@ -380,6 +516,9 @@
"as distributable in the <literal>web.xml</literal> descriptor. Here's an "
"example:"
msgstr ""
+"To enable replication of your web application you must tag the application "
+"as distributable in the <literal>web.xml</literal> descriptor. Here's an "
+"example:"
#. Tag: para
#, no-c-format
@@ -390,6 +529,11 @@
"set if one or more of the default values described below is unacceptable. "
"Here is an example:"
msgstr ""
+"You can futher configure session replication using the <literal>replication-"
+"config</literal> element in the <literal>jboss-web.xml</literal> file. "
+"However, the <literal>replication-config</literal> element only needs to be "
+"set if one or more of the default values described below is unacceptable. "
+"Here is an example:"
#. Tag: para
#, no-c-format
@@ -399,6 +543,10 @@
"very infrequently changed from the defaults. We'll cover the commonly used "
"ones first."
msgstr ""
+"All of the above configuration elements are optional and can be ommitted if "
+"the default value is acceptable. A couple are commonly used; the rest are "
+"very infrequently changed from the defaults. We'll cover the commonly used "
+"ones first."
#. Tag: para
#, no-c-format
@@ -412,6 +560,14 @@
"state) has been modified and needs to be replicated. This element has 3 "
"valid values:"
msgstr ""
+"The <emphasis role=\"bold\"><literal>replication-trigger</literal></"
+"emphasis> element determines when the container should consider that session "
+"data must be replicated across the cluster. The rationale for this setting "
+"is that after a mutable object stored as a session attribute is accessed "
+"from the session, in the absence of a <literal>setAttribute</literal> call "
+"the container has no clear way to know if the object (and hence the session "
+"state) has been modified and needs to be replicated. This element has 3 "
+"valid values:"
#. Tag: para
#, no-c-format
@@ -425,6 +581,14 @@
"thing at much lower cost, using <literal>SET_AND_GET</literal> makes no "
"sense with AS 5."
msgstr ""
+"<emphasis role=\"bold\">SET_AND_GET</emphasis> is conservative but not "
+"optimal (performance-wise): it will always replicate session data even if "
+"its content has not been modified but simply accessed. This setting made (a "
+"little) sense in AS 4 since using it was a way to ensure that every request "
+"triggered replication of the session's timestamp. Since setting "
+"<literal>max_unreplicated_interval</literal> to 0 accomplishes the same "
+"thing at much lower cost, using <literal>SET_AND_GET</literal> makes no "
+"sense with AS 5."
#. Tag: para
#, no-c-format
@@ -435,6 +599,11 @@
"<literal>Integer</literal>, <literal>Long</literal>, <literal>String</"
"literal>, etc.) This is the default value."
msgstr ""
+"<emphasis role=\"bold\">SET_AND_NON_PRIMITIVE_GET</emphasis> is conservative "
+"but will only replicate if an object of a non-primitive type has been "
+"accessed (i.e. the object is not of a well-known immutable JDK type such as "
+"<literal>Integer</literal>, <literal>Long</literal>, <literal>String</"
+"literal>, etc.) This is the default value."
#. Tag: para
#, no-c-format
@@ -446,6 +615,12 @@
"coding practices to ensure <literal>setAttribute</literal> is always called "
"whenever a mutable object stored in the session is modified."
msgstr ""
+"<emphasis role=\"bold\">SET</emphasis> assumes that the developer will "
+"explicitly call <literal>setAttribute</literal> on the session if the data "
+"needs to be replicated. This setting prevents unnecessary replication and "
+"can have a major beneficial impact on performance, but requires very good "
+"coding practices to ensure <literal>setAttribute</literal> is always called "
+"whenever a mutable object stored in the session is modified."
#. Tag: para
#, no-c-format
@@ -453,6 +628,8 @@
"In all cases, calling <literal>setAttribute</literal> marks the session as "
"needing replication."
msgstr ""
+"In all cases, calling <literal>setAttribute</literal> marks the session as "
+"needing replication."
#. Tag: para
#, no-c-format
@@ -461,6 +638,9 @@
"emphasis> element determines the granularity of what gets replicated if the "
"container determines session replication is needed. The supported values are:"
msgstr ""
+"The <emphasis role=\"bold\"><literal>replication-granularity</literal></"
+"emphasis> element determines the granularity of what gets replicated if the "
+"container determines session replication is needed. The supported values are:"
#. Tag: para
#, no-c-format
@@ -473,6 +653,13 @@
"attribute values will not be broken when the session is deserialized. For "
"this reason it is the default setting."
msgstr ""
+"<emphasis role=\"bold\">SESSION</emphasis> indicates that the entire session "
+"attribute map should be replicated when any attribute is considered "
+"modified. Replication occurs at request end. This option replicates the most "
+"data and thus incurs the highest replication cost, but since all attributes "
+"values are always replicated together it ensures that any references between "
+"attribute values will not be broken when the session is deserialized. For "
+"this reason it is the default setting."
#. Tag: para
#, no-c-format
@@ -489,6 +676,17 @@
"This is because if the attributes are separately replicated, when the "
"session is deserialized on remote nodes the shared references will be broken."
msgstr ""
+"<emphasis role=\"bold\">ATTRIBUTE</emphasis> indicates that only attributes "
+"that the session considers to be potentially modified are replicated. "
+"Replication occurs at request end. For sessions carrying large amounts of "
+"data, parts of which are infrequently updated, this option can significantly "
+"increase replication performance. However, it is not suitable for "
+"applications that store objects in different attributes that share "
+"references with each other (e.g. a <literal>Person</literal> object in the "
+"\"husband\" attribute sharing with another <literal>Person</literal> in the "
+"\"wife\" attribute a reference to an <literal>Address</literal> object). "
+"This is because if the attributes are separately replicated, when the "
+"session is deserialized on remote nodes the shared references will be b"
#. Tag: para
#, no-c-format
@@ -502,6 +700,14 @@
"be preserved across the cluster. Potentially most performant, but requires "
"changes to your application (this will be discussed later)."
msgstr ""
+"<emphasis role=\"bold\">FIELD</emphasis> is useful if the classes stored in "
+"the session have been bytecode enhanced for use by POJO Cache. If they have "
+"been, the session management layer will detect field level changes within "
+"objects stored to the session, and will replicate only those changes. This "
+"is the most performant setting. Replication is only for individual changed "
+"data fields inside session attribute objects. Shared object references will "
+"be preserved across the cluster. Potentially most performant, but requires "
+"changes to your application (this will be discussed later)."
#. Tag: para
#, no-c-format
@@ -509,6 +715,8 @@
"The other elements under the <literal>replication-config</literal> element "
"are much less frequently used."
msgstr ""
+"The other elements under the <literal>replication-config</literal> element "
+"are much less frequently used."
#. Tag: para
#, no-c-format
@@ -525,6 +733,17 @@
"<xref linkend=\"clustering-http-state-cacheconfig\" /> for more details on "
"JBoss Cache configuration for web tier clustering."
msgstr ""
+"The <literal>cacheName</literal> element indicates the name of the JBoss "
+"Cache configuration that should be used for storing distributable sessions "
+"and replicating them around the cluster. This element lets web applications "
+"that require different caching characteristics specify the use of separate, "
+"differently configured, JBoss Cache instances. In JBoss AS 4 the cache to "
+"use was a server-wide configuration that could not be changed per web "
+"application. The default value is <literal>standard-session-cache</literal> "
+"if the <literal>replication-granularity</literal> is not <literal>FIELD</"
+"literal>, <literal>field-granularity-session-cache</literal> if it is. See "
+"<xref linkend=\"clustering-http-state-cacheconfig\" /> for more details on "
+"JBoss Cache configuration for web tier clustering."
#. Tag: para
#, no-c-format
@@ -539,6 +758,15 @@
"occur. Setting this to <literal>false</literal> is not advised. Default is "
"<literal>true</literal>."
msgstr ""
+"The <literal>replication-field-batch-mode</literal> element indicates "
+"whether all replication messages associated with a request will be batched "
+"into one message. This is applicable only if <literal>replication-"
+"granularity</literal> is <literal>FIELD</literal>. If <literal>replication-"
+"field-batch-mode</literal> is set to <literal>true</literal>, fine-grained "
+"changes made to objects stored in the session attribute map will replicate "
+"only when the HTTP request is finished; otherwise they replicate as they "
+"occur. Setting this to <literal>false</literal> is not advised. Default is "
+"<literal>true</literal>."
#. Tag: para
#, no-c-format
@@ -550,6 +778,12 @@
"associated with every request and replace the <literal>jvmRoute</literal> "
"portion of the session ID if it detects a failover."
msgstr ""
+"The <literal>useJK</literal> element indicates whether the container should "
+"assume that a JK-based software load balancer (e.g. mod_jk, mod_proxy, "
+"mod_cluster) is being used for load balancing for this web application. If "
+"set to <literal>true</literal>, the container will examine the session ID "
+"associated with every request and replace the <literal>jvmRoute</literal> "
+"portion of the session ID if it detects a failover."
#. Tag: para
#, no-c-format
@@ -560,6 +794,11 @@
"<literal>Engine</literal> (see <xref linkend=\"clustering-http-jboss\" />) "
"to determine whether JK is used."
msgstr ""
+"The default value is <literal>null</literal> (i.e. unspecified). In this "
+"case the session manager will use the presence or absence of a "
+"<literal>jvmRoute</literal> configuration on its enclosing JBoss Web "
+"<literal>Engine</literal> (see <xref linkend=\"clustering-http-jboss\" />) "
+"to determine whether JK is used."
#. Tag: para
#, no-c-format
@@ -567,6 +806,8 @@
"You need only set this to <literal>false</literal> for web applications "
"whose URL cannot be handled by the JK load balancer."
msgstr ""
+"You need only set this to <literal>false</literal> for web applications "
+"whose URL cannot be handled by the JK load balancer."
#. Tag: para
#, no-c-format
@@ -580,6 +821,14 @@
"upon failover. It also results in correct values for <literal>HttpSession."
"getLastAccessedTime()</literal> calls following failover."
msgstr ""
+"The <literal>max-unreplicated-interval</literal> element configures the "
+"maximum interval between requests, in seconds, after which a request will "
+"trigger replication of the session's timestamp 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 <literal>HttpSession."
+"getLastAccessedTime()</literal> calls following failover."
#. Tag: para
#, no-c-format
@@ -594,6 +843,15 @@
"i.e. replicate the metadata on every request. Default value is <literal>60</"
"literal>."
msgstr ""
+"A value of <literal>0</literal> means the timestamp will be replicated "
+"whenever the session is accessed. A value of <literal>-1</literal> means the "
+"timestamp 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 "
+"<literal>HttpSession.getMaxInactiveInterval()</literal> value will be "
+"treated as probable misconfiguration and converted to <literal>0</literal>; "
+"i.e. replicate the metadata on every request. Default value is <literal>60</"
+"literal>."
#. Tag: para
#, no-c-format
@@ -602,6 +860,9 @@
"replicated to the other nodes. Possible values are <literal>instant</"
"literal> (the default) and <literal>interval</literal>."
msgstr ""
+"The <literal>snapshot-mode</literal> element configures when sessions are "
+"replicated to the other nodes. Possible values are <literal>instant</"
+"literal> (the default) and <literal>interval</literal>."
#. Tag: para
#, no-c-format
@@ -611,6 +872,10 @@
"perform the replication. In this case, the <literal>snapshot-interval</"
"literal> property is ignored."
msgstr ""
+"he typical value, <literal>instant</literal>, replicates changes to the "
+"other nodes at the end of requests, using the request processing thread to "
+"perform the replication. In this case, the <literal>snapshot-interval</"
+"literal> property is ignored."
#. Tag: para
#, no-c-format
@@ -619,6 +884,9 @@
"runs every <literal>snapshot-interval</literal> milliseconds, checking for "
"modified sessions and replicating them."
msgstr ""
+"With <literal>interval</literal> mode, a background task is created that "
+"runs every <literal>snapshot-interval</literal> milliseconds, checking for "
+"modified sessions and replicating them."
#. Tag: para
#, no-c-format
@@ -627,6 +895,9 @@
"literal> is set to <literal>FIELD</literal>. If it is <literal>FIELD</"
"literal>, <literal>instant</literal> mode will be used."
msgstr ""
+"Note that this property has no effect if <literal>replication-granularity</"
+"literal> is set to <literal>FIELD</literal>. If it is <literal>FIELD</"
+"literal>, <literal>instant</literal> mode will be used."
#. Tag: para
#, no-c-format
@@ -636,6 +907,10 @@
"be started for this web application. Only meaningful if <literal>snapshot-"
"mode</literal> is set to <literal>interval</literal>."
msgstr ""
+"The <literal>snapshot-interval</literal> element defines how often (in "
+"milliseconds) the background task that replicates modified sessions should "
+"be started for this web application. Only meaningful if <literal>snapshot-"
+"mode</literal> is set to <literal>interval</literal>."
#. Tag: para
#, no-c-format
@@ -648,6 +923,13 @@
"<literal>HttpSessionAttributeListener</literal> and/or "
"<literal>HttpSessionBindingListener</literal>."
msgstr ""
+"The <literal>session-notification-policy</literal> element specifies the "
+"fully qualified class name of the implementation of the "
+"<literal>ClusteredSessionNotificationPolicy</literal> interface that should "
+"be used to govern whether servlet specification notifications should be "
+"emitted to any registered <literal>HttpSessionListener</literal>, "
+"<literal>HttpSessionAttributeListener</literal> and/or "
+"<literal>HttpSessionBindingListener</literal>."
#. Tag: para
#, no-c-format
More information about the jboss-cvs-commits
mailing list