[jboss-cvs] JBossAS SVN: r68118 - projects/docs/trunk/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Dec 10 17:26:23 EST 2007
Author: xhuang at jboss.com
Date: 2007-12-10 17:26:23 -0500 (Mon, 10 Dec 2007)
New Revision: 68118
Removed:
projects/docs/trunk/Server_Configuration_Guide/zh-CN/Connectors.po
projects/docs/trunk/Server_Configuration_Guide/zh-CN/J2EE_Transactions_On_JBOSS.po
projects/docs/trunk/Server_Configuration_Guide/zh-CN/JBossCache_And_JGroups_Services.po
Log:
Merge with latest en-US
Deleted: projects/docs/trunk/Server_Configuration_Guide/zh-CN/Connectors.po
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/zh-CN/Connectors.po 2007-12-10 18:28:16 UTC (rev 68117)
+++ projects/docs/trunk/Server_Configuration_Guide/zh-CN/Connectors.po 2007-12-10 22:26:23 UTC (rev 68118)
@@ -1,2235 +0,0 @@
-# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
-# Automatically generated, 2007.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: JBEAP 420\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2007-11-05 06:03+0000\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#: Connectors.xml:6
-#, no-c-format
-msgid "Connectors on JBoss"
-msgstr ""
-
-#. Tag: subtitle
-#: Connectors.xml:7
-#, fuzzy, no-c-format
-msgid "The JCA Configuration and Architecture"
-msgstr "JBoss 类加载器架构"
-
-#. Tag: para
-#: Connectors.xml:8
-#, no-c-format
-msgid ""
-"This chapter discusses the JBoss server implementation of the J2EE Connector "
-"Architecture (JCA). JCA is a resource manager integration API whose goal is "
-"to standardize access to non-relational resources in the same way the JDBC "
-"API standardized access to relational data. The purpose of this chapter is "
-"to introduce the utility of the JCA APIs and then describe the architecture "
-"of JCA in JBoss."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:12
-#, fuzzy, no-c-format
-msgid "JCA Overview"
-msgstr "概况（Overview）"
-
-#. Tag: para
-#: Connectors.xml:13
-#, no-c-format
-msgid ""
-"J2EE 1.4 contains a connector architecture (JCA) specification that allows "
-"for the integration of transacted and secure resource adaptors into a J2EE "
-"application server environment. The JCA specification describes the notion "
-"of such resource managers as Enterprise Information Systems (EIS). Examples "
-"of EIS systems include enterprise resource planning packages, mainframe "
-"transaction processing, non-Java legacy applications, etc."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:16
-#, no-c-format
-msgid ""
-"The reason for focusing on EIS is primarily because the notions of "
-"transactions, security, and scalability are requirements in enterprise "
-"software systems. However, the JCA is applicable to any resource that needs "
-"to integrate into JBoss in a secure, scalable and transacted manner. In this "
-"introduction we will focus on resource adapters as a generic notion rather "
-"than something specific to the EIS environment."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:19
-#, no-c-format
-msgid ""
-"The connector architecture defines a standard SPI (Service Provider "
-"Interface) for integrating the transaction, security and connection "
-"management facilities of an application server with those of a resource "
-"manager. The SPI defines the system level contract between the resource "
-"adaptor and the application server."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:22
-#, no-c-format
-msgid ""
-"The connector architecture also defines a Common Client Interface (CCI) for "
-"accessing resources. The CCI is targeted at EIS development tools and other "
-"sophisticated users of integrated resources. The CCI provides a way to "
-"minimize the EIS specific code required by such tools. Typically J2EE "
-"developers will access a resource using such a tool, or a resource specific "
-"interface rather than using CCI directly. The reason is that the CCI is not "
-"a type specific API. To be used effectively it must be used in conjunction "
-"with metadata that describes how to map from the generic CCI API to the "
-"resource manager specific data types used internally by the resource manager."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:25
-#, no-c-format
-msgid ""
-"The purpose of the connector architecture is to enable a resource vendor to "
-"provide a standard adaptor for its product. A resource adaptor is a system-"
-"level software driver that is used by a Java application to connect to "
-"resource. The resource adaptor plugs into an application server and provides "
-"connectivity between the resource manager, the application server, and the "
-"enterprise application. A resource vendor need only implement a JCA "
-"compliant adaptor once to allow use of the resource manager in any JCA "
-"capable application server."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:28
-#, no-c-format
-msgid ""
-"An application server vendor extends its architecture once to support the "
-"connector architecture and is then assured of seamless connectivity to "
-"multiple resource managers. Likewise, a resource manager vendor provides one "
-"standard resource adaptor and it has the capability to plug in to any "
-"application server that supports the connector architecture."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:32
-#, no-c-format
-msgid ""
-"The relationship between a J2EE application server and a JCA resource adaptor"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:39
-#, no-c-format
-msgid ""
-"illustrates that the application server is extended to provide support for "
-"the JCA SPI to allow a resource adaptor to integrate with the server "
-"connection pooling, transaction management and security management "
-"facilities. This integration API defines a three-part system contract."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:44
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Connection management</emphasis>: a contract that "
-"allows the application server to pool resource connections. The purpose of "
-"the pool management is to allow for scalability. Resource connections are "
-"typically expense objects to create and pooling them allows for more "
-"effective reuse and management."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:49
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Transaction Management</emphasis>: a contract that "
-"allows the application server transaction manager to manage transactions "
-"that engage resource managers."
-msgstr ""
-"<emphasis role=\"bold\">TransactionManagerService</emphasis>：JTA 事务管理服"
-"务的 JMX ObjectName。"
-
-#. Tag: para
-#: Connectors.xml:54
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Security Management</emphasis>: a contract that "
-"enables secured access to resource managers."
-msgstr "<emphasis role=\"bold\">Instrumentation</emphasis> 它是所管理的资源"
-
-#. Tag: para
-#: Connectors.xml:59
-#, no-c-format
-msgid ""
-"The resource adaptor implements the resource manager side of the system "
-"contract. This entails using the application server connection pooling, "
-"providing transaction resource information and using the security "
-"integration information. The resource adaptor also exposes the resource "
-"manager to the application server components. This can be done using the CCI "
-"and/or a resource adaptor specific API."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:62
-#, no-c-format
-msgid ""
-"The application component integrates into the application server using a "
-"standard J2EE container to component contract. For an EJB component this "
-"contract is defined by the EJB specification. The application component "
-"interacts with the resource adaptor in the same way as it would with any "
-"other standard resource factory, for example, a <literal>javax.sql."
-"DataSource</literal> JDBC resource factory. The only difference with a JCA "
-"resource adaptor is that the client has the option of using the resource "
-"adaptor independent CCI API if the resource adaptor supports this."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:65
-#, no-c-format
-msgid ""
-"(from the JCA 1.5 specification) illustrates the relationship between the "
-"JCA architecture participants in terms of how they relate to the JCA SPI, "
-"CCI and JTA packages."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:69
-#, no-c-format
-msgid ""
-"The JCA 1.0 specification class diagram for the connection management "
-"architecture."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:76
-#, no-c-format
-msgid ""
-"The JBossCX architecture provides the implementation of the application "
-"server specific classes. <xref linkend=\"JCA_Overview-"
-"The_JCA_1.0_specification_class_diagram_for_the_connection_management_architecture."
-"\"/> shows that this comes down to the implementation of the <literal>javax."
-"resource.spi.ConnectionManager</literal> and <literal>javax.resource.spi."
-"ConnectionEventListener</literal> interfaces. The key aspects of this "
-"implementation are discussed in the following section on the JBossCX "
-"architecture."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:82
-#, fuzzy, no-c-format
-msgid "An Overview of the JBossCX Architecture"
-msgstr "JBossNS 架构"
-
-#. Tag: para
-#: Connectors.xml:83
-#, no-c-format
-msgid ""
-"The JBossCX framework provides the application server architecture extension "
-"required for the use of JCA resource adaptors. This is primarily a "
-"connection pooling and management extension along with a number of MBeans "
-"for loading resource adaptors into the JBoss server."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:86
-#, no-c-format
-msgid ""
-"There are three coupled MBeans that make up a RAR deployment. These are the "
-"<literal>org.jboss.resource.deployment.RARDeployment</literal>, <literal>org."
-"jboss.resource.connectionmanager.RARDeployment</literal>, and <literal>org."
-"jboss.resource.connectionmanager.BaseConnectionManager2</literal>. The "
-"<literal>org.jboss.resource.deployment.RARDeployment</literal> is simply an "
-"encapsulation of the metadata of a RAR <literal>META-INF/ra.xml</literal> "
-"descriptor. It exposes this information as a DynamicMBean simply to make it "
-"available to the <literal>org.jboss.resource.connectionmanager."
-"RARDeployment</literal> MBean."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:89
-#, no-c-format
-msgid ""
-"The RARDeployer service handles the deployment of archives files containing "
-"resource adaptors (RARs). It creates the <literal>org.jboss.resource."
-"deployment.RARDeployment</literal> MBeans when a RAR file is deployed. "
-"Deploying the RAR file is the first step in making the resource adaptor "
-"available to application components. For each deployed RAR, one or more "
-"connection factories must be configured and bound into JNDI. This task "
-"performed using a JBoss service descriptor that sets up a <literal>org.jboss."
-"resource.connectionmanager.BaseConnectionManager2</literal> MBean "
-"implementation with a <literal>org.jboss.resource.connectionmgr."
-"RARDeployment</literal> dependent."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:93
-#, no-c-format
-msgid "BaseConnectionManager2 MBean"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:94
-#, no-c-format
-msgid ""
-"The <literal>org.jboss.resource.connectionmanager.BaseConnectionManager2</"
-"literal> MBean is a base class for the various types of connection managers "
-"required by the JCA spec. Subclasses include <literal>NoTxConnectionManager</"
-"literal>, <literal>LocalTxConnectionManager</literal> and "
-"<literal>XATxConnectionManager</literal>. These correspond to resource "
-"adaptors that support no transactions, local transaction and XA transaction "
-"respectively. You choose which subclass to use based on the type of "
-"transaction semantics you want, provided the JCA resource adaptor supports "
-"the corresponding transaction capability."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:97
-#, no-c-format
-msgid ""
-"The common attributes supported by the BaseConnectionManager2 MBean are:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:102
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ManagedConnectionPool</emphasis>: This specifies the "
-"ObjectName of the MBean representing the pool for this connection manager. "
-"The MBean must have a <literal>ManagedConnectionPool</literal> attribute "
-"that is an implementation of the <literal>org.jboss.resource."
-"connectionmanager.ManagedConnectionPool</literal> interface. Normally it "
-"will be an embedded MBean in a depends tag rather than an "
-"<literal>ObjectName</literal> reference to an existing MBean. The default "
-"MBean for use is the <literal>org.jboss.resource.connectionmanager."
-"JBossManagedConnectionPool</literal>. Its configurable attributes are "
-"discussed below."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:107
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">CachedConnectionManager</emphasis>: This specifies "
-"the <literal>ObjectName</literal> of the <literal>CachedConnectionManager</"
-"literal> MBean implementation used by the connection manager. Normally this "
-"is specified using a depends tag with the <literal>ObjectName</literal> of "
-"the unique <literal>CachedConnectionManager</literal> for the server. The "
-"name <literal>jboss.jca:service=CachedConnectionManager</literal> is the "
-"standard setting to use."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:112
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">SecurityDomainJndiName</emphasis>: This specifies "
-"the JNDI name of the security domain to use for authentication and "
-"authorization of resource connections. This is typically of the form "
-"<literal>java:/jaas/<domain></literal> where the <literal><"
-"domain></literal> value is the name of an entry in the <literal>conf/"
-"login-config.xml</literal> JAAS login module configuration file. This "
-"defines which JAAS login modules execute to perform authentication. <xref "
-"linkend=\"Security_on_JBoss\"/> has more information on the security "
-"settings."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:117
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">JaasSecurityManagerService</emphasis>: This is the "
-"<literal>ObjectName</literal> of the security manager service. This should "
-"be set to the security manager MBean name as defined in the <literal>conf/"
-"jboss-service.xml</literal> descriptor, and currently this is <literal>jboss."
-"security:service=JaasSecurityManager</literal>. This attribute will likely "
-"be removed in the future."
-msgstr ""
-"<emphasis role=\"bold\">InvokerName</emphasis>：<literal>conf/jboss-service."
-"xml</literal> 描述符里定义的 <literal>NamingService</literal> 的 JMX "
-"<literal>ObjectName</literal>。JBoss 发行版本里定义的标准设定是 "
-"<literal>jboss:service=Naming</literal>。"
-
-#. Tag: title
-#: Connectors.xml:125
-#, fuzzy, no-c-format
-msgid "RARDeployment MBean"
-msgstr "The SARDeployer MBean"
-
-#. Tag: para
-#: Connectors.xml:126
-#, no-c-format
-msgid ""
-"The <literal>org.jboss.resource.connectionmanager.RARDeployment</literal> "
-"MBean manages configuration and instantiation "
-"<literal>ManagedConnectionFactory</literal> instance. It does this using the "
-"resource adaptor metadata settings from the RAR <literal>META-INF/ra.xml</"
-"literal> descriptor along with the <literal>RARDeployment</literal> "
-"attributes. The configurable attributes are:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:131
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">OldRarDeployment</emphasis>: This is the "
-"<literal>ObjectName</literal> of the <literal>org.jboss.resource."
-"RarDeployment</literal> MBean that contains the resource adaptor metadata. "
-"The form of this name is <literal>jboss.jca:service=RARDeployment,name=<"
-"ra-display-name></literal> where the <literal><ra-display-name></"
-"literal> is the <literal>ra.xml</literal> descriptor <literal>display-name</"
-"literal> attribute value. The <literal>RARDeployer</literal> creates this "
-"when it deploys a RAR file. This attribute will likely be removed in the "
-"future."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:136
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ManagedConnectionFactoryProperties</emphasis>: This "
-"is a collection of (name, type, value) triples that define attributes of the "
-"<literal>ManagedConnectionFactory</literal> instance. Therefore, the names "
-"of the attributes depend on the resource adaptor "
-"<literal>ManagedConnectionFactory</literal> instance. The following example "
-"shows the structure of the content of this attribute."
-msgstr ""
-
-#. Tag: programlisting
-#: Connectors.xml:139
-#, no-c-format
-msgid ""
-"<properties>\n"
-" <config-property>\n"
-" <config-property-name>Attr0Name</config-property-name>\n"
-" <config-property-type>Attr0Type</config-property-type>\n"
-" <config-property-value>Attr0Value</config-property-"
-"value>\n"
-" </config-property>\n"
-" <config-property>\n"
-" <config-property-name>Attr1Name</config-property-name>\n"
-" <config-property-type>Attr2Type</config-property-type>\n"
-" <config-property-value>Attr2Value</config-property-"
-"value>\n"
-" </config-property> \n"
-" ...\n"
-"</properties>"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:140
-#, no-c-format
-msgid ""
-"<literal>AttrXName</literal> is the Xth attribute name, <literal>AttrXType</"
-"literal> is the fully qualified Java type of the attribute, and "
-"<literal>AttrXValue</literal> is the string representation of the value. The "
-"conversion from string to <literal>AttrXType</literal> is done using the "
-"<literal>java.beans.PropertyEditor</literal> class for the "
-"<literal>AttrXType</literal>."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:145
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">JndiName</emphasis>: This is the JNDI name under "
-"which the resource adaptor will be made available. Clients of the resource "
-"adaptor use this name to obtain either the <literal>javax.resource.cci."
-"ConnectionFactory</literal> or resource adaptor specific connection factory. "
-"The full JNDI name will be <literal>java:/<JndiName></literal> meaning "
-"that the <literal>JndiName</literal> attribute value will be prefixed with "
-"<literal>java:/</literal>. This prevents use of the connection factory "
-"outside of the JBoss server VM. In the future this restriction may be "
-"configurable."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:153
-#, no-c-format
-msgid "JBossManagedConnectionPool MBean"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:154
-#, no-c-format
-msgid ""
-"The <literal>org.jboss.resource.connectionmanager."
-"JBossManagedConnectionPool</literal> MBean is a connection pooling MBean. It "
-"is typically used as the embedded MBean value of the "
-"<literal>BaseConnectionManager2</literal><literal>ManagedConnectionPool</"
-"literal> attribute. When you setup a connection manager MBean you typically "
-"embed the pool configuration in the connection manager descriptor. The "
-"configurable attributes of the <literal>JBossManagedConnectionPool</literal> "
-"are:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:159
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ManagedConnectionFactoryName</emphasis>: This "
-"specifies the <literal>ObjectName</literal> of the MBean that creates "
-"<literal>javax.resource.spi.ManagedConnectionFactory</literal> instances. "
-"Normally this is configured as an embedded MBean in a depends element rather "
-"than a separate MBean reference using the <literal>RARDeployment</literal> "
-"MBean. The MBean must provide an appropriate "
-"<literal>startManagedConnectionFactory</literal> operation."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:164
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">MinSize</emphasis>: This attribute indicates the "
-"minimum number of connections this pool should hold. These are not created "
-"until a <literal>Subject</literal> is known from a request for a connection. "
-"<literal>MinSize</literal> connections will be created for each sub-pool."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:169
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">MaxSize</emphasis>: This attribute indicates the "
-"maximum number of connections for a pool. No more than MaxSize connections "
-"will be created in each sub-pool."
-msgstr ""
-"<emphasis role=\"bold\">timeout</emphasis> 指定对 are-you-alive 信息的应答的"
-"最长等待时间（毫秒数）。"
-
-#. Tag: para
-#: Connectors.xml:174
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">BlockingTimeoutMillis</emphasis>: This attribute "
-"indicates the maximum time to block while waiting for a connection before "
-"throwing an exception. Note that this blocks only while waiting for a permit "
-"for a connection, and will never throw an exception if creating a new "
-"connection takes an inordinately long time."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:179
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">IdleTiemoutMinutes</emphasis>: This attribute "
-"indicates the maximum time a connection may be idle before being closed. The "
-"actual maximum time depends also on the idle remover thread scan time, which "
-"is 1/2 the smallest idle timeout of any pool."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:184
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">NoTxSeparatePools</emphasis>: Setting this to true "
-"doubles the available pools. One pool is for connections used outside a "
-"transaction the other inside a transaction. The actual pools are lazily "
-"constructed on first use. This is only relevant when setting the pool "
-"parameters associated with the <literal>LocalTxConnectionManager</literal> "
-"and <literal>XATxConnectionManager</literal>. Its use case is for Oracle "
-"(and possibly other vendors) XA implementations that don't like using an "
-"XA connection with and without a JTA transaction."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:189
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Criteria</emphasis>: This attribute indicates if the "
-"JAAS <literal>javax.security.auth.Subject</literal> from security domain "
-"associated with the connection, or app supplied parameters (such as from "
-"<literal>getConnection(user, pw)</literal>) are used to distinguish "
-"connections in the pool. The allowed values are:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:194
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ByContainer</emphasis>: use <literal>Subject</"
-"literal>"
-msgstr "<emphasis role=\"strong\">例如：</emphasis><literal>prefix</literal>"
-
-#. Tag: para
-#: Connectors.xml:199
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ByApplication</emphasis>: use application supplied "
-"parameters only"
-msgstr "<emphasis role=\"bold\">description</emphasis>：参数的可选描述。"
-
-#. Tag: para
-#: Connectors.xml:204
-#, fuzzy, no-c-format
-msgid "<emphasis role=\"bold\">ByContainerAndApplication</emphasis>: use both"
-msgstr "<emphasis role=\"bold\">jboss-aop.deployer</emphasis>,"
-
-#. Tag: para
-#: Connectors.xml:209
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ByNothing</emphasis>: all connections are "
-"equivalent, usually if adapter supports reauthentication"
-msgstr "<emphasis role=\"bold\">name</emphasis>：这个元素包含通知类的类全名。"
-
-#. Tag: title
-#: Connectors.xml:219
-#, no-c-format
-msgid "CachedConnectionManager MBean"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:220
-#, no-c-format
-msgid ""
-"The <literal>org.jboss.resource.connectionmanager.CachedConnectionManager</"
-"literal> MBean manages associations between meta-aware objects (those "
-"accessed through interceptor chains) and connection handles, as well as "
-"between user transactions and connection handles. Normally there should only "
-"be one such MBean, and this is configured in the core <literal>jboss-service."
-"xml</literal> descriptor. It is used by "
-"<literal>CachedConnectionInterceptor</literal>, JTA "
-"<literal>UserTransaction</literal> implementation and all "
-"<literal>BaseConnectionManager2</literal> instances. The configurable "
-"attributes of the <literal>CachedConnectionManager</literal> MBean are:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:225
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">SpecCompliant</emphasis>: Enable this boolean "
-"attribute for spec compliant non-shareable connections reconnect processing. "
-"This allows a connection to be opened in one call and used in another. Note "
-"that specifying this behavior disables connection close processing."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:230
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Debug</emphasis>: Enable this boolean property for "
-"connection close processing. At the completion of an EJB method invocation, "
-"unclosed connections are registered with a transaction synchronization. If "
-"the transaction ends without the connection being closed, an error is "
-"reported and JBoss closes the connection. This is a development feature that "
-"should be turned off in production for optimal performance."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:235
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">TransactionManagerServiceName</emphasis>: This "
-"attribute specifies the JMX <literal>ObjectName</literal> of the JTA "
-"transaction manager service. Connection close processing is now synchronized "
-"with the transaction manager and this attribute specifies the transaction "
-"manager to use."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:243
-#, no-c-format
-msgid "A Sample Skeleton JCA Resource Adaptor"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:244
-#, no-c-format
-msgid ""
-"To conclude our discussion of the JBoss JCA framework we will create and "
-"deploy a single non-transacted resource adaptor that simply provides a "
-"skeleton implementation that stubs out the required interfaces and logs all "
-"method calls. We will not discuss the details of the requirements of a "
-"resource adaptor provider as these are discussed in detail in the JCA "
-"specification. The purpose of the adaptor is to demonstrate the steps "
-"required to create and deploy a RAR in JBoss, and to see how JBoss interacts "
-"with the adaptor."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:247
-#, no-c-format
-msgid ""
-"The adaptor we will create could be used as the starting point for a non-"
-"transacted file system adaptor. The source to the example adaptor can be "
-"found in the <literal>src/main/org/jboss/chap7/ex1</literal> directory of "
-"the book examples. A class diagram that shows the mapping from the required "
-"<literal>javax.resource.spi</literal> interfaces to the resource adaptor "
-"implementation is given in <xref linkend="
-"\"A_Sample_Skeleton_JCA_Resource_Adaptor-The_file_system_RAR_class_diagram\"/"
-">."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:251
-#, no-c-format
-msgid "The file system RAR class diagram"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:258
-#, no-c-format
-msgid ""
-"We will build the adaptor, deploy it to the JBoss server and then run an "
-"example client against an EJB that uses the resource adaptor to demonstrate "
-"the basic steps in a complete context. We'll then take a look at the "
-"JBoss server log to see how the JBoss JCA framework interacts with the "
-"resource adaptor to help you better understand the components in the JCA "
-"system level contract."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:261
-#, no-c-format
-msgid ""
-"To build the example and deploy the RAR to the JBoss server <literal>deploy/"
-"lib</literal> directory, execute the following Ant command in the book "
-"examples directory."
-msgstr ""
-
-#. Tag: programlisting
-#: Connectors.xml:264
-#, fuzzy, no-c-format
-msgid "[examples]$ ant -Dchap=chap7 build-chap"
-msgstr "[examples]$ ant -Dchap=chap2 -Dex=3 run-example"
-
-#. Tag: para
-#: Connectors.xml:265
-#, no-c-format
-msgid ""
-"The deployed files include a <literal>chap7-ex1.sar</literal> and a "
-"<literal>notxfs-service.xml</literal> service descriptor. The example "
-"resource adaptor deployment descriptor is shown in <xref linkend="
-"\"A_Sample_Skeleton_JCA_Resource_Adaptor-"
-"The_nontransactional_file_system_resource_adaptor_deployment_descriptor.\"/>."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:268
-#, no-c-format
-msgid ""
-"The nontransactional file system resource adaptor deployment descriptor."
-msgstr ""
-
-#. Tag: programlisting
-#: Connectors.xml:269
-#, no-c-format
-msgid ""
-"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
-"<connector xmlns=\"http://java.sun.com/xml/ns/\"Whats_new_in_JBoss_4-"
-"J2EE_Certification_and_Standards_Compliance\"\n"
-" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
-" xsi:schemaLocation=\"http://java.sun.com/xml/ns/j2ee \n"
-" http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd\" "
-"version=\"1.5\">\n"
-" <display-name>File System Adapter</display-name>\n"
-" <vendor-name>JBoss</vendor-name>\n"
-" <eis-type>FileSystem</eis-type>\n"
-" <resourceadapter-version>1.0</resourceadapter-version>\n"
-" <license>\n"
-" <description>LGPL</description>\n"
-" <license-required>false</license-required>\n"
-" </license>\n"
-" <resourceadapter>\n"
-" <resourceadapter-class>\n"
-" org.jboss.resource.deployment.DummyResourceAdapter\n"
-" </resourceadapter-class>\n"
-" <outbound-resourceadapter>\n"
-" <connection-definition>\n"
-" <emphasis role=\"bold\"><managedconnectionfactory-"
-"class> org.jboss.chap7.ex1.ra.FSManagedConnectionFactory </"
-"managedconnectionfactory-class></emphasis>\n"
-" <config-property>\n"
-" <config-property-name>FileSystemRootDir</config-"
-"property-name>\n"
-" <config-property-type>java.lang.String</config-"
-"property-type>\n"
-" <config-property-value>/tmp/db/fs_store</config-"
-"property-value>\n"
-" </config-property>\n"
-" <config-property>\n"
-" <config-property-name>UserName</config-property-"
-"name>\n"
-" <config-property-type>java.lang.String</config-"
-"property-type>\n"
-" <config-property-value/>\n"
-" </config-property>\n"
-" <config-property>\n"
-" <config-property-name>Password</config-property-"
-"name>\n"
-" <config-property-type>java.lang.String</config-"
-"property-type>\n"
-" <config-property-value/>\n"
-" </config-property>\n"
-" <emphasis role=\"bold\"><connectionfactory-interface> "
-"org.jboss.chap7.ex1.ra.DirContextFactory </connectionfactory-"
-"interface> <connectionfactory-impl-class> org.jboss.chap7.ex1.ra."
-"DirContextFactoryImpl </connectionfactory-impl-class> <connection-"
-"interface> javax.naming.directory.DirContext </connection-"
-"interface> <connection-impl-class> org.jboss.chap7.ex1.ra."
-"FSDirContext </connection-impl-class></emphasis>\n"
-" </connection-definition>\n"
-" <transaction-support>NoTransaction</transaction-"
-"support>\n"
-" <authentication-mechanism>\n"
-" <authentication-mechanism-type>BasicPassword</"
-"authentication-mechanism-type>\n"
-" <credential-interface>\n"
-" javax.resource.spi.security.PasswordCredential\n"
-" </credential-interface>\n"
-" </authentication-mechanism>\n"
-" <emphasis role=\"bold\"><reauthentication-support>true</"
-"reauthentication-support></emphasis>\n"
-" </outbound-resourceadapter>\n"
-" <security-permission>\n"
-" <description> Read/Write access is required to the "
-"contents of the\n"
-" FileSystemRootDir </description>\n"
-" <security-permission-spec> permission java.io."
-"FilePermission\n"
-" \"/tmp/db/fs_store/*\", \"read,write\"; \n"
-" </security-permission-spec>\n"
-" </security-permission>\n"
-" </resourceadapter>\n"
-"</connector>"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:270
-#, no-c-format
-msgid ""
-"The key items in the resource adaptor deployment descriptor are highlighted "
-"in bold. These define the classes of the resource adaptor, and the elements "
-"are:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:275
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">managedconnectionfactory-class</emphasis>: The "
-"implementation of the <literal>ManagedConnectionFactory</literal> interface, "
-"<literal>org.jboss.chap7.ex1.ra.FSManagedConnectionFactory</literal>"
-msgstr ""
-"<emphasis role=\"bold\">java.naming.factory.initial</emphasis>：指定初始上下"
-"文工厂(initial context factory)的环境属性名，它必须是 <literal>org.jboss."
-"naming.HttpNamingContextFactory</literal>。"
-
-#. Tag: para
-#: Connectors.xml:280
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">connectionfactory-interface</emphasis>: This is the "
-"interface that clients will obtain when they lookup the connection factory "
-"instance from JNDI, here a proprietary resource adaptor value, <literal>org."
-"jboss.chap7.ex1.ra.DirContextFactory</literal>. This value will be needed "
-"when we create the JBoss <literal>ds.xml</literal> to use the resource."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:285
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">connectionfactory-impl-class</emphasis>: This is the "
-"class that provides the implementation of the <literal>connectionfactory-"
-"interface</literal>, <literal>org.jboss.chap7.ex1.ra.DirContextFactoryImpl</"
-"literal>."
-msgstr ""
-"<emphasis role=\"bold\">java.naming.factory.initial</emphasis>：指定初始上下"
-"文工厂(initial context factory)的环境属性名，它必须是 <literal>org.jboss."
-"naming.HttpNamingContextFactory</literal>。"
-
-#. Tag: para
-#: Connectors.xml:290
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">connection-interface</emphasis>: This is the "
-"interface for the connections returned by the resource adaptor connection "
-"factory, here the JNDI <literal>javax.naming.directory.DirContext</literal> "
-"interface."
-msgstr ""
-"<emphasis role=\"bold\">java.naming.factory.initial</emphasis>：指定初始上下"
-"文工厂(initial context factory)的环境属性名，它必须是 <literal>org.jboss."
-"naming.HttpNamingContextFactory</literal>。"
-
-#. Tag: para
-#: Connectors.xml:295
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">connection-impl-class</emphasis>: This is he class "
-"that provides the <literal>connection-interface</literal> implementation, "
-"<literal>org.jboss.chap7.ex1.ra.FSDirContext</literal>."
-msgstr ""
-"<emphasis role=\"bold\">className</emphasis>：这是 <literal>org.apache."
-"catalina.Engine</literal> 接口实现的类的全名。它的缺省值是 <literal>org."
-"apache.catalina.core.StandardEngine</literal>。"
-
-#. Tag: para
-#: Connectors.xml:300
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">transaction-support</emphasis>: The level of "
-"transaction support, here defined as <literal>NoTransaction</literal>, "
-"meaning the file system resource adaptor does not do transactional work."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:305
-#, no-c-format
-msgid ""
-"The RAR classes and deployment descriptor only define a resource adaptor. To "
-"use the resource adaptor it must be integrated into the JBoss application "
-"server using a <literal>ds.xml</literal> descriptor file. An example of this "
-"for the file system adaptor is shown in <xref linkend="
-"\"A_Sample_Skeleton_JCA_Resource_Adaptor-The_notxfs_ds."
-"xml_resource_adaptor_MBeans_service_descriptor.\"/>."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:308
-#, no-c-format
-msgid "The notxfs-ds.xml resource adaptor MBeans service descriptor."
-msgstr ""
-
-#. Tag: programlisting
-#: Connectors.xml:309
-#, no-c-format
-msgid ""
-"<!DOCTYPE connection-factories PUBLIC\n"
-" \"-//JBoss//DTD JBOSS JCA Config 1.5//EN\"\n"
-" \"http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd\">\n"
-"<!-- \n"
-" The non-transaction FileSystem resource adaptor service "
-"configuration\n"
-"-->\n"
-"<connection-factories>\n"
-" <no-tx-connection-factory>\n"
-" <jndi-name>NoTransFS</jndi-name>\n"
-" <rar-name>chap7-ex1.rar</rar-name>\n"
-" <connection-definition>\n"
-" org.jboss.chap7.ex1.ra.DirContextFactory\n"
-" </connection-definition>\n"
-" <config-property name=\"FileSystemRootDir\"\n"
-" type=\"java.lang.String\">/tmp/db/fs_store</"
-"config-property>\n"
-" </no-tx-connection-factory>\n"
-"</connection-factories>"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:310
-#, fuzzy, no-c-format
-msgid "The main attributes are:"
-msgstr "The Attributes"
-
-#. Tag: para
-#: Connectors.xml:315
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">jndi-name</emphasis>: This specifies where the "
-"connection factory will be bound into JNDI. For this deployment that binding "
-"will be <literal>java:/NoTransFS</literal>."
-msgstr ""
-"<emphasis role=\"bold\">PartitionName</emphasis> 指定了部署这个 farm 的群集的"
-"名字。它的缺省值是 <literal>DefaultPartition</literal>。"
-
-#. Tag: para
-#: Connectors.xml:320
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">rar-name</emphasis>: This is the name of the RAR "
-"file that contains the definition for the resource we want to provide. For "
-"nested RAR files, the name would look like <literal>myapplication.ear#my."
-"rar</literal>. In this example, it is simply <literal>chap7-ex1.rar</"
-"literal>."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:325
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">connection-definition</emphasis>: This is the "
-"connection factory interface class. It should match the "
-"<literal>connectionfactory-interface</literal> in the <literal>ra.xml</"
-"literal> file. Here our connection factory interface is <literal>org.jboss."
-"chap7.ex1.ra.DirContextFactory</literal>."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:330
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">config-property</emphasis>: This can be used to "
-"provide non-default settings to the resource adaptor connection factory. "
-"Here the <literal>FileSystemRootDir</literal> is being set to <literal>/tmp/"
-"db/fs_store</literal>. This overrides the default value in the <literal>ra."
-"xml</literal> file."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:335
-#, no-c-format
-msgid ""
-"To deploy the RAR and connection manager configuration to the JBoss server, "
-"run the following:"
-msgstr ""
-
-#. Tag: programlisting
-#: Connectors.xml:338
-#, fuzzy, no-c-format
-msgid "[examples]$ ant -Dchap=chap7 config"
-msgstr "[examples]$ ant -Dchap=naming config"
-
-#. Tag: para
-#: Connectors.xml:339
-#, no-c-format
-msgid ""
-"The server console will display some logging output indicating that the "
-"resource adaptor has been deployed."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:342
-#, no-c-format
-msgid ""
-"Now we want to test access of the resource adaptor by a J2EE component. To "
-"do this we have created a trivial stateless session bean that has a single "
-"method called <literal>echo</literal>. Inside of the <literal>echo</literal> "
-"method the EJB accesses the resource adaptor connection factory, creates a "
-"connection, and then immediately closes the connection. The <literal>echo</"
-"literal> method code is shown below."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:345
-#, no-c-format
-msgid ""
-"The stateless session bean echo method code that shows the access of the "
-"resource adaptor connection factory."
-msgstr ""
-
-#. Tag: programlisting
-#: Connectors.xml:346
-#, no-c-format
-msgid ""
-"public String echo(String arg)\n"
-"{\n"
-" log.info(\"echo, arg=\"+arg);\n"
-" try {\n"
-" InitialContext ctx = new InitialContext();\n"
-" Object ref = ctx.lookup(\"java:comp/env/ra/DirContextFactory"
-"\");\n"
-" log.info(\"echo, ra/DirContextFactory=\" + ref);\n"
-"\n"
-" DirContextFactory dcf = (DirContextFactory) ref;\n"
-" log.info(\"echo, found dcf=\" + dcf);\n"
-"\n"
-" DirContext dc = dcf.getConnection();\n"
-" log.info(\"echo, lookup dc=\" + dc);\n"
-"\n"
-" dc.close();\n"
-" } catch(NamingException e) {\n"
-" log.error(\"Failed during JNDI access\", e);\n"
-" }\n"
-" return arg;\n"
-"}"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:347
-#, no-c-format
-msgid ""
-"The EJB is not using the CCI interface to access the resource adaptor. "
-"Rather, it is using the resource adaptor specific API based on the "
-"proprietary <literal>DirContextFactory</literal> interface that returns a "
-"JNDI <literal>DirContext</literal> object as the connection object. The "
-"example EJB is simply exercising the system contract layer by looking up the "
-"resource adaptor connection factory, creating a connection to the resource "
-"and closing the connection. The EJB does not actually do anything with the "
-"connection, as this would only exercise the resource adaptor implementation "
-"since this is a non-transactional resource."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:350
-#, no-c-format
-msgid ""
-"Run the test client which calls the <literal>EchoBean.echo</literal> method "
-"by running Ant as follows from the examples directory:"
-msgstr ""
-
-#. Tag: programlisting
-#: Connectors.xml:353
-#, fuzzy, no-c-format
-msgid "[examples]$ ant -Dchap=chap7 -Dex=1 run-example"
-msgstr "[examples]$ ant -Dchap=chap2 -Dex=3 run-example"
-
-#. Tag: para
-#: Connectors.xml:354
-#, no-c-format
-msgid ""
-"You'll see some output from the bean in the system console, but much "
-"more detailed logging output can be found in the <literal>server/default/log/"
-"server.log</literal> file. Don't worry if you see exceptions. They are "
-"just stack traces to highlight the call path into parts of the adaptor. To "
-"help understand the interaction between the adaptor and the JBoss JCA layer, "
-"we'll summarize the events seen in the log using a sequence diagram. "
-"<xref linkend=\"A_Sample_Skeleton_JCA_Resource_Adaptor-"
-"A_sequence_diagram_illustrating_the_key_interactions_between_the_JBossCX_framework_and_the_example_resource_adaptor_that_result_when_the_EchoBean_accesses_the_resource_adaptor_connection_factory."
-"\"/> is a sequence diagram that summarizes the events that occur when the "
-"<literal>EchoBean</literal> accesses the resource adaptor connection factory "
-"from JNDI and creates a connection."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:358
-#, no-c-format
-msgid ""
-"A sequence diagram illustrating the key interactions between the JBossCX "
-"framework and the example resource adaptor that result when the EchoBean "
-"accesses the resource adaptor connection factory."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:365
-#, no-c-format
-msgid ""
-"The starting point is the client's invocation of the <literal>EchoBean."
-"echo</literal> method. For the sake of conciseness of the diagram, the "
-"client is shown directly invoking the EchoBean.echo method when in reality "
-"the JBoss EJB container handles the invocation. There are three distinct "
-"interactions between the <literal>EchoBean</literal> and the resource "
-"adaptor; the lookup of the connection factory, the creation of a connection, "
-"and the close of the connection."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:368
-#, no-c-format
-msgid ""
-"The lookup of the resource adaptor connection factory is illustrated by the "
-"1.1 sequences of events. The events are:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:373
-#, no-c-format
-msgid ""
-"1, the echo method invokes the <literal>getConnection</literal> method on "
-"the resource adaptor connection factory obtained from the JNDI lookup on the "
-"<literal>java:comp/env/ra/DirContextFactory</literal> name which is a link "
-"to the <literal>java:/NoTransFS</literal> location."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:378
-#, no-c-format
-msgid ""
-"1.1, the <literal>DirContextFactoryImpl</literal> class asks its associated "
-"<literal>ConnectionManager</literal> to allocate a connection. It passes in "
-"the <literal>ManagedConnectionFactory</literal> and <literal>FSRequestInfo</"
-"literal> that were associated with the <literal>DirContextFactoryImpl</"
-"literal> during its construction."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:383
-#, no-c-format
-msgid ""
-"1.1.1, the <literal>ConnectionManager</literal> invokes its "
-"<literal>getManagedConnection</literal> method with the current "
-"<literal>Subject</literal> and <literal>FSRequestInfo</literal>."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:388
-#, no-c-format
-msgid ""
-"1.1.1.1, the <literal>ConnectionManager</literal> asks its object pool for a "
-"connection object. The <literal>JBossManagedConnectionPool$BasePool</"
-"literal> is get the key for the connection and then asks the matching "
-"<literal>InternalPool</literal> for a connection."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:393
-#, no-c-format
-msgid ""
-"1.1.1.1.1, Since no connections have been created the pool must create a new "
-"connection. This is done by requesting a new managed connection from the "
-"<literal>ManagedConnectionFactory</literal>. The <literal>Subject</literal> "
-"associated with the pool as well as the <literal>FSRequestInfo</literal> "
-"data are passed as arguments to the <literal>createManagedConnection</"
-"literal> method invocation."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:398
-#, no-c-format
-msgid ""
-"1.1.1.1.1.1, the <literal>ConnectionFactory</literal> creates a new "
-"<literal>FSManagedConnection</literal> instance and passes in the "
-"<literal>Subject</literal> and <literal>FSRequestInfo</literal> data."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:403
-#, no-c-format
-msgid ""
-"1.1.1.2, a <literal>javax.resource.spi.ConnectionListener</literal> instance "
-"is created. The type of listener created is based on the type of "
-"<literal>ConnectionManager</literal>. In this case it is an <literal>org."
-"jboss.resource.connectionmgr.BaseConnectionManager2$NoTransactionListener</"
-"literal> instance."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:408
-#, no-c-format
-msgid ""
-"1.1.1.2.1, the listener registers as a <literal>javax.resource.spi."
-"ConnectionEventListener</literal> with the <literal>ManagedConnection</"
-"literal> instance created in 1.2.1.1."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:413
-#, no-c-format
-msgid ""
-"1.1.2, the <literal>ManagedConnection</literal> is asked for the underlying "
-"resource manager connection. The <literal>Subject</literal> and "
-"<literal>FSRequestInfo</literal> data are passed as arguments to the "
-"<literal>getConnection</literal> method invocation."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:418
-#, no-c-format
-msgid ""
-"The resulting connection object is cast to a <literal>javax.naming.directory."
-"DirContext</literal> instance since this is the public interface defined by "
-"the resource adaptor."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:423
-#, no-c-format
-msgid ""
-"After the <literal>EchoBean</literal> has obtained the <literal>DirContext</"
-"literal> for the resource adaptor, it simply closes the connection to "
-"indicate its interaction with the resource manager is complete."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:428
-#, no-c-format
-msgid ""
-"This concludes the resource adaptor example. Our investigation into the "
-"interaction between the JBossCX layer and a trivial resource adaptor should "
-"give you sufficient understanding of the steps required to configure any "
-"resource adaptor. The example adaptor can also serve as a starting point for "
-"the creation of your own custom resource adaptors if you need to integrate "
-"non-JDBC resources into the JBoss server environment."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:436
-#, fuzzy, no-c-format
-msgid "Configuring JDBC DataSources"
-msgstr "配置 JBoss"
-
-#. Tag: para
-#: Connectors.xml:437
-#, no-c-format
-msgid ""
-"Rather than configuring the connection manager factory related MBeans "
-"discussed in the previous section via a mbean services deployment "
-"descriptor, JBoss provides a simplified datasource centric descriptor. This "
-"is transformed into the standard <literal>jboss-service.xml</literal> MBean "
-"services deployment descriptor using a XSL transform applied by the "
-"<literal>org.jboss.deployment.XSLSubDeployer</literal> included in the "
-"<literal>jboss-jca.sar</literal> deployment. The simplified configuration "
-"descriptor is deployed the same as other deployable components. The "
-"descriptor must be named using a <literal>*-ds.xml</literal> pattern in "
-"order to be recognized by the <literal>XSLSubDeployer</literal>."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:440
-#, no-c-format
-msgid ""
-"The schema for the top-level datasource elements of the <literal>*-ds.xml</"
-"literal> configuration deployment file is shown in <xref linkend="
-"\"Configuring_JDBC_DataSources-"
-"The_simplified_JCA_DataSource_configuration_descriptor_top_level_schema_elements"
-"\"/>."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:444
-#, no-c-format
-msgid ""
-"The simplified JCA DataSource configuration descriptor top-level schema "
-"elements"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:451
-#, no-c-format
-msgid ""
-"Multiple datasource configurations may be specified in a configuration "
-"deployment file. The child elements of the datasources root are:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:456
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mbean</emphasis>: Any number mbean elements may be "
-"specified to define MBean services that should be included in the "
-"<literal>jboss-service.xml</literal> descriptor that results from the "
-"transformation. This may be used to configure services used by the "
-"datasources."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:461
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">no-tx-datasource</emphasis>: This element is used to "
-"specify the (<literal>org.jboss.resource.connectionmanager</literal>) "
-"<literal>NoTxConnectionManager</literal> service configuration. "
-"<literal>NoTxConnectionManager</literal> is a JCA connection manager with no "
-"transaction support. The <literal>no-tx-datasource</literal> child element "
-"schema is given in <xref linkend=\"Configuring_JDBC_DataSources-"
-"The_non_transactional_DataSource_configuration_schema\"/>."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:466
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">local-tx-datasource</emphasis>: This element is used "
-"to specify the (<literal>org.jboss.resource.connectionmanager</literal>) "
-"<literal>LocalTxConnectionManager</literal> service configuration. "
-"<literal>LocalTxConnectionManager</literal> implements a "
-"<literal>ConnectionEventListener</literal> that implements "
-"<literal>XAResource</literal> to manage transactions through the transaction "
-"manager. To ensure that all work in a local transaction occurs over the same "
-"<literal>ManagedConnection</literal>, it includes a xid to "
-"<literal>ManagedConnection</literal> map. When a Connection is requested or "
-"a transaction started with a connection handle in use, it checks to see if a "
-"<literal>ManagedConnection</literal> already exists enrolled in the global "
-"transaction and uses it if found. Otherwise, a free "
-"<literal>ManagedConnection</literal> has its <literal>LocalTransaction</"
-"literal> started and is used. The <literal>local-tx-datasource</literal> "
-"child element schema is given in"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:471
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">xa-datasource</emphasis>: This element is used to "
-"specify the (<literal>org.jboss.resource.connectionmanager</literal>) "
-"<literal>XATxConnectionManager</literal> service configuration. "
-"<literal>XATxConnectionManager</literal> implements a "
-"<literal>ConnectionEventListener</literal> that obtains the "
-"<literal>XAResource</literal> to manage transactions through the transaction "
-"manager from the adaptor <literal>ManagedConnection</literal>. To ensure "
-"that all work in a local transaction occurs over the same "
-"<literal>ManagedConnection</literal>, it includes a xid to "
-"<literal>ManagedConnection</literal> map. When a <literal>Connection</"
-"literal> is requested or a transaction started with a connection handle in "
-"use, it checks to see if a <literal>ManagedConnection</literal> already "
-"exists enrolled in the global transaction and uses it if found. Otherwise, a "
-"free <literal>ManagedConnection</literal> has its <literal>LocalTransaction</"
-"literal> started and is used. The <literal>xa-datasource</literal> child "
-"element schema is given in <xref linkend=\"Configuring_JDBC_DataSources-"
-"The_XA_DataSource_configuration_schema\"/>."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:476
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ha-local-tx-datasource</emphasis>: This element is "
-"identical to <literal>local-tx-datasource</literal>, with the addition of "
-"the experimental datasource failover capability allowing JBoss to failover "
-"to an alternate database in the event of a database failure."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:481
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ha-xa-datasource</emphasis>: This element is "
-"identical to <literal>xa-datasource</literal>, with the addition of the "
-"experimental datasource failover capability allowing JBoss to failover to an "
-"alternate database in the event of a database failure."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:487
-#, fuzzy, no-c-format
-msgid "The non-transactional DataSource configuration schema"
-msgstr "事务策略配置"
-
-#. Tag: title
-#: Connectors.xml:495
-#, fuzzy, no-c-format
-msgid "The non-XA DataSource configuration schema"
-msgstr "The JBoss AS installer configuration sets"
-
-#. Tag: title
-#: Connectors.xml:503
-#, fuzzy, no-c-format
-msgid "The XA DataSource configuration schema"
-msgstr "The JBoss AS installer configuration sets"
-
-#. Tag: title
-#: Connectors.xml:511
-#, no-c-format
-msgid "The schema for the experimental non-XA DataSource with failover"
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:519
-#, no-c-format
-msgid "The schema for the experimental XA Datasource with failover"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:526
-#, no-c-format
-msgid "Elements that are common to all datasources include:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:531
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">jndi-name</emphasis>: The JNDI name under which the "
-"<literal>DataSource</literal> wrapper will be bound. Note that this name is "
-"relative to the <literal>java:/</literal> context, unless <literal>use-java-"
-"context</literal> is set to false. <literal>DataSource</literal> wrappers "
-"are not usable outside of the server VM, so they are normally bound under "
-"the <literal>java:/</literal>, which isn't shared outside the local VM."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:536
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">use-java-context</emphasis>: If this is set to false "
-"the the datasource will be bound in the global JNDI context rather than the "
-"<literal>java:</literal> context."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:541
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">user-name</emphasis>: This element specifies the "
-"default username used when creating a new connection. The actual username "
-"may be overridden by the application code <literal>getConnection</literal> "
-"parameters or the connection creation context JAAS Subject."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:546
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">password</emphasis>: This element specifies the "
-"default password used when creating a new connection. The actual password "
-"may be overridden by the application code <literal>getConnection</literal> "
-"parameters or the connection creation context JAAS Subject."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:551
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">application-managed-security</emphasis>: Specifying "
-"this element indicates that connections in the pool should be distinguished "
-"by application code supplied parameters, such as from <literal>getConnection"
-"(user, pw)</literal>."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:556
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">security-domain</emphasis>: Specifying this element "
-"indicates that connections in the pool should be distinguished by JAAS "
-"Subject based information. The content of the <literal>security-domain</"
-"literal> is the name of the JAAS security manager that will handle "
-"authentication. This name correlates to the JAAS <literal>login-config.xml</"
-"literal> descriptor <literal>application-policy/name</literal> attribute."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:561
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">security-domain-and-application</emphasis>: "
-"Specifying this element indicates that connections in the pool should be "
-"distinguished both by application code supplied parameters and JAAS Subject "
-"based information. The content of the <literal>security-domain</literal> is "
-"the name of the JAAS security manager that will handle authentication. This "
-"name correlates to the JAAS <literal>login-config.xml</literal> descriptor "
-"<literal>application-policy/name</literal> attribute."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:566
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">min-pool-size</emphasis>: This element specifies the "
-"minimum number of connections a pool should hold. These pool instances are "
-"not created until an initial request for a connection is made. This default "
-"to 0."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:571
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">max-pool-size</emphasis>: This element specifies the "
-"maximum number of connections for a pool. No more than the <literal>max-pool-"
-"size</literal> number of connections will be created in a pool. This "
-"defaults to 20."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:576
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">blocking-timeout-millis</emphasis>: This element "
-"specifies the maximum time in milliseconds to block while waiting for a "
-"connection before throwing an exception. Note that this blocks only while "
-"waiting for a permit for a connection, and will never throw an exception if "
-"creating a new connection takes an inordinately long time. The default is "
-"5000."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:581
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">idle-timeout-minutes</emphasis>: This element "
-"specifies the maximum time in minutes a connection may be idle before being "
-"closed. The actual maximum time depends also on the <literal>IdleRemover</"
-"literal> scan time, which is 1/2 the smallest idle-timeout-minutes of any "
-"pool."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:586
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">new-connection-sql</emphasis>: This is a SQL "
-"statement that should be executed when a new connection is created. This can "
-"be used to configure a connection with database specific settings not "
-"configurable via connection properties."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:591
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">check-valid-connection-sql</emphasis>: This is a SQL "
-"statement that should be run on a connection before it is returned from the "
-"pool to test its validity to test for stale pool connections. An example "
-"statement could be: <literal>select count(*) from x</literal>."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:596
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">exception-sorter-class-name</emphasis>: This "
-"specifies a class that implements the <literal>org.jboss.resource.adapter."
-"jdbc.ExceptionSorter</literal> interface to examine database exceptions to "
-"determine whether or not the exception indicates a connection error. Current "
-"implementations include:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:601
-#, no-c-format
-msgid "org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:606
-#, no-c-format
-msgid "org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:611
-#, no-c-format
-msgid "org.jboss.resource.adapter.jdbc.vendor.SybaseExceptionSorter"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:616
-#, no-c-format
-msgid "org.jboss.resource.adapter.jdbc.vendor.InformixExceptionSorte"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:623
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">valid-connection-checker-class-name</emphasis>: This "
-"specifies a class that implements the <literal>org.jboss.resource.adapter."
-"jdbc.ValidConnectionChecker</literal> interface to provide a "
-"<literal>SQLException isValidConnection(Connection e)</literal> method that "
-"is called with a connection that is to be returned from the pool to test its "
-"validity. This overrides the <literal>check-valid-connection-sql</literal> "
-"when present. The only provided implementation is <literal>org.jboss."
-"resource.adapter.jdbc.vendor.OracleValidConnectionChecker</literal>."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:628
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">track-statements</emphasis>: This boolean element "
-"specifies whether to check for unclosed statements when a connection is "
-"returned to the pool. If true, a warning message is issued for each unclosed "
-"statement. If the log4j category <literal>org.jboss.resource.adapter.jdbc."
-"WrappedConnection</literal> has trace level enabled, a stack trace of the "
-"connection close call is logged as well. This is a debug feature that can be "
-"turned off in production."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:633
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">prepared-statement-cache-size</emphasis>: This "
-"element specifies the number of prepared statements per connection in an LRU "
-"cache, which is keyed by the SQL query. Setting this to zero disables the "
-"cache."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:638
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">depends</emphasis>: The <literal>depends</literal> "
-"element specifies the JMX <literal>ObjectName</literal> string of a service "
-"that the connection manager services depend on. The connection manager "
-"service will not be started until the dependent services have been started."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:643
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">type-mapping</emphasis>: This element declares a "
-"default type mapping for this datasource. The type mapping should match a "
-"<literal>type-mapping/name</literal> element from <literal>standardjbosscmp-"
-"jdbc.xml</literal>."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:648
-#, no-c-format
-msgid ""
-"Additional common child elements for both <literal>no-tx-datasource</"
-"literal> and <literal>local-tx-datasource</literal> include:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:653
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">connection-url</emphasis>: This is the JDBC driver "
-"connection URL string, for example, <literal>jdbc:hsqldb:hsql://"
-"localhost:1701</literal>."
-msgstr ""
-"<emphasis role=\"bold\">prefix</emphasis>：这是每个日志文件名的前缀。它的缺省"
-"值是 <literal>access_log</literal>。"
-
-#. Tag: para
-#: Connectors.xml:658
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">driver-class</emphasis>: This is the fully qualified "
-"name of the JDBC driver class, for example, <literal>org.hsqldb.jdbcDriver</"
-"literal>."
-msgstr ""
-"<emphasis role=\"bold\">className</emphasis>：这是 <literal>org.apache."
-"catalina.Valve</literal> 接口实现的类全名。"
-
-#. Tag: para
-#: Connectors.xml:663
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">connection-property</emphasis>: The "
-"<literal>connection-property</literal> element allows you to pass in "
-"arbitrary connection properties to the <literal>java.sql.Driver.connect(url, "
-"props)</literal> method. Each <literal>connection-property</literal> "
-"specifies a string name/value pair with the property name coming from the "
-"name attribute and the value coming from the element content."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:668
-#, fuzzy, no-c-format
-msgid ""
-"Elements in common to the <literal>local-tx-datasource</literal> and "
-"<literal>xa-datasource</literal> are:"
-msgstr ""
-"在 <literal>Order</literal> 中，<literal>OrderLine</literal> 的集合则是这样："
-
-#. Tag: para
-#: Connectors.xml:673
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">transaction-isolation</emphasis>: This element "
-"specifies the <literal>java.sql.Connection</literal> transaction isolation "
-"level to use. The constants defined in the Connection interface are the "
-"possible element content values and include:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:678
-#, no-c-format
-msgid "TRANSACTION_READ_UNCOMMITTED"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:683
-#, no-c-format
-msgid "TRANSACTION_READ_COMMITTED"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:688
-#, no-c-format
-msgid "TRANSACTION_REPEATABLE_READ"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:693
-#, no-c-format
-msgid "TRANSACTION_SERIALIZABLE"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:698
-#, no-c-format
-msgid "TRANSACTION_NONE"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:705
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">no-tx-separate-pools</emphasis>: The presence of "
-"this element indicates that two connection pools are required to isolate "
-"connections used with JTA transaction from those used without a JTA "
-"transaction. The pools are lazily constructed on first use. Its use case is "
-"for Oracle (and possibly other vendors) XA implementations that don't "
-"like using an XA connection with and without a JTA transaction."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:710
-#, fuzzy, no-c-format
-msgid "The unique <literal>xa-datasource</literal> child elements are:"
-msgstr "<literal>attribute</literal>元素所支持的属性包括："
-
-#. Tag: para
-#: Connectors.xml:715
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">track-connection-by-tx</emphasis>: Specifying a true "
-"value for this element makes the connection manager keep an xid to "
-"connection map and only put the connection back in the pool when the "
-"transaction completes and all the connection handles are closed or "
-"disassociated (by the method calls returning). As a side effect, we never "
-"suspend and resume the xid on the connection's <literal>XAResource</"
-"literal>. This is the same connection tracking behavior used for local "
-"transactions."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:718
-#, no-c-format
-msgid ""
-"The XA spec implies that any connection may be enrolled in any transaction "
-"using any xid for that transaction at any time from any thread (suspending "
-"other transactions if necessary). The original JCA implementation assumed "
-"this and aggressively delisted connections and put them back in the pool as "
-"soon as control left the EJB they were used in or handles were closed. Since "
-"some other transaction could be using the connection the next time work "
-"needed to be done on the original transaction, there is no way to get the "
-"original connection back. It turns out that most <literal>XADataSource</"
-"literal> driver vendors do not support this, and require that all work done "
-"under a particular xid go through the same connection."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:723
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">xa-datasource-class</emphasis>: The fully qualified "
-"name of the <literal>javax.sql.XADataSource</literal> implementation class, "
-"for example, <literal>com.informix.jdbcx.IfxXADataSource</literal>."
-msgstr ""
-"<emphasis role=\"bold\">className</emphasis>：这是 <literal>org.apache."
-"catalina.Host</literal> 接口实现的类的全名。它的缺省值是 <literal>org.apache."
-"catalina.core.StandardHost</literal>。"
-
-#. Tag: para
-#: Connectors.xml:728
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">xa-datasource-property</emphasis>: The <literal>xa-"
-"datasource-property</literal> element allows for specification of the "
-"properties to assign to the <literal>XADataSource</literal> implementation "
-"class. Each property is identified by the name attribute and the property "
-"value is given by the <literal>xa-datasource-property</literal> element "
-"content. The property is mapped onto the <literal>XADataSource</literal> "
-"implementation by looking for a JavaBeans style getter method for the "
-"property name. If found, the value of the property is set using the "
-"JavaBeans setter with the element text translated to the true property type "
-"using the <literal>java.beans.PropertyEditor</literal> for the type."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:733
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">isSameRM-override-value</emphasis>: A boolean flag "
-"that allows one to override the behavior of the <literal>javax.transaction."
-"xa.XAResource.isSameRM(XAResource xaRes)</literal> method behavior on the XA "
-"managed connection. If specified, this value is used unconditionally as the "
-"<literal>isSameRM(xaRes)</literal> return value regardless of the "
-"<literal>xaRes</literal> parameter."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:738
-#, fuzzy, no-c-format
-msgid ""
-"The failover options common to <literal>ha-xa-datasource</literal> and "
-"<literal>ha-local-tx-datasource</literal> are:"
-msgstr ""
-"在 <literal>Order</literal> 中，<literal>OrderLine</literal> 的集合则是这样："
-
-#. Tag: para
-#: Connectors.xml:743
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">url-delimeter</emphasis>: This element specifies a "
-"character used to separate multiple JDBC URLs."
-msgstr ""
-"<emphasis role=\"bold\">description</emphasis>：这个元素指定操作的易读的描"
-"述。"
-
-#. Tag: para
-#: Connectors.xml:748
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">url-property</emphasis>: In the case of XA "
-"datasources, this property specifies the name of the <literal>xa-datasource-"
-"property</literal> that contains the list of JDBC URLs to use."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:753
-#, no-c-format
-msgid ""
-"Example configurations for many third-party JDBC drivers are included in the "
-"<literal>JBOSS_DIST/docs/examples/jca</literal> directory. Current example "
-"configurations include:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:758
-#, no-c-format
-msgid "asapxcess-jb3.2-ds.xml"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:763
-#, fuzzy, no-c-format
-msgid "cicsr9s-service.xml"
-msgstr "cluster-service.xml"
-
-#. Tag: para
-#: Connectors.xml:768
-#, fuzzy, no-c-format
-msgid "db2-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:773
-#, fuzzy, no-c-format
-msgid "db2-xa-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:778
-#, fuzzy, no-c-format
-msgid "facets-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:783
-#, no-c-format
-msgid "fast-objects-jboss32-ds.xml"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:788
-#, fuzzy, no-c-format
-msgid "firebird-ds.xml"
-msgstr "Firebird"
-
-#. Tag: para
-#: Connectors.xml:793
-#, fuzzy, no-c-format
-msgid "firstsql-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:798
-#, fuzzy, no-c-format
-msgid "firstsql-xa-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:803
-#, no-c-format
-msgid "generic-ds.xml"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:808
-#, no-c-format
-msgid "hsqldb-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:813
-#, fuzzy, no-c-format
-msgid "informix-ds.xml"
-msgstr "Informix"
-
-#. Tag: para
-#: Connectors.xml:818
-#, no-c-format
-msgid "informix-xa-ds.xml"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:823
-#, no-c-format
-msgid "jdatastore-ds.xml"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:828
-#, fuzzy, no-c-format
-msgid "jms-ds.xml"
-msgstr "jms/jms-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:833
-#, fuzzy, no-c-format
-msgid "jsql-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:838
-#, fuzzy, no-c-format
-msgid "lido-versant-service.xml"
-msgstr "client-deployer-service.xml"
-
-#. Tag: para
-#: Connectors.xml:843
-#, fuzzy, no-c-format
-msgid "mimer-ds.xml"
-msgstr "jms/jms-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:848
-#, fuzzy, no-c-format
-msgid "mimer-xa-ds.xml"
-msgstr "jms/jms-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:853
-#, fuzzy, no-c-format
-msgid "msaccess-ds.xml"
-msgstr "jms/jms-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:858
-#, fuzzy, no-c-format
-msgid "mssql-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:863
-#, fuzzy, no-c-format
-msgid "mssql-xa-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:868
-#, fuzzy, no-c-format
-msgid "mysql-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:873
-#, fuzzy, no-c-format
-msgid "oracle-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:878
-#, no-c-format
-msgid "oracle-xa-ds.xml"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:883
-#, fuzzy, no-c-format
-msgid "postgres-ds.xml"
-msgstr "jms/jms-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:888
-#, fuzzy, no-c-format
-msgid "sapdb-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:893
-#, fuzzy, no-c-format
-msgid "sapr3-ds.xml"
-msgstr "standardjaws.xml"
-
-#. Tag: para
-#: Connectors.xml:898
-#, fuzzy, no-c-format
-msgid "solid-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: para
-#: Connectors.xml:903
-#, fuzzy, no-c-format
-msgid "sybase-ds.xml"
-msgstr "hsqldb-ds.xml"
-
-#. Tag: title
-#: Connectors.xml:911
-#, no-c-format
-msgid "Configuring Generic JCA Adaptors"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:912
-#, no-c-format
-msgid ""
-"The XSLSubDeployer also supports the deployment of arbitrary non-JDBC JCA "
-"resource adaptors. The schema for the top-level connection factory elements "
-"of the <literal>*-ds.xml</literal> configuration deployment file is shown in "
-"<xref linkend=\"Configuring_Generic_JCA_Adaptors-"
-"The_simplified_JCA_adaptor_connection_factory_configuration_descriptor_top_level_schema_elements"
-"\"/>."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:916
-#, no-c-format
-msgid ""
-"The simplified JCA adaptor connection factory configuration descriptor top-"
-"level schema elements"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:923
-#, no-c-format
-msgid ""
-"Multiple connection factory configurations may be specified in a "
-"configuration deployment file. The child elements of the <literal>connection-"
-"factories</literal> root are:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:928
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mbean</emphasis>: Any number mbean elements may be "
-"specified to define MBean services that should be included in the "
-"<literal>jboss-service.xml</literal> descriptor that results from the "
-"transformation. This may be used to configure additional services used by "
-"the adaptor."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:933
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">no-tx-connection-factory</emphasis>: this element is "
-"used to specify the (<literal>org.jboss.resource.connectionmanager</"
-"literal>) <literal>NoTxConnectionManager</literal> service configuration. "
-"<literal>NoTxConnectionManager</literal> is a JCA connection manager with no "
-"transaction support. The <literal>no-tx-connection-factory</literal> child "
-"element schema is given in <xref linkend=\"Configuring_Generic_JCA_Adaptors-"
-"The_no_tx_connection_factory_element_schema\"/>."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:938
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">tx-connection-factory</emphasis>: this element is "
-"used to specify the (<literal>org.jboss.resource.connectionmanager</"
-"literal>) <literal>TxConnectionManager</literal> service configuration. The "
-"<literal>tx-connection-factory</literal> child element schema is given in "
-"<xref linkend=\"Configuring_Generic_JCA_Adaptors-"
-"The_tx_connection_factory_element_schema\"/>."
-msgstr ""
-
-#. Tag: title
-#: Connectors.xml:944
-#, fuzzy, no-c-format
-msgid "The no-tx-connection-factory element schema"
-msgstr "Connector 元素"
-
-#. Tag: title
-#: Connectors.xml:952
-#, fuzzy, no-c-format
-msgid "The tx-connection-factory element schema"
-msgstr "Connector 元素"
-
-#. Tag: para
-#: Connectors.xml:959
-#, no-c-format
-msgid ""
-"The majority of the elements are the same as those of the datasources "
-"configuration. The element unique to the connection factory configuration "
-"include:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:964
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">adaptor-display-name</emphasis>: A human readable "
-"display name to assign to the connection manager MBean."
-msgstr ""
-"<emphasis role=\"bold\">descriptors</emphasis>：与操作元数据关联的任何描述"
-"符。"
-
-#. Tag: para
-#: Connectors.xml:969
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">local-transaction</emphasis>: This element specifies "
-"that the <literal>tx-connection-factory</literal> supports local "
-"transactions."
-msgstr ""
-"<emphasis role=\"bold\">description</emphasis>：这个元素指定操作的易读的描"
-"述。"
-
-#. Tag: para
-#: Connectors.xml:974
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">xa-transaction</emphasis>: This element specifies "
-"that the <literal>tx-connection-factory</literal> supports XA transactions."
-msgstr ""
-"<emphasis role=\"bold\">description</emphasis>：这个元素指定操作的易读的描"
-"述。"
-
-#. Tag: para
-#: Connectors.xml:979
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">track-connection-by-tx</emphasis>: This element "
-"specifies that a connection should be used only on a single transaction and "
-"that a transaction should only be associated with one connection."
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:984
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">rar-name</emphasis>: This is the name of the RAR "
-"file that contains the definition for the resource we want to provide. For "
-"nested RAR files, the name would look like <literal>myapplication.ear#my."
-"rar</literal>."
-msgstr ""
-"<emphasis role=\"bold\">PartitionName</emphasis> 指定了部署这个 farm 的群集的"
-"名字。它的缺省值是 <literal>DefaultPartition</literal>。"
-
-#. Tag: para
-#: Connectors.xml:989
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">connection-definition</emphasis>: This is the "
-"connection factory interface class. It should match the "
-"<literal>connectionfactory-interface</literal> in the <literal>ra.xml</"
-"literal> file."
-msgstr ""
-"<emphasis role=\"bold\">DefaultSecurityDomain</emphasis>：它指定在 WAR 文件"
-"的 <literal>jboss-web.xml</literal> 里的 <literal>security-domain</literal> "
-"没有显性地指定的情况下的 JAAS 安全域名。"
-
-#. Tag: para
-#: Connectors.xml:994
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">config-property</emphasis>: Any number of properties "
-"to supply to the <literal>ManagedConnectionFactory</literal> (MCF) MBean "
-"service configuration. Each <literal>config-property</literal> element "
-"specifies the value of a MCF property. The <literal>config-property</"
-"literal> element has two required attributes:"
-msgstr ""
-
-#. Tag: para
-#: Connectors.xml:999
-#, fuzzy, no-c-format
-msgid "<emphasis role=\"bold\">name</emphasis>: The name of the property"
-msgstr "<emphasis role=\"bold\">name</emphasis>：参数的变量名，这是必须的。"
-
-#. Tag: para
-#: Connectors.xml:1004
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">type</emphasis>: The fully qualified type of the "
-"property"
-msgstr "<emphasis role=\"bold\">type</emphasis>：attribute类型的类全名。"
-
-#. Tag: para
-#: Connectors.xml:1009
-#, no-c-format
-msgid ""
-"The content of the <literal>config-property</literal> element provides the "
-"string representation of the property value. This will be converted to the "
-"true property type using the associated type <literal>PropertyEditor</"
-"literal>."
-msgstr ""
Deleted: projects/docs/trunk/Server_Configuration_Guide/zh-CN/J2EE_Transactions_On_JBOSS.po
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/zh-CN/J2EE_Transactions_On_JBOSS.po 2007-12-10 18:28:16 UTC (rev 68117)
+++ projects/docs/trunk/Server_Configuration_Guide/zh-CN/J2EE_Transactions_On_JBOSS.po 2007-12-10 22:26:23 UTC (rev 68118)
@@ -1,764 +0,0 @@
-# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
-# Automatically generated, 2007.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: JBEAP 420\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2007-11-05 06:04+0000\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:6
-#, fuzzy, no-c-format
-msgid "Transactions on JBoss"
-msgstr "Naming on JBoss"
-
-#. Tag: subtitle
-#: J2EE_Transactions_On_JBOSS.xml:7
-#, fuzzy, no-c-format
-msgid "The JTA Transaction Service"
-msgstr "JTA TransactionManagers"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:8
-#, no-c-format
-msgid ""
-"This chapter discusses transaction management in JBoss and the JBossTX "
-"architecture. The JBossTX architecture allows for any Java Transaction API "
-"(JTA) transaction manager implementation to be used. JBossTX includes a fast "
-"in-VM implementation of a JTA compatible transaction manager that is used as "
-"the default transaction manager. We will first provide an overview of the "
-"key transaction concepts and notions in the JTA to provide sufficient "
-"background for the JBossTX architecture discussion. We will then discuss the "
-"interfaces that make up the JBossTX architecture and conclude with a "
-"discussion of the MBeans available for integration of alternate transaction "
-"managers."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:12
-#, fuzzy, no-c-format
-msgid "Transaction/JTA Overview"
-msgstr "事务超时"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:13
-#, no-c-format
-msgid ""
-"For the purpose of this discussion, we can define a transaction as a unit of "
-"work containing one or more operations involving one or more shared "
-"resources having ACID properties. ACID is an acronym for atomicity, "
-"consistency, isolation and durability, the four important properties of "
-"transactions. The meanings of these terms is:"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:18
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Atomicity</emphasis>: A transaction must be atomic. "
-"This means that either all the work done in the transaction must be "
-"performed, or none of it must be performed. Doing part of a transaction is "
-"not allowed."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:23
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Consistency</emphasis>: When a transaction is "
-"completed, the system must be in a stable and consistent condition."
-msgstr ""
-"<emphasis role=\"bold\">INFO</emphasis>：操作不应该修改MBean组件的状态(读操"
-"作)。"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:28
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Isolation</emphasis>: Different transactions must be "
-"isolated from each other. This means that the partial work done in one "
-"transaction is not visible to other transactions until the transaction is "
-"committed, and that each process in a multi-user system can be programmed as "
-"if it was the only process accessing the system."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:33
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Durability</emphasis>: The changes made during a "
-"transaction are made persistent when it is committed. When a transaction is "
-"committed, its changes will not be lost, even if the server crashes "
-"afterwards."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:38
-#, no-c-format
-msgid ""
-"To illustrate these concepts, consider a simple banking account application. "
-"The banking application has a database with a number of accounts. The sum of "
-"the amounts of all accounts must always be 0. An amount of money M is moved "
-"from account A to account B by subtracting M from account A and adding M to "
-"account B. This operation must be done in a transaction, and all four ACID "
-"properties are important."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:41
-#, no-c-format
-msgid ""
-"The atomicity property means that both the withdrawal and deposit is "
-"performed as an indivisible unit. If, for some reason, both cannot be done "
-"nothing will be done."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:44
-#, no-c-format
-msgid ""
-"The consistency property means that after the transaction, the sum of the "
-"amounts of all accounts must still be 0."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:47
-#, no-c-format
-msgid ""
-"The isolation property is important when more than one bank clerk uses the "
-"system at the same time. A withdrawal or deposit could be implemented as a "
-"three-step process: First the amount of the account is read from the "
-"database; then something is subtracted from or added to the amount read from "
-"the database; and at last the new amount is written to the database. Without "
-"transaction isolation several bad things could happen. For example, if two "
-"processes read the amount of account A at the same time, and each "
-"independently added or subtracted something before writing the new amount to "
-"the database, the first change would be incorrectly overwritten by the last."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:50
-#, no-c-format
-msgid ""
-"The durability property is also important. If a money transfer transaction "
-"is committed, the bank must trust that some subsequent failure cannot undo "
-"the money transfer."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:54
-#, fuzzy, no-c-format
-msgid "Pessimistic and optimistic locking"
-msgstr "悲观锁定（Pessimistic Locking）"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:55
-#, no-c-format
-msgid ""
-"Transactional isolation is usually implemented by locking whatever is "
-"accessed in a transaction. There are two different approaches to "
-"transactional locking: Pessimistic locking and optimistic locking."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:58
-#, no-c-format
-msgid ""
-"The disadvantage of pessimistic locking is that a resource is locked from "
-"the time it is first accessed in a transaction until the transaction is "
-"finished, making it inaccessible to other transactions during that time. If "
-"most transactions simply look at the resource and never change it, an "
-"exclusive lock may be overkill as it may cause lock contention, and "
-"optimistic locking may be a better approach. With pessimistic locking, locks "
-"are applied in a fail-safe way. In the banking application example, an "
-"account is locked as soon as it is accessed in a transaction. Attempts to "
-"use the account in other transactions while it is locked will either result "
-"in the other process being delayed until the account lock is released, or "
-"that the process transaction will be rolled back. The lock exists until the "
-"transaction has either been committed or rolled back."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:61
-#, no-c-format
-msgid ""
-"With optimistic locking, a resource is not actually locked when it is first "
-"is accessed by a transaction. Instead, the state of the resource at the time "
-"when it would have been locked with the pessimistic locking approach is "
-"saved. Other transactions are able to concurrently access to the resource "
-"and the possibility of conflicting changes is possible. At commit time, when "
-"the resource is about to be updated in persistent storage, the state of the "
-"resource is read from storage again and compared to the state that was saved "
-"when the resource was first accessed in the transaction. If the two states "
-"differ, a conflicting update was made, and the transaction will be rolled "
-"back."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:64
-#, no-c-format
-msgid ""
-"In the banking application example, the amount of an account is saved when "
-"the account is first accessed in a transaction. If the transaction changes "
-"the account amount, the amount is read from the store again just before the "
-"amount is about to be updated. If the amount has changed since the "
-"transaction began, the transaction will fail itself, otherwise the new "
-"amount is written to persistent storage."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:70
-#, no-c-format
-msgid "The components of a distributed transaction"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:71
-#, no-c-format
-msgid ""
-"There are a number of participants in a distributed transaction. These "
-"include:"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:76
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Transaction Manager</emphasis>: This component is "
-"distributed across the transactional system. It manages and coordinates the "
-"work involved in the transaction. The transaction manager is exposed by the "
-"<literal>javax.transaction.TransactionManager</literal> interface in JTA."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:81
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Transaction Context</emphasis>: A transaction "
-"context identifies a particular transaction. In JTA the corresponding "
-"interface is <literal>javax.transaction.Transaction</literal>."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:86
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Transactional Client</emphasis>: A transactional "
-"client can invoke operations on one or more transactional objects in a "
-"single transaction. The transactional client that started the transaction is "
-"called the transaction originator. A transaction client is either an "
-"explicit or implicit user of JTA interfaces and has no interface "
-"representation in the JTA."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:91
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Transactional Object</emphasis>: A transactional "
-"object is an object whose behavior is affected by operations performed on it "
-"within a transactional context. A transactional object can also be a "
-"transactional client. Most Enterprise Java Beans are transactional objects."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:96
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Recoverable Resource</emphasis>: A recoverable "
-"resource is a transactional object whose state is saved to stable storage if "
-"the transaction is committed, and whose state can be reset to what it was at "
-"the beginning of the transaction if the transaction is rolled back. At "
-"commit time, the transaction manager uses the two-phase XA protocol when "
-"communicating with the recoverable resource to ensure transactional "
-"integrity when more than one recoverable resource is involved in the "
-"transaction being committed. Transactional databases and message brokers "
-"like JBossMQ are examples of recoverable resources. A recoverable resource "
-"is represented using the <literal>javax.transaction.xa.XAResource</literal> "
-"interface in JTA."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:104
-#, no-c-format
-msgid "The two-phase XA protocol"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:105
-#, no-c-format
-msgid ""
-"When a transaction is about to be committed, it is the responsibility of the "
-"transaction manager to ensure that either all of it is committed, or that "
-"all of is rolled back. If only a single recoverable resource is involved in "
-"the transaction, the task of the transaction manager is simple: It just has "
-"to tell the resource to commit the changes to stable storage."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:108
-#, no-c-format
-msgid ""
-"When more than one recoverable resource is involved in the transaction, "
-"management of the commit gets more complicated. Simply asking each of the "
-"recoverable resources to commit changes to stable storage is not enough to "
-"maintain the atomic property of the transaction. The reason for this is that "
-"if one recoverable resource has committed and another fails to commit, part "
-"of the transaction would be committed and the other part rolled back."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:111
-#, no-c-format
-msgid ""
-"To get around this problem, the two-phase XA protocol is used. The XA "
-"protocol involves an extra prepare phase before the actual commit phase. "
-"Before asking any of the recoverable resources to commit the changes, the "
-"transaction manager asks all the recoverable resources to prepare to commit. "
-"When a recoverable resource indicates it is prepared to commit the "
-"transaction, it has ensured that it can commit the transaction. The resource "
-"is still able to rollback the transaction if necessary as well."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:114
-#, no-c-format
-msgid ""
-"So the first phase consists of the transaction manager asking all the "
-"recoverable resources to prepare to commit. If any of the recoverable "
-"resources fails to prepare, the transaction will be rolled back. But if all "
-"recoverable resources indicate they were able to prepare to commit, the "
-"second phase of the XA protocol begins. This consists of the transaction "
-"manager asking all the recoverable resources to commit the transaction. "
-"Because all the recoverable resources have indicated they are prepared, this "
-"step cannot fail."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:120
-#, fuzzy, no-c-format
-msgid "Heuristic exceptions"
-msgstr "处理异常"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:121
-#, no-c-format
-msgid ""
-"In a distributed environment communications failures can happen. If "
-"communication between the transaction manager and a recoverable resource is "
-"not possible for an extended period of time, the recoverable resource may "
-"decide to unilaterally commit or rollback changes done in the context of a "
-"transaction. Such a decision is called a heuristic decision. It is one of "
-"the worst errors that may happen in a transaction system, as it can lead to "
-"parts of the transaction being committed while other parts are rolled back, "
-"thus violating the atomicity property of transaction and possibly leading to "
-"data integrity corruption."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:124
-#, no-c-format
-msgid ""
-"Because of the dangers of heuristic exceptions, a recoverable resource that "
-"makes a heuristic decision is required to maintain all information about the "
-"decision in stable storage until the transaction manager tells it to forget "
-"about the heuristic decision. The actual data about the heuristic decision "
-"that is saved in stable storage depends on the type of recoverable resource "
-"and is not standardized. The idea is that a system manager can look at the "
-"data, and possibly edit the resource to correct any data integrity problems."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:127
-#, no-c-format
-msgid ""
-"There are several different kinds of heuristic exceptions defined by the "
-"JTA. The <literal>javax.transaction.HeuristicCommitException</literal> is "
-"thrown when a recoverable resource is asked to rollback to report that a "
-"heuristic decision was made and that all relevant updates have been "
-"committed. On the opposite end is the <literal>javax.transaction."
-"HeuristicRollbackException</literal>, which is thrown by a recoverable "
-"resource when it is asked to commit to indicate that a heuristic decision "
-"was made and that all relevant updates have been rolled back."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:130
-#, no-c-format
-msgid ""
-"The <literal>javax.transaction.HeuristicMixedException</literal> is the "
-"worst heuristic exception. It is thrown to indicate that parts of the "
-"transaction were committed, while other parts were rolled back. The "
-"transaction manager throws this exception when some recoverable resources "
-"did a heuristic commit, while other recoverable resources did a heuristic "
-"rollback."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:136
-#, fuzzy, no-c-format
-msgid "Transaction IDs and branches"
-msgstr "事务和并发"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:137
-#, no-c-format
-msgid ""
-"In JTA, the identity of transactions is encapsulated in objects implementing "
-"the <literal>javax.transaction.xa.Xid</literal> interface. The transaction "
-"ID is an aggregate of three parts:"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:142
-#, no-c-format
-msgid ""
-"The format identifier indicates the transaction family and tells how the "
-"other two parts should be interpreted."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:147
-#, no-c-format
-msgid ""
-"The global transaction id identified the global transaction within the "
-"transaction family."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:152
-#, no-c-format
-msgid ""
-"The branch qualifier denotes a particular branch of the global transaction."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:157
-#, no-c-format
-msgid ""
-"Transaction branches are used to identify different parts of the same global "
-"transaction. Whenever the transaction manager involves a new recoverable "
-"resource in a transaction it creates a new transaction branch."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:165
-#, fuzzy, no-c-format
-msgid "JBoss Transaction Internals"
-msgstr "JTA TransactionManagers"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:166
-#, no-c-format
-msgid ""
-"The JBoss application server is written to be independent of the actual "
-"transaction manager used. JBoss uses the JTA <literal>javax.transaction."
-"TransactionManager</literal> interface as its view of the server transaction "
-"manager. Thus, JBoss may use any transaction manager which implements the "
-"JTA <literal>TransactionManager</literal> interface. Whenever a transaction "
-"manager is used it is obtained from the well-known JNDI location, "
-"<literal>java:/TransactionManager</literal>. This is the globally available "
-"access point for the server transaction manager."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:169
-#, no-c-format
-msgid ""
-"If transaction contexts are to be propagated with RMI/JRMP calls, the "
-"transaction manager must also implement two simple interfaces for the import "
-"and export of transaction propagation contexts (TPCs). The interfaces are "
-"<literal>TransactionPropagationContextImporter</literal>, and "
-"<literal>TransactionPropagationContextFactory</literal>, both in the "
-"<literal>org.jboss.tm</literal> package."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:172
-#, no-c-format
-msgid ""
-"Being independent of the actual transaction manager used also means that "
-"JBoss does not specify the format of type of the transaction propagation "
-"contexts used. In JBoss, a TPC is of type <literal>Object</literal>, and the "
-"only requirement is that the TPC must implementation the <literal>java.io."
-"Serializable</literal> interface."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:175
-#, no-c-format
-msgid ""
-"When using the RMI/JRMP protocol for remote calls, the TPC is carried as a "
-"field in the <literal>org.jboss.ejb.plugins.jrmp.client."
-"RemoteMethodInvocation</literal> class that is used to forward remote method "
-"invocation requests."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:179
-#, fuzzy, no-c-format
-msgid "Adapting a Transaction Manager to JBoss"
-msgstr "JTA TransactionManagers"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:180
-#, no-c-format
-msgid ""
-"A transaction manager has to implement the Java Transaction API to be easily "
-"integrated with JBoss. As almost everything in JBoss, the transaction "
-"manager is managed as an MBean. Like all JBoss services, it should implement "
-"<literal>org.jboss.system.ServiceMBean</literal> to ensure proper life-cycle "
-"management."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:183
-#, no-c-format
-msgid ""
-"The primary requirement of the transaction manager service on startup is "
-"that it binds its implementation of the three required interfaces into JNDI. "
-"These interfaces and their JNDI locations are:"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:188
-#, no-c-format
-msgid ""
-"The <literal>javax.transaction.TransactionManager</literal> interface is "
-"used by the application server to manage transactions on behalf of the "
-"transactional objects that use container managed transactions. It must be "
-"bound under the JNDI name <literal>java:/TransactionManager</literal>."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:193
-#, no-c-format
-msgid ""
-"The <literal>TransactionPropagationContextFactory</literal> interface is "
-"called by JBoss whenever a transaction propagation context is needed for "
-"transporting a transaction with a remote method call. It must be bound under "
-"the JNDI name <literal>java:/TransactionPropagationContextImporter</literal>."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:198
-#, no-c-format
-msgid ""
-"The <literal>TransactionPropagationContextImporter</literal> interface is "
-"called by JBoss whenever a transaction propagation context from an incoming "
-"remote method invocation has to be converted to a transaction that can be "
-"used within the receiving JBoss server VM."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:203
-#, no-c-format
-msgid ""
-"Establishing these JNDI bindings is all the transaction manager service "
-"needs to do to install its implementation as the JBoss server transaction "
-"manager."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:209
-#, fuzzy, no-c-format
-msgid "The Default Transaction Manager"
-msgstr "JTA TransactionManagers"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:210
-#, no-c-format
-msgid ""
-"JBoss is by default configured to use the fast in-VM transaction manager. "
-"This transaction manager is very fast, but does have two limitations."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:215
-#, no-c-format
-msgid ""
-"It does not do transactional logging, and is thus incapable of automated "
-"recovery after a server crash."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:220
-#, no-c-format
-msgid ""
-"While it does support propagating transaction contexts with remote calls, it "
-"does not support propagating transaction contexts to other virtual machines, "
-"so all transactional work must be done in the same virtual machine as the "
-"JBoss server."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:225
-#, no-c-format
-msgid ""
-"The corresponding default transaction manager MBean service is the "
-"<literal>org.jboss.tm.TransactionManagerService</literal> MBean. It has two "
-"configurable attributes:"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:230
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">TransactionTimeout</emphasis>: The default "
-"transaction timeout in seconds. The default value is 300 seconds (5 minutes)."
-msgstr ""
-"<emphasis role=\"bold\">jnp.discoveryTimeout</emphasis>：等待发现查询的应答的"
-"毫秒数。缺省值为 5000(5 秒)。"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:235
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">InterruptThreads</emphasis>: Indicates whether or "
-"not the transaction manager should interrupt threads when the transaction "
-"times out. The default value is false."
-msgstr ""
-"<emphasis role=\"bold\">NumAcceptThreads</emphasis>：用来接受客户联接的线程的"
-"数量。它的缺省值是 1。"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:240
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">GlobalIdsEnabled</emphasis>: Indicates whether or "
-"not the transaction manager should use global transaction ids. This should "
-"be set to true for transaction demarcation over IIOP. The default value is "
-"true."
-msgstr ""
-"<emphasis role=\"bold\">NumAcceptThreads</emphasis>：用来接受客户联接的线程的"
-"数量。它的缺省值是 1。"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:245
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">XidFactory</emphasis>: The JMX <literal>ObjectName</"
-"literal> of the MBean service that provides the <literal>org.jboss.tm."
-"XidFactoryMBean</literal> implementation. The <literal>XidFactoryMBean</"
-"literal> interface is used to create <literal>javax.transaction.xa.Xid</"
-"literal> instances. This is a workaround for XA JDBC drivers that only work "
-"with their own Xid implementation. Examples of such drivers are the older "
-"Oracle XA drivers. The default factory is <literal>jboss:service=XidFactory</"
-"literal>."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:251
-#, fuzzy, no-c-format
-msgid "org.jboss.tm.XidFactory"
-msgstr "The org.jboss.naming.NamingContextFactory"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:252
-#, no-c-format
-msgid ""
-"The <literal>XidFactory</literal> MBean is a factory for <literal>javax."
-"transaction.xa.Xid</literal> instances in the form of <literal>org.jboss.tm."
-"XidImpl</literal>. The <literal>XidFactory</literal> allows for "
-"customization of the <literal>XidImpl</literal> that it constructs through "
-"the following attributes:"
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:257
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">BaseGlobalId</emphasis>: This is used for building "
-"globally unique transaction identifiers. This must be set individually if "
-"multiple JBoss instances are running on the same machine. The default value "
-"is the host name of the JBoss server, followed by a slash."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:262
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">GlobalIdNumber</emphasis>: A long value used as "
-"initial transaction id. The default is 0."
-msgstr ""
-"<emphasis role=\"bold\">Backlog</emphasis>：与服务器接受套接字关联的 "
-"backlog。缺省值是 200。"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:267
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Pad</emphasis>: The pad value determines whether the "
-"byte[] returned by the Xid <literal>getGlobalTransactionId</literal> and "
-"<literal>getBranchQualifier</literal> methods should be equal to maximum 64 "
-"byte length or a variable value <= 64. Some resource managers (Oracle, "
-"for example) require ids that are max length in size."
-msgstr ""
-
-#. Tag: title
-#: J2EE_Transactions_On_JBOSS.xml:277
-#, fuzzy, no-c-format
-msgid "UserTransaction Support"
-msgstr "jta.UserTransaction"
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:278
-#, no-c-format
-msgid ""
-"The JTA <literal>javax.transaction.UserTransaction</literal> interface "
-"allows applications to explicitly control transactions. For enterprise "
-"session beans that manage transaction themselves (BMT), a "
-"<literal>UserTransaction</literal> can be obtained by calling the "
-"<literal>getUserTransaction</literal> method on the bean context object, "
-"<literal>javax.ejb.SessionContext</literal>."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:281
-#, no-c-format
-msgid ""
-"The <literal>ClientUserTransactionService</literal> MBean publishes a "
-"<literal>UserTransaction</literal> implementation under the JNDI name "
-"<literal>UserTransaction</literal>. When the <literal>UserTransaction</"
-"literal> is obtained with a JNDI lookup from a external client, a very "
-"simple <literal>UserTransaction</literal> suitable for thin clients is "
-"returned. This <literal>UserTransaction</literal> implementation only "
-"controls the transactions on the server the <literal>UserTransaction</"
-"literal> object was obtained from. Local transactional work done in the "
-"client is not done within the transactions started by this "
-"<literal>UserTransaction</literal> object."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:284
-#, no-c-format
-msgid ""
-"When a <literal>UserTransaction</literal> object is obtained by looking up "
-"JNDI name <literal>UserTransaction</literal> in the same virtual machine as "
-"JBoss, a simple interface to the JTA <literal>TransactionManager</literal> "
-"is returned. This is suitable for web components running in web containers "
-"embedded in JBoss. When components are deployed in an embedded web server, "
-"the deployer will make a JNDI link from the standard <literal>java:comp/"
-"UserTransaction</literal> ENC name to the global <literal>UserTransaction</"
-"literal> binding so that the web components can lookup the "
-"<literal>UserTransaction</literal> instance under JNDI name as specified by "
-"the J2EE."
-msgstr ""
-
-#. Tag: para
-#: J2EE_Transactions_On_JBOSS.xml:287
-#, no-c-format
-msgid ""
-"Note: For BMT beans, do not obtain the <literal>UserTransaction</literal> "
-"interface using a JNDI lookup. Doing this violates the EJB specification, "
-"and the returned <literal>UserTransaction</literal> object does not have the "
-"hooks the EJB container needs to make important checks."
-msgstr ""
Deleted: projects/docs/trunk/Server_Configuration_Guide/zh-CN/JBossCache_And_JGroups_Services.po
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/zh-CN/JBossCache_And_JGroups_Services.po 2007-12-10 18:28:16 UTC (rev 68117)
+++ projects/docs/trunk/Server_Configuration_Guide/zh-CN/JBossCache_And_JGroups_Services.po 2007-12-10 22:26:23 UTC (rev 68118)
@@ -1,2274 +0,0 @@
-# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
-# Automatically generated, 2007.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: JBEAP 420\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2007-11-05 06:04+0000\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:6
-#, no-c-format
-msgid "JBossCache and JGroups Services"
-msgstr "JBossCache 和 JGroups 服务"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:7
-#, no-c-format
-msgid ""
-"JGroups and JBossCache provide the underlying communication, node "
-"replication and caching services, for JBoss AS clusters. Those services are "
-"configured as MBeans. There is a set of JBossCache and JGroups MBeans for "
-"each type of clustering applications (e.g., the Stateful Session EJBs, the "
-"distributed entity EJBs etc.)."
-msgstr ""
-"JGroups 和 JBossCache 为 JBoss AS 群集提供底层的通信，节点复制和缓存服务。这"
-"些服务都配置成 MBeans。对于每一个类型的群集应用程序（如 Stateful Session "
-"EJBs， distributed entity EJBs 等），都有一个 JBossCache 和 JGroups 的 "
-"MBeans 的集合。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:10
-#, no-c-format
-msgid ""
-"The JBoss AS ships with a reasonable set of default JGroups and JBossCache "
-"MBean configurations. Most applications just work out of the box with the "
-"default MBean configurations. You only need to tweak them when you are "
-"deploying an application that has special network or performance "
-"requirements."
-msgstr ""
-"JBoss AS 带有缺省的 JGroups 和 JBossCache 的配置集。大部分应用程序使用这些缺"
-"省的配置就够了。只是在部署有特殊网络或性能要求的应用程序时，你才需要做更多的"
-"配置。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:14
-#, no-c-format
-msgid "JGroups Configuration"
-msgstr "JGroups Configuration"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:15
-#, fuzzy, no-c-format
-msgid ""
-"The JGroups framework provides services to enable peer-to-peer "
-"communications between nodes in a cluster. It is built on top a stack of "
-"network communication protocols that provide transport, discovery, "
-"reliability and failure detection, and cluster membership management "
-"services. <xref linkend=\"JGroups_Configuration-Protocol_stack_in_JGroups\"/"
-"> shows the protocol stack in JGroups."
-msgstr ""
-"JGroups 框架提供了启用群集系统里节点间到对点通信的服务。它建立在网络通信协议"
-"栈的顶层，它提供传输，发现（discovery），可靠性（reliability）和故障"
-"（failure）检测，以及群集成员资格管理服务。<xref linkend=\"jbosscache-"
-"JGroupsStack.fig\"/> 展示了 JGroups 的协议栈。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:19
-#, no-c-format
-msgid "Protocol stack in JGroups"
-msgstr "Protocol stack in JGroups"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:26
-#, no-c-format
-msgid ""
-"JGroups configurations often appear as a nested attribute in cluster related "
-"MBean services, such as the <literal>PartitionConfig</literal> attribute in "
-"the <literal>ClusterPartition</literal> MBean or the <literal>ClusterConfig</"
-"literal> attribute in the <literal>TreeCache</literal> MBean. You can "
-"configure the behavior and properties of each protocol in JGroups via those "
-"MBean attributes. Below is an example JGroups configuration in the "
-"<literal>ClusterPartition</literal> MBean."
-msgstr ""
-"JGroups 配置经常以和群集相关的 MBean 服务的嵌套属性的面目出现，例如 "
-"<literal>ClusterPartition</literal> MBean 的<literal>PartitionConfig</"
-"literal> 属性或 <literal>TreeCache</literal> MBean 的 "
-"<literal>ClusterConfig</literal> 属性。你可以通过这些 MBean 属性来配置 "
-"JGroups 每一个协议的行为和属性（properties）。下面是一个 "
-"<literal>ClusterPartition</literal> MBean 里的 JGroups 配置的例子。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:29
-#, no-c-format
-msgid ""
-"<mbean code=\"org.jboss.ha.framework.server.ClusterPartition\"\n"
-" name=\"jboss:service=DefaultPartition\">\n"
-"\n"
-" ... ...\n"
-" \n"
-" <attribute name=\"PartitionConfig\">\n"
-" <Config>\n"
-" <UDP mcast_addr=\"228.1.2.3\" mcast_port=\"45566\"\n"
-" ip_ttl=\"8\" ip_mcast=\"true\"\n"
-" mcast_send_buf_size=\"800000\" mcast_recv_buf_size=\"150000"
-"\"\n"
-" ucast_send_buf_size=\"800000\" ucast_recv_buf_size=\"150000"
-"\"\n"
-" loopback=\"false\"/>\n"
-" <PING timeout=\"2000\" num_initial_members=\"3\"\n"
-" up_thread=\"true\" down_thread=\"true\"/>\n"
-" <MERGE2 min_interval=\"10000\" max_interval=\"20000\"/>\n"
-" <FD shun=\"true\" up_thread=\"true\" down_thread=\"true\"\n"
-" timeout=\"2500\" max_tries=\"5\"/>\n"
-" <VERIFY_SUSPECT timeout=\"3000\" num_msgs=\"3\"\n"
-" up_thread=\"true\" down_thread=\"true\"/>\n"
-" <pbcast.NAKACK gc_lag=\"50\"\n"
-" retransmit_timeout=\"300,600,1200,2400,4800\"\n"
-" max_xmit_size=\"8192\"\n"
-" up_thread=\"true\" down_thread=\"true\"/>\n"
-" <UNICAST timeout=\"300,600,1200,2400,4800\" \n"
-" window_size=\"100\" min_threshold=\"10\"\n"
-" down_thread=\"true\"/>\n"
-" <pbcast.STABLE desired_avg_gossip=\"20000\"\n"
-" up_thread=\"true\" down_thread=\"true\"/>\n"
-" <FRAG frag_size=\"8192\"\n"
-" down_thread=\"true\" up_thread=\"true\"/>\n"
-" <pbcast.GMS join_timeout=\"5000\" join_retry_timeout=\"2000"
-"\"\n"
-" shun=\"true\" print_local_addr=\"true\"/>\n"
-" <pbcast.STATE_TRANSFER up_thread=\"true\" down_thread=\"true"
-"\"/>\n"
-" </Config>\n"
-" </attribute>\n"
-"</mbean>"
-msgstr ""
-"<mbean code=\"org.jboss.ha.framework.server.ClusterPartition\"\n"
-" name=\"jboss:service=DefaultPartition\">\n"
-"\n"
-" ... ...\n"
-" \n"
-" <attribute name=\"PartitionConfig\">\n"
-" <Config>\n"
-" <UDP mcast_addr=\"228.1.2.3\" mcast_port=\"45566\"\n"
-" ip_ttl=\"8\" ip_mcast=\"true\"\n"
-" mcast_send_buf_size=\"800000\" mcast_recv_buf_size=\"150000"
-"\"\n"
-" ucast_send_buf_size=\"800000\" ucast_recv_buf_size=\"150000"
-"\"\n"
-" loopback=\"false\"/>\n"
-" <PING timeout=\"2000\" num_initial_members=\"3\"\n"
-" up_thread=\"true\" down_thread=\"true\"/>\n"
-" <MERGE2 min_interval=\"10000\" max_interval=\"20000\"/>\n"
-" <FD shun=\"true\" up_thread=\"true\" down_thread=\"true\"\n"
-" timeout=\"2500\" max_tries=\"5\"/>\n"
-" <VERIFY_SUSPECT timeout=\"3000\" num_msgs=\"3\"\n"
-" up_thread=\"true\" down_thread=\"true\"/>\n"
-" <pbcast.NAKACK gc_lag=\"50\"\n"
-" retransmit_timeout=\"300,600,1200,2400,4800\"\n"
-" max_xmit_size=\"8192\"\n"
-" up_thread=\"true\" down_thread=\"true\"/>\n"
-" <UNICAST timeout=\"300,600,1200,2400,4800\" \n"
-" window_size=\"100\" min_threshold=\"10\"\n"
-" down_thread=\"true\"/>\n"
-" <pbcast.STABLE desired_avg_gossip=\"20000\"\n"
-" up_thread=\"true\" down_thread=\"true\"/>\n"
-" <FRAG frag_size=\"8192\"\n"
-" down_thread=\"true\" up_thread=\"true\"/>\n"
-" <pbcast.GMS join_timeout=\"5000\" join_retry_timeout=\"2000"
-"\"\n"
-" shun=\"true\" print_local_addr=\"true\"/>\n"
-" <pbcast.STATE_TRANSFER up_thread=\"true\" down_thread=\"true"
-"\"/>\n"
-" </Config>\n"
-" </attribute>\n"
-"</mbean>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:30
-#, no-c-format
-msgid ""
-"All the JGroups configuration data is contained in the <literal><"
-"Config></literal> element under the JGroups config MBean attribute. In "
-"the next several sections, we will dig into the options in the <literal><"
-"Config></literal> element and explain exactly what they mean."
-msgstr ""
-"所有的 JGroups 配置数据包含在 JGroups config MBean 属性下的 <literal><"
-"Config></literal> 元素里。在后面的内容里，我们将探究 <literal><"
-"Config></literal> 元素的选项及它们的含义。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:34
-#, no-c-format
-msgid "Transport Protocols"
-msgstr "传输协议"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:35
-#, no-c-format
-msgid ""
-"The transport protocols send messages from one cluster node to another "
-"(unicast) or from cluster node to all other nodes in the cluster (mcast). "
-"JGroups supports UDP, TCP, and TUNNEL as transport protocols."
-msgstr ""
-"传输协议（transport protocols）从一个群集节点发送信息到另外一个节点（单播 "
-"unicast）或发送到群集里所有其他节点（mcast）。JGroups 支持 UDP，TCP 和 "
-"TUNNEL 等传输协议。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:39
-#, no-c-format
-msgid ""
-"The <literal>UDP</literal>, <literal>TCP</literal>, and <literal>TUNNEL</"
-"literal> elements are mutually exclusive. You can only have one transport "
-"protocol in each JGroups <literal>Config</literal> element"
-msgstr ""
-"<literal>UDP</literal>，<literal>TCP</literal> 和 <literal>TUNNEL</literal> "
-"元素是相互排斥的。你只能在每个 JGroups <literal>Config</literal> 元素里使用一"
-"个传输协议。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:44
-#, no-c-format
-msgid "UDP configuration"
-msgstr "UDP 配置"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:45
-#, no-c-format
-msgid ""
-"UDP is the preferred protocol for JGroups. UDP uses multicast or multiple "
-"unicasts to send and receive messages. If you choose UDP as the transport "
-"protocol for your cluster service, you need to configure it in the "
-"<literal>UDP</literal> sub-element in the JGroups <literal>Config</literal> "
-"element. Here is an example."
-msgstr ""
-"UDP 是 JGroups 的首选协议。UDP 使用多点传送（multicast ）或多个单播"
-"（unicast）来发送和接收信息。如果你选择 UDP 作为你的群集服务的传输协议，你需"
-"要在 JGroups <literal>Config</literal> 元素的 <literal>UDP</literal> 子元素里"
-"配置它。下面是一个示例。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:48
-#, no-c-format
-msgid ""
-"<UDP mcast_send_buf_size=\"32000\"\n"
-" mcast_port=\"45566\"\n"
-" ucast_recv_buf_size=\"64000\"\n"
-" mcast_addr=\"228.8.8.8\"\n"
-" bind_to_all_interfaces=\"true\"\n"
-" loopback=\"true\"\n"
-" mcast_recv_buf_size=\"64000\"\n"
-" max_bundle_size=\"30000\"\n"
-" max_bundle_timeout=\"30\"\n"
-" use_incoming_packet_handler=\"false\"\n"
-" use_outgoing_packet_handler=\"false\"\n"
-" ucast_send_buf_size=\"32000\"\n"
-" ip_ttl=\"32\"\n"
-" enable_bundling=\"false\"/>"
-msgstr ""
-"<UDP mcast_send_buf_size=\"32000\"\n"
-" mcast_port=\"45566\"\n"
-" ucast_recv_buf_size=\"64000\"\n"
-" mcast_addr=\"228.8.8.8\"\n"
-" bind_to_all_interfaces=\"true\"\n"
-" loopback=\"true\"\n"
-" mcast_recv_buf_size=\"64000\"\n"
-" max_bundle_size=\"30000\"\n"
-" max_bundle_timeout=\"30\"\n"
-" use_incoming_packet_handler=\"false\"\n"
-" use_outgoing_packet_handler=\"false\"\n"
-" ucast_send_buf_size=\"32000\"\n"
-" ip_ttl=\"32\"\n"
-" enable_bundling=\"false\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:49
-#, no-c-format
-msgid ""
-"The available attributes in the above JGroups configuration are listed below."
-msgstr "下列是在上述 JGroups 配置里的可用属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:54
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ip_mcast</emphasis> specifies whether or not to use "
-"IP multicasting. The default is <literal>true</literal>."
-msgstr ""
-"<emphasis role=\"bold\">ip_mcast</emphasis> 指定是否使用 IP 多点传送"
-"（multicasting）。它的缺省值是 <literal>true</literal>。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:59
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mcast_addr</emphasis> specifies the multicast "
-"address (class D) for joining a group (i.e., the cluster). The default is "
-"<literal>228.8.8.8</literal>."
-msgstr ""
-"<emphasis role=\"bold\">mcast_addr</emphasis> 指定加入到组（就是群集）里的多"
-"点传送地址（class D）。它的缺省值是 <literal>228.8.8.8</literal>。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:64
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mcast_port</emphasis> specifies the multicast port "
-"number. The default is <literal>45566</literal>."
-msgstr ""
-"<emphasis role=\"bold\">mcast_port</emphasis> 指定多点传送端口号码。它的缺省"
-"值是 <literal>45566</literal>。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:69
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">bind_addr</emphasis> specifies the interface on "
-"which to receive and send multicasts (uses the <literal>bind.address</"
-"literal> system property, if present). If you have a multihomed machine, set "
-"the <literal>bind_addr</literal> attribute to the appropriate NIC IP "
-"address. Ignored if the <literal>ignore.bind.address</literal> property is "
-"true."
-msgstr ""
-"<emphasis role=\"bold\">bind_addr</emphasis> 指定接收和发送多点传送的接口（如"
-"果可用，使用 <literal>bind.address</literal> 系统属性）。如果你有一个多宿主主"
-"机，把 <literal>bind_addr</literal> 属性设置为合适的 NIC IP 地址。如果 "
-"<literal>ignore.bind.address</literal> 属性为真（true）的话，这个属性将被忽"
-"略。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:74
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">bind_to_all_interfaces</emphasis> specifies whether "
-"this node should listen on all interfaces for multicasts. The default is "
-"<literal>false</literal>. It overrides the <literal>bind_addr</literal> "
-"property for receiving multicasts. However, <literal>bind_addr</literal> (if "
-"set) is still used to send multicasts."
-msgstr ""
-"<emphasis role=\"bold\">bind_to_all_interfaces</emphasis> 指定是否这个节点应"
-"该为多点传送侦听所有的接口。它的缺省值是 <literal>false</literal>。它覆盖了接"
-"收多点传送的 <literal>bind_addr</literal> 属性。然而，<literal>bind_addr</"
-"literal>（如果设置了）仍会用来发送多点传送信息。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:79
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ip_ttl</emphasis> specifies the TTL for multicast "
-"packets."
-msgstr ""
-"<emphasis role=\"bold\">ip_ttl</emphasis> 指定了多点传送数据包（packet）的 "
-"TTL。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:84
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">use_incoming_packet_handler</emphasis> specifies "
-"whether to use a separate thread to process incoming messages."
-msgstr ""
-"<emphasis role=\"bold\">use_incoming_packet_handler</emphasis> 指定是否使用单"
-"独的线程来处理输入的信息。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:89
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">use_outgoing_packet_handler</emphasis> specifies "
-"whether to use a separate thread to process outgoing messages."
-msgstr ""
-"<emphasis role=\"bold\">use_outgoing_packet_handler</emphasis> 指定是否使用单"
-"独的线程来处理输出的（outgoing）信息。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:94
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">enable_bundling</emphasis> specifies whether to "
-"enable bundling. If it is <literal>true</literal>, the node would queue "
-"outgoing messages until <literal>max_bundle_size</literal> bytes have "
-"accumulated, or <literal>max_bundle_time</literal> milliseconds have "
-"elapsed, whichever occurs first. Then bundle queued messages into a large "
-"message and send it. The messages are unbundled at the receiver. The default "
-"is <literal>false</literal>."
-msgstr ""
-"<emphasis role=\"bold\">enable_bundling</emphasis> 指定是否启用捆绑"
-"（bundling）。如果它设为<literal>true</literal>，节点将会把输出的信息排队，一"
-"直到积累了 <literal>max_bundle_size</literal> 个字节，或者是 "
-"<literal>max_bundle_time</literal> 毫秒后，依哪个先发生而定。然后把排队的信息"
-"捆绑成一个大的信息发送出去。这个信息在接收端再解开。它的缺省值是 "
-"<literal>false</literal>。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:99
-#: JBossCache_And_JGroups_Services.xml:142
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">loopback</emphasis> specifies whether to loop "
-"outgoing message back up the stack. In <literal>unicast</literal> mode, the "
-"messages are sent to self. In <literal>mcast</literal> mode, a copy of the "
-"mcast message is sent."
-msgstr ""
-"<emphasis role=\"bold\">loopback</emphasis> 指定是否在堆栈里回送（loop back）"
-"输出信息。在单播 <literal>unicast</literal> 模式下，信息都会发送给自己。如果"
-"是 <literal>mcast</literal> 模式，多点传送信息的备份将被发送。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:104
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">discard_incompatibe_packets</emphasis> specifies "
-"whether to discard packets from different JGroups versions. Each message in "
-"the cluster is tagged with a JGroups version. When a message from a "
-"different version of JGroups is received, it will be discarded if set to "
-"true, otherwise a warning will be logged."
-msgstr ""
-"<emphasis role=\"bold\">discard_incompatibe_packets</emphasis> 指定是否丢弃从"
-"不同版本的 JGroups 过来的数据包。群集里的每个数据包都用 JGroups 版本号来标"
-"记。如果它设置为 true，当接收到一个不同 JGroups 版本的信息时，这个信息将被丢"
-"弃; 否则，将记录一个警告。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:109
-#: JBossCache_And_JGroups_Services.xml:147
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mcast_send_buf_size, mcast_recv_buf_size, "
-"ucast_send_buf_size, ucast_recv_buf_size</emphasis> define receive and send "
-"buffer sizes. It is good to have a large receiver buffer size, so packets "
-"are less likely to get dropped due to buffer overflow."
-msgstr ""
-"<emphasis role=\"bold\">mcast_send_buf_size，mcast_recv_buf_size，"
-"ucast_send_buf_size，ucast_recv_buf_size</emphasis> 定义接收和发送的缓冲区大"
-"小。设置大的接收缓冲区会比较好，这样数据包就不会因为缓冲区溢出而被丢弃。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:115
-#, fuzzy, no-c-format
-msgid ""
-"On Windows 2000 machines, because of the media sense feature being broken "
-"with multicast (even after disabling media sense), you need to set the UDP "
-"protocol's <literal>loopback</literal> attribute to <literal>true</"
-"literal>."
-msgstr ""
-"在安装 Windows 2000 的机器里，由于 media sense 特征与多点传送冲突（即使你关闭"
-"了 media sense），你需要把 UDP 协议的 <literal>loopback</literal> 属性设为 "
-"<literal>true</literal>。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:122
-#, no-c-format
-msgid "TCP configuration"
-msgstr "TCP 配置"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:123
-#, no-c-format
-msgid ""
-"Alternatively, a JGroups-based cluster can also work over TCP connections. "
-"Compared with UDP, TCP generates more network traffic when the cluster size "
-"increases but TCP is more reliable. TCP is fundamentally a unicast protocol. "
-"To send multicast messages, JGroups uses multiple TCP unicasts. To use TCP "
-"as a transport protocol, you should define a <literal>TCP</literal> element "
-"in the JGroups <literal>Config</literal> element. Here is an example of the "
-"<literal>TCP</literal> element."
-msgstr ""
-"另外，基于 JGroups 的群集系统也可以使用 TCP 连接。和 UDP 相比，当群集规模扩大"
-"时 TCP 会产生更多的网络流量，但是 TCP 更加可靠。TCP 从根本来说是一个单播"
-"（unicast）的协议。为了发送多点传送的信息，JGroups 使用多个 TCP 单播。如要把 "
-"TCP 作为一个传输协议来使用，你应该定义 JGroups <literal>Config</literal> 元素"
-"里的 <literal>TCP</literal> 元素。这是一个 <literal>TCP</literal> 元素的例"
-"子。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:126
-#, no-c-format
-msgid ""
-"<TCP start_port=\"7800\"\n"
-" bind_addr=\"192.168.5.1\"\n"
-" loopback=\"true\"/>"
-msgstr ""
-"<TCP start_port=\"7800\"\n"
-" bind_addr=\"192.168.5.1\"\n"
-" loopback=\"true\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:127
-#, no-c-format
-msgid ""
-"Below are the attributes available in the <literal>TCP</literal> element."
-msgstr "下列是 <literal>TCP</literal> 元素里的可用属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:132
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">bind_addr</emphasis> specifies the binding address. "
-"It can also be set with the <literal>-Dbind.address</literal> command line "
-"option at server startup."
-msgstr ""
-"<emphasis role=\"bold\">bind_addr</emphasis> 指定了绑定的地址。它也可以在服务"
-"器启动时用 <literal>-Dbind.address</literal> 命令行选项来设定。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:137
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">start_port, end_port</emphasis> define the range of "
-"TCP ports the server should bind to. The server socket is bound to the first "
-"available port from <literal>start_port</literal>. If no available port is "
-"found (e.g., because of a firewall) before the <literal>end_port</literal>, "
-"the server throws an exception."
-msgstr ""
-"<emphasis role=\"bold\">start_port，end_port</emphasis> 定义了服务器应该绑定"
-"的 TCP 端口范围。服务器套接字绑定从 <literal>start_port</literal> 开始的第一"
-"个可用端口。如果直到 <literal>end_port</literal> 都没有找到可用端口（例如，由"
-"于防火墙的缘故），服务器将抛出一个异常（exception）。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:152
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">conn_expire_time</emphasis> specifies the time (in "
-"milliseconds) after which a connection can be closed by the reaper if no "
-"traffic has been received."
-msgstr ""
-"<emphasis role=\"bold\">conn_expire_time</emphasis> 指定在多久（毫秒数）没有"
-"网络流量后，reaper 可以关闭这个连接。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:157
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">reaper_interval</emphasis> specifies interval (in "
-"milliseconds) to run the reaper. If both values are 0, no reaping will be "
-"done. If either value is > 0, reaping will be enabled."
-msgstr ""
-"<emphasis role=\"bold\">reaper_interval</emphasis> 指定运行 reaper 的时间（毫"
-"秒）。如果两个值都是 0，reaper 将不会运行。如果其中一个是 > 0，reaper 将被"
-"启用。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:165
-#, no-c-format
-msgid "TUNNEL configuration"
-msgstr "TUNNEL 配置"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:166
-#, no-c-format
-msgid ""
-"The TUNNEL protocol uses an external router to send messages. The external "
-"router is known as a <literal>GossipRouter</literal>. Each node has to "
-"register with the router. All messages are sent to the router and forwarded "
-"on to their destinations. The TUNNEL approach can be used to setup "
-"communication with nodes behind firewalls. A node can establish a TCP "
-"connection to the GossipRouter through the firewall (you can use port 80). "
-"The same connection is used by the router to send messages to nodes behind "
-"the firewall. The TUNNEL configuration is defined in the <literal>TUNNEL</"
-"literal> element in the JGroups <literal>Config</literal> element. Here is "
-"an example."
-msgstr ""
-"TUNNEL 协议使用外部的路由器来发送信息。这个外部路由器是 "
-"<literal>GossipRouter</literal>。每个节点都得在这个路由器上注册。所有信息都被"
-"发送到这个路由器并被转发到目的地。TUNNEL 方法可以用来设置与防火墙后面的节点通"
-"信。节点可以穿过防火墙（你可以用 80 端口）和 GossipRouter 建立一个 TCP 连接。"
-"路由器使用同一个连接来发送信息到防火墙后面的节点。TUNNEL 配置在 JGroups "
-"<literal>Config</literal> 元素里的 <literal>TUNNEL</literal> 元素里被定义。下"
-"面是一个例子。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:169
-#, no-c-format
-msgid ""
-"<TUNNEL router_port=\"12001\"\n"
-" router_host=\"192.168.5.1\"/>"
-msgstr ""
-"<TUNNEL router_port=\"12001\"\n"
-" router_host=\"192.168.5.1\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:170
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>TUNNEL</literal> element are listed "
-"below."
-msgstr "下列是 <literal>TUNNEL</literal> 元素里的可用属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:175
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">router_host</emphasis> specifies the host on which "
-"the GossipRouter is running."
-msgstr ""
-"<emphasis role=\"bold\">router_host</emphasis> 指定 GossipRouter 运行在哪个主"
-"机上。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:180
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">router_port</emphasis> specifies the port on which "
-"the GossipRouter is listening."
-msgstr ""
-"<emphasis role=\"bold\">router_port</emphasis> 指定 GossipRouter 侦听的端口。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:185
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">loopback</emphasis> specifies whether to loop "
-"messages back up the stack. The default is <literal>true</literal>."
-msgstr ""
-"<emphasis role=\"bold\">loopback</emphasis> 是否在堆栈里回送信息。它的缺省值"
-"是 <literal>true</literal>。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:195
-#, no-c-format
-msgid "Discovery Protocols"
-msgstr "发现协议（Discovery Protocols）"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:196
-#, fuzzy, no-c-format
-msgid ""
-"The cluster need to maintain a list of current member nodes at all times so "
-"that the load balancer and client interceptor know how to route their "
-"requests. The discovery protocols are used to discover active nodes in the "
-"cluster. All initial nodes are discovered when the cluster starts up. When a "
-"new node joins the cluster later, it is only discovered after the group "
-"membership protocol (GMS, see <xref linkend=\"Other_Configuration_Options-"
-"Group_Membership\"/>) admits it into the group."
-msgstr ""
-"群集系统需要一直维护当前成员节点的列表，这样负载平衡系统（load balancer）和客"
-"户端拦截器（client interceptor）就知道怎样去指引它们的请求。发现协议"
-"（discovery protocols）用来在群集系统里探索活动节点。当群集系统启动时将检测到"
-"所有的初始节点。之后如果有新的节点加入，它只有在组成员协议（group membership "
-"protocol）（GMS，参见 <xref linkend=\"jbosscache-jgroups-other-gms\"/>）批准"
-"后才能被探索（discovered）到。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:199
-#, no-c-format
-msgid ""
-"Since the discovery protocols sit on top of the transport protocol. You can "
-"choose to use different discovery protocols based on your transport "
-"protocol. The discovery protocols are also configured as sub-elements in the "
-"JGroups MBean <literal>Config</literal> element."
-msgstr ""
-"既然发现协议（discovery protocols）处于传输协议之上，你可以根据你的传输协议选"
-"择不同的发现协议。发现协议在 JGroups MBean <literal>Config</literal> 元素里也"
-"被配置成子元素（sub-elements）。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:203
-#, no-c-format
-msgid "PING"
-msgstr "PING"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:204
-#, no-c-format
-msgid ""
-"The PING discovery protocol normally sits on top of the UDP transport "
-"protocol. Each node responds with a unicast UDP datagram back to the sender. "
-"Here is an example PING configuration under the JGroups <literal>Config</"
-"literal> element."
-msgstr ""
-"PING 发现协议（discovery protocol）通常在 UDP 传输协议之上。每个节点用一个单"
-"播的 UDP 数据报文（datagram）来应答发送者。下面是 JGroups <literal>Config</"
-"literal> 元素下 PING 配置的例子。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:207
-#, no-c-format
-msgid ""
-"<PING timeout=\"2000\"\n"
-" num_initial_members=\"2\"/>"
-msgstr ""
-"<PING timeout=\"2000\"\n"
-" num_initial_members=\"2\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:208
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>PING</literal> element are listed "
-"below."
-msgstr "下列是 <literal>PING</literal> 元素里的可用属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:213
-#: JBossCache_And_JGroups_Services.xml:264
-#: JBossCache_And_JGroups_Services.xml:292
-#: JBossCache_And_JGroups_Services.xml:325
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">timeout</emphasis> specifies the maximum number of "
-"milliseconds to wait for any responses."
-msgstr ""
-"<emphasis role=\"bold\">timeout</emphasis> 指定等待应答的最长时间（毫秒数）"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:218
-#: JBossCache_And_JGroups_Services.xml:269
-#: JBossCache_And_JGroups_Services.xml:297
-#: JBossCache_And_JGroups_Services.xml:330
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">num_initial_members</emphasis> specifies the maximum "
-"number of responses to wait for."
-msgstr ""
-"<emphasis role=\"bold\">num_initial_members</emphasis> 指定等待的最大的应答数"
-"量。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:223
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">gossip_host</emphasis> specifies the host on which "
-"the GossipRouter is running."
-msgstr ""
-"<emphasis role=\"bold\">gossip_host</emphasis> 指定 GossipRouter 在哪个主机上"
-"运行。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:228
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">gossip_port</emphasis> specifies the port on which "
-"the GossipRouter is listening on."
-msgstr ""
-"<emphasis role=\"bold\">gossip_port</emphasis> 指定 GossipRouter 所侦听的端"
-"口。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:233
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">gossip_refresh</emphasis> specifies the interval (in "
-"milliseconds) for the lease from the GossipRouter."
-msgstr ""
-"<emphasis role=\"bold\">gossip_refresh</emphasis> 指定 GossipRouter 的租约"
-"（lease）的时间间隔（毫秒数）。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:238
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">initial_hosts</emphasis> is a comma-separated list "
-"of addresses (e.g., <literal>host1[12345],host2[23456]</literal>), which are "
-"pinged for discovery."
-msgstr ""
-"<emphasis role=\"bold\">initial_hosts</emphasis> 是一个用逗号隔开的地址列表"
-"（如：<literal>host1[12345],host2[23456]</literal>），群集系统会 ping 这个列"
-"表来进行探索（discovery）。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:243
-#, no-c-format
-msgid ""
-"If both <literal>gossip_host</literal> and <literal>gossip_port</literal> "
-"are defined, the cluster uses the GossipRouter for the initial discovery. If "
-"the <literal>initial_hosts</literal> is specified, the cluster pings that "
-"static list of addresses for discovery. Otherwise, the cluster uses IP "
-"multicasting for discovery."
-msgstr ""
-"如果<literal>gossip_host</literal> 和 <literal>gossip_port</literal> 都被定义"
-"了，群集系统会使用 GossipRouter 作初始探索（initial discovery）。如果指定了 "
-"<literal>initial_hosts</literal>，群集系统会 ping 这个静态地址列表来进行探"
-"索。否则，群集系统用 IP 多点传送来进行探索。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:247
-#, no-c-format
-msgid ""
-"The discovery phase returns when the <literal>timeout</literal> ms have "
-"elapsed or the <literal>num_initial_members</literal> responses have been "
-"received."
-msgstr ""
-"当已经过了 <literal>timeout</literal> 毫秒后或者已经接收到 "
-"<literal>num_initial_members</literal> 应答后，探索阶段就会返回。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:254
-#, no-c-format
-msgid "TCPGOSSIP"
-msgstr "TCPGOSSIP"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:255
-#, no-c-format
-msgid ""
-"The TCPGOSSIP protocol only works with a GossipRouter. It works essentially "
-"the same way as the PING protocol configuration with valid "
-"<literal>gossip_host</literal> and <literal>gossip_port</literal> "
-"attributes. It works on top of both UDP and TCP transport protocols. Here is "
-"an example."
-msgstr ""
-"TCPGOSSIP 协议只用于 GossipRouter。它和 PING 协议配置基本上一样，有着有效的 "
-"<literal>gossip_host</literal> 和 <literal>gossip_port</literal> 属性。它处"
-"于 UDP 和 TCP 协议的上面。下面是一个例子。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:258
-#, no-c-format
-msgid ""
-"<PING timeout=\"2000\"\n"
-" initial_hosts=\"192.168.5.1[12000],192.168.0.2[12000]\"\n"
-" num_initial_members=\"3\"/>"
-msgstr ""
-"<PING timeout=\"2000\"\n"
-" initial_hosts=\"192.168.5.1[12000],192.168.0.2[12000]\"\n"
-" num_initial_members=\"3\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:259
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>TCPGOSSIP</literal> element are "
-"listed below."
-msgstr "下列是 <literal>TCPGOSSIP</literal> 元素里的可用属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:274
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">initial_hosts</emphasis> is a comma-separated list "
-"of addresses (e.g., <literal>host1[12345],host2[23456]</literal>) for "
-"GossipRouters to register with."
-msgstr ""
-"<emphasis role=\"bold\">initial_hosts</emphasis> 是一个 GossipRouters 用来注"
-"册的用逗号隔开的地址列表（如：<literal>host1[12345],host2[23456]</"
-"literal>）。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:282
-#, no-c-format
-msgid "TCPPING"
-msgstr "TCPPING"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:283
-#, no-c-format
-msgid ""
-"The TCPPING protocol takes a set of known members and ping them for "
-"discovery. This is essentially a static configuration. It works on top of "
-"TCP. Here is an example of the <literal>TCPPING</literal> configuration "
-"element in the JGroups <literal>Config</literal> element."
-msgstr ""
-"TCPPING 协议使用一套知名成员并 ping 它们来进行探索。它基本上是一个静态的配"
-"置。它工作于 TCP 协议的上面。这里是一个 JGroups <literal>Config</literal> 元"
-"素里的 <literal>TCPPING</literal> 配置元素的例子。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:286
-#, no-c-format
-msgid ""
-"<TCPPING timeout=\"2000\"\n"
-" initial_hosts=\"192.168.5.1[7800],192.168.0.2[7800]\"\n"
-" port_range=\"2\"\n"
-" num_initial_members=\"3\"/>"
-msgstr ""
-"<TCPPING timeout=\"2000\"\n"
-" initial_hosts=\"192.168.5.1[7800],192.168.0.2[7800]\"\n"
-" port_range=\"2\"\n"
-" num_initial_members=\"3\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:287
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>TCPPING</literal> element are "
-"listed below."
-msgstr "下列是 <literal>TCPPING</literal> 元素的可用属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:302
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">initial_hosts</emphasis> is a comma-separated list "
-"of addresses (e.g., <literal>host1[12345],host2[23456]</literal>) for "
-"pinging."
-msgstr ""
-"<emphasis role=\"bold\">initial_hosts</emphasis> 是一个用来 pinging 的用逗号"
-"隔开的地址列表（如：<literal>host1[12345],host2[23456]</literal>）。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:307
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">port_range</emphasis> specifies the range of ports "
-"to ping on each host in the <literal>initial_hosts</literal> list. That is "
-"because multiple nodes can run on the same host. In the above example, the "
-"cluster would ping ports 7800, 7801, and 7802 on both hosts."
-msgstr ""
-"<emphasis role=\"bold\">port_range</emphasis> 指定了 <literal>initial_hosts</"
-"literal> 列表里的主机用来 ping 的端口范围。那是因为多个节点可以在同一主机上运"
-"行。在上面的例子里，群集系统将 ping 两个主机上的端口 7800，7801，和 7802。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:315
-#, no-c-format
-msgid "MPING"
-msgstr "MPING"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:316
-#, no-c-format
-msgid ""
-"The MPING protocol is a multicast ping over TCP. It works almost the same "
-"way as PING works on UDP. It does not require external processes "
-"(GossipRouter) or static configuration (initial host list). Here is an "
-"example of the <literal>MPING</literal> configuration element in the JGroups "
-"<literal>Config</literal> element."
-msgstr ""
-"MPING 协议是 TCP 上的多点传送 ping 协议。它和 PING 在 UDP 上工作的方式一样。"
-"它不要求外部的进程（GossipRouter）或静态配置（初始主机列表）。这里是一个 "
-"JGroups <literal>Config</literal> 元素的 <literal>MPING</literal> 配置元素的"
-"例子。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:319
-#, no-c-format
-msgid ""
-"<MPING timeout=\"2000\"\n"
-" bind_to_all_interfaces=\"true\"\n"
-" mcast_addr=\"228.8.8.8\"\n"
-" mcast_port=\"7500\"\n"
-" ip_ttl=\"8\"\n"
-" num_initial_members=\"3\"/>"
-msgstr ""
-"<MPING timeout=\"2000\"\n"
-" bind_to_all_interfaces=\"true\"\n"
-" mcast_addr=\"228.8.8.8\"\n"
-" mcast_port=\"7500\"\n"
-" ip_ttl=\"8\"\n"
-" num_initial_members=\"3\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:320
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>MPING</literal> element are listed "
-"below."
-msgstr "下列是 <literal>MPING</literal> 元素的可用属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:335
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">bind_addr</emphasis> specifies the interface on "
-"which to send and receive multicast packets."
-msgstr ""
-"<emphasis role=\"bold\">bind_addr</emphasis> 指定在哪个接口上发送和接收多点传"
-"送数据包。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:340
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">bind_to_all_interfaces</emphasis> overrides the "
-"<literal>bind_addr</literal> and uses all interfaces in multihome nodes."
-msgstr ""
-"<emphasis role=\"bold\">bind_to_all_interfaces</emphasis> 覆盖了 "
-"<literal>bind_addr</literal> 并使用多宿主节点上的所有接口。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:345
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mcast_addr, mcast_port, ip_ttl</emphasis> attributes "
-"are the same as related attributes in the UDP protocol configuration."
-msgstr ""
-"<emphasis role=\"bold\">mcast_addr，mcast_port，ip_ttl</emphasis> 属性和 UDP "
-"协议配置的相关属性相同。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:355
-#, no-c-format
-msgid "Failure Detection Protocols"
-msgstr "故障检测协议（Failure Detection Protocols）"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:356
-#, no-c-format
-msgid ""
-"The failure detection protocols are used to detect failed nodes. Once a "
-"failed node is detected, the cluster updates its view so that the load "
-"balancer and client interceptors know to avoid the dead node. The failure "
-"detection protocols are configured as sub-elements in the JGroups MBean "
-"<literal>Config</literal> element."
-msgstr ""
-"故障检测协议（failure detection protocols）用来检测发生故障的节点。一旦检测到"
-"了一个发生故障的节点，群集系统会更新它的视图，使负载平衡系统（load balancer）"
-"和客户拦截器（client interceptors）避开死节点。故障检测协议被配置为 JGroups "
-"MBean <literal>Config</literal> 元素里的子元素。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:360
-#, no-c-format
-msgid "<title>FD</title>"
-msgstr "<title>FD</title>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:361
-#, fuzzy, no-c-format
-msgid ""
-"The FD discovery protocol requires each node periodically sends are-you-"
-"alive messages to its neighbor. If the neighbor fails to respond, the "
-"calling node sends a SUSPECT message to the cluster. The current group "
-"coordinator double checks that the suspect node is indeed dead and updates "
-"the cluster's view. Here is an example FD configuration."
-msgstr ""
-"FD 发现协议（FD discovery protocol）要求每个节点定期地发送 are-you-alive 信息"
-"给它的邻居节点。如果这个邻居没有应答，呼叫节点将给群集系统发送一个 SUSPECT 信"
-"息。当前的 group coordinator 会复核这个可能有问题的节点是否真的已经崩溃了，并"
-"更新群集系统的视图。这里是一个 FD 配置的例子。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:364
-#, no-c-format
-msgid ""
-"<FD timeout=\"2000\"\n"
-" max_tries=\"3\"\n"
-" shun=\"true\"/>"
-msgstr ""
-"<FD timeout=\"2000\"\n"
-" max_tries=\"3\"\n"
-" shun=\"true\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:365
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>FD</literal> element are listed "
-"below."
-msgstr "下列是 <literal>FD</literal> 元素的可用属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:370
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">timeout</emphasis> specifies the maximum number of "
-"milliseconds to wait for the responses to the are-you-alive messages."
-msgstr ""
-"<emphasis role=\"bold\">timeout</emphasis> 指定对 are-you-alive 信息的应答的"
-"最长等待时间（毫秒数）。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:375
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">max_tries</emphasis> specifies the number of missed "
-"are-you-alive messages from a node before the node is suspected."
-msgstr ""
-"<emphasis role=\"bold\">max_tries</emphasis> 指定在一个节点被怀疑为崩溃前，所"
-"丢失的 are-you-alive 信息的次数。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:380
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">shun</emphasis> specifies whether a failed node will "
-"be shunned. Once shunned, the node will be expelled from the cluster even if "
-"it comes back later. The shunned node would have to re-join the cluster "
-"through the discovery process."
-msgstr ""
-"<emphasis role=\"bold\">shun</emphasis> 指定崩溃的节点是否该被剔除"
-"（shunned）。一旦被剔除，这个节点将从群集里开除，即使之后它又恢复了。被剔除的"
-"节点可以通过探索过程（discovery process）重新加入到群集系统里来。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:386
-#, no-c-format
-msgid ""
-"Regular traffic from a node counts as if it is a live. So, the are-you-alive "
-"messages are only sent when there is no regular traffic to the node for "
-"sometime."
-msgstr ""
-"从某个节点的有规律的网络流量可以判定它是否正常工作。所以，are-you-alive 信息"
-"只是在节点有一段时间没有有规律的网络流量时才发送。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:393
-#, no-c-format
-msgid "FD_SOCK"
-msgstr "FD_SOCK"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:394
-#, fuzzy, no-c-format
-msgid ""
-"The are-you-alive messages in the FD protocol could increase the network "
-"load when there are many nodes. It could also produce false suspicions. For "
-"instance, if the network is too busy and the timeout is too short, nodes "
-"could be falsely suspected. Also, if one node is suspended in a debugger or "
-"profiler, it could also be suspected and shunned. The FD_SOCK protocol "
-"addresses the above issues by suspecting node failures only when a regular "
-"TCP connection to the node fails. However, the problem with such passive "
-"detection is that hung nodes will not be detected until it is accessed and "
-"the TCP timeouts after several minutes. FD_SOCK works best in high load "
-"networks where all nodes are frequently accessed. The simplest FD_SOCK "
-"configuration does not take any attribute. You can just declare an empty "
-"<literal>FD_SOCK</literal> element in JGroups's <literal>Config</"
-"literal> element."
-msgstr ""
-"当有很多节点时， FD 协议的 are-you-alive 信息会增加网络的负载。它也会产生误"
-"判。例如，如果网络太繁忙了而且超时时间（timeout）设置的很短，节点就有可能被误"
-"怀疑为崩溃了。此外，如果节点在调试器（debugger）或剖析工具（profiler）里被挂"
-"起时，它有可能被怀疑或剔除（shunned）。为了解决上述问题，FD_SOCK 协议依据只有"
-"有规律的与节点的 TCP 连接失败后才怀疑节点崩溃。然而，这种消极检测的问题是，挂"
-"起的节点只有被访问时或者 TCP 连接超时几分钟后才会被检测到。FD_SOCK 在所有节点"
-"都被频繁访问的高负载的网络里表现最好。最简单的 FD_SOCK 配置不要设置任何属性。"
-"你可以只在 JGroups 的 <literal>Config</literal> 元素里声明一个空的 "
-"<literal>FD_SOCK</literal> 就可以了。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:397
-#, no-c-format
-msgid "<FD_SOCK/>"
-msgstr "<FD_SOCK/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:398
-#, no-c-format
-msgid ""
-"There is only one optional attribute in the <literal>FD_SOCK</literal> "
-"element."
-msgstr "<literal>FD_SOCK</literal> 元素只有一个可选属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:403
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">srv_sock_bind_addr</emphasis> specifies the "
-"interface to which the server socket should bind to. If it is omitted, the "
-"<literal>-D bind.address</literal> property from the server startup command "
-"line is used."
-msgstr ""
-"<emphasis role=\"bold\">srv_sock_bind_addr</emphasis> 指定服务器套接字应该绑"
-"定的接口。如果它被忽略，服务器启动时命令行里的 <literal>-D bind.address</"
-"literal> 属性将被使用。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:411
-#, no-c-format
-msgid "FD_SIMPLE"
-msgstr "FD_SIMPLE"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:412
-#, fuzzy, no-c-format
-msgid ""
-"The FD_SIMPLE protocol is a more tolerant (less false suspicions) protocol "
-"based on are-you-alive messages. Each node periodically sends are-you-alive "
-"messages to a randomly chosen node and wait for a response. If a response "
-"has not been received within a certain timeout time, a counter associated "
-"with that node will be incremented. If the counter exceeds a certain value, "
-"that node will be suspected. When a response to an are-you-alive message is "
-"received, the counter resets to zero. Here is an example configuration for "
-"the <literal>FD_SIMPLE</literal> protocol."
-msgstr ""
-"FD_SIMPLE 协议是一个基于 are-you-alive 信息的更加宽容（更少误判）的协议。每个"
-"节点定期地发送 are-you-alive 信息给随机选取的节点然后等待应答。如果在某一超时"
-"时间内还没有收到应答，和这个节点相关的计数器将增加。如果计数器超过了某一个"
-"值，这个节点就会被怀疑。当接收到对 are-you-alive 信息的应答时,这个计数器将清"
-"零。下面是 <literal>FD_SIMPLE</literal> 协议的一个配置例子。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:415
-#, no-c-format
-msgid ""
-"<FD_SIMPLE timeout=\"2000\"\n"
-" max_missed_hbs=\"10\"/>"
-msgstr ""
-"<FD_SIMPLE timeout=\"2000\"\n"
-" max_missed_hbs=\"10\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:416
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>FD_SIMPLE</literal> element are "
-"listed below."
-msgstr "下列是 <literal>FD_SIMPLE</literal> 元素的可用属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:421
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">timeout</emphasis> specifies the timeout (in "
-"milliseconds) for the are-you-alive message. If a response is not received "
-"within timeout, the counter for the target node is increased."
-msgstr ""
-"<emphasis role=\"bold\">timeout</emphasis> 指定对 are-you-alive 信息应答的以"
-"毫秒为单位的超时时间。如果在这个时间内没有收到应答，目标节点的计数器将增加。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:426
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">max_missed_hbs</emphasis> specifies maximum number "
-"of are-you-alive messages (i.e., the counter value) a node can miss before "
-"it is suspected failure."
-msgstr ""
-"<emphasis role=\"bold\">max_missed_hbs</emphasis> 指定节点被怀疑为崩溃前可以"
-"丢失的 are-you-alive 信息（也就是计数器值）的最高次数。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:436
-#, no-c-format
-msgid "Reliable Delivery Protocols"
-msgstr "可靠传输协议（Reliable Delivery Protocols）"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:437
-#, no-c-format
-msgid ""
-"The reliable delivery protocols in the JGroups stack ensure that data "
-"pockets are actually delivered in the right order (FIFO) to the destination "
-"node. The basis for reliable message delivery is positive and negative "
-"delivery acknowledgments (ACK and NAK). In the ACK mode, the sender resends "
-"the message until the acknowledgment is received from the receiver. In the "
-"NAK mode, the receiver requests retransmission when it discovers a gap."
-msgstr ""
-"JGroups 栈里的可靠传输协议（reliable delivery protocols）确保数据包按正确的顺"
-"序（FIFO）正确地递送到目的节点。可靠的信息递送的基础是肯定和否定的递送确认"
-"（delivery acknowledgments）（ACK 和 NAK）。在 ACK 模式下，发送者重新发送信息"
-"直到收到接收者的确认。在 NAK 模式下，当接收者发现一个间断时，它会请求重新传"
-"送。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:441
-#, no-c-format
-msgid "UNICAST"
-msgstr "UNICAST"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:442
-#, no-c-format
-msgid ""
-"The UNICAST protocol is used for unicast messages. It uses ACK. It is "
-"configured as a sub-element under the JGroups <literal>Config</literal> "
-"element. Here is an example configuration for the <literal>UNICAST</literal> "
-"protocol."
-msgstr ""
-"UNICAST 协议用于单播信息。它使用 ACK。它被配置成 JGroups <literal>Config</"
-"literal> 元素下的一个子元素。这里有一个配置 <literal>UNICAST</literal> 协议的"
-"例子。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:445
-#, no-c-format
-msgid "<UNICAST timeout=\"100,200,400,800\"/>"
-msgstr "<UNICAST timeout=\"100,200,400,800\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:446
-#, no-c-format
-msgid ""
-"There is only one configurable attribute in the <literal>UNICAST</literal> "
-"element."
-msgstr "<literal>UNICAST</literal> 元素里只有一个可配置属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:451
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">timeout</emphasis> specifies the retransmission "
-"timeout (in milliseconds). For instance, if the timeout is \"100,200,400,800"
-"\", the sender resends the message if it hasn't received an ACK after "
-"100 ms the first time, and the second time it waits for 200 ms before "
-"resending, and so on."
-msgstr ""
-"<emphasis role=\"bold\">timeout</emphasis> 指定重新传送的超时时间（毫秒数）。"
-"例如，如果这个超时时间是 \"100,200,400,800\"，如果发送者在 100 毫秒后还没有接"
-"到 ACK，它会重新发送信息，第二此重发会在 200 毫秒后，以此类推。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:459
-#, no-c-format
-msgid "NAKACK"
-msgstr "NAKACK"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:460
-#, no-c-format
-msgid ""
-"The NAKACK protocol is used for multicast messages. It uses NAK. Under this "
-"protocol, each message is tagged with a sequence number. The receiver keeps "
-"track of the sequence numbers and deliver the messages in order. When a gap "
-"in the sequence number is detected, the receiver asks the sender to "
-"retransmit the missing message. The NAKACK protocol is configured as the "
-"<literal>pbcast.NAKACK</literal> sub-element under the JGroups "
-"<literal>Config</literal> element. Here is an example configuration."
-msgstr ""
-"NAKACK 协议用于多点传送信息。它使用 NAK。在这个协议下，每个信息用一个序列号标"
-"识。接收者根据这个序列号来按顺序递送信息。当检测到序列号存在一个间断时，接收"
-"者会要求发送者重新传送丢失的信息。NAKACK 协议被配置为 JGroups "
-"<literal>Config</literal> 元素下的 <literal>pbcast.NAKACK</literal> 子元素。"
-"这里有一个配置示例。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:463
-#, no-c-format
-msgid ""
-"<pbcast.NAKACK\n"
-" max_xmit_size=\"8192\"\n"
-" use_mcast_xmit=\"true\" \n"
-" retransmit_timeout=\"600,1200,2400,4800\"/>"
-msgstr ""
-"<pbcast.NAKACK\n"
-" max_xmit_size=\"8192\"\n"
-" use_mcast_xmit=\"true\" \n"
-" retransmit_timeout=\"600,1200,2400,4800\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:464
-#, no-c-format
-msgid ""
-"The configurable attributes in the <literal>pbcast.NAKACK</literal> element "
-"are as follows."
-msgstr "下列是 <literal>pbcast.NAKACK</literal> 元素的可配置属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:469
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">retransmit_timeout</emphasis> specifies the "
-"retransmission timeout (in milliseconds). It is the same as the "
-"<literal>timeout</literal> attribute in the UNICAST protocol."
-msgstr ""
-"<emphasis role=\"bold\">retransmit_timeout</emphasis> 指定重发的超时时间（毫"
-"秒数）。它和 UNICAST 协议里的 <literal>timeout</literal> 属性是一样的。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:474
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">use_mcast_xmit</emphasis> determines whether the "
-"sender should send the retransmission to the entire cluster rather than just "
-"the node requesting it. This is useful when the sender drops the pocket -- "
-"so we do not need to retransmit for each node."
-msgstr ""
-"<emphasis role=\"bold\">use_mcast_xmit</emphasis> 决定发送者是否应该重发给整"
-"个群集而不只是请求的节点。这在发送者取消数据包时很有用 - 我们不需要对每个节点"
-"都重发。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:479
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">max_xmit_size</emphasis> specifies maximum size for "
-"a bundled retransmission, if multiple packets are reported missing."
-msgstr ""
-"<emphasis role=\"bold\">max_xmit_size</emphasis> 指定当多个数据包丢失时，捆绑"
-"在一起的重发的最大规模。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:484
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">discard_delivered_msgs</emphasis> specifies whether "
-"to discard delivery messages on the receiver nodes. By default, we save all "
-"delivered messages. However, if we only ask the sender to resend their "
-"messages, we can enable this option and discard delivered messages."
-msgstr ""
-"<emphasis role=\"bold\">discard_delivered_msgs</emphasis> 指定是否丢弃接收节"
-"点上的递送信息。在缺省情况下，我们保存所有的递送的信息。然而，如果我们只需要"
-"发送者重发信息，我们就可以启用这个选项来丢弃递送的信息。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:494
-#, no-c-format
-msgid "Other Configuration Options"
-msgstr "其他配置选项"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:495
-#, no-c-format
-msgid ""
-"In addition to the protocol stacks, you can also configure JGroups network "
-"services in the <literal>Config</literal> element."
-msgstr ""
-"除了协议栈以外，你也可以在 <literal>Config</literal> 元素里配置 JGroups 网络"
-"服务。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:499
-#, no-c-format
-msgid "Group Membership"
-msgstr "组成员资格（Group Membership）"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:500
-#, no-c-format
-msgid ""
-"The group membership service in the JGroups stack maintains a list of active "
-"nodes. It handles the requests to join and leave the cluster. It also "
-"handles the SUSPECT messages sent by failure detection protocols. All nodes "
-"in the cluster, as well as the load balancer and client side interceptors, "
-"are notified if the group membership changes. The group membership service "
-"is configured in the <literal>pbcast.GMS</literal> sub-element under the "
-"JGroups <literal>Config</literal> element. Here is an example configuration."
-msgstr ""
-"JGroups 栈里的组成员资格（group membership）服务维护一个活动节点的列表。它处"
-"理加入和离开群集系统的请求。它也处理故障检测协议（failure detection "
-"protocols）发送的 SUSPECT 信息。当组成员资格有变动时，它通知群集系统里的所有"
-"节点，负载平衡系统（load balancer）和客户端拦截器（client side "
-"interceptors）。组成员资格（group membership）服务可以在 JGroups "
-"<literal>Config</literal> 元素下的 <literal>pbcast.GMS</literal> 子元素里配"
-"置。这里是一个配置示例。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:503
-#, no-c-format
-msgid ""
-"<pbcast.GMS print_local_addr=\"true\"\n"
-" join_timeout=\"3000\"\n"
-" down_thread=\"false\" \n"
-" join_retry_timeout=\"2000\"\n"
-" shun=\"true\"/>"
-msgstr ""
-"<pbcast.GMS print_local_addr=\"true\"\n"
-" join_timeout=\"3000\"\n"
-" down_thread=\"false\" \n"
-" join_retry_timeout=\"2000\"\n"
-" shun=\"true\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:504
-#, no-c-format
-msgid ""
-"The configurable attributes in the <literal>pbcast.GMS</literal> element are "
-"as follows."
-msgstr "下列是 <literal>pbcast.GMS</literal> 元素里的可配置属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:509
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">join_timeout</emphasis> specifies the maximum number "
-"of milliseconds to wait for a new node JOIN request to succeed. Retry "
-"afterwards."
-msgstr ""
-"<emphasis role=\"bold\">join_timeout</emphasis> 指定了等待新节点 JOIN 请求成"
-"功的最长时间（毫秒数）。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:514
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">join_retry_timeout</emphasis> specifies the maximum "
-"number of milliseconds to wait after a failed JOIN to re-submit it."
-msgstr ""
-"<emphasis role=\"bold\">join_retry_timeout</emphasis> 指定 JOIN 失败后重新递"
-"交前所等待的时间（毫秒数）。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:519
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">print_local_addr</emphasis> specifies whether to "
-"dump the node's own address to the output when started."
-msgstr ""
-"<emphasis role=\"bold\">print_local_addr</emphasis> 指定是否在启动时输出节点"
-"自己的地址。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:524
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">shun</emphasis> specifies whether a node should shun "
-"itself if it receives a cluster view that it is not a member node."
-msgstr ""
-"<emphasis role=\"bold\">shun</emphasis> 指定如果收到指明自己并非成员节点的群"
-"集视图，节点是否剔除（shun）自己。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:529
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">disable_initial_coord</emphasis> specifies whether "
-"to prevent this node as the cluster coordinator."
-msgstr ""
-"<emphasis role=\"bold\">disable_initial_coord</emphasis> 指定是否阻止这个节点"
-"成为群集控制点（cluster coordinator）。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:537
-#, no-c-format
-msgid "Flow Control"
-msgstr "流量控制（Flow Control）"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:538
-#, fuzzy, no-c-format
-msgid ""
-"The flow control service tries to adapt the sending data rate and the "
-"receiving data among nodes. If a sender node is too fast, it might overwhelm "
-"the receiver node and result in dropped packets that have to be "
-"retransmitted. In JGroups, the flow control is implemented via a credit-"
-"based system. The sender and receiver nodes have the same number of credits "
-"(bytes) to start with. The sender subtracts credits by the number of bytes "
-"in messages it sends. The receiver accumulates credits for the bytes in the "
-"messages it receives. When the sender's credit drops to a threshold, the "
-"receivers sends some credit to the sender. If the sender's credit is "
-"used up, the sender blocks until it receives credits from the receiver. The "
-"flow control service is configured in the <literal>FC</literal> sub-element "
-"under the JGroups <literal>Config</literal> element. Here is an example "
-"configuration."
-msgstr ""
-"流量控制（flow control）服务试图在节点间控制发送和接收数据传输率。如果一个节"
-"点发送的过快，它可能会使接收节点难以负荷，导致数据包的丢失而且不得不重新发"
-"送。在 JGroups 里，流量控制通过基于信用值（credit-based）的系统来实现。发送和"
-"接收节点具有相同的初始信用值（credits）（字节数）。发送者减去所发送信息的字节"
-"数，而接收者积累它接收到的信息的字节数。当发送者的信用值减少至某一极限时，接"
-"收者将把一些信用值发送给发送者。如果发送者的信用值被用光了，发送者将暂停，直"
-"到它收到接收者的信用值为止。流量控制服务在 JGroups <literal>Config</literal> "
-"元素下的 <literal>FC</literal> 子元素里配置。下面是一个配置示例。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:541
-#, no-c-format
-msgid ""
-"<FC max_credits=\"1000000\"\n"
-" down_thread=\"false\" \n"
-" min_threshold=\"0.10\"/>"
-msgstr ""
-"<FC max_credits=\"1000000\"\n"
-" down_thread=\"false\" \n"
-" min_threshold=\"0.10\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:542
-#: JBossCache_And_JGroups_Services.xml:611
-#, no-c-format
-msgid ""
-"The configurable attributes in the <literal>FC</literal> element are as "
-"follows."
-msgstr "下列是 <literal>FC</literal> 元素的可配置属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:547
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">max_credits</emphasis> specifies the maximum number "
-"of credits (in bytes). This value should be smaller than the JVM heap size."
-msgstr ""
-"<emphasis role=\"bold\">max_credits</emphasis> 指定最大的信用值（字节数）。这"
-"个值应该小于 JVM 的 heap size。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:552
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">min_credits</emphasis> specifies the threshold "
-"credit on the sender, below which the receiver should send in more credits."
-msgstr ""
-"<emphasis role=\"bold\">min_credits</emphasis> 指定发送者的极限信用值，如果低"
-"于这个值，接收者就应该发送更多的信用值给发送者。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:557
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">min_threshold</emphasis> specifies percentage value "
-"of the threshold. It overrides the <literal>min_credits</literal> attribute."
-msgstr ""
-"<emphasis role=\"bold\">min_threshold</emphasis> 指定极限值的百分比。它可以覆"
-"盖 <literal>min_credits</literal> 属性。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:565
-#, no-c-format
-msgid "State Transfer"
-msgstr "状态传输（State Transfer）"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:566
-#, no-c-format
-msgid ""
-"The state transfer service transfers the state from an existing node (i.e., "
-"the cluster coordinator) to a newly joining node. It is configured in the "
-"<literal>pbcast.STATE_TRANSFER</literal> sub-element under the JGroups "
-"<literal>Config</literal> element. It does not have any configurable "
-"attribute. Here is an example configuration."
-msgstr ""
-"状态传输服务（state transfer service）把状态从一个现存的节点（就是群集控制"
-"点）传输到新加入的节点上。它可以在 JGroups <literal>Config</literal> 元素下"
-"的 <literal>pbcast.STATE_TRANSFER</literal> 子元素里配置。它没有任何可配置属"
-"性。下面是一个配置示例。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:569
-#, no-c-format
-msgid ""
-"<pbcast.STATE_TRANSFER \n"
-" down_thread=\"false\"\n"
-" up_thread=\"false\"/>"
-msgstr ""
-"<pbcast.STATE_TRANSFER \n"
-" down_thread=\"false\"\n"
-" up_thread=\"false\"/>"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:573
-#, no-c-format
-msgid "Distributed Garbage Collection"
-msgstr "分布式垃圾收集（Distributed Garbage Collection）"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:574
-#, no-c-format
-msgid ""
-"In a JGroups cluster, all nodes have to store all messages received for "
-"potential retransmission in case of a failure. However, if we store all "
-"messages forever, we will run out of memory. So, the distributed garbage "
-"collection service in JGroups periodically purges messages that have seen by "
-"all nodes from the memory in each node. The distributed garbage collection "
-"service is configured in the <literal>pbcast.STABLE</literal> sub-element "
-"under the JGroups <literal>Config</literal> element. Here is an example "
-"configuration."
-msgstr ""
-"在 JGroups 群集系统里，在失败的情况下，所有的节点都得保存所有接收到的信息，用"
-"于可能发生的重新传送。然而，如果我们一直保存这些信息，就会用光所有的内存。所"
-"以，JGroups 的分布式垃圾收集（distributed garbage collection ）服务定期地从每"
-"个节点的内存里清理所有节点都已经看过的信息。我们在 JGroups <literal>Config</"
-"literal> 元素下的 <literal>pbcast.STABLE</literal> 子元素里配置分布式垃圾收集"
-"（distributed garbage collection ）服务。下面是一个配置示例。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:577
-#, no-c-format
-msgid ""
-"<pbcast.STABLE stability_delay=\"1000\"\n"
-" desired_avg_gossip=\"5000\" \n"
-" down_thread=\"false\"\n"
-" max_bytes=\"250000\"/>"
-msgstr ""
-"<pbcast.STABLE stability_delay=\"1000\"\n"
-" desired_avg_gossip=\"5000\" \n"
-" down_thread=\"false\"\n"
-" max_bytes=\"250000\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:578
-#, no-c-format
-msgid ""
-"The configurable attributes in the <literal>pbcast.STABLE</literal> element "
-"are as follows."
-msgstr "下列是 <literal>pbcast.STABLE</literal> 元素里的可配置属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:583
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">desired_avg_gossip</emphasis> specifies intervals "
-"(in milliseconds) of garbage collection runs. Value <literal>0</literal> "
-"disables this service."
-msgstr ""
-"<emphasis role=\"bold\">desired_avg_gossip</emphasis> 指定垃圾收集（garbage "
-"collection）服务运行的时间间隔（毫秒数）。它如果为 0，这个服务将不会运行。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:588
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">max_bytes</emphasis> specifies the maximum number of "
-"bytes received before the cluster triggers a garbage collection run. Value "
-"<literal>0</literal> disables this service."
-msgstr ""
-"<emphasis role=\"bold\">max_bytes</emphasis> 指定了在群集系统触发垃圾收集"
-"（garbage collection）服务之前，能接收的最多字节数。它如果为 0，这个服务将不"
-"会运行。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:593
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">max_gossip_runs</emphasis> specifies the maximum "
-"garbage collections runs before any changes. After this number is reached, "
-"there is no garbage collection until the message is received."
-msgstr ""
-"<emphasis role=\"bold\">max_gossip_runs</emphasis> 指定在任何改变之前，垃圾收"
-"集（garbage collection）服务运行的最大次数。达到这个数值后，将不会有垃圾收集"
-"（garbage collection）服务，直到收到指令。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:599
-#, no-c-format
-msgid ""
-"Set the <literal>max_bytes</literal> attribute when you have a high traffic "
-"cluster."
-msgstr "当你有一个大流量的群集系统时，设置 <literal>max_bytes</literal> 属性。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:606
-#, no-c-format
-msgid "Merging"
-msgstr "Merging"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:607
-#, no-c-format
-msgid ""
-"When a network error occurs, the cluster might be partitioned into several "
-"different partitions. JGroups has a MERGE service that allows the "
-"coordinators in partitions to communicate with each other and form a single "
-"cluster back again. The flow control service is configured in the "
-"<literal>MERGE2</literal> sub-element under the JGroups <literal>Config</"
-"literal> element. Here is an example configuration."
-msgstr ""
-"当有网络错误发生时，群集系统可能分为己个不同的子分区（partitions）。JGroups "
-"有一个 MERGE 服务，它允许分区里的控制点（coordinators）相互通信且再次组成单一"
-"群集系统。流量控制服务可以在 JGroups <literal>Config</literal> 元素下的 "
-"<literal>MERGE2</literal> 子元素里配置。下面是一个配置示例。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:610
-#, no-c-format
-msgid ""
-"<MERGE2 max_interval=\"10000\"\n"
-" min_interval=\"2000\"/>"
-msgstr ""
-"<MERGE2 max_interval=\"10000\"\n"
-" min_interval=\"2000\"/>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:616
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">max_interval</emphasis> specifies the maximum number "
-"of milliseconds to send out a MERGE message."
-msgstr ""
-"<emphasis role=\"bold\">max_interval</emphasis> 指定发送 MERGE 信息的最大时间"
-"间隔（毫秒数）。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:621
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">min_interval</emphasis> specifies the minimum number "
-"of milliseconds to send out a MERGE message."
-msgstr ""
-"<emphasis role=\"bold\">min_interval</emphasis> 指定发送 MERGE 信息的最小时间"
-"间隔（毫秒数）。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:626
-#, no-c-format
-msgid ""
-"JGroups chooses a random value between <literal>min_interval</literal> and "
-"<literal>max_interval</literal> to send out the MERGE message."
-msgstr ""
-"JGroups 在 <literal>min_interval</literal> 之间 <literal>max_interval</"
-"literal> 选取一个随机值来发送 MERGE 信息。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:630
-#, no-c-format
-msgid ""
-"The cluster states are not merged in a merger. This has to be done by the "
-"application."
-msgstr "群集状态不会在 merger 里被合并（merged）。这得要应用程序来完成。"
-
-#. Tag: title
-#: JBossCache_And_JGroups_Services.xml:641
-#, no-c-format
-msgid "JBossCache Configuration"
-msgstr "JBossCache 配置"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:642
-#, no-c-format
-msgid ""
-"JBoss Cache provides distributed cache and state replication services for "
-"the JBoss cluster. A JBoss cluster can have multiple JBoss Cache MBeans "
-"(known as the <literal>TreeCache</literal> MBean), one for HTTP session "
-"replication, one for stateful session beans, one for cached entity beans, "
-"etc. A generic <literal>TreeCache</literal> MBean configuration is listed "
-"below. Application specific <literal>TreeCache</literal> MBean "
-"configurations are covered in later chapters when those applications are "
-"discussed."
-msgstr ""
-"JBoss Cache 为 JBoss 群集系统提供分布式的缓存和状态复制服务。JBoss 群集系统可"
-"以有多个 JBoss Cache MBeans（称作 <literal>TreeCache</literal> MBean），一个"
-"用于 HTTP 会话复制，一个用于 stateful session beans，一个用于 cached entity "
-"beans，等等。下列是一个普通的 <literal>TreeCache</literal> MBean 配置。在后"
-"面的章节讨论应用程序时，我们会提及与应用程序相关的 <literal>TreeCache</"
-"literal> MBean 配置。"
-
-#. Tag: programlisting
-#: JBossCache_And_JGroups_Services.xml:645
-#, no-c-format
-msgid ""
-"<mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=TreeCache\">\n"
-" \n"
-" <depends>jboss:service=Naming</depends> \n"
-" <depends>jboss:service=TransactionManager</depends> \n"
-"\n"
-" <! -- Configure the TransactionManager --> \n"
-" <attribute name=\"TransactionManagerLookupClass\">\n"
-" org.jboss.cache.DummyTransactionManagerLookup\n"
-" </attribute> \n"
-"\n"
-" <! -- \n"
-" Node locking level : SERIALIZABLE\n"
-" REPEATABLE_READ (default)\n"
-" READ_COMMITTED\n"
-" READ_UNCOMMITTED\n"
-" NONE \n"
-" --> \n"
-" <attribute name=\"IsolationLevel\">REPEATABLE_READ</"
-"attribute> \n"
-"\n"
-" <! -- Valid modes are LOCAL\n"
-" REPL_ASYNC\n"
-" REPL_SYNC\n"
-" --> \n"
-" <attribute name=\"CacheMode\">LOCAL</attribute>\n"
-" \n"
-" <! -- Name of cluster. Needs to be the same for all clusters, in "
-"order\n"
-" to find each other --> \n"
-" <attribute name=\"ClusterName\">TreeCache-Cluster</"
-"attribute> \n"
-"\n"
-" <! -- The max amount of time (in milliseconds) we wait until the\n"
-" initial state (ie. the contents of the cache) are \n"
-" retrieved from existing members in a clustered environment\n"
-" --> \n"
-" <attribute name=\"InitialStateRetrievalTimeout\">5000</"
-"attribute> \n"
-"\n"
-" <! -- Number of milliseconds to wait until all responses for a\n"
-" synchronous call have been received.\n"
-" --> \n"
-" <attribute name=\"SyncReplTimeout\">10000</attribute> \n"
-"\n"
-" <! -- Max number of milliseconds to wait for a lock acquisition --"
-"> \n"
-" <attribute name=\"LockAcquisitionTimeout\">15000</"
-"attribute> \n"
-"\n"
-" <! -- Name of the eviction policy class. --> \n"
-" <attribute name=\"EvictionPolicyClass\">\n"
-" org.jboss.cache.eviction.LRUPolicy\n"
-" </attribute> \n"
-"\n"
-" <! -- Specific eviction policy configurations. This is LRU --> \n"
-" <attribute name=\"EvictionPolicyConfig\">\n"
-" <config>\n"
-" <attribute name=\"wakeUpIntervalSeconds\">5</"
-"attribute> \n"
-" <!-- Cache wide default --> \n"
-" <region name=\"/_default_\">\n"
-" <attribute name=\"maxNodes\">5000</attribute> \n"
-" <attribute name=\"timeToLiveSeconds\">1000</"
-"attribute> \n"
-" </region>\n"
-"\n"
-" <region name=\"/org/jboss/data\">\n"
-" <attribute name=\"maxNodes\">5000</attribute> \n"
-" <attribute name=\"timeToLiveSeconds\">1000</"
-"attribute> \n"
-" </region>\n"
-"\n"
-" <region name=\"/org/jboss/test/data\">\n"
-" <attribute name=\"maxNodes\">5</attribute> \n"
-" <attribute name=\"timeToLiveSeconds\">4</"
-"attribute> \n"
-" </region>\n"
-" </config>\n"
-" </attribute>\n"
-"\n"
-" <attribute name=\"CacheLoaderClass\">\n"
-" org.jboss.cache.loader.bdbje.BdbjeCacheLoader\n"
-" </attribute>\n"
-" \n"
-" <attribute name=\"CacheLoaderConfig\">\n"
-" location=c:\\\\tmp\n"
-" </attribute>\n"
-" <attribute name=\"CacheLoaderShared\">true</attribute>\n"
-" <attribute name=\"CacheLoaderPreload\">\n"
-" /a/b/c,/all/my/objects\n"
-" </attribute>\n"
-" <attribute name=\"CacheLoaderFetchTransientState\">false</"
-"attribute>\n"
-" <attribute name=\"CacheLoaderFetchPersistentState\">true</"
-"attribute>\n"
-" \n"
-" <attribute name=\"ClusterConfig\">\n"
-" ... JGroups config for the cluster ...\n"
-" </attribute>\n"
-"</mbean>"
-msgstr ""
-"<mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=TreeCache\">\n"
-" \n"
-" <depends>jboss:service=Naming</depends> \n"
-" <depends>jboss:service=TransactionManager</depends> \n"
-"\n"
-" <! -- Configure the TransactionManager --> \n"
-" <attribute name=\"TransactionManagerLookupClass\">\n"
-" org.jboss.cache.DummyTransactionManagerLookup\n"
-" </attribute> \n"
-"\n"
-" <! -- \n"
-" Node locking level : SERIALIZABLE\n"
-" REPEATABLE_READ (default)\n"
-" READ_COMMITTED\n"
-" READ_UNCOMMITTED\n"
-" NONE \n"
-" --> \n"
-" <attribute name=\"IsolationLevel\">REPEATABLE_READ</"
-"attribute> \n"
-"\n"
-" <! -- Valid modes are LOCAL\n"
-" REPL_ASYNC\n"
-" REPL_SYNC\n"
-" --> \n"
-" <attribute name=\"CacheMode\">LOCAL</attribute>\n"
-" \n"
-" <! -- Name of cluster. Needs to be the same for all clusters, in "
-"order\n"
-" to find each other --> \n"
-" <attribute name=\"ClusterName\">TreeCache-Cluster</"
-"attribute> \n"
-"\n"
-" <! -- The max amount of time (in milliseconds) we wait until the\n"
-" initial state (ie. the contents of the cache) are \n"
-" retrieved from existing members in a clustered environment\n"
-" --> \n"
-" <attribute name=\"InitialStateRetrievalTimeout\">5000</"
-"attribute> \n"
-"\n"
-" <! -- Number of milliseconds to wait until all responses for a\n"
-" synchronous call have been received.\n"
-" --> \n"
-" <attribute name=\"SyncReplTimeout\">10000</attribute> \n"
-"\n"
-" <! -- Max number of milliseconds to wait for a lock acquisition --"
-"> \n"
-" <attribute name=\"LockAcquisitionTimeout\">15000</"
-"attribute> \n"
-"\n"
-" <! -- Name of the eviction policy class. --> \n"
-" <attribute name=\"EvictionPolicyClass\">\n"
-" org.jboss.cache.eviction.LRUPolicy\n"
-" </attribute> \n"
-"\n"
-" <! -- Specific eviction policy configurations. This is LRU --> \n"
-" <attribute name=\"EvictionPolicyConfig\">\n"
-" <config>\n"
-" <attribute name=\"wakeUpIntervalSeconds\">5</"
-"attribute> \n"
-" <!-- Cache wide default --> \n"
-" <region name=\"/_default_\">\n"
-" <attribute name=\"maxNodes\">5000</attribute> \n"
-" <attribute name=\"timeToLiveSeconds\">1000</"
-"attribute> \n"
-" </region>\n"
-"\n"
-" <region name=\"/org/jboss/data\">\n"
-" <attribute name=\"maxNodes\">5000</attribute> \n"
-" <attribute name=\"timeToLiveSeconds\">1000</"
-"attribute> \n"
-" </region>\n"
-"\n"
-" <region name=\"/org/jboss/test/data\">\n"
-" <attribute name=\"maxNodes\">5</attribute> \n"
-" <attribute name=\"timeToLiveSeconds\">4</"
-"attribute> \n"
-" </region>\n"
-" </config>\n"
-" </attribute>\n"
-"\n"
-" <attribute name=\"CacheLoaderClass\">\n"
-" org.jboss.cache.loader.bdbje.BdbjeCacheLoader\n"
-" </attribute>\n"
-" \n"
-" <attribute name=\"CacheLoaderConfig\">\n"
-" location=c:\\\\tmp\n"
-" </attribute>\n"
-" <attribute name=\"CacheLoaderShared\">true</attribute>\n"
-" <attribute name=\"CacheLoaderPreload\">\n"
-" /a/b/c,/all/my/objects\n"
-" </attribute>\n"
-" <attribute name=\"CacheLoaderFetchTransientState\">false</"
-"attribute>\n"
-" <attribute name=\"CacheLoaderFetchPersistentState\">true</"
-"attribute>\n"
-" \n"
-" <attribute name=\"ClusterConfig\">\n"
-" ... JGroups config for the cluster ...\n"
-" </attribute>\n"
-"</mbean>"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:646
-#, fuzzy, no-c-format
-msgid ""
-"The JGroups configuration element (i.e., the <literal>ClusterConfig</"
-"literal> attribute) is omitted from the above listing. You have learned how "
-"to configure JGroups earlier in this chapter (<xref linkend="
-"\"JBossCache_and_JGroups_Services-JGroups_Configuration\"/>). The "
-"<literal>TreeCache</literal> MBean takes the following attributes."
-msgstr ""
-"上面的列表忽略了 JGroups 配置元素（就是 <literal>ClusterConfig</literal> 属"
-"性）。在本章内容（<xref linkend=\"jbosscache-jgroups\"/>）里，你已经学习了怎"
-"样配置 JGroups。<literal>TreeCache</literal> MBean 带有下面的属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:651
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">CacheLoaderClass</emphasis> specifies the fully "
-"qualified class name of the <literal>CacheLoader</literal> implementation."
-msgstr ""
-"<emphasis role=\"bold\">CacheLoaderClass</emphasis> 指定了 "
-"<literal>CacheLoader</literal> 实现的完整类名。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:656
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">CacheLoaderConfig</emphasis> contains a set of "
-"properties from which the specific CacheLoader implementation can configure "
-"itself."
-msgstr ""
-"<emphasis role=\"bold\">CacheLoaderConfig</emphasis> 包含了特定的 "
-"CacheLoader 实现可以用来配置自己的一组属性。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:661
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">CacheLoaderFetchPersistentState</emphasis> specifies "
-"whether to fetch the persistent state from another node. The persistence is "
-"fetched only if <literal>CacheLoaderShared</literal> is <literal>false</"
-"literal>. This attribute is only used if <literal>FetchStateOnStartup</"
-"literal> is <literal>true</literal>."
-msgstr ""
-"<emphasis role=\"bold\">CacheLoaderFetchPersistentState</emphasis> 指定是否从"
-"其他节点取得持久化状态。只有 <literal>CacheLoaderShared</literal> 为 "
-"<literal>false</literal> 时才可以取得持久化。这个属性只有在 "
-"<literal>FetchStateOnStartup</literal> 为 <literal>true</literal> 时才被使"
-"用。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:666
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">CacheLoaderFetchTransientState</emphasis> specifies "
-"whether to fetch the in-memory state from another node. This attribute is "
-"only used if <literal>FetchStateOnStartup</literal> is <literal>true</"
-"literal>."
-msgstr ""
-"<emphasis role=\"bold\">CacheLoaderFetchTransientState</emphasis> 指定是否从"
-"其他节点获取 in-memory 状态。这个属性只有在 <literal>FetchStateOnStartup</"
-"literal> 为 <literal>true</literal> 时才被使用。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:671
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">CacheLoaderPreload</emphasis> contains a list of "
-"comma-separate nodes that need to be preloaded (e.g., <literal>/aop</"
-"literal>, <literal>/productcatalogue</literal>)."
-msgstr ""
-"<emphasis role=\"bold\">CacheLoaderPreload</emphasis> 包含了需要预先加载的用"
-"逗号隔开的节点列表（如：<literal>/aop</literal>，<literal>/productcatalogue</"
-"literal>）"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:676
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">CacheLoaderShared</emphasis> specifies whether we "
-"want to shared a datastore, or whether each node wants to have its own local "
-"datastore."
-msgstr ""
-"<emphasis role=\"bold\">CacheLoaderShared</emphasis> 指定我们是否要共享数据"
-"库，或者是否每个节点要有自己的本地数据库。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:681
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">CacheMode</emphasis> specifies how to synchronize "
-"cache between nodes. The possible values are <literal>LOCAL</literal>, "
-"<literal>REPL_SYNC</literal>, or <literal>REPL_ASYNC</literal>."
-msgstr ""
-"<emphasis role=\"bold\">CacheMode</emphasis> 指定怎么在节点间使缓存同步。可能"
-"的值是 <literal>LOCAL</literal>，<literal>REPL_SYNC</literal> 或 "
-"<literal>REPL_ASYNC</literal>。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:686
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ClusterName</emphasis> specifies the name of the "
-"cluster. This value needs to be the same for all nodes in a cluster in order "
-"for them to find each other."
-msgstr ""
-"<emphasis role=\"bold\">ClusterName</emphasis> 指定群集系统的名字。这个值必须"
-"对群集系统里的所有节点都一样，这样它们才能相互找到对方。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:691
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ClusterConfig</emphasis> contains the configuration "
-"of the underlying JGroups stack (see <xref linkend="
-"\"JBossCache_and_JGroups_Services-JGroups_Configuration\"/>."
-msgstr ""
-"<emphasis role=\"bold\">ClusterConfig</emphasis> 包含底层 JGroups 栈（参见 "
-"<xref linkend=\"jbosscache-jgroups\"/>）的配置。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:696
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">EvictionPolicyClass</emphasis> specifies the name of "
-"a class implementing <literal>EvictionPolicy</literal>. You can use a JBoss "
-"Cache provided <literal>EvictionPolicy</literal> class or provide your own "
-"policy implementation. If this attribute is empty, no eviction policy is "
-"enabled."
-msgstr ""
-"<emphasis role=\"bold\">EvictionPolicyClass</emphasis> 指定了实现 "
-"<literal>EvictionPolicy</literal> 的类的名字。你可以使用 JBoss Cache 提供的 "
-"<literal>EvictionPolicy</literal> 类或者自己的策略实现类。如果这个属性为空，"
-"则表示没有启用清除策略（eviction policy）。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:701
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">EvictionPolicyConfig</emphasis> contains the "
-"configuration parameter for the specified eviction policy. Note that the "
-"content is provider specific."
-msgstr ""
-"<emphasis role=\"bold\">EvictionPolicyConfig</emphasis> 包含指定的清除策略"
-"（eviction policy）的配置参数。注意这是与提供者相关的内容。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:706
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">FetchStateOnStartup</emphasis> specifies whether or "
-"not to acquire the initial state from existing members. It allows for warm/"
-"hot caches (<literal>true/false</literal>). This can be further defined by "
-"<literal>CacheLoaderFetchTransientState</literal> and "
-"<literal>CacheLoaderFetchPersistentState</literal>."
-msgstr ""
-"<emphasis role=\"bold\">FetchStateOnStartup</emphasis> 指定是否从现存的成员获"
-"取初始状态。它允许 warm/hot 缓存（<literal>true/false</literal>）。它可以用 "
-"<literal>CacheLoaderFetchTransientState</literal> 和 "
-"<literal>CacheLoaderFetchPersistentState</literal> 进一步定义。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:711
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">InitialStateRetrievalTimeout</emphasis> specifies "
-"the time in milliseconds to wait for initial state retrieval."
-msgstr ""
-"<emphasis role=\"bold\">InitialStateRetrievalTimeout</emphasis> 指定的取得初"
-"始状态所需要等待的时间（毫秒数）。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:716
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">IsolationLevel</emphasis> specifies the node locking "
-"level. Possible values are <literal>SERIALIZABLE</literal>, "
-"<literal>REPEATABLE_READ</literal> (default), <literal>READ_COMMITTED</"
-"literal>, <literal>READ_UNCOMMITTED</literal>, and <literal>NONE</literal>."
-msgstr ""
-"<emphasis role=\"bold\">IsolationLevel</emphasis> 指定节点的锁定级别。可能的"
-"值是 <literal>SERIALIZABLE</literal>，<literal>REPEATABLE_READ</literal>（缺"
-"省值），<literal>READ_COMMITTED</literal>，<literal>READ_UNCOMMITTED</"
-"literal>，和 <literal>NONE</literal>。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:721
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">LockAcquisitionTimeout</emphasis> specifies the time "
-"in milliseconds to wait for a lock to be acquired. If a lock cannot be "
-"acquired an exception will be thrown."
-msgstr ""
-"<emphasis role=\"bold\">LockAcquisitionTimeout</emphasis> 指定获取一个锁定需"
-"等待的时间（毫秒数）。如果不能够获取锁定，将抛出一个异常。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:726
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ReplQueueInterval</emphasis> specifies the time in "
-"milliseconds for elements from the replication queue to be replicated."
-msgstr ""
-"<emphasis role=\"bold\">ReplQueueInterval</emphasis> 指定复制复制队列里的元素"
-"所需的时间（毫秒数）。"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:731
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">SyncReplTimeout</emphasis> specifies the time in "
-"milliseconds to wait until replication ACKs have been received from all "
-"nodes in the cluster. This attribute applies to synchronous replication mode "
-"only (i.e., <literal>CacheMode</literal> attribute is <literal>REPL_SYNC</"
-"literal>)."
-msgstr ""
-"<emphasis role=\"bold\">SyncReplTimeout</emphasis> 指定从群集系统里的所有节点"
-"接收到复制 ACKs 所需要等待的毫秒数。这个属性只适用于同步复制模式（也就是："
-"<literal>CacheMode</literal> 属性为 <literal>REPL_SYNC</literal>）"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:736
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">UseReplQueue</emphasis> specifies whether or not to "
-"use a replication queue (<literal>true/false</literal>). This attribute "
-"applies to synchronous replication mode only (i.e., <literal>CacheMode</"
-"literal> attribute is <literal>REPL_ASYNC</literal>)."
-msgstr ""
-"<emphasis role=\"bold\">UseReplQueue</emphasis> 指定是否使用复制队列"
-"（<literal>true/false</literal>）。这个属性只适用于同步复制模式（那就是："
-"<literal>CacheMode</literal> 属性为 <literal>REPL_ASYNC</literal>）"
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:741
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ReplQueueMaxElements</emphasis> specifies the "
-"maximum number of elements in the replication queue until replication kicks "
-"in."
-msgstr ""
-"<emphasis role=\"bold\">ReplQueueMaxElements</emphasis> 指定直到开始复制时，"
-"复制队列里的元素的最大数量， "
-
-#. Tag: para
-#: JBossCache_And_JGroups_Services.xml:746
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">TransactionManagerLookupClass</emphasis> specifies "
-"the fully qualified name of a class implementing "
-"<literal>TransactionManagerLookup</literal>. The default is "
-"<literal>JBossTransactionManagerLookup</literal> for the transaction manager "
-"inside the JBoss AS. There is also an option of "
-"<literal>DummyTransactionManagerLookup</literal> for simple standalone "
-"examples."
-msgstr ""
-"<emphasis role=\"bold\">TransactionManagerLookupClass</emphasis> 指定实现 "
-"<literal>TransactionManagerLookup</literal> 的类的完整类名。它的缺省值是用于 "
-"JBoss AS 里的失事物管理器（transaction manager）的 "
-"<literal>JBossTransactionManagerLookup</literal>。对于简单的独立服务器，也有"
-"一个选项为 <literal>DummyTransactionManagerLookup</literal>。"
More information about the jboss-cvs-commits
mailing list