[jboss-cvs] JBossAS SVN: r92412 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Aug 17 00:17:31 EDT 2009
Author: ldelima at redhat.com
Date: 2009-08-17 00:17:30 -0400 (Mon, 17 Aug 2009)
New Revision: 92412
Removed:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Clustering_Guide_Introduction.po
Log:
there was redudancy in this file
Deleted: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Clustering_Guide_Introduction.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Clustering_Guide_Introduction.po 2009-08-17 04:16:30 UTC (rev 92411)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Clustering_Guide_Introduction.po 2009-08-17 04:17:30 UTC (rev 92412)
@@ -1,10182 +0,0 @@
-# translation of Clustering_Guide_Introduction.po to Portuguese
-# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007, 2009 Free Software Foundation, Inc.
-#
-# Automatically generated, 2007.
-# Glaucia Cintra <gcintra at redhat.com>, 2009.
-msgid ""
-msgstr ""
-"Project-Id-Version: Clustering_Guide_Introduction\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-02-09 12:58+1000\n"
-"Last-Translator: Glaucia Cintra <gcintra at redhat.com>\n"
-"Language-Team: Portuguese <en at li.org>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"X-Generator: KBabel 1.11.4\n"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:5
-#, no-c-format
-msgid "Clustering"
-msgstr "Agrupamento "
-
-#. Tag: subtitle
-#: Clustering_Guide_Introduction.xml:6
-#, no-c-format
-msgid "High Availability Enterprise Services via JBoss Clusters"
-msgstr "Serviços Empresariais de Alta Disponibilidade através dos Clusters do JBoss"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:9
-#, no-c-format
-msgid "Introduction"
-msgstr "Introdução"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:10
-#, no-c-format
-msgid ""
-"Clustering allows us to run an application on several parallel servers (a.k."
-"a cluster nodes) while providing a single view to application clients. Load "
-"is distributed across different servers, and even if one or more of the "
-"servers fails, the application is still accessible via the surviving cluster "
-"nodes. Clustering is crucial for scalable enterprise applications, as you "
-"can improve performance by simply adding more nodes to the cluster. "
-"Clustering is crucial for highly available enterprise applications, as it is "
-"the clustering infrastructure that supports the redundancy needed for high "
-"availability."
-msgstr ""
-"O Agrupamento permite que os aplicativos sejam rodados em diversos "
-"servidores em paralelo (mais conhecidos como nós de um cluster). A carga é "
-"distribuída para servidores distintos e no caso de todos os servidores "
-"falharem, ainda pode-se acessar o aplicativo através de outros nós de "
-"cluster. O Agrupamento é crucial para aplicativos empresariais escaláveis, "
-"pois é possível melhorar o desempenho do aplicativo, adicionando mais nós ao "
-"cluster. O Agrupamento é crucial para aplicativos corporativos altamente disponíveis, como é a infraestrutura do clustering que suporta a redundância necessária para alta disponibilidade. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:14
-#, no-c-format
-msgid ""
-"The JBoss Application Server (AS) comes with clustering support out of the "
-"box. The simplest way to start a JBoss server cluster is to start several "
-"JBoss instances on the same local network, using the <literal>run -c all</"
-"literal> command for each instance. Those server instances, all started in "
-"the <literal>all</literal> configuration, detect each other and "
-"automatically form a cluster."
-msgstr ""
-"O Servidor do Aplicativo JBoss (AS) inclui o suporte de agrupamento para uso "
-"imediato. A forma mais simples de iniciar o servidor cluster é iniciando "
-"diversas instâncias no mesmo local da rede de trabalho, utilizando o comando "
-"<literal>run -c all</literal> para cada instância. Todas as instâncias do "
-"servidor que foram iniciadas com a configuração <literal>all</literal>, se "
-"detectam e formam automaticamente um cluster. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:17
-#, no-c-format
-msgid ""
-"In the first section of this chapter, we discuss basic concepts behind "
-"JBoss's clustering services. It is important that you understand these "
-"concepts before reading the rest of the chapter. Clustering configurations "
-"for specific types of applications are covered after this section."
-msgstr ""
-"Durante a primeira sessão deste capítulo, estarei discutindo sobre os "
-"conceitos básicos por trás dos serviços de agrupamento do JBoss. É "
-"importante que você entenda estes conceitos antes de continuar a ler este "
-"capítulo. Após esta sessão, trataremos das configurações do Agrupamento para "
-"tipos específicos de aplicativos. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:23
-#, no-c-format
-msgid "Cluster Definition"
-msgstr "Definição de Cluster"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:24
-#, no-c-format
-msgid ""
-"A cluster is a set of nodes that communicate with each other and work toward "
-"a common goal. In a JBoss Application Server cluster (also known as a "
-"“partition”), a node is an JBoss Application Server instance. Communication "
-"between the nodes is handled by the JGroups group communication library, "
-"with a JGroups Channel providing the core functionality of tracking who is "
-"in the cluster and reliably exchanging messages between the cluster members. "
-"JGroups channels with the same configuration and name have the ability to "
-"dynamically discover each other and form a group. This is why simply "
-"executing “run -c all” on two AS instances on the same network is enough for "
-"them to form a cluster – each AS starts a Channel (actually, several) with "
-"the same default configuration, so they dynamically discover each other and "
-"form a cluster. Nodes can be dynamically added to or removed from clusters "
-"at any time, simply by starting or stopping a Channel with a configuration "
-"and name that matches the other cluster members. In summary, a JBoss cluster "
-"is a set of AS server instances each of which is running an identically "
-"configured and named JGroups Channel."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:29
-#, no-c-format
-msgid ""
-"On the same AS instance, different services can create their own Channel. In "
-"a default 5.0.x AS, four different services create channels – the web "
-"session replication service, the EJB3 SFSB replication service, the EJB3 "
-"entity caching service, and a core general purpose clustering service known "
-"as HAPartition. In order to differentiate these channels, each must have a "
-"unique name, and its configuration must match its peers yet differ from the "
-"other channels."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:32
-#, no-c-format
-msgid ""
-"So, if you go to two AS 5.0.x instances and execute <literal>run -c all</"
-"literal>, the channels will discover each other and you'll have a conceptual "
-"<literal>cluster</literal>. It's easy to think of this as a two node "
-"cluster, but it's important to understand that you really have 4 channels, "
-"and hence 4 two node clusters."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:36
-#, no-c-format
-msgid ""
-"On the same network, even for the same service, we may have different "
-"clusters. <xref linkend=\"clustering-Partition.fig\"/> shows an example "
-"network of JBoss server instances divided into three clusters, with the "
-"third cluster only having one node. This sort of topology can be set up "
-"simply by configuring the AS instances such that within a set of nodes meant "
-"to form a cluster the Channel configurations and names match while they "
-"differ from any other channels on the same network."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:38
-#, no-c-format
-msgid "Clusters and server nodes"
-msgstr "Clusters e nós de servidor"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:46
-#, no-c-format
-msgid ""
-"The section on “JGroups Configuration” and on “Isolating JGroups Channels” "
-"covers in detail how to configure Channels such that desired peers find each "
-"other and unwanted peers do not. As mentioned above, by default JBoss AS "
-"uses four separate JGroups Channels. These can be divided into two broad "
-"categories: the Channel used by the general purpose HAPartition service, and "
-"three Channels created by JBoss Cache for special purpose caching and "
-"cluster wide state replication."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:50
-#, no-c-format
-msgid "HAPartition"
-msgstr "HAPartition"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:52
-#, no-c-format
-msgid ""
-"HAPartition is a general purpose service used for a variety of tasks in AS "
-"clustering. At its core, it is an abstraction built on top of a JGroups "
-"Channel that provides support for making/receiving RPC invocations on/from "
-"one or more cluster members. HAPartition also supports a distributed "
-"registry of which clustering services are running on which cluster members. "
-"It provides notifications to interested listeners when the cluster "
-"membership changes or the clustered service registry changes. HAPartition "
-"forms the core of many of the clustering services we'll be discussing in the "
-"rest of this guide, including smart client-side clustered proxies, EJB 2 "
-"SFSB replication and entity cache management, farming, HA-JNDI and HA "
-"singletons."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:58
-#, no-c-format
-msgid ""
-"The following example shows the <literal>HAPartition</literal> MBean "
-"definition packaged with the standard JBoss AS distribution. So, if you "
-"simply start JBoss servers with their default clustering settings on a local "
-"network, you would get a default cluster named <literal>DefaultPartition</"
-"literal> that includes all server instances as its nodes."
-msgstr ""
-"Os exemplos a seguir mostram a definição MBean <literal>HAPartition</literal> fechada, com a distribuição "
-"padrão do JBoss AS. Portanto, se você simplesmente iniciar o servidor JBoss, "
-"em uma rede de trabalho local, com as configurações de agrupamento padrão "
-"que eles oferecem , você criará um cluster padrão chamado <literal>DefaultPartition</literal> que inclui todas as instâncias de "
-"servidores, assim como seus nós."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:62
-#, no-c-format
-msgid ""
-"<mbean code=\"org.jboss.ha.framework.server.ClusterPartition\"\n"
-" name=\"jboss:service=DefaultPartition\">\n"
-" \n"
-" <! -- Name of the partition being built -->\n"
-" <attribute name=\"PartitionName\">\n"
-" ${jboss.partition.name:DefaultPartition}\n"
-" </attribute>\n"
-"\n"
-" <! -- The address used to determine the node name -->\n"
-" <attribute name=\"NodeAddress\">${jboss.bind.address}</"
-"attribute>\n"
-"\n"
-" <! -- Determine if deadlock detection is enabled -->\n"
-" <attribute name=\"DeadlockDetection\">False</attribute>\n"
-" \n"
-" <! -- Max time (in ms) to wait for state transfer to complete. \n"
-" Increase for large states -->\n"
-" <attribute name=\"StateTransferTimeout\">30000</attribute>\n"
-"\n"
-" <! -- The JGroups protocol configuration -->\n"
-" <attribute name=\"PartitionConfig\">\n"
-" ... ...\n"
-" </attribute>\n"
-"</mbean>"
-msgstr ""
-"<mbean code=\"org.jboss.ha.framework.server.ClusterPartition\"\n"
-" name=\"jboss:service=DefaultPartition\">\n"
-" \n"
-" <! -- Nome da partição sendo construída-->\n"
-" <attribute name=\"PartitionName\">\n"
-" ${jboss.partition.name:DefaultPartition}\n"
-" </attribute>\n"
-"\n"
-" <! -- Endereço utilizado para determinar o nome do nó -->\n"
-" <attribute name=\"NodeAddress\">${jboss.bind.address}</"
-"attribute>\n"
-"\n"
-" <! -- Determina se uma detecção de falha está habilitada -->\n"
-" <attribute name=\"DeadlockDetection\">False</attribute>\n"
-" \n"
-" <! -- Tempo máximo (em ms) de espera pelo término da transferência de "
-"estado. \n"
-" Aumentar para estados grandes -->\n"
-" <attribute name=\"StateTransferTimeout\">30000</attribute>\n"
-"\n"
-" <! --A configuração do protocolo JGroups -->\n"
-" <attribute name=\"PartitionConfig\">\n"
-" ... ...\n"
-" </attribute>\n"
-"</mbean>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:63
-#, no-c-format
-msgid ""
-"Here, we omitted the detailed JGroups protocol configuration for this "
-"channel. JGroups handles the underlying peer-to-peer communication between "
-"nodes, and its configuration is discussed in <xref linkend=\"jbosscache-"
-"jgroups\"/>. The following list shows the available configuration attributes "
-"in the <literal>HAPartition</literal> MBean."
-msgstr ""
-"Aqui, a configuração do protocolo JGroups detalhado foi omitida neste "
-"cluster. O JGroup lida com a comunicação ponto a ponto entre os nós, e sua "
-"configuração é discutida em <xref linkend=\"jbosscache-jgroups\"/>. A "
-"próxima lista mostra as funções de configuração disponíveis no MBean "
-"<literal>HAPartition</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:68
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">PartitionName</emphasis> is an optional attribute to "
-"specify the name of the cluster. Its default value is "
-"<literal>DefaultPartition</literal>. Use the <literal>-g </literal> (a.k.a. "
-"--partition) command line switch to set this value at JBoss startup."
-msgstr ""
-"<emphasis role=\"bold\">PartitionName</emphasis>é uma função alternativa "
-"para especificar o nome de um cluster. Seu valor padrão é "
-"<literal>DefaultPartition</literal>. Use a linha de comando <literal>-g </literal> (mais conhecido como --partition) para estabelecer este valor na inicialização do JBoss."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:72
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">NodeAddress</emphasis> is an optional attribute used "
-"to help generate a unique name for this node."
-msgstr ""
-"<emphasis role=\"bold\">NodeAddress</emphasis> é uma função alternativa para "
-"ajudar a gerar um nome único para este nó."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:75
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">DeadlockDetection</emphasis> is an optional boolean "
-"attribute that tells JGroups to run message deadlock detection algorithms "
-"with every request. Its default value is <literal>false</literal>."
-msgstr ""
-"<emphasis role=\"bold\">DeadlockDetection</emphasis> é uma função booleana "
-"opcional que diz ao JGroup para rodar a mensagem dos algoritmos de detecção "
-"de falhas em todas as solicitações. Seu valor padrão é <literal>false</"
-"literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:80
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">StateTransferTimeout</emphasis> is an optional "
-"attribute to specify the timeout for state replication across the cluster "
-"(in milliseconds). State replication refers to the process of obtaining "
-"initial application state from other already-running cluster members at "
-"service startup. Its default value is <literal>30000</literal>."
-msgstr ""
-"A função <emphasis role=\"bold\">StateTransferTimeout</emphasis> é opcional "
-"e especifica o tempo de espera para a replicação de estado no cluster (em "
-"milisegundos). A replicação de estado se refere ao processo de obtenção inicial do estado do aplicativo de outros membros já rodando em cluster na inicialização do serviço. Seu valor padrão é <literal>30000</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:83
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">PartitionConfig</emphasis> is an element to specify "
-"JGroup configuration options for this cluster (see <xref linkend="
-"\"jbosscache-jgroups\"/>)."
-msgstr ""
-"<emphasis role=\"bold\">PartitionConfig</emphasis> é um elemento para "
-"especificar as opções de configuração do JGroup para este cluster (veja "
-"<xref linkend=\"jbosscache-jgroups\"/>)."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:87
-#, no-c-format
-msgid ""
-"In order for nodes to form a cluster, they must have the exact same "
-"<literal>PartitionName</literal> and the <literal>ParitionConfig</literal> "
-"elements. Changes in either element on some but not all nodes would cause "
-"the cluster to split."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:90
-#, no-c-format
-msgid ""
-"You can view the current cluster information by pointing your browser to the "
-"JMX console of any JBoss instance in the cluster (i.e., <literal>http://"
-"hostname:8080/jmx-console/</literal>) and then clicking on the "
-"<literal>jboss:service=DefaultPartition</literal> MBean (change the MBean "
-"name to reflect your partitionr name if you use the -g startup switch). A "
-"list of IP addresses for the current cluster members is shown in the "
-"CurrentView field."
-msgstr ""
-"Você poderá visualizar as informações atuais do cluster, passando o "
-"navegador pelo console JMX de qualquer instância JBoss no cluster (ou seja, "
-"<literal>http://hostname:8080/jmx-console/</literal>) e então selecionando o "
-"MBean <literal>jboss:service=DefaultPartition</literal> (mude o nome do "
-"MBean para o mesmo nome da sua partição, caso você use a opção da inicialização -g). Já está disponível uma lista de endereços IP para os membros atuais do cluster no campo "
-"CurrentView."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:94 Clustering_Guide_Introduction.xml:398
-#: Clustering_Guide_Introduction.xml:405 Clustering_Guide_Introduction.xml:411
-#: Clustering_Guide_Introduction.xml:1061
-#: Clustering_Guide_Introduction.xml:1486
-#: Clustering_Guide_Introduction.xml:2454
-#: Clustering_Guide_Introduction.xml:2478
-#, no-c-format
-msgid "Note"
-msgstr "Nota"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:95
-#, no-c-format
-msgid ""
-"While it is technically possible to put a JBoss server instance into "
-"multiple HAPartitions at the same time, this practice is generally not "
-"recommended, as it increases management complexity."
-msgstr ""
-"Embora seja tecnicamente possível colocar uma instância do servidor JBoss em "
-"clusters múltiplos ao mesmo tempo, geralmente não é muito recomendado, pois "
-"aumenta a complexidade do gerenciamento. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:101
-#, no-c-format
-msgid "JBoss Cache channels"
-msgstr "Canais JBoss Cache"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:102
-#, no-c-format
-msgid ""
-"JBoss Cache is a fully featured distributed cache framework that can be used "
-"in any application server environment or standalone. JBoss AS integrates "
-"JBoss Cache to provide cache services for HTTP sessions, EJB 3.0 session "
-"beans, and EJB 3.0 entity beans. Each of these cache services is defined in "
-"a separate Mbean, and each cache creates its own JGroups Channel. We will "
-"cover those MBeans when we discuss specific services in the next several "
-"sections."
-msgstr ""
-"O Cache JBoss é uma moldura proeminente de cache distribuído, que pode ser "
-"utilizado em qualquer ambiente de servidor de aplicativo e autônomo. O JBoss "
-"AS integra o JBoss Cache para oferecer serviços de cache para sessões de "
-"HTTP, EJB 3.0 e beans de entidade, assim como objetos de persistência do "
-"Hibernate. Cada um destes serviços de cache está definido em um MBean "
-"separadamente. Falaremos a respeito destes MBeans quando discutirmos sobre "
-"os serviços específicos nas próximas seções. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:107
-#, no-c-format
-msgid "Service Architectures"
-msgstr "Arquitetura de Serviços"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:108
-#, no-c-format
-msgid ""
-"The clustering topography defined by the <literal>HAPartition</literal> "
-"MBean on each node is of great importance to system administrators. But for "
-"most application developers, you are probably more concerned about the "
-"cluster architecture from a client application's point of view. Two basic "
-"clustering architectures are used with JBoss AS: client-side interceptors (a."
-"k.a smart proxies or stubs) and external load balancers. Which architecture "
-"your application will use will depend on what type of client you have."
-msgstr ""
-"A topografia de agrupamento definida pelo MBean <literal>HAPartition</"
-"literal> em cada nó é de grande importância para os administradores de "
-"sistema. Mas como para a maioria dos desenvolvedores de aplicativo, você "
-"deve estar mais preocupado com a arquitetura do cluster do ponto de vista "
-"dos aplicativos de clientes. Duas arquiteturas em cluster básicas são usadas com o JBoss AS: interceptores do cliente (mais conhecido como, smart proxies ou stubs) e balanceadores de carga externos. Qual aplicativo de arquitetura seu aplicativo irá usar dependerá de qual tipo de cliente você tem. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:114 Clustering_Guide_Introduction.xml:160
-#, no-c-format
-msgid "Client-side interceptor architecture"
-msgstr "Arquitetura do Interceptador do cliente."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:115
-#, no-c-format
-msgid ""
-"Most remote services provided by the JBoss application server, including "
-"JNDI, EJB, JMS, RMI and JBoss Remoting, require the client to obtain (e.g., "
-"to look up and download) a stub (or proxy) object. The stub object is "
-"generated by the server and it implements the business interface of the "
-"service. The client then makes local method calls against the stub object. "
-"The stub automatically routes the call across the network and where it is "
-"invoked against service objects managed in the server. In a clustering "
-"environment, the server-generated stub object includes an interceptor that "
-"understands how to route calls to multiple nodes in the cluster. The stub "
-"object figures out how to find the appropriate server node, marshal call "
-"parameters, un-marshall call results, and return the result to the caller "
-"client."
-msgstr ""
-"A maior parte dos serviços remotos oferecidos pelo servidor do aplicativo "
-"JBoss, incluindo JNDI, EJB, JMS, RMI e o Remoting JBoss, precisam que o cliente "
-"obtenha um objeto stub, ou proxy (ex.: para consultar e realizar o "
-"download). O objeto stub é gerado pelo servidor e implementa a interface de "
-"negócios do serviço. Depois disso, o cliente realiza chamadas de método "
-"local junto aos objetos de stub. A chamada é automaticamente trilhada pela "
-"rede de trabalho e invocada junto aos objetos de serviço gerenciados no "
-"servidor. Em um ambiente de agrupamento, o objeto de serviço gerado pelo "
-"servidor é também um interceptador, que sabe como trilhar os nós de cluster. "
-"O objeto stub descobre como encontrar um nó de servidor apropriado, ordenar "
-"os parâmetros de chamadas, desordenar os resultados das chamadas e por fim, "
-"retornar os resultados para o cliente que realizou a chamada."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:120
-#, no-c-format
-msgid ""
-"The stub interceptors maintain up-to-date knowledge about the cluster. For "
-"instance, they know the IP addresses of all available server nodes, the "
-"algorithm to distribute load across nodes (see next section), and how to "
-"failover the request if the target node not available. As part of handling "
-"each service request, if the cluster topology has changed the server node "
-"updates the stub interceptor with the latest changes in the cluster. For "
-"instance, if a node drops out of the cluster, each of client stub "
-"interceptor is updated with the new configuration the next time it connects "
-"to any active node in the cluster. All the manipulations done by the service "
-"stub are transparent to the client application. The client-side interceptor "
-"clustering architecture is illustrated in <xref linkend=\"clustering-"
-"InterceptorArch.fig\"/>."
-msgstr ""
-"Os interceptadores stub mantém as informações atualizadas sobre os clusters. Por "
-"exemplo, eles conhecem o endereço IP de todos os nós de servidores "
-"disponíveis, o algoritmo para distribuir carga para os nós (veja na próxima "
-"seção) e como fazer o failover da solicitação, caso o nó alvo não esteja "
-"disponível. Durante a manipulação de cada requisição de serviço, se a topologia do cluster mudou as atualizações do nó do servidor , o interceptador do stub com as mudanças recentes no cluster. Por exemplo, se um nó cair do cluster, cada um dos interceptadores de stub do cliente será "
-"atualizado com uma nova configuração da próxima vez que se conectar a "
-"qualquer nó ativo no cluster. Toda a manipulação no stub do serviço é "
-"transparente ao aplicativo do cliente. A arquitetura de agrupamento do "
-"interceptador do cliente está ilustrada em <xref linkend=\"clustering-"
-"InterceptorArch.fig\"/>."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:123
-#, no-c-format
-msgid "The client-side interceptor (proxy) architecture for clustering"
-msgstr "A arquitetura do interceptador do cliente (proxy) para agrupamento"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:131
-#, no-c-format
-msgid ""
-"describes how to enable the client proxy to handle the entire cluster "
-"restart."
-msgstr ""
-"descreve como habilitar o proxy do cliente para lidar com todo o reinício do "
-"cluster "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:136
-#, no-c-format
-msgid "Load balancer"
-msgstr "Balanceador de carga"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:137
-#, fuzzy, no-c-format
-msgid ""
-"Other JBoss services, in particular the HTTP-based services, do not require "
-"the client to download anything. The client (e.g., a web browser) sends in "
-"requests and receives responses directly over the wire according to certain "
-"communication protocols (e.g., the HTTP protocol). In this case, an external "
-"load balancer is required to process all requests and dispatch them to "
-"server nodes in the cluster. The client only needs to know about how to "
-"contact the load balancer; it has no knowledge of the JBoss AS instances "
-"behind the load balancer. The load balancer is logically part of the "
-"cluster, but we refer to it as “external” because it is not running in the "
-"same process as either the client or any of the JBoss AS instances. It can "
-"be implemented either in software or hardware. There are many vendors of "
-"hardware load balancers; the mod_jk Apache module is an excellent example of "
-"a software load balancer. An external load balancer implements its own "
-"mechanism for understanding the cluster configuration and provides its own "
-"load balancing and failover policies. The external load balancer clustering "
-"architecture is illustrated in <xref linkend=\"clustering-BalancerArch.fig\"/"
-">."
-msgstr ""
-"Outros serviços JBoss, especialmente os serviços de web HTTP, não requerem "
-"que o cliente baixe nada. De acordo com certos protocolos de comunicação "
-"(ex.: o protocolo HTTP), o cliente (ex.: navegador da web) envia uma "
-"solicitação e recebe a resposta diretamente pela rede. Neste caso, é "
-"necessário um balanceador de carga para processar todas as solicitações e "
-"despachá-las aos nós de servidor no cluster. O balanceador de carga faz "
-"parte do cluster. Ele entende as configurações do cluster, assim como as "
-"políticas de falha. O cliente só precisa saber sobre o balanceador de carga. "
-"A arquitetura do agrupamento do balanceador de carga está ilustrada em <xref "
-"linkend=\"clustering-BalancerArch.fig\"/>."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:141
-#, no-c-format
-msgid "The external load balancer architecture for clustering"
-msgstr "A arquitetura do balanceador de carga para agrupamento. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:148
-#, fuzzy, no-c-format
-msgid ""
-"A potential problem with an external load balancer architecture is that the "
-"load balancer itself may be a single point of failure. It needs to be "
-"monitored closely to ensure high availability of the entire cluster's "
-"services."
-msgstr ""
-"O maior problema com a solução do balanceador de carga é que o próprio "
-"balanceador é um ponto de falha. Ele precisa ser monitorado cuidadosamente "
-"para assegurar a alta disponibilidade de todos os serviços do cluster. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:155
-#, no-c-format
-msgid "Load-Balancing Policies"
-msgstr "Políticas de Balanceamento de Carga "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:156
-#, fuzzy, no-c-format
-msgid ""
-"Both the JBoss client-side interceptor (stub) and load balancer use load "
-"balancing policies to determine which server node to which node a new "
-"request should be sent. In this section, let's go over the load balancing "
-"policies available in JBoss AS."
-msgstr ""
-"Tanto o interceptador do cliente da JBoss (stub) quanto o balanceador de "
-"carga, utilizam políticas de balanceamento que determinam para qual nó de "
-"servidor deve-se enviar uma nova solicitação. Nesta seção, veremos as "
-"políticas de balanceamento de carga disponíveis no JBoss AS."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:161
-#, no-c-format
-msgid ""
-"In JBoss 5.0.0, the following load balancing options are available when the "
-"client-side interceptor architecture is used. The client-side stub maintains "
-"a list of all nodes providing the target service; the job of the load "
-"balance policy is to pick a node from this list for each request."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:166
-#, fuzzy, no-c-format
-msgid ""
-"Round-Robin (<literal>org.jboss.ha.framework.interfaces.RoundRobin</"
-"literal>): each call is dispatched to a new node, proceeding sequentially "
-"through the list of nodes. The first target node is randomly selected from "
-"the list."
-msgstr ""
-"Round-Robin (<literal>org.jboss.ha.framework.interfaces.RoundRobin</"
-"literal>): cada chamada é despachada para um novo nó. O primeiro nó alvo é "
-"selecionado a partir da lista, de forma aleatória."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:172
-#, fuzzy, no-c-format
-msgid ""
-"Random-Robin (<literal>org.jboss.ha.framework.interfaces.RandomRobin</"
-"literal>): for each call the target node is randomly selected from the list."
-msgstr ""
-"Round-Robin (<literal>org.jboss.ha.framework.interfaces.RoundRobin</"
-"literal>): cada chamada é despachada para um novo nó. O primeiro nó alvo é "
-"selecionado a partir da lista, de forma aleatória."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:177
-#, fuzzy, no-c-format
-msgid ""
-"First Available (<literal>org.jboss.ha.framework.interfaces.FirstAvailable</"
-"literal>): one of the available target nodes is elected as the main target "
-"and is thereafter used for every call; this elected member is randomly "
-"chosen from the list of members in the cluster. When the list of target "
-"nodes changes (because a node starts or dies), the policy will choose a new "
-"target node unless the currently elected node is still available. Each "
-"client-side stub elects its own target node independently of the other "
-"stubs, so if a particular client downloads two stubs for the same target "
-"service (e.g., an EJB), each stub will independently pick its target. This "
-"is an example of a policy that provides “session affinity” or “sticky "
-"sessions”, since the target node does not change once established."
-msgstr ""
-"Primeiro Disponível (<literal>org.jboss.ha.framework.interfaces."
-"FirstAvailable</literal>): Elege-se um dos nós alvos disponíveis como o alvo "
-"principal e utiliza-se esse alvo para todas as chamadas: este membro eleito "
-"é escolhido de forma aleatória a partir das listas dos membros no cluster. "
-"Quando a lista de nós de alvos mudar (caso um nó iniciar ou falhar), a "
-"política re-elegerá um outro nó alvo, a não ser que o nó atual ainda esteja "
-"disponível. Cada interceptador do cliente ou balanceador de carga elege seu "
-"próprio nó alvo independentemente dos outros proxys. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:184
-#, fuzzy, no-c-format
-msgid ""
-"First Available Identical All Proxies (<literal>org.jboss.ha.framework."
-"interfaces.FirstAvailableIdenticalAllProxies</literal>): has the same "
-"behaviour as the \"First Available\" policy but the elected target node is "
-"shared by all stubs in the same client-side VM that are associated with the "
-"same target service. So if a particular client downloads two stubs for the "
-"same target service (e.g. an EJB), each stub will use the same target."
-msgstr ""
-"A nova opção de balanceamento de carga no JBoss 3.2 é \"Primeiro Disponível "
-"de Todos os Proxies\" (<literal>org.jboss.ha.framework.interfaces."
-"FirstAvailableIdenticalAllProxies</literal>). Esta nova opção possui o mesmo "
-"comportamento da política \"Primeiro Disponível\", mas o nó alvo eleito é "
-"compartilhado por todos os interceptadores do cliente da mesma \"família\"."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:190
-#, no-c-format
-msgid ""
-"Each of the above is an implementation of the org.jboss.ha.framework."
-"interfaces.LoadBalancePolicy interface; users are free to write their own "
-"implementation of this simple interface if they need some special behavior. "
-"In later sections we'll see how to configure the load balance policies used "
-"by different services."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:194
-#, no-c-format
-msgid "External load balancer architecture"
-msgstr "A arquitetura do balanceador de carga externo"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:196
-#, no-c-format
-msgid ""
-"As noted above, an external load balancer provides its own load balancing "
-"capabilities. What capabilities are supported depends on the provider of the "
-"load balancer. The only JBoss requirement is that the load balancer support "
-"“session affinitiy” (a.k.a. “sticky sessions”). With session affinitiy "
-"enabled, once the load balancer routes a request from a client to node A and "
-"the server initiates a session, all future requests associated with that "
-"session must be routed to node A, so long as node A is available."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:206
-#, no-c-format
-msgid "Farming Deployment"
-msgstr "Implementação de Farming"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:207
-#, no-c-format
-msgid ""
-"The easiest way to deploy an application into the cluster is to use the "
-"farming service. That is to hot-deploy the application archive file (e.g., "
-"the EAR, WAR or SAR file) in the <code>all/farm/</code> directory of any of "
-"the cluster members and the application will be automatically duplicated "
-"across all nodes in the same cluster. If node joins the cluster later, it "
-"will pull in all farm deployed applications in the cluster and deploy them "
-"locally at start-up time. If you delete the application from one of the "
-"running cluster server node's <literal>farm/</literal> folder, the "
-"application will be undeployed locally and then removed from all other "
-"cluster server nodes farm folder (triggers undeployment.) You should "
-"manually delete the application from the farm folder of any server node not "
-"currently connected to the cluster."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:217
-#, no-c-format
-msgid ""
-"Currently, due to an implementation weakness, the farm deployment service "
-"only works for 1) archives located in the farm/ directory of the first node "
-"to join the cluster or 2) hot-deployed archives. If you first put a new "
-"application in the farm/ directory and then start the server to have it join "
-"an already running cluster, the application will not be pushed across the "
-"cluster or deployed. This is because the farm service does not know whether "
-"the application really represents a new deployment or represents an old "
-"deployment that was removed from the rest of the cluster while the newly "
-"starting node was off-line. We are working to resolve this issue."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:220
-#, no-c-format
-msgid ""
-"You can only put zipped archive files, not exploded directories, in the farm "
-"directory. If exploded directories are placed in farm the directory contents "
-"will be replicated around the cluster piecemeal, and it is very likely that "
-"remote nodes will begin trying to deploy things before all the pieces have "
-"arrived, leading to deployment failure."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:223
-#, no-c-format
-msgid ""
-"Farmed deployment is not atomic. A problem deploying, undeploying or "
-"redeploying an application on one node in the cluster will not prevent the "
-"deployment, undeployment or redeployment being done on the other nodes. "
-"There is no rollback capability. Deployment is also not staggered; it is "
-"quite likely, for example, that a redeployment will happen on all nodes in "
-"the cluster simultaneously, briefly leaving no nodes in the cluster "
-"providing service."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:227
-#, fuzzy, no-c-format
-msgid ""
-"Farming is enabled by default in the <literal>all</literal> configuration in "
-"JBoss AS distributions, so you will not have to set it up yourself. The "
-"<literal>farm-service.xml</literal> configuration file is located in the "
-"deploy/deploy.last directory. If you want to enable farming in a custom "
-"configuration, simply copy the farm-service.xml file and copy it to the "
-"JBoss deploy directory <literal>$JBOSS_HOME/server/your_own_config/deploy/"
-"deploy.last</literal>. Make sure that your custom configuration has "
-"clustering enabled."
-msgstr ""
-"O Farming já é permitido como padrão na configuração <literal>all</literal> "
-"nas distribuições do JBoss AS, portanto você mesmo poderá instalá-lo. O "
-"arquivo de configuração está localizado no diretório <literal>deploy/deploy."
-"last</literal>. Se você quiser habilitar o farming de forma personalizada, "
-"simplesmente crie o arquivo XML que aparece abaixo (chamado <literal>farm-"
-"service.xml</literal>) e o copie para o diretório de implementação JBoss "
-"<literal>$JBOSS_HOME/server/your_own_config/deploy</literal>.Tenha a certeza "
-"de que sua configuração personalizada possui o agrupamento habilitado."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:229
-#, fuzzy, no-c-format
-msgid ""
-"After deploying farm-service.xml you are ready to rumble. The required "
-"FarmMemberService MBean attributes for configuring a farm are listed below."
-msgstr ""
-"Após implementar o <literal>farm-service.xml</literal> você estará pronto "
-"para comemorar. As funções do MBean, <literal>FarmMemberService</literal> "
-"solicitadas para configurar um farm, estão listados abaixo:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:232
-#, no-c-format
-msgid ""
-"<?xml version=\"1.0\" encoding=\"UTF-8\"?> \n"
-"<server> \n"
-" \n"
-" <mbean code=\"org.jboss.ha.framework.server.FarmMemberService\" \n"
-" name=\"jboss:service=FarmMember,partition=DefaultPartition"
-"\"> \n"
-" ... \n"
-" \n"
-" <depends optional-attribute-name=\"ClusterPartition\" \n"
-" proxy-type=\"attribute\">\n"
-" jboss:service=${jboss.partition.name:DefaultPartition}\n"
-" </depends> \n"
-" <attribute name=\"ScanPeriod\">5000</"
-"attribute> \n"
-" <attribute name=\"URLs\">farm/</attribute> \n"
-" ...\n"
-" </mbean> \n"
-"</server>"
-msgstr ""
-"<?xml version=\"1.0\" encoding=\"UTF-8\"?> \n"
-"<server> \n"
-" \n"
-" <mbean code=\"org.jboss.ha.framework.server.FarmMemberService\" \n"
-" name=\"jboss:service=FarmMember,partition=DefaultPartition"
-"\"> \n"
-" ... \n"
-" \n"
-" <depends optional-attribute-name=\"ClusterPartition\" \n"
-" proxy-type=\"attribute\">\n"
-" jboss:service=${jboss.partition.name:DefaultPartition}\n"
-" </depends> \n"
-" <attribute name=\"ScanPeriod\">5000</"
-"attribute> \n"
-" <attribute name=\"URLs\">farm/</attribute> \n"
-" ...\n"
-" </mbean> \n"
-"</server>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:237
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ClusterPartition</emphasis> is a required attribute "
-"to inject the HAPartition service that the farm service uses for intra-"
-"cluster communication."
-msgstr ""
-"<emphasis role=\"bold\">PartitionName</emphasis>é uma função alternativa "
-"para especificar o nome de um cluster. Seu valor padrão é "
-"<literal>DefaultPartition</literal>.."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:240
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">URLs</emphasis> points to the directory where "
-"deployer watches for files to be deployed. This MBean will create this "
-"directory is if does not already exist. If a full URL is not provided, it is "
-"assumed that the value is a filesytem path relative to the configuration "
-"directory (e.g. <literal>$JBOSS_HOME/server/all/</literal>)."
-msgstr ""
-"<emphasis role=\"bold\">URLs</emphasis> aponta para o diretório onde o "
-"implementador cuida dos arquivos a serem implementados. Este MBean irá criar "
-"este diretório, a não ser que ele já exista. O símbolo \".\", também "
-"pertence ao diretório de configuração (ou seja, <literal>$JBOSS_HOME/server/"
-"all/</literal>)"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:245
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ScanPeriod</emphasis> specifies the interval at "
-"which the folder must be scanned for changes.. Its default value is "
-"<literal>5000</literal>."
-msgstr ""
-"<emphasis role=\"bold\">ScanPeriod</emphasis> especifica o intervalo, quando "
-"a pasta deve ser escaneada para mudanças. Seu valor padrão é <literal>5000</"
-"literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:249
-#, fuzzy, no-c-format
-msgid ""
-"The farming service is an extension of the <literal>URLDeploymentScanner</"
-"literal>, which scans for hot deployments in the <literal>deploy/</literal> "
-"directory. So, you can use all the attributes defined in the "
-"<literal>URLDeploymentScanner</literal> MBean in the "
-"<literal>FarmMemberService</literal> MBean. In fact, the <literal>URLs</"
-"literal> and <literal>ScanPeriod</literal> attributes listed above are "
-"inherited from the <literal>URLDeploymentScanner</literal> MBean."
-msgstr ""
-"O serviço Farming é uma extensão do <literal>URLDeploymentScanner</literal> "
-"que pode procurar por um hot deployment no diretório <literal>deploy/</"
-"literal>. Portanto, você poderá utilizar todas as funções definidas no MBean "
-"<literal>URLDeploymentScanner</literal>. Na verdade, as funções "
-"<literal>URLs</literal> e <literal>ScanPeriod</literal> listadas abaixo são "
-"herdadas do MBean <literal>URLDeploymentScanner</literal>."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:258
-#, no-c-format
-msgid "Distributed state replication services"
-msgstr "Serviços de replicação de estado distribuídos"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:259
-#, fuzzy, no-c-format
-msgid ""
-"In a clustered server environment, distributed state management is a key "
-"service the cluster must provide. For instance, in a stateful session bean "
-"application, the session state must be synchronized among all bean instances "
-"across all nodes, so that the client application reaches the same session "
-"state no matter which node serves the request. In an entity bean "
-"application, the bean object sometimes needs to be cached across the cluster "
-"to reduce the database load. Currently, the state replication and "
-"distributed cache services in JBoss AS are provided via three ways: the "
-"<literal>HASessionState</literal> Mbean, the <literal>DistributedState</"
-"literal> MBean and the JBoss Cache framework."
-msgstr ""
-"Em um ambiente de servidor em cluster, o gerenciamento de estado distribuído "
-"é um serviço chave que o cluster deve oferecer. Como por exemplo, em um "
-"aplicativo de bean de sessão com estado, o estado da sessão deve ser "
-"sincronizado com todas as instâncias de todos os nós, portanto o aplicativo "
-"do cliente chegará ao mesmo estado de sessão, independente de qual servidor "
-"de nós ele solicitar. Em um aplicativo de bean de entidade, o objeto do bean "
-"precisa, às vezes, passar pelo mecanismo de cache através do cluster para "
-"reduzir a carga do banco de dados. Atualmente, a replicação do estado e os "
-"serviços de cache distribuído no JBoss AS são oferecidos de duas formas: o "
-"MBean e a moldura do JBoss Cache <literal>HASessionState</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:266
-#, fuzzy, no-c-format
-msgid ""
-"The <literal>HASessionState</literal> MBean is a legacy service that "
-"provides session replication and distributed cache services for EJB 2.x "
-"stateful session beans. The MBean is defined in the <literal>all/deploy/"
-"cluster-service.xml</literal> file. We will show its configuration options "
-"in the EJB 2.x stateful session bean section later."
-msgstr ""
-"O MBean <literal>HASessionState</literal> oferece uma replicação de sessão e "
-"serviços de cache distribuídos para os beans de sessão com estado EJB 2.x "
-"e HTTP balanceadores de carga no JBoss 3.x e 4.x. A definição do MBeans "
-"encontra-se no arquivo <literal>all/deploy/cluster-service.xml</literal>. "
-"Mostraremos suas opções de configuração em bean de sessão com estado EJB 2."
-"x , em uma seção mais adiante. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:269
-#, no-c-format
-msgid ""
-"The <literal>DistributedState</literal> Mbean is a legacy service built on "
-"the HAPartition service. It is supported for backwards compatibility "
-"reasons, but new applications should not use it; they should use the much "
-"more sophisticated JBoss Cache instead."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:275
-#, no-c-format
-msgid ""
-"As mentioned above JBoss Cache is used to provide cache services for HTTP "
-"sessions, EJB 3.0 session beans and EJB 3.0 entity beans. It is the primary "
-"distributed state management tool in JBoss AS, and is an excellent choice "
-"for any custom caching requirements your applications may have. We will "
-"cover JBoss Cache in more detail when we discuss specific services in the "
-"next several sections.."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:286
-#, no-c-format
-msgid "Clustered JNDI Services"
-msgstr "Serviços JNDI em Cluster "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:287
-#, no-c-format
-msgid ""
-"JNDI is one of the most important services provided by the application "
-"server. The JBoss HA-JNDI (High Availability JNDI) service brings the "
-"following features to JNDI:"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:291
-#, no-c-format
-msgid ""
-"Transparent failover of naming operations. If an HA-JNDI naming Context is "
-"connected to the HA-JNDI service on a particular JBoss AS instance, and that "
-"service fails or is shut down, the HA-JNDI client can transparently fail "
-"over to another AS instance."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:296
-#, no-c-format
-msgid ""
-"Load balancing of naming operations. An HA-JNDI naming Context will "
-"automatically load balance its requests across all the HA-JNDI servers in "
-"the cluster."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:301
-#, no-c-format
-msgid "Automatic client discovery of HA-JNDI servers (using multicast)."
-msgstr "Descoberta de cliente automático dos servidores HA-JNDI (usando o multicast)"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:306
-#, no-c-format
-msgid ""
-"Unified view of JNDI trees cluster-wide. Client can connect to the HA-JNDI "
-"service running on any node in the cluster and find objects bound in JNDI on "
-"any other node. This is accomplished via two mechanisms:"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:314
-#, no-c-format
-msgid ""
-"Cross-cluster lookups. A client can perform a lookup and the server side HA-"
-"JNDI service has the ability to find things bound in regular JNDI on any "
-"node in the cluster."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:318
-#, no-c-format
-msgid ""
-"A replicated cluster-wide context tree. An object bound into the HA-JNDI "
-"service will be replicated around the cluster, and a copy of that object "
-"will be available in-VM on each node in the cluster."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:327
-#, no-c-format
-msgid ""
-"JNDI is a key component for many other interceptor-based clustering "
-"services: those services register themselves with the JNDI so that the "
-"client can lookup their proxies and make use of their services. HA-JNDI "
-"completes the picture by ensuring that clients have a highly-available means "
-"to look up those proxies. However, it is important to understand that using "
-"HA-JNDI (or not) has no effect whatsoever on the clustering behavior of the "
-"objects that are looked up. To illustrate:"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:332
-#, no-c-format
-msgid ""
-"If an EJB is not configured as clustered, looking up the EJB via HA-JNDI "
-"does not somehow result in the addition of clustering capabilities (load "
-"balancing of EJB calls, transparent failover, state replication) to the EJB."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:337
-#, no-c-format
-msgid ""
-"If an EJB is configured as clustered, looking up the EJB via regular JNDI "
-"instead of HA-JNDI does not somehow result in the removal of the bean "
-"proxy's clustering capabilities."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:347
-#, no-c-format
-msgid "How it works"
-msgstr "Como funciona"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:348
-#, no-c-format
-msgid ""
-"The JBoss client-side HA-JNDI naming Context is based on the client-side "
-"interceptor architecture. The client obtains an HA-JNDI proxy object (via "
-"the InitialContext object) and invokes JNDI lookup services on the remote "
-"server through the proxy. The client specifies that it wants an HA-JNDI "
-"proxy by configuring the naming properties used by the InitialContext "
-"object. This is covered in detail in the “Client Configuration” section. "
-"Other than the need to ensure the appropriate naming properties are provided "
-"to the InitialContext, the fact that the naming Context is using HA-JNDI is "
-"completely transparent to the client."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:351
-#, fuzzy, no-c-format
-msgid ""
-"On the server side, he the HA-JNDI service maintains a cluster-wide context "
-"tree. The cluster wide tree is always available as long as there is one node "
-"left in the cluster. Each node in the cluster also maintains its own local "
-"JNDI context tree. The HA-JNDI service on that node is able to find objects "
-"bound into the local JNDI context tree. An application can bind its objects "
-"to either tree. The design rationale for this architecture is as follows:"
-msgstr ""
-"O serviço JBoss HA-JNDI (JNDI altamente disponível), mantém uma árvore de "
-"contexto cluster global. A árvore em cluster global está sempre disponível, "
-"desde que haja um nó no cluster. Cada nó JNDI no cluster também mantém seu "
-"próprio contexto local JNDI. O aplicativo do servidor pode conectar seus "
-"objetos a qualquer uma das árvores. Nesta seção, você aprenderá a diferença "
-"entre os dois tipos de árvores e as melhores práticas no desenvolvimento do "
-"aplicativo. Segue abaixo um exemplo do desenho lógico desta arquitetura."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:356
-#, fuzzy, no-c-format
-msgid ""
-"It avoids migration issues with applications that assume that their JNDI "
-"implementation is local. This allows clustering to work out-of-the-box with "
-"just a few tweaks of configuration files."
-msgstr ""
-"Não queriamos ter problemas de migração com aplicativos, considerando que "
-"suas implementações de JNDI fossem locais. Queriamos que o agrupamento "
-"funcionasse imediatamente com somente alguns ajustes de arquivos de "
-"configuração. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:362
-#, fuzzy, no-c-format
-msgid ""
-"In a homogeneous cluster, this configuration actually cuts down on the "
-"amount of network traffic. A homogenous cluster is one where the same types "
-"of objects are bound under the same names on each node."
-msgstr ""
-"Na verdade, em um cluster homogênio, esta configuração diminui o tráfego "
-"intenso na rede de trabalho. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:367
-#, no-c-format
-msgid ""
-"Designing it in this way makes the HA-JNDI service an optional service since "
-"all underlying cluster code uses a straight new <literal>InitialContext()</"
-"literal> to lookup or create bindings."
-msgstr ""
-"Com este formato, o serviço HA-JNDI torna-se um serviço opcional, uma vez "
-"que todos os códigos de cluster subjacentes utilizam um novo "
-"<literal>InitialContext()</literal> para consultar ou criar vinculações."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:373
-#, fuzzy, no-c-format
-msgid ""
-"On the server side, a naming <literal>Context</literal> obtained via a call "
-"to new <literal>InitialContext()</literal> will be bound to the local-only, "
-"non-cluster-wide JNDI Context (this is actually basic JNDI). So, all EJB "
-"homes and such will not be bound to the cluster-wide JNDI Context, but "
-"rather, each home will be bound into the local JNDI."
-msgstr ""
-"Para o servidor, o <literal>new InitialContext()</literal>, será limitado "
-"somente para Contexto JNDI local, cluster não global (ou seja, JNDI básico). "
-"Portanto, todos os diretórios base EJB e similares, não serão vinculados ao "
-"Contexto JNDI em cluster global, e sim cada diretório base será vinculado ao "
-"JNDI local. Quando um cliente remoto realiza uma consulta através do HA-"
-"JNDI, este delega para o Contexto JNDI local caso não consiga encontrar o "
-"objeto dentro do Contexto cluster global. Segue abaixo, políticas de "
-"consulta mais detalhadas: "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:376
-#, no-c-format
-msgid ""
-"When a remote client does a lookup through HA-JNDI, HA-JNDI will delegate to "
-"the local JNDI Context when it cannot find the object within the global "
-"cluster-wide Context. The detailed lookup rule is as follows."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:381
-#, no-c-format
-msgid "If the binding is available in the cluster-wide JNDI tree, return it."
-msgstr "Caso a vinculação esteja disponível na árvore JNDI em cluster global, retorne-a."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:384
-#, fuzzy, no-c-format
-msgid ""
-"If the binding is not in the cluster-wide tree, delegate the lookup query to "
-"the local JNDI service and return the received answer if available."
-msgstr ""
-"Caso a vinculação não esteja na árvore em cluster global, ela solicita uma "
-"consulta para o serviço JNDI local e retorna as respostas enviadas, caso "
-"estejam disponíveis."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:387
-#, fuzzy, no-c-format
-msgid ""
-"If not available, the HA-JNDI services asks all other nodes in the cluster "
-"if their local JNDI service owns such a binding and returns the answer from "
-"the set it receives."
-msgstr ""
-"Caso não esteja disponível, os serviços HA-JNDI pergunta à todos os nós no "
-"cluster se seus serviços JNDI locais, como uma vinculação, e retorna a "
-"resposta a partir do conjunto que ele recebe. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:390
-#, no-c-format
-msgid ""
-"If no local JNDI service owns such a binding, a "
-"<literal>NameNotFoundException</literal> is finally raised."
-msgstr ""
-"Caso o serviço JNDI possua tal vinculação, aparecerá finalmente um "
-"<literal>NameNotFoundException</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:394
-#, no-c-format
-msgid ""
-"In practice, objects are rarely bound in the cluster-wide JNDI tree; rather "
-"they are bound in the local JNDI tree. For example, when EJBs are deployed, "
-"their proxies are always bound in local JNDI, not HA-JNDI. So, an EJB home "
-"lookup done through HA-JNDI will always be delegated to the local JNDI "
-"instance."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:399
-#, fuzzy, no-c-format
-msgid ""
-"If different beans (even of the same type, but participating in different "
-"clusters) use the same JNDI name, this means that each JNDI server will have "
-"a logically different \"target\" bound (JNDI on node 1 will have a binding "
-"for bean A and JNDI on node 2 will have a binding, under the same name, for "
-"bean B). Consequently, if a client performs a HA-JNDI query for this name, "
-"the query will be invoked on any JNDI server of the cluster and will return "
-"the locally bound stub. Nevertheless, it may not be the correct stub that "
-"the client is expecting to receive! So, it is always best practice to ensure "
-"that across the cluster different names are used for logically different "
-"bindings."
-msgstr ""
-"Portanto, uma consulta no diretório base EJB através do HA-JNDI, será sempre "
-"delegada à instância JNDI local. Caso beans distintos (até mesmo do mesmo "
-"tipo, mas participando em clusters diferentes) usarem o mesmo nome JNDI, "
-"significa que cada servidor JNDI terá um limite \"alvo\"diferenciado (JNDI "
-"em nó 1 terá uma vinculação para o bean A e JNDI em nó 2 terá uma vinculação "
-"com o mesmo nome, para o bean B). Dessa forma, caso um cliente rode uma "
-"solicitação HA-JNDI para este mesmo nome, a solicitação será invocada em "
-"qualquer servidor JNDI de um cluster e retornará para o stub local "
-"vinculado. De qualquer forma, pode não ser o stub correto que o cliente "
-"esteja esperando receber. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:406
-#, fuzzy, no-c-format
-msgid ""
-"You cannot currently use a non-JNP JNDI implementation (i.e. LDAP) for your "
-"local JNDI implementation if you want to use HA-JNDI. However, you can use "
-"JNDI federation using the ExternalContext MBean to bind non-JBoss JNDI trees "
-"into the JBoss JNDI namespace. Furthermore, nothing prevents you using one "
-"centralized JNDI server for your whole cluster and scrapping HA-JNDI and JNP."
-msgstr ""
-"Se você quiser utilizar o HA-JNDI, você não poderá utilizar uma "
-"implementação que não seja JNP JNDI (ou seja, LDAP) para sua implementação "
-"JNDI local. No entanto, você poderá utilizar a comunidade JNDI utilizando o "
-"MBean <literal>ExternalContext</literal> para vincular as árvores JNDI, que "
-"não seja JBoss, para um espaço de nomes JNDI da JBoss. Além disso, nada o "
-"impede de utilizar um servidor JNDI centralizado para todo o seu cluster e "
-"desfazer-se do HA-JNDI e JNP."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:412
-#, fuzzy, no-c-format
-msgid ""
-"If a binding is only made available on a few nodes in the cluster (for "
-"example because a bean is only deployed on a small subset of nodes in the "
-"cluster), the probability that a lookup will hit a HA-JNDI server that does "
-"not own this binding is higher and thus the lookup will need to be forwarded "
-"to all nodes in the cluster. Consequently, the query time will be longer "
-"than if the binding would have been available locally. Moral of the story: "
-"as much as possible, cache the result of your JNDI queries in your client."
-msgstr ""
-"Caso uma vinculação esteja disponível somente em alguns nós no cluster ( por "
-"exemplo: porque um bean é implementado somente em um pequeno subconjunto de "
-"nós no cluster) a probabilidade de consultar um servidor HA-JNDI que não "
-"possua esta vinculação é maior, e a consulta será encaminhada para todos os "
-"nós no cluster. Dessa forma, o tempo de consulta será maior do que se a "
-"vinculação tivesse sido disponibilizada no local. Moral da estória, faça o "
-"cache do resultado de suas consultas do JNDI em seu cliente quantas vezes "
-"for preciso, "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:420
-#, no-c-format
-msgid ""
-"So, an EJB home lookup through HA-JNDI, will always be delegated to the "
-"local JNDI instance. If different beans (even of the same type, but "
-"participating in different clusters) use the same JNDI name, it means that "
-"each JNDI server will have a different \"target\" bound (JNDI on node 1 will "
-"have a binding for bean A and JNDI on node 2 will have a binding, under the "
-"same name, for bean B). Consequently, if a client performs a HA-JNDI query "
-"for this name, the query will be invoked on any JNDI server of the cluster "
-"and will return the locally bound stub. Nevertheless, it may not be the "
-"correct stub that the client is expecting to receive!"
-msgstr ""
-"Portanto, uma consulta no diretório base EJB através do HA-JNDI, será sempre "
-"delegada à instância JNDI local. Caso beans distintos (até mesmo do mesmo "
-"tipo, mas participando em clusters diferentes) usarem o mesmo nome JNDI, "
-"significa que cada servidor JNDI terá um limite \"alvo\"diferenciado (JNDI "
-"em nó 1 terá uma vinculação para o bean A e JNDI em nó 2 terá uma vinculação "
-"com o mesmo nome, para o bean B). Dessa forma, caso um cliente rode uma "
-"solicitação HA-JNDI para este mesmo nome, a solicitação será invocada em "
-"qualquer servidor JNDI de um cluster e retornará para o stub local "
-"vinculado. De qualquer forma, pode não ser o stub correto que o cliente "
-"esteja esperando receber. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:428
-#, no-c-format
-msgid ""
-"You cannot currently use a non-JNP JNDI implementation (i.e. LDAP) for your "
-"local JNDI implementation if you want to use HA-JNDI. However, you can use "
-"JNDI federation using the <literal>ExternalContext</literal> MBean to bind "
-"non-JBoss JNDI trees into the JBoss JNDI namespace. Furthermore, nothing "
-"prevents you though of using one centralized JNDI server for your whole "
-"cluster and scrapping HA-JNDI and JNP."
-msgstr ""
-"Se você quiser utilizar o HA-JNDI, você não poderá utilizar uma "
-"implementação que não seja JNP JNDI (ou seja, LDAP) para sua implementação "
-"JNDI local. No entanto, você poderá utilizar a comunidade JNDI utilizando o "
-"MBean <literal>ExternalContext</literal> para vincular as árvores JNDI, que "
-"não seja JBoss, para um espaço de nomes JNDI da JBoss. Além disso, nada o "
-"impede de utilizar um servidor JNDI centralizado para todo o seu cluster e "
-"desfazer-se do HA-JNDI e JNP."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:435
-#, no-c-format
-msgid ""
-"If a binding is only made available on a few nodes in the cluster (for "
-"example because a bean is only deployed on a small subset of nodes in the "
-"cluster), the probability to lookup a HA-JNDI server that does not own this "
-"binding is higher and the lookup will need to be forwarded to all nodes in "
-"the cluster. Consequently, the query time will be longer than if the binding "
-"would have been available locally. Moral of the story: as much as possible, "
-"cache the result of your JNDI queries in your client."
-msgstr ""
-"Caso uma vinculação esteja disponível somente em alguns nós no cluster ( por "
-"exemplo: porque um bean é implementado somente em um pequeno subconjunto de "
-"nós no cluster) a probabilidade de consultar um servidor HA-JNDI que não "
-"possua esta vinculação é maior, e a consulta será encaminhada para todos os "
-"nós no cluster. Dessa forma, o tempo de consulta será maior do que se a "
-"vinculação tivesse sido disponibilizada no local. Moral da estória, faça o "
-"cache do resultado de suas consultas do JNDI em seu cliente quantas vezes "
-"for preciso, "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:447
-#, no-c-format
-msgid "Client configuration"
-msgstr "Configuração do cliente"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:449
-#, no-c-format
-msgid "For clients running inside the application server"
-msgstr "Para clientes rodando dentro de servidor de aplicativo"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:450
-#, fuzzy, no-c-format
-msgid ""
-"If you want to access HA-JNDI from inside the application server, you must "
-"explicitly get an InitialContext by passing in JNDI properties. The "
-"following code shows how to create a naming Context bound to HA-JNDI:"
-msgstr ""
-"Se quiser acessar o HA-JNDI a partir do servidor, deve-se obter "
-"explicitamente um <literal>InitialContext</literal>, passando pelas "
-"propriedades do JNDI. O seguinte código mostra como acessar o HA-JNDI."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:453
-#, no-c-format
-msgid ""
-"Properties p = new Properties(); \n"
-" p.put(Context.INITIAL_CONTEXT_FACTORY, \n"
-" \"org.jnp.interfaces.NamingContextFactory\"); \n"
-" p.put(Context.URL_PKG_PREFIXES, \"jboss.naming:org.jnp.interfaces"
-"\"); \n"
-" p.put(Context.PROVIDER_URL, \"localhost:1100\"); // HA-JNDI port. \n"
-" return new InitialContext(p);"
-msgstr ""
-"Properties p = new Properties(); \n"
-" p.put(Context.INITIAL_CONTEXT_FACTORY, \n"
-" \"org.jnp.interfaces.NamingContextFactory\"); \n"
-" p.put(Context.URL_PKG_PREFIXES, \"jboss.naming:org.jnp.interfaces"
-"\"); \n"
-" p.put(Context.PROVIDER_URL, \"localhost:1100\"); // HA-JNDI port. \n"
-" return new InitialContext(p);"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:454
-#, fuzzy, no-c-format
-msgid ""
-"The Context.PROVIDER_URL property points to the HA-JNDI service configured "
-"in the HANamingService MBean (see the section called “JBoss configuration”)."
-msgstr ""
-"A propriedade <literal>Context.PROVIDER_URL</literal> aponta para o serviço "
-"HA-JNDI configurado em MBean <literal>HANamingService</literal> (veja<xref "
-"linkend=\"clustering-jndi-jboss\"/>). "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:457
-#, no-c-format
-msgid ""
-"Do not attempt to simplify things by placing a jndi.properties file in your "
-"deployment or by editing the AS's conf/jndi.properties file. Doing either "
-"will almost certainly break things for your application and quite possibly "
-"across the application server. If you want to externalize your client "
-"configuration, one approach is to deploy a properties file not named jndi."
-"properties, and then programatically create a Properties object that loads "
-"that file's contents."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:464
-#, no-c-format
-msgid "For clients running outside the application server"
-msgstr "Para clientes rodando fora do servidor de aplicativo"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:466
-#, fuzzy, no-c-format
-msgid ""
-"The JNDI client needs to be aware of the HA-JNDI cluster. You can pass a "
-"list of JNDI servers (i.e., the nodes in the HA-JNDI cluster) to the "
-"<literal>java.naming.provider.url</literal> JNDI setting in the "
-"<literal>jndi.properties</literal> file. Each server node is identified by "
-"its IP address and the JNDI port number. The server nodes are separated by "
-"commas (see <xref linkend=\"clustering-jndi-jboss\"/> for how to configure "
-"the servers and ports)."
-msgstr ""
-"O cliente JNDI precisa estar ciente do cluster HA-JNDI. Você poderá passar "
-"uma lista dos servidores JNDI ( ou seja, os nós no cluster HA-JNDI) às "
-"configurações JNDI <literal>java.naming.provider.url</literal> no arquivo "
-"<literal>jndi.properties</literal>. Cada nó de servidor é identificado pelos "
-"seus endereços IP e número da porta JNDI. Os nós de servidor são separados "
-"por vírgulas (veja <xref linkend=\"clustering-jndi-jboss\"/> em como "
-"configurar o servidor e portas). "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:468
-#, no-c-format
-msgid "java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100"
-msgstr "java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:469
-#, no-c-format
-msgid ""
-"When initialising, the JNP client code will try to get in touch with each "
-"server node from the list, one after the other, stopping as soon as one "
-"server has been reached. It will then download the HA-JNDI stub from this "
-"node."
-msgstr ""
-"Ao inicializar o código do cliente JNP, tente contatar cada nó de servidor a "
-"partir da lista, um por um, parando assim que um servidor tenha sido "
-"contatado. Ele irá baixar o stub do HA-JNDI a partir deste nó."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:473
-#, fuzzy, no-c-format
-msgid ""
-"There is no load balancing behavior in the JNP client lookup process itself. "
-"It just goes through the provider lists and uses the first available server "
-"to obtain the stub. The HA-JNDI provider list only needs to contain a subset "
-"of HA-JNDI nodes in the cluster."
-msgstr ""
-"Não há um comportamento de balanceamento de carga no processo de consulta do "
-"cliente JNP. Ele só passa pela lista do provedor e utiliza o primeiro "
-"servidor disponível. A lista do provedor HA-JNDI só precisa ter um "
-"subconjunto dos nós HA-JNDI no cluster. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:476
-#, fuzzy, no-c-format
-msgid ""
-"The downloaded smart proxy contains the list of currently running nodes and "
-"the logic to load balance naming requests and to fail-over to another node "
-"if necessary. Furthermore, each time a JNDI invocation is made to the "
-"server, the list of targets in the proxy interceptor is updated (only if the "
-"list has changed since the last call)."
-msgstr ""
-"O stub smart baixado contém a lógica de realizar o failover para outro nó, "
-"caso seja necessário, e uma lista atualizada dos nós que estejam rodando "
-"atualmente. Além disso, cada vez que é feita uma invocação JNDI para o "
-"servidor, a lista de alvos no interceptador do stub é atualizada (somente no "
-"caso da lista ter mudado desde a última chamada). "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:480
-#, fuzzy, no-c-format
-msgid ""
-"If the property string java.naming.provider.url is empty or if all servers "
-"it mentions are not reachable, the JNP client will try to discover a HA-JNDI "
-"server through a multicast call on the network (auto-discovery). See the "
-"section called “JBoss configuration” on how to configure auto-discovery on "
-"the JNDI server nodes. Through auto-discovery, the client might be able to "
-"get a valid HA-JNDI server node without any configuration. Of course, for "
-"auto-discovery to work, the network segment(s) between the client and the "
-"server cluster must be configured to propagate such multicast datagrams."
-msgstr ""
-"Caso a faixa de propriedade <literal>java.naming.provider.url</literal> "
-"esteja vazia ou se todos os servidores mencionados não estejam acessíveis, o "
-"cliente JNP tentará descobrir um servidor bootstrap HA-JNDI através de uma "
-"chamada multicast na rede de trabalho (auto-descoberta) Veja em <xref "
-"linkend=\"clustering-jndi-jboss\"/> como configurar o recurso auto-"
-"descoberta nos nós de servidor JNDI. Através do recurso auto-descoberta o "
-"cliente pode conseguir um nó de servidor HA-JNDI válido, sem nenhuma "
-"configuração. É claro que, para o recurso auto-descoberta funcionar, o "
-"cliente deve estar no mesmo LAN como um cluster de servidor (ex.: o web "
-"servlets utilizando os servidores EJB) O LAN ou WAN também deve estar "
-"configurado para propagar tais datagramas multicast. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:484
-#, no-c-format
-msgid ""
-"By default the auto-discovery feature uses multicast group address 230.0.0.4 "
-"and port1102."
-msgstr ""
-"O recurso de auto-descoberta utiliza o endereço do grupo de multicast "
-"230.0.0.4 e porta1102"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:486
-#, fuzzy, no-c-format
-msgid ""
-"In addition to the <literal>java.naming.provider.url</literal> property, you "
-"can specify a set of other properties. The following list shows all "
-"clustering-related client side properties you can specify when creating a "
-"new InitialContext. (All of the standard, non-clustering-related environment "
-"properties used with regular JNDI are also available.)"
-msgstr ""
-"Além da propriedade <literal>java.naming.provier.url</literal>, você poderá "
-"especificar outras propriedades. A lista a seguir mostra todas as "
-"propriedades de clientes que você poderá especificar ao criar um novo "
-"<literal>InitialContext</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:489
-#, fuzzy, no-c-format
-msgid ""
-"<literal>java.naming.provider.url</literal>: Provides a list of IP addresses "
-"and port numbers for HA-JNDI provider nodes in the cluster. The client tries "
-"those providers one by one and uses the first one that responds."
-msgstr ""
-"<literal>java.naming.provier.url</literal>: Oferece uma lista de endereços "
-"IP e números de portas para nós de proveodor HA-JNDI em cluster. O cliente "
-"tenta esses provedores um por um e utiliza o primeiro que responder. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:494
-#, no-c-format
-msgid ""
-"<literal>jnp.disableDiscovery</literal>: When set to <literal>true</"
-"literal>, this property disables the automatic discovery feature. Default is "
-"<literal>false</literal>."
-msgstr ""
-"<literal>jnp.disableDiscovery</literal>: Quando configurado como "
-"<literal>true</literal> esta propriedade desabilita o recurso da descoberta "
-"automática. O padrão é <literal>false</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:499
-#, fuzzy, no-c-format
-msgid ""
-"<literal>jnp.partitionName</literal>: In an environment where multiple HA-"
-"JNDI services bound to distinct clusters (a.k.a. partitions), are running, "
-"this property allows you to ensure that your client only accepts automatic-"
-"discovery responses from servers in the desired partition. If you do not use "
-"the automatic discovery feature (i.e. jnp.disableDiscovery is true), this "
-"property is not used. By default, this property is not set and the automatic "
-"discovery select the first HA-JNDI server that responds, irregardless of the "
-"cluster partition name."
-msgstr ""
-"<literal>jnp.partitionName</literal>: Em um ambiente onde os serviços "
-"múltiplos, que são vinculados a clusters distintos (ou seja, partições) são "
-"iniciados, esta propriedade permite que você configure para qual cluster "
-"você deve transmitir quando o recurso descoberta automática for utilizado. "
-"Se você não quiser utilizar o recurso descoberta automática (ex.: você "
-"poderia fornecer explicitamente uma lista de nós JNDI válidos em "
-"<literal>java.naming.provider.url</literal>), esta propriedade não será "
-"utilizada. Como padrão, esta propriedade não é configurada e o recurso "
-"descoberta automática seleciona o primeiro servidor HA-JNDI que responder, "
-"independentemente do nome da partição do cluster. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:502
-#, no-c-format
-msgid ""
-"<literal>jnp.discoveryTimeout</literal>: Determines how much time the "
-"context will wait for a response to its automatic discovery packet. Default "
-"is 5000 ms."
-msgstr ""
-"<literal>jnp.discoveryTimeout</literal>: Determina quanto tempo o contexto "
-"precisará esperar para obter a resposta do seu pacote descoberta automática. "
-"Seu valor padrão é 5000min."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:506
-#, fuzzy, no-c-format
-msgid ""
-"<literal>jnp.discoveryGroup</literal>: Determines which multicast group "
-"address is used for the automatic discovery. Default is 230.0.0.4. Must "
-"match the value of the AutoDiscoveryAddress configured on the server side HA-"
-"JNDI service."
-msgstr ""
-"<literal>jnp.discoveryGroup</literal>: Determina qual endereço de grupo "
-"multicast é usado para o recurso descoberta automática. Seu valor padrão é "
-"<literal>230.0.0.4</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:509
-#, fuzzy, no-c-format
-msgid ""
-"<literal>jnp.discoveryPort</literal>: Determines which multicast group port "
-"is used for the automatic discovery. Default is 1102. Must match the value "
-"of the AutoDiscoveryPort configured on the server side HA-JNDI service."
-msgstr ""
-"<literal>jnp.discoveryPort</literal>: Determina qual porta de grupo "
-"multicast é utilizado para o recurso descoberta automática. Padrão é "
-"<literal>1102</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:512
-#, no-c-format
-msgid ""
-"<literal>jnp.discoveryTTL</literal>: specifies the TTL (time-to-live) for "
-"autodiscovery IP multicast packets. This value represents the number of "
-"network hops a multicast packet can be allowed to propagate before "
-"networking equipment should drop the packet. Despite its name, it does not "
-"represent a unit of time."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:523
-#, no-c-format
-msgid "JBoss configuration"
-msgstr "Configuração do JBoss"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:524
-#, no-c-format
-msgid ""
-"The <literal>cluster-service.xml</literal> file in the <literal>all/deploy</"
-"literal> directory includes the following MBean to enable HA-JNDI services."
-msgstr ""
-"O arquivo <literal>cluster-service.xml</literal> no diretório <literal>all/"
-"deploy</literal>, inclui o seguinte MBean, para habilitar os serviços HA-"
-"JNDI."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:526
-#, no-c-format
-msgid ""
-"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
-" name=\"jboss:service=HAJNDI\"> \n"
-" <depends optional-attribute-name=\"ClusterPartition\" \n"
-" proxy-type=\"attribute\">jboss:service=${jboss.partition."
-"name:DefaultPartition}</depends> \n"
-" \n"
-"<mbean>"
-msgstr ""
-"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
-" name=\"jboss:service=HAJNDI\"> \n"
-" <depends optional-attribute-name=\"ClusterPartition\" \n"
-" proxy-type=\"attribute\">jboss:service=${jboss.partition."
-"name:DefaultPartition}</depends> \n"
-" \n"
-"<mbean>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:527
-#, fuzzy, no-c-format
-msgid ""
-"You can see that this MBean depends on the <literal>DefaultPartition</"
-"literal> MBean defined above it (discussed earlier in this chapter). In "
-"other configurations, you can put that element in the <literal>jboss-service."
-"xml</literal> file or any other JBoss configuration files in the <literal>/"
-"deploy</literal> directory to enable HA-JNDI services. The available "
-"attributes for this MBean are listed below."
-msgstr ""
-"Como você pode perceber, este MBean depende do MBean "
-"<literal>DefaultPartition</literal> definido acima deste (discutido em uma "
-"seção anterior neste mesmo capítulo). Em outras configurações, você pode "
-"colocar este elemento no arquivo <literal>jboss-services.xml</literal> ou em "
-"qualquer outro arquivo de configuração JBoss no diretório <literal>/deploy</"
-"literal> para habilitar os serviços HA-JNDI. As funções disponíveis para "
-"este MBean estão listadas abaixo:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:533
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Cluster Partition</emphasis> is a required attribute "
-"to inject the HAPartition service that HA-JNDI uses for intra-cluster "
-"communication."
-msgstr ""
-"<emphasis role=\"bold\">PartitionName</emphasis>é uma função alternativa "
-"para especificar o nome de um cluster. Seu valor padrão é "
-"<literal>DefaultPartition</literal>.."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:536
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">BindAddress</emphasis> is an optional attribute to "
-"specify the address to which the HA-JNDI server will bind waiting for JNP "
-"clients. Only useful for multi-homed computers. The default value is the "
-"value of the jboss.bind.address system property, or the host's default "
-"addresss if that property is not set. The jboss.bind.address system property "
-"is set if the -b command line switch is used when JBoss is started."
-msgstr ""
-"<emphasis role=\"bold\">BindAddress</emphasis> é uma função opcional para "
-"especificar o endereço onde o servidor HA-JNDI irá se conectar a espera por "
-"clientes JNP. Será útil somente para computadores de bases múltiplas."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:539
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Port</emphasis> is an optional attribute to specify "
-"the port to which the HA-JNDI server will bind waiting for JNP clients. The "
-"default value is <literal>1100</literal>."
-msgstr ""
-"<emphasis role=\"bold\">Port</emphasis> é uma função alternativa para "
-"especificar a porta onde o servidor HA-JNDI irá se conectar a espera de "
-"clientes JNP. Seu valor padrão é <literal>1100</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:544
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Backlog</emphasis> is an optional attribute to "
-"specify the backlog value used for the TCP server socket waiting for JNP "
-"clients. The default value is <literal>50</literal>."
-msgstr ""
-"<emphasis role=\"bold\">Backlog</emphasis> é uma função alternativa para "
-"especificar o valor do backlog utilizado para o soquete do servidor TCP a "
-"espera de clientes JNP. Seu valor padrão é <literal>50</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:549
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">RmiPort</emphasis> determines which port the server "
-"should use to communicate with the downloaded stub. This attribute is "
-"optional. The default value is 1101. If no value is set, the server "
-"automatically assigns a RMI port."
-msgstr ""
-"<emphasis role=\"bold\">RmiPort</emphasis> determina qual porta o servidor "
-"deve utilizar para se comunicar com o stub baixado. Esta função é "
-"alternativa. Caso não exista, o servidor escolherá automaticamente um porta "
-"RMI."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:552
-#, fuzzy, no-c-format
-msgid ""
-"<literal>DiscoveryDisabled</literal> is a boolean flag that disables "
-"configuration of the auto discovery multicast listener."
-msgstr ""
-"<emphasis role=\"bold\">DiscoveryDisabled</emphasis> é um sinalizador "
-"booleano que desabilita a configuração de ouvintes multicast do recurso auto "
-"descoberta."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:558
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">AutoDiscoveryAddress</emphasis> is an optional "
-"attribute to specify the multicast address to listen to for JNDI automatic "
-"discovery. The default value is the value of the jboss.partition.udpGroup "
-"system property, or 230.0.0.4 if that is not set. The jboss.partition."
-"udpGroup system property is set if the -u command line switch is used when "
-"JBoss is started."
-msgstr ""
-"<emphasis role=\"bold\">AutoDiscoveryAddress</emphasis> é uma função "
-"alternativa para especificar o endereço multicast para o recurso descoberta "
-"automática JNDI. O valor padrão é <literal>230.0.0.4</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:561
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">AutoDiscoveryGroup</emphasis> is an optional "
-"attribute to specify the multicast group to listen to for JNDI automatic "
-"discovery.. The default value is <literal>1102</literal>."
-msgstr ""
-"<emphasis role=\"bold\">AutoDiscoveryGroup</emphasis> é uma função "
-"alternativa para especificar um grupo multicast para um recurso descoberta "
-"automática. O valor padrão é <literal>1102</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:567
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">AutoDiscoveryBindAddress</emphasis> sets the "
-"interface on which HA-JNDI should listen for auto-discovery request packets. "
-"If this attribute is not specified and a <literal>BindAddress</literal> is "
-"specified, the <literal>BindAddress</literal> will be used.."
-msgstr ""
-"<emphasis role=\"bold\">AutoDiscoveryBindAddress</emphasis> estabelece o "
-"endereço de vinculação do bootstrap multicast da auto descoberta. Se esta "
-"função não estiver especificada e um<literal>BindAddress</literal> for "
-"especificado, será usado <literal>BindAddress</literal> ."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:570
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">AutoDiscoveryTTL</emphasis> specifies the TTL (time-"
-"to-live) for autodiscovery IP multicast packets. This value represents the "
-"number of network hops a multicast packet can be allowed to propagate before "
-"networking equipment should drop the packet. Despite its name, it does not "
-"represent a unit of time."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:573
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">LoadBalancePolicy</emphasis> specifies the class "
-"name of the LoadBalancePolicyimplementation that should be included in the "
-"client proxy. See the earlier section on “Load-Balancing Policies” for "
-"details."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:578
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">LookupPool</emphasis> specifies the thread pool "
-"service used to control the bootstrap and auto discovery lookups."
-msgstr ""
-"<emphasis role=\"bold\">LookupPool</emphasis> especifica o serviço de pool "
-"de discussão usado no controle de bootstrap e consultas ao recurso auto "
-"descoberta."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:583
-#, no-c-format
-msgid ""
-"The full default configuration of the <literal>HANamingService</literal> "
-"MBean is as follows."
-msgstr ""
-"A seguir, veja a configuração padrão completa do MBean "
-"<literal>HANamingService</literal> "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:584
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-" <mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
-" name=\"jboss:service=HAJNDI\"> \n"
-" <!-- We now inject the partition into the HAJNDI service instead \n"
-" of requiring that the partition name be passed --> \n"
-" <depends optional-attribute-name=\"ClusterPartition\" \n"
-" proxy-type=\"attribute\">jboss:service=${jboss.partition.name:"
-"DefaultPartition}</depends> \n"
-" <!-- Bind address of bootstrap and HA-JNDI RMI endpoints --> \n"
-" <attribute name=\"BindAddress\">${jboss.bind.address}</attribute> \n"
-" <!-- Port on which the HA-JNDI stub is made available --> \n"
-" <attribute name=\"Port\">1100</attribute> \n"
-" <!-- RmiPort to be used by the HA-JNDI service once bound. 0 => "
-"auto. --> \n"
-" <attribute name=\"RmiPort\">1101</attribute> \n"
-" <!-- Accept backlog of the bootstrap socket --> \n"
-" <attribute name=\"Backlog\">50</attribute> \n"
-" <!-- The thread pool service used to control the bootstrap and auto "
-"discovery lookups --> \n"
-" <depends optional-attribute-name=\"LookupPool\" \n"
-" proxy-type=\"attribute\">jboss.system:service=ThreadPool</"
-"depends> \n"
-" <!-- A flag to disable the auto discovery via multicast --> \n"
-" <attribute name=\"DiscoveryDisabled\">false</attribute> \n"
-" <!-- Set the auto-discovery bootstrap multicast bind address. If "
-"not \n"
-" specified and a BindAddress is specified, the BindAddress will be "
-"used. --> \n"
-" <attribute name=\"AutoDiscoveryBindAddress\">${jboss.bind.address}</"
-"attribute> \n"
-" <!-- Multicast Address and group port used for auto-discovery --> \n"
-" <attribute name=\"AutoDiscoveryAddress\">${jboss.partition."
-"udpGroup:230.0.0.4}</attribute> \n"
-" <attribute name=\"AutoDiscoveryGroup\">1102</attribute> \n"
-" <!-- The TTL (time-to-live) for autodiscovery IP multicast packets "
-"--> \n"
-" <attribute name=\"AutoDiscoveryTTL\">16</attribute> \n"
-" <!-- The load balancing policy for HA-JNDI --> \n"
-" <attribute name=\"LoadBalancePolicy\">org.jboss.ha.framework."
-"interfaces.RoundRobin</attribute> \n"
-" \n"
-" <!-- Client socket factory to be used for client-server \n"
-" RMI invocations during JNDI queries \n"
-" <attribute name=\"ClientSocketFactory\">custom</attribute> \n"
-" --> \n"
-" <!-- Server socket factory to be used for client-server \n"
-" RMI invocations during JNDI queries \n"
-" <attribute name=\"ServerSocketFactory\">custom</attribute> \n"
-" --> \n"
-" </mbean>]]>"
-msgstr ""
-"<![CDATA[\n"
-" <mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
-" name=\"jboss:service=HAJNDI\"> \n"
-" <!-- We now inject the partition into the HAJNDI service instead \n"
-" of requiring that the partition name be passed --> \n"
-" <depends optional-attribute-name=\"ClusterPartition\" \n"
-" proxy-type=\"attribute\">jboss:service=${jboss.partition.name:"
-"DefaultPartition}</depends> \n"
-" <!-- Bind address of bootstrap and HA-JNDI RMI endpoints --> \n"
-" <attribute name=\"BindAddress\">${jboss.bind.address}</attribute> \n"
-" <!-- Port on which the HA-JNDI stub is made available --> \n"
-" <attribute name=\"Port\">1100</attribute> \n"
-" <!-- RmiPort to be used by the HA-JNDI service once bound. 0 => "
-"auto. --> \n"
-" <attribute name=\"RmiPort\">1101</attribute> \n"
-" <!-- Accept backlog of the bootstrap socket --> \n"
-" <attribute name=\"Backlog\">50</attribute> \n"
-" <!-- The thread pool service used to control the bootstrap and auto "
-"discovery lookups --> \n"
-" <depends optional-attribute-name=\"LookupPool\" \n"
-" proxy-type=\"attribute\">jboss.system:service=ThreadPool</"
-"depends> \n"
-" <!-- A flag to disable the auto discovery via multicast --> \n"
-" <attribute name=\"DiscoveryDisabled\">false</attribute> \n"
-" <!-- Set the auto-discovery bootstrap multicast bind address. If "
-"not \n"
-" specified and a BindAddress is specified, the BindAddress will be "
-"used. --> \n"
-" <attribute name=\"AutoDiscoveryBindAddress\">${jboss.bind.address}</"
-"attribute> \n"
-" <!-- Multicast Address and group port used for auto-discovery --> \n"
-" <attribute name=\"AutoDiscoveryAddress\">${jboss.partition."
-"udpGroup:230.0.0.4}</attribute> \n"
-" <attribute name=\"AutoDiscoveryGroup\">1102</attribute> \n"
-" <!-- The TTL (time-to-live) for autodiscovery IP multicast packets "
-"--> \n"
-" <attribute name=\"AutoDiscoveryTTL\">16</attribute> \n"
-" <!-- The load balancing policy for HA-JNDI --> \n"
-" <attribute name=\"LoadBalancePolicy\">org.jboss.ha.framework."
-"interfaces.RoundRobin</attribute> \n"
-" \n"
-" <!-- Client socket factory to be used for client-server \n"
-" RMI invocations during JNDI queries \n"
-" <attribute name=\"ClientSocketFactory\">custom</attribute> \n"
-" --> \n"
-" <!-- Server socket factory to be used for client-server \n"
-" RMI invocations during JNDI queries \n"
-" <attribute name=\"ServerSocketFactory\">custom</attribute> \n"
-" --> \n"
-" </mbean>]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:585
-#, fuzzy, no-c-format
-msgid ""
-"It is possible to start several HA-JNDI services that use different "
-"clusters. This can be used, for example, if a node is part of many clusters. "
-"In this case, make sure that you set a different port or IP address for "
-"eachservices. For instance, if you wanted to hook up HA-JNDI to the example "
-"cluster you set up and change the binding port, the Mbean descriptor would "
-"look as follows."
-msgstr ""
-"É impossível iniciar diversos serviços HA-JNDI que use clusters distintos. "
-"Isto pode ser usado, por exemplo, se um nó fizer parte de vários clusters. "
-"Neste caso, tenha certeza de que criou uma porta diferente ou um endereço IP "
-"para ambos os serviços. Como por exemplo, se quisesse unir HA-JNDI ao "
-"cluster que criou e mudar a porta de vinculação, o descritor MBean se "
-"pareceria com o seguinte: "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:588
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
-" name=\"jboss:service=HAJNDI\"> \n"
-"\n"
-" <depends optional-attribute-name=\"ClusterPartition\" \n"
-" proxy-type=\"attribute\">jboss:service=MySpecialPartition</depends> \n"
-" <attribute name=\"Port\">56789</attribute> \n"
-"</mbean> ]]>"
-msgstr ""
-"<![CDATA[\n"
-"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
-" name=\"jboss:service=HAJNDI\"> \n"
-"\n"
-" <depends optional-attribute-name=\"ClusterPartition\" \n"
-" proxy-type=\"attribute\">jboss:service=MySpecialPartition</depends> \n"
-" <attribute name=\"Port\">56789</attribute> \n"
-"</mbean> ]]>"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:595
-#, no-c-format
-msgid "Clustered Session EJBs"
-msgstr "EJBs de Sessão em Cluster. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:596
-#, no-c-format
-msgid ""
-"Session EJBs provide remote invocation services. They are clustered based on "
-"the client-side interceptor architecture. The client application for a "
-"clustered session bean is exactly the same as the client for the non-"
-"clustered version of the session bean, except for a minor change to the "
-"<literal>java.naming.provier.url</literal> system property to enable HA-JNDI "
-"lookup (see previous section). No code change or re-compilation is needed on "
-"the client side. Now, let's check out how to configure clustered session "
-"beans in EJB 2.x and EJB 3.0 server applications respectively."
-msgstr ""
-"Os EJBs de sessão oferecem serviços de invocação remotos. Eles são baseados "
-"em cluster na arquitetura do interceptador do cliente. O aplicativo do "
-"cliente para um bean de sessão em cluster é exatamente igual ao cliente para "
-"uma versão de bean de sessão que não seja em cluster, com exceção de uma "
-"pequena mudança na propriedade do sistema <literal>java.naming.provier.url</"
-"literal> para permitir a consulta HA-JNDI (veja a seção anterior). Não é "
-"necessário nenhuma mudança de código ou recompilação no cliente. Agora, "
-"vamos ver como configurar o bean de sessão em cluster nos aplicativos dos "
-"servidores EJB 2.x e EJB 3.0 respectivamente. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:603
-#, no-c-format
-msgid "Stateless Session Bean in EJB 2.x"
-msgstr "Bean de Sessão sem Estado em EJB 2.x"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:604
-#, no-c-format
-msgid ""
-"Clustering stateless session beans is most probably the easiest case: as no "
-"state is involved, calls can be load-balanced on any participating node (i."
-"e. any node that has this specific bean deployed) of the cluster. To make a "
-"bean clustered, you need to modify its <literal>jboss.xml</literal> "
-"descriptor to contain a <literal><clustered></literal> tag."
-msgstr ""
-"É bastante provável que o bean de sessão sem estado em cluster seja o caso "
-"mais fácil: como não envolve o estado, as chamadas podem ser balanceadas em "
-"qualquer nó do cluster (ex.: 'qualquer nó que tenha implementado este bean "
-"em específico). Para fazer um bean em cluster, você precisará modificar seu "
-"descritor <literal>jboss.xml</literal> a fim de conter uma tag <literal><"
-"clustered></literal>"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:608
-#, no-c-format
-msgid ""
-"<jboss> \n"
-" <enterprise-beans> \n"
-" <session> \n"
-" <ejb-name>nextgen.StatelessSession</ejb-"
-"name> \n"
-" <jndi-name>nextgen.StatelessSession</jndi-"
-"name> \n"
-" <clustered>True</clustered> \n"
-" <cluster-config> \n"
-" <partition-name>DefaultPartition</partition-"
-"name> \n"
-" <home-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces.RoundRobin \n"
-" </home-load-balance-policy> \n"
-" <bean-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces.RoundRobin\n"
-" </bean-load-balance-policy>\n"
-" </cluster-config>\n"
-" </session>\n"
-" </enterprise-beans>\n"
-"</jboss>"
-msgstr ""
-"<jboss> \n"
-" <enterprise-beans> \n"
-" <session> \n"
-" <ejb-name>nextgen.StatelessSession</ejb-"
-"name> \n"
-" <jndi-name>nextgen.StatelessSession</jndi-"
-"name> \n"
-" <clustered>True</clustered> \n"
-" <cluster-config> \n"
-" <partition-name>DefaultPartition</partition-"
-"name> \n"
-" <home-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces.RoundRobin \n"
-" </home-load-balance-policy> \n"
-" <bean-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces.RoundRobin\n"
-" </bean-load-balance-policy>\n"
-" </cluster-config>\n"
-" </session>\n"
-" </enterprise-beans>\n"
-"</jboss>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:611
-#, fuzzy, no-c-format
-msgid ""
-"The <literal><clustered>True</clustered></literal> element is "
-"really just an alias for the <literal><configuration-name>Clustered "
-"Stateless SessionBean</configuration-name></literal> element in the "
-"conf/standard-jboss.xml file."
-msgstr ""
-"O elemento <literal><clustered>True</clustered></literal> é na "
-"verdade, somente um outro nome para o elemento <literal><configuration-"
-"name>ClusteredStateless SessionBean</configuration-name></literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:616
-#, fuzzy, no-c-format
-msgid ""
-"In the bean configuration, only the <clustered> element is mandatory. "
-"It indicates that the bean needs to support clustering features. The <"
-"cluster-config> element is optional and the default values of its "
-"attributes are indicated in the sample configuration above. Below is a "
-"description of the attributes in the <cluster-config> element.."
-msgstr ""
-"Na configuração do bean, somente o elemento <literal><clustered></"
-"literal> é obrigatório. Ele indica que o bean funciona em um cluster. O "
-"elemento <literal><cluster-config></literal> é alternativo e os "
-"valores padrão de sua função estão indicados no exemplo de configuração "
-"acima. Abaixo segue uma descrição das funções do elemento <literal><"
-"cluster-config></literal>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:619
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">partition-name</emphasis> specifies the name of the "
-"cluster the bean participates in. The default value is "
-"<literal>DefaultPartition</literal>. The default partition name can also be "
-"set system-wide using the <literal>jboss.partition.name</literal> system "
-"property."
-msgstr ""
-"<emphasis role=\"bold\">partition-name</emphasis> especifica o nome do "
-"cluster em que o bean se encontra. O valor padrão é "
-"<literal>DefaultPartition</literal>. O nome da partição padrão também pode "
-"ser estabelecido em todo o sistema utilizando a propriedade do sistema "
-"<literal>jboss.partition.name</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:625
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">home-load-balance-policy</emphasis> indicates the "
-"class to be used by the home stub to balance calls made on the nodes of the "
-"cluster. By default, the proxy will load-balance calls in a "
-"<literal>RoundRobin</literal> fashion. You can also implement your own load-"
-"balance policy class or use the class <literal>FirstAvailable</literal> that "
-"persists to use the first node available that it meets until it fails."
-msgstr ""
-"<emphasis role=\"bold\">home-load-balance-policy</emphasis>indica a classe a "
-"ser utilizada pelo diretório base stub para balancear chamadas feitas nos "
-"nós do cluster. O proxy irá balancear a carga de chamadas como padrão. Você "
-"também pode implementar sua própria classe de políticas de balanceamento de "
-"carga <literal>FirstAvailable</literal> que continuará utilizando o primeiro "
-"nó disponível que encontrar, até falhar."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:632
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">bean-load-balance-policy</emphasis> Indicates the "
-"class to be used by the bean stub to balance calls made on the nodes of the "
-"cluster. Comments made for the <literal>home-load-balance-policy</literal> "
-"attribute also apply."
-msgstr ""
-"<emphasis role=\"bold\">bean-load-balance-policy</emphasis> indica a classe "
-"a ser utilizada pelo bean stub para balancear chamadas feitas em nós de "
-"cluster. Comentários feitos pela função <literal>home-load-balance-policy</"
-"literal> também se aplicam a essa política."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:641
-#, no-c-format
-msgid "Stateful Session Bean in EJB 2.x"
-msgstr "Bean de Sessão com Estado em EJB 2.x"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:642
-#, no-c-format
-msgid ""
-"Clustering stateful session beans is more complex than clustering their "
-"stateless counterparts since JBoss needs to manage the state information. "
-"The state of all stateful session beans are replicated and synchronized "
-"across the cluster each time the state of a bean changes. The JBoss AS uses "
-"the <literal>HASessionState</literal> MBean to manage distributed session "
-"states for clustered EJB 2.x stateful session beans. In this section, we "
-"cover both the session bean configuration and the <literal>HASessionState</"
-"literal> MBean configuration."
-msgstr ""
-"O Agrupamento de beans de sessão com estado é mais complexo do que realizar "
-"o agrupamento de seus complementos sem estado, uma vez que o JBoss precisa "
-"gerenciar informações sobre o estado. O estado de todos os beans de sessão "
-"com estado são replicados e sincronizados com o cluster cada vez que o "
-"estado de um bean muda. O JBoss AS utiliza o MBean <literal>HASessionState</"
-"literal> para gerenciar os estados de sessão distribuídos para beans de "
-"sessão com estado EJB 2.x em cluster. Nesta seção, trataremos tanto das "
-"configurações de bean de sessão quanto da configuração MBean "
-"<literal>HASessionState</literal>."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:649
-#, no-c-format
-msgid "The EJB application configuration"
-msgstr "A configuração do aplicativo EJB"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:650
-#, no-c-format
-msgid ""
-"In the EJB application, you need to modify the <literal>jboss.xml</literal> "
-"descriptor file for each stateful session bean and add the <literal><"
-"clustered></literal> tag."
-msgstr ""
-"No aplicativo EJB, você precisará modificar o arquivo do descritor "
-"<literal>jboss.xml</literal> para cada bean de sessão com estado e "
-"adicionar a aba <literal><clustered></literal>."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:652
-#, no-c-format
-msgid ""
-"<jboss> \n"
-" <enterprise-beans>\n"
-" <session> \n"
-" <ejb-name>nextgen.StatefulSession</ejb-"
-"name> \n"
-" <jndi-name>nextgen.StatefulSession</jndi-"
-"name> \n"
-" <clustered>True</clustered> \n"
-" <cluster-config> \n"
-" <partition-name>DefaultPartition</partition-"
-"name>\n"
-" <home-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces.RoundRobin \n"
-" </home-load-balance-policy> \n"
-" <bean-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces."
-"FirstAvailable \n"
-" </bean-load-balance-policy> \n"
-" <session-state-manager-jndi-name> \n"
-" /HASessionState/Default \n"
-" </session-state-manager-jndi-name> \n"
-" </cluster-config> \n"
-" </session> \n"
-" </enterprise-beans>\n"
-"</jboss>"
-msgstr ""
-"<jboss> \n"
-" <enterprise-beans>\n"
-" <session> \n"
-" <ejb-name>nextgen.StatefulSession</ejb-"
-"name> \n"
-" <jndi-name>nextgen.StatefulSession</jndi-"
-"name> \n"
-" <clustered>True</clustered> \n"
-" <cluster-config> \n"
-" <partition-name>DefaultPartition</partition-"
-"name>\n"
-" <home-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces.RoundRobin \n"
-" </home-load-balance-policy> \n"
-" <bean-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces."
-"FirstAvailable \n"
-" </bean-load-balance-policy> \n"
-" <session-state-manager-jndi-name> \n"
-" /HASessionState/Default \n"
-" </session-state-manager-jndi-name> \n"
-" </cluster-config> \n"
-" </session> \n"
-" </enterprise-beans>\n"
-"</jboss>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:653
-#, no-c-format
-msgid ""
-"In the bean configuration, only the <literal><clustered></literal> tag "
-"is mandatory to indicate that the bean works in a cluster. The <literal><"
-"cluster-config></literal> element is optional and its default attribute "
-"values are indicated in the sample configuration above."
-msgstr ""
-"Na configuração do bean, somente a aba <literal><clustered></literal> "
-"é obrigatória para indicar que o bean funciona em um cluster. O elemento "
-"<literal><cluster-config></literal> é opcional e os valores de sua "
-"função padrão estão indicados no exemplo de configuração logo abaixo:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:657
-#, no-c-format
-msgid ""
-"The <literal><session-state-manager-jndi-name></literal> tag is used "
-"to give the JNDI name of the <literal>HASessionState</literal> service to be "
-"used by this bean."
-msgstr ""
-"A aba <literal><session-state-manager-jndi-name></literal>é utilizada "
-"para dar o nome do JNDI do serviço <literal>HASessionState</literal> para "
-"ser utilizada por este bean. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:659
-#, no-c-format
-msgid ""
-"The description of the remaining tags is identical to the one for stateless "
-"session bean. Actions on the clustered stateful session bean's home "
-"interface are by default load-balanced, round-robin. Once the bean's remote "
-"stub is available to the client, calls will not be load-balanced round-robin "
-"any more and will stay \"sticky\" to the first node in the list."
-msgstr ""
-"A descrição das abas restantes é idêntica ao bean de sessão sem estado. As "
-"ações na interface do diretório base do bean de sessão sem estado em "
-"cluster, possuem a carga balanceada, round-robin por padrão. Uma vez que o "
-"stub remoto do bean está disponível para o cliente, as chamadas não terão "
-"mais o round-robin de carga balanceada e ficarão \"aderentes\" ao o primeiro "
-"nó da lista. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:665
-#, no-c-format
-msgid "Optimize state replication"
-msgstr "Otimizar a replicação do estado"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:666
-#, no-c-format
-msgid ""
-"As the replication process is a costly operation, you can optimise this "
-"behaviour by optionally implementing in your bean class a method with the "
-"following signature:"
-msgstr ""
-"Como o processo de replicação é uma operação custosa, você pode otimizar "
-"este comportamento implementando em sua classe de bean, um método com a "
-"seguinte assinatura:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:668
-#, no-c-format
-msgid "public boolean isModified ();"
-msgstr "O Booleano público está modificado ();"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:669
-#, no-c-format
-msgid ""
-"Before replicating your bean, the container will detect if your bean "
-"implements this method. If your bean does, the container calls the "
-"<literal>isModified()</literal> method and it only replicates the bean when "
-"the method returns <literal>true</literal>. If the bean has not been "
-"modified (or not enough to require replication, depending on your own "
-"preferences), you can return <literal>false</literal> and the replication "
-"would not occur. This feature is available on JBoss AS 3.0.1+ only."
-msgstr ""
-"Antes de replicar seu bean o recipiente irá detectar se ele irá implementar "
-"este método. Caso isto aconteça, o recipiente chama o método "
-"<literal>isModified()</literal> e ele só replica o bean quando o método "
-"retornar para<literal>true</literal>. Caso o bean não tenha sido modificado "
-"(ou não o suficiente para pedir a replicação, dependendo de suas "
-"preferências), você poderá retornar para <literal>false</literal> e a "
-"replicação não acontecerá. Esta função está disponível somente em JBoss AS "
-"3.0.1+"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:677
-#, no-c-format
-msgid "The HASessionState service configuration"
-msgstr "A configuração do serviço de Estado de Sessão HA."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:678
-#, no-c-format
-msgid ""
-"The <literal>HASessionState</literal> service MBean is defined in the "
-"<code>all/deploy/cluster-service.xml</code> file."
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:680
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"<mbean code=\"org.jboss.ha.hasessionstate.server.HASessionStateService\"\n"
-" name=\"jboss:service=HASessionState\">\n"
-" \n"
-" <depends>jboss:service=Naming</depends> \n"
-" <!-- We now inject the partition into the HAJNDI service instead \n"
-" of requiring that the partition name be passed --> \n"
-" <depends optional-attribute-name=\"ClusterPartition\" \n"
-" proxy-type=\"attribute\">\n"
-" jboss:service=${jboss.partition.name:DefaultPartition}\n"
-" </depends>\n"
-" <!-- JNDI name under which the service is bound -->\n"
-" <attribute name=\"JndiName\">/HASessionState/Default</attribute>\n"
-" <!-- Max delay before cleaning unreclaimed state.\n"
-"Defaults to 30*60*1000 => 30 minutes -->\n"
-"<attribute name=\"BeanCleaningDelay\">0</attribute>\n"
-"</mbean> ]]>"
-msgstr ""
-"<![CDATA[ \n"
-"<mbean code=\"org.jboss.ha.hasessionstate.server.HASessionStateService\"\n"
-" name=\"jboss:service=HASessionState\">\n"
-" \n"
-" <depends>jboss:service=Naming</depends> \n"
-" <!-- We now inject the partition into the HAJNDI service instead \n"
-" of requiring that the partition name be passed --> \n"
-" <depends optional-attribute-name=\"ClusterPartition\" \n"
-" proxy-type=\"attribute\">\n"
-" jboss:service=${jboss.partition.name:DefaultPartition}\n"
-" </depends>\n"
-" <!-- JNDI name under which the service is bound -->\n"
-" <attribute name=\"JndiName\">/HASessionState/Default</attribute>\n"
-" <!-- Max delay before cleaning unreclaimed state.\n"
-"Defaults to 30*60*1000 => 30 minutes -->\n"
-"<attribute name=\"BeanCleaningDelay\">0</attribute>\n"
-"</mbean> ]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:682
-#, no-c-format
-msgid ""
-"The configuration attributes in the <literal>HASessionState</literal> MBean "
-"are listed below."
-msgstr ""
-"As funções de configuração no MBean <literal>HASessionState</literal> estão "
-"listadas abaixo:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:685
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ClusterPartition</emphasis> is a required attribute "
-"to inject the HAPartition service that HA-JNDI uses for intra-cluster "
-"communication."
-msgstr ""
-"<emphasis role=\"bold\">PartitionName</emphasis>é uma função alternativa "
-"para especificar o nome de um cluster. Seu valor padrão é "
-"<literal>DefaultPartition</literal>.."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:690
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">JndiName</emphasis> is an optional attribute to "
-"specify the JNDI name under which this <literal>HASessionState</literal> "
-"service is bound. The default value is <literal>/HAPartition/Default</"
-"literal>."
-msgstr ""
-"<emphasis role=\"bold\">JndiName</emphasis> é uma função opcional para "
-"especificar o nome JNDI sob o qual este serviço <literal>HASessionState</"
-"literal> está vinculado. Seu valor padrão é <literal>/HAPartition/Default</"
-"literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:696
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">BeanCleaningDelay</emphasis> is an optional "
-"attribute to specify the number of miliseconds after which the "
-"<literal>HASessionState</literal> service can clean a state that has not "
-"been modified. If a node, owning a bean, crashes, its brother node will take "
-"ownership of this bean. Nevertheless, the container cache of the brother "
-"node will not know about it (because it has never seen it before) and will "
-"never delete according to the cleaning settings of the bean. That is why the "
-"<literal>HASessionState</literal> service needs to do this cleanup "
-"sometimes. The default value is <literal>30*60*1000</literal> milliseconds "
-"(i.e., 30 minutes)."
-msgstr ""
-"<emphasis role=\"bold\">BeanCleaningDelay</emphasis> é uma função "
-"alternativa para especificar quantos milisegundos o serviço precisará "
-"esperar para poder limpar o estado que não tenha sido modificado. Caso um nó "
-"com um bean, travar, seu nó irmão tomará posse deste bean. No entanto, o "
-"recipiente cache do nó irmão não saberá nada sobre isso (pois nunca foi "
-"visto antes) e não irá deletar de acordo com as configurações da limpeza do "
-"bean. É por isso que o serviço <literal>HASessionState</literal> precisa, às "
-"vezes, fazer uma limpeza. Seu valor padrão é <literal>30*60*1000</literal> "
-"milisegundos (ou seja, 30 minutos)"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:707
-#, no-c-format
-msgid "Handling Cluster Restart"
-msgstr "Manipulando a Reinicialização do Cluster"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:708
-#, fuzzy, no-c-format
-msgid ""
-"We have covered the HA smart client architecture in the section called "
-"“Client-side interceptor architecture”. The default HA smart proxy client "
-"can only failover as long as one node in the cluster exists. If there is a "
-"complete cluster shutdown, the proxy becomes orphaned and loses knowledge of "
-"the available nodes in the cluster. There is no way for the proxy to recover "
-"from this. The proxy needs to look up a fresh set of targets out of JNDI/"
-"HAJNDI when the nodes are restarted."
-msgstr ""
-"Tratamos da arquitetura de cliente smart HA em <xref linkend=\"clustering-"
-"intro-arch-proxy\"/>. O cliente smart proxy do HA padrão, pode acontecer "
-"somente no caso de um nó em cluster existir. Se o Cluster se fechar "
-"completamente, o proxy se tornará órfão e não perderá a informação sobre a "
-"disponibilidade dos nós em cluster. Não existe uma maneira do proxy se "
-"recuperar disto. O proxy precisa estar trancado no JNDI/HAJNDI quando os nós "
-"forem reiniciados. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:711
-#, fuzzy, no-c-format
-msgid ""
-"The 3.2.7+/4.0.2+ releases contain a RetryInterceptor that can be added to "
-"the proxy client side interceptor stack to allow for a transparent recovery "
-"from such a restart failure. To enable it for an EJB, setup an invoker-proxy-"
-"binding that includes the RetryInterceptor. Below is an example jboss.xml "
-"configuration."
-msgstr ""
-"O 3.2.7+/4.0.2+ possui um <literal>RetryInterceptor</literal> que pode ser "
-"adicionado à pilha de interceptador do cliente proxy para considerar uma "
-"recuperação transparente de uma falha de reinício. Para habilitá-lo para um "
-"EJB, instale um <literal>invoker-proxy-binding</literal> que inclui o "
-"<literal>RetryInterceptor</literal>. Segue abaixo um exemplo de configuração "
-"<literal>jboss.xml</literal>."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:714
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-" <jboss>\n"
-" <session>\n"
-" <ejb-name>nextgen_RetryInterceptorStatelessSession</ejb-name>\n"
-" <invoker-bindings>\n"
-" <invoker>\n"
-" <invoker-proxy-binding-name>\n"
-" clustered-retry-stateless-rmi-invoker\n"
-" </invoker-proxy-binding-name>\n"
-" <jndi-name>\n"
-" nextgen_RetryInterceptorStatelessSession\n"
-" </jndi-name>\n"
-" </invoker>\n"
-" </invoker-bindings>\n"
-" <clustered>true</clustered>\n"
-" </session>\n"
-" \n"
-" <invoker-proxy-binding>\n"
-" <name>clustered-retry-stateless-rmi-invoker</name>\n"
-" <invoker-mbean>jboss:service=invoker,type=jrmpha</invoker-mbean>\n"
-" <proxy-factory>org.jboss.proxy.ejb.ProxyFactoryHA</proxy-factory>\n"
-" <proxy-factory-config>\n"
-" <client-interceptors>\n"
-" <home>\n"
-" <interceptor>\n"
-" org.jboss.proxy.ejb.HomeInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.SecurityInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.TransactionInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.ejb.RetryInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.invocation.InvokerInterceptor\n"
-" </interceptor>\n"
-" </home>\n"
-" <bean>\n"
-" <interceptor>\n"
-" org.jboss.proxy.ejb.StatelessSessionInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.SecurityInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.TransactionInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.ejb.RetryInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.invocation.InvokerInterceptor\n"
-" </interceptor>\n"
-" </bean>\n"
-" </client-interceptors>\n"
-" </proxy-factory-config>\n"
-" </invoker-proxy-binding> ]]>"
-msgstr ""
-"<![CDATA[ \n"
-" <jboss>\n"
-" <session>\n"
-" <ejb-name>nextgen_RetryInterceptorStatelessSession</ejb-name>\n"
-" <invoker-bindings>\n"
-" <invoker>\n"
-" <invoker-proxy-binding-name>\n"
-" clustered-retry-stateless-rmi-invoker\n"
-" </invoker-proxy-binding-name>\n"
-" <jndi-name>\n"
-" nextgen_RetryInterceptorStatelessSession\n"
-" </jndi-name>\n"
-" </invoker>\n"
-" </invoker-bindings>\n"
-" <clustered>true</clustered>\n"
-" </session>\n"
-" \n"
-" <invoker-proxy-binding>\n"
-" <name>clustered-retry-stateless-rmi-invoker</name>\n"
-" <invoker-mbean>jboss:service=invoker,type=jrmpha</invoker-mbean>\n"
-" <proxy-factory>org.jboss.proxy.ejb.ProxyFactoryHA</proxy-factory>\n"
-" <proxy-factory-config>\n"
-" <client-interceptors>\n"
-" <home>\n"
-" <interceptor>\n"
-" org.jboss.proxy.ejb.HomeInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.SecurityInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.TransactionInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.ejb.RetryInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.invocation.InvokerInterceptor\n"
-" </interceptor>\n"
-" </home>\n"
-" <bean>\n"
-" <interceptor>\n"
-" org.jboss.proxy.ejb.StatelessSessionInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.SecurityInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.TransactionInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.ejb.RetryInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.invocation.InvokerInterceptor\n"
-" </interceptor>\n"
-" </bean>\n"
-" </client-interceptors>\n"
-" </proxy-factory-config>\n"
-" </invoker-proxy-binding> ]]>"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:718
-#, no-c-format
-msgid "JNDI Lookup Process"
-msgstr "Processo de Procura do JNDI"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:719
-#, no-c-format
-msgid ""
-"In order to recover the HA proxy, the RetryInterceptor does a lookup in "
-"JNDI. This means that internally it creates a new InitialContext and does a "
-"JNDI lookup. But, for that lookup to succeed, the InitialContext needs to be "
-"configured properly to find your naming server. The RetryInterceptor will go "
-"through the following steps in attempting to determine the proper naming "
-"environment properties:"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:723
-#, no-c-format
-msgid ""
-"It will check its own static retryEnv field. This field can be set by client "
-"code via a call to RetryInterceptor.setRetryEnv(Properties). This approach "
-"to configuration has two downsides: first, it reduces portability by "
-"introducing JBoss-specific calls to the client code; and second, since a "
-"static field is used only a single configuration per JVM is possible."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:728
-#, no-c-format
-msgid ""
-"If the retryEnv field is null, it will check for any environment properties "
-"bound to a ThreadLocal by the org.jboss.naming.NamingContextFactory class. "
-"To use this class as your naming context factory, in your jndi.properties "
-"set property java.naming.factory.initial=org.jboss.naming."
-"NamingContextFactory. The advantage of this approach is use of org.jboss."
-"naming.NamingContextFactory is simply a configuration option in your jndi."
-"properties file, and thus your java code is unaffected. The downside is the "
-"naming properties are stored in a ThreadLocal and thus are only visible to "
-"the thread that originally created an InitialContext."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:733
-#, no-c-format
-msgid ""
-"If neither of the above approaches yield a set of naming environment "
-"properties, a default InitialContext is used. If the attempt to contact a "
-"naming server is unsuccessful, by default the InitialContext will attempt to "
-"fall back on multicast discovery to find an HA-JNDI naming server. See the "
-"section on “ClusteredJNDI Services” for more on multicast discovery of HA-"
-"JNDI."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:742
-#, no-c-format
-msgid "SingleRetryInterceptor"
-msgstr "SingleRetryInterceptor"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:743
-#, no-c-format
-msgid ""
-"The RetryInterceptor is useful in many use cases, but a disadvantage it has "
-"is that it will continue attempting to re-lookup the HA proxy in JNDI until "
-"it succeeds. If for some reason it cannot succeed, this process could go on "
-"forever, and thus the EJB call that triggered the RetryInterceptor will "
-"never return. For many client applications, this possibility is "
-"unacceptable. As a result, JBoss doesn't make the RetryInterceptor part of "
-"its default client interceptor stacks for clustered EJBs."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:746
-#, no-c-format
-msgid ""
-"In the 4.0.4.RC1 release, a new flavor of retry interceptor was introduced, "
-"the org.jboss.proxy.ejb.SingleRetryInterceptor. This version works like the "
-"RetryInterceptor, but only makes a single attempt to re-lookup the HA proxy "
-"in JNDI. If this attempt fails, the EJB call will fail just as if no retry "
-"interceptor was used. Beginning with 4.0.4.CR2, the SingleRetryInterceptor "
-"is part of the default client interceptor stacks for clustered EJBs."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:749
-#, no-c-format
-msgid ""
-"The downside of the SingleRetryInterceptor is that if the retry attempt is "
-"made during a portion of a cluster restart where no servers are available, "
-"the retry will fail and no further attempts will be made."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:759
-#, no-c-format
-msgid "Stateless Session Bean in EJB 3.0"
-msgstr "Bean de Sessão sem Estado em EJB 3.0"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:760
-#, fuzzy, no-c-format
-msgid ""
-"To cluster a stateless session bean in EJB 3.0, all you need to do is to "
-"annotate the bean class withe the <literal>@Clustered</literal> annotation. "
-"You can pass in the load balance policy and cluster partition as parameters "
-"to the annotation. The default load balance policy is <literal>org.jboss.ha."
-"framework.interfaces.RandomRobin</literal> and the default cluster is "
-"<literal>DefaultPartition</literal>. Below is the definition of the "
-"<literal>@Cluster</literal> annotation."
-msgstr ""
-"Para realizar o cluster de um bean de sessão sem estado em EJB 3.0, tudo que "
-"você precisa fazer é anotar a classe do bean com as anotações "
-"<literal>@Cluster</literal>. Você poderá passar pela política de "
-"balanceamento de carga e partição do cluster como parâmetros para a "
-"anotação. A política de balanceamento de carga padrão é <literal>org.jboss."
-"ha.framework.interfaces.RandomRobin</literal>. Segue abaixo a definição da "
-"anotação <literal>@Cluster</literal>."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:766
-#, no-c-format
-msgid ""
-"public @interface Clustered {\n"
-" Class loadBalancePolicy() default LoadBalancePolicy.class;\n"
-" String partition() default \"${jboss.partition.name:DefaultPartition}"
-"\";\n"
-"}"
-msgstr ""
-"public @interface Clustered {\n"
-" Class loadBalancePolicy() default LoadBalancePolicy.class;\n"
-" String partition() default \"${jboss.partition.name:DefaultPartition}"
-"\";\n"
-"}"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:767
-#, no-c-format
-msgid ""
-"Here is an example of a clustered EJB 3.0 stateless session bean "
-"implementation."
-msgstr ""
-"Veja aqui um exemplo da implementação de um bean de sessão sem estado de um "
-"EJB 3.0 em cluster. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:768
-#, no-c-format
-msgid ""
-"@Stateless\n"
-"@Clustered\n"
-"public class MyBean implements MySessionInt {\n"
-" \n"
-" public void test() {\n"
-" // Do something cool\n"
-" }\n"
-"}"
-msgstr ""
-"@Stateless\n"
-"@Clustered\n"
-"public class MyBean implements MySessionInt {\n"
-" \n"
-" public void test() {\n"
-" // Faça algo bom\n"
-" }\n"
-"}"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:769
-#, no-c-format
-msgid ""
-"The <literal>@Clustered</literal> annotation can also be omitted and the "
-"clustering configuration applied in jboss.xml:"
-msgstr "A anotação do <literal>@Clustered</literal> pode também ser omitida e a configuração em cluster aplicada no jboss.xml:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:772
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"<jboss> \n"
-" <enterprise-beans>\n"
-" <session>\n"
-" <ejb-name>NonAnnotationStateful</ejb-name>\n"
-" <clustered>true</clustered>\n"
-" <cluster-config>\n"
-" <partition-name>FooPartition</partition-name>\n"
-" <load-balance-policy>\n"
-" org.jboss.ha.framework.interfaces.RandomRobin\n"
-" </load-balance-policy>\n"
-" </cluster-config>\n"
-" </session> \n"
-" </enterprise-beans>\n"
-"</jboss> ]]>"
-msgstr ""
-"<![CDATA[ \n"
-"<jboss> \n"
-" <enterprise-beans>\n"
-" <session>\n"
-" <ejb-name>NonAnnotationStateful</ejb-name>\n"
-" <clustered>true</clustered>\n"
-" <cluster-config>\n"
-" <partition-name>FooPartition</partition-name>\n"
-" <load-balance-policy>\n"
-" org.jboss.ha.framework.interfaces.RandomRobin\n"
-" </load-balance-policy>\n"
-" </cluster-config>\n"
-" </session> \n"
-" </enterprise-beans>\n"
-"</jboss> ]]>"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:777
-#, no-c-format
-msgid "Stateful Session Beans in EJB 3.0"
-msgstr "Bean de Sessão sem Estado em EJB 3.0 "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:778
-#, fuzzy, no-c-format
-msgid ""
-"To cluster stateful session beans in EJB 3.0, you need to tag the bean "
-"implementation class with the <literal>@Cluster</literal> annotation, just "
-"as we did with the EJB 3.0 stateless session bean earlier. The @org.jboss."
-"ejb3.annotation.cache.tree.CacheConfig annotation can also be applied to the "
-"bean to specify caching behavior. Below is the definition of the "
-"@CacheConfig annotation:"
-msgstr ""
-"Para fazer um cluster de um bean de sessão sem estado em EJB 3.0, você "
-"precisará marcar a classe de implementação do bean com a anotação "
-"<literal>@Cluster</literal>, exatamente como fizemos anteriormente com o "
-"bean de sessão sem estado EJB 3.0. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:783
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"public @interface CacheConfig\n"
-"{\n"
-"String name() default \"jboss.cache:service=EJB3SFSBClusteredCache\";\n"
-"int maxSize() default 10000;\n"
-"long idleTimeoutSeconds() default 300; \n"
-"boolean replicationIsPassivation() default true; \n"
-"long removalTimeoutSeconds() default 0;\n"
-"} ]]>"
-msgstr ""
-"<![CDATA[ \n"
-"public @interface CacheConfig\n"
-"{\n"
-"String name() default \"jboss.cache:service=EJB3SFSBClusteredCache\";\n"
-"int maxSize() default 10000;\n"
-"long idleTimeoutSeconds() default 300; \n"
-"boolean replicationIsPassivation() default true; \n"
-"long removalTimeoutSeconds() default 0;\n"
-"} ]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:786
-#, no-c-format
-msgid ""
-"<literal>name</literal> specifies the object name of the JBoss Cache Mbean "
-"that should be used for caching the bean (see below for more on this Mbean)."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:788
-#, no-c-format
-msgid ""
-"<literal>maxSize</literal> specifies the maximum number of beans that can "
-"cached before the cache should start passivating beans, using an LRU "
-"algorithm."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:790
-#, no-c-format
-msgid ""
-"<literal>idleTimeoutSeconds</literal> specifies the max period of time a "
-"bean can go unused before the cache should passivate it (irregardless of "
-"whether maxSize beans are cached.)"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:792
-#, no-c-format
-msgid ""
-"<literal>removalTimeoutSeconds</literal> specifies the max period of time a "
-"bean can go unused before the cache should remove it altogether."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:794
-#, no-c-format
-msgid ""
-"<literal>replicationIsPassivation</literal> specifies whether the cache "
-"should consider a replication as being equivalent to a passivation, and "
-"invoke any @PrePassivate and @PostActivate callbacks on the bean. By default "
-"true, since replication involves serializing the bean, and preparing for and "
-"recovering from serialization is a common reason for implementing the "
-"callback methods."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:799
-#, no-c-format
-msgid ""
-"Here is an example of a clustered EJB 3.0 stateful session bean "
-"implementation."
-msgstr ""
-"Veja aqui um exemplo da implementação de um bean de sessão com estado de um "
-"EJB 3.0 em cluster. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:806
-#, no-c-format
-msgid ""
-"@Stateful\n"
-"@Clustered\n"
-"@CacheConfig(maxSize=5000,removalTimeoutSeconds=18000)\n"
-"public class MyBean implements MySessionInt {\n"
-" \n"
-" private int state = 0;\n"
-"\n"
-" public void increment() {\n"
-" System.out.println(\"counter: \" + (state++));\n"
-" }\n"
-"}"
-msgstr ""
-"@Stateful\n"
-"@Clustered\n"
-"@CacheConfig(maxSize=5000,removalTimeoutSeconds=18000)\n"
-"public class MyBean implements MySessionInt {\n"
-" \n"
-" private int state = 0;\n"
-"\n"
-" public void increment() {\n"
-" System.out.println(\"counter: \" + (state++));\n"
-" }\n"
-"}"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:808
-#, no-c-format
-msgid ""
-"As with stateless beans, the @Clustered annotation can also be omitted and "
-"the clustering configuration applied in jboss.xml; see the example above."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:811
-#, no-c-format
-msgid ""
-"As with EJB 2.0 clustered SFSBs, JBoss provides a mechanism whereby a bean "
-"implementation can expose a method the container can invoke to check whether "
-"the bean's state is not dirty after a request and doesn't need to be "
-"replicated. With EJB3, the mechanism is a little more formal; instead of "
-"just exposing a method with a known signature, an EJB3 SFSB must implement "
-"the org.jboss.ejb3.cache.Optimized interface:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:814
-#, no-c-format
-msgid ""
-"public interface Optimized {\n"
-"boolean isModified();\n"
-"}"
-msgstr ""
-"public interface Optimized {\n"
-"boolean isModified();\n"
-"}"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:816
-#, no-c-format
-msgid ""
-"JBoss Cache provides the session state replication service for EJB 3.0 "
-"stateful session beans. The related MBean service is defined in the "
-"<literal>ejb3-clustered-sfsbcache-service.xml</literal> file in the "
-"<literal>deploy</literal> directory. The contents of the file are as follows."
-msgstr ""
-"O JBoss Cache oferece o serviço de replicação do estado de sessão para os "
-"beans de sessão com estado de EJB 3.0. O serviço MBean relacionado, está "
-"definido no arquivo <literal>ejb3-clustered-sfsbcache-service.xml</literal> "
-"no diretório <literal>deploy</literal>. Segue abaixo o conteúdo deste "
-"arquivo:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:819
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"<server>\n"
-" <mbean code=\"org.jboss..cache.TreeCache\"\n"
-" name=\"jboss.cache:service=EJB3SFSBClusteredCache\">\n"
-" \n"
-" <attribute name=\"ClusterName\">\n"
-" ${jboss.partition.name:DefaultPartition}-SFSBCache\n"
-" </attribute>\n"
-" <attribute name=\"IsolationLevel\">REPEATABLE_READ</"
-"attribute>\n"
-" <attribute name=\"CacheMode\">REPL_ASYNC</"
-"attribute> \n"
-" \n"
-" <!-- We want to activate/inactivate regions as beans "
-"are deployed --> \n"
-" <attribute name=\"UseRegionBasedMarshalling\">true</"
-"attribute> \n"
-" <!-- Must match the value of "
-"\"useRegionBasedMarshalling\" --> \n"
-" <attribute name=\"InactiveOnStartup\">true</"
-"attribute>\n"
-" \n"
-" <attribute name=\"ClusterConfig\">\n"
-" ... ...\n"
-" </attribute> \n"
-" \n"
-" <!-- The max amount of time (in milliseconds) we "
-"wait until the \n"
-" initial state (ie. the contents of the cache) are "
-"retrieved from \n"
-" existing members. --> \n"
-" <attribute name=\"InitialStateRetrievalTimeout"
-"\">17500</attribute>\n"
-" \n"
-" <!-- Number of milliseconds to wait until all "
-"responses for a\n"
-" synchronous call have been received.\n"
-" -->\n"
-" <attribute name=\"SyncReplTimeout\">17500</"
-"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"
-" <name>statefulClustered</name> \n"
-" <!-- So default region would never timeout --"
-">\n"
-" <region name=\"/_default_\">\n"
-" <attribute name=\"maxNodes\">0</attribute>\n"
-" <attribute name=\"timeToIdleSeconds\">0</"
-"attribute>\n"
-" </region>\n"
-" </config>\n"
-" </attribute> \n"
-" \n"
-" <!-- Store passivated sessions to the file system --> \n"
-" <attribute name=\"CacheLoaderConfiguration\"> \n"
-" <config> \n"
-" \n"
-" <passivation>true</passivation> \n"
-" <shared>false</shared> \n"
-" \n"
-" <cacheloader> \n"
-" <class>org.jboss.cache.loader.FileCacheLoader</class> \n"
-" <!-- Passivate to the server data dir --> \n"
-" <properties> \n"
-" location=${jboss.server.data.dir}${/}sfsb \n"
-" </properties> \n"
-" <async>false</async> \n"
-" <fetchPersistentState>true</fetchPersistentState> \n"
-" <ignoreModifications>false</ignoreModifications> \n"
-" </cacheloader> \n"
-" \n"
-" </config> \n"
-" </attribute>\n"
-" </mbean>\n"
-"</server>]]>"
-msgstr ""
-"<![CDATA[ \n"
-"<server>\n"
-" <mbean code=\"org.jboss..cache.TreeCache\"\n"
-" name=\"jboss.cache:service=EJB3SFSBClusteredCache\">\n"
-" \n"
-" <attribute name=\"ClusterName\">\n"
-" ${jboss.partition.name:DefaultPartition}-SFSBCache\n"
-" </attribute>\n"
-" <attribute name=\"IsolationLevel\">REPEATABLE_READ</"
-"attribute>\n"
-" <attribute name=\"CacheMode\">REPL_ASYNC</"
-"attribute> \n"
-" \n"
-" <!-- We want to activate/inactivate regions as beans "
-"are deployed --> \n"
-" <attribute name=\"UseRegionBasedMarshalling\">true</"
-"attribute> \n"
-" <!-- Must match the value of "
-"\"useRegionBasedMarshalling\" --> \n"
-" <attribute name=\"InactiveOnStartup\">true</"
-"attribute>\n"
-" \n"
-" <attribute name=\"ClusterConfig\">\n"
-" ... ...\n"
-" </attribute> \n"
-" \n"
-" <!-- The max amount of time (in milliseconds) we "
-"wait until the \n"
-" initial state (ie. the contents of the cache) are "
-"retrieved from \n"
-" existing members. --> \n"
-" <attribute name=\"InitialStateRetrievalTimeout"
-"\">17500</attribute>\n"
-" \n"
-" <!-- Number of milliseconds to wait until all "
-"responses for a\n"
-" synchronous call have been received.\n"
-" -->\n"
-" <attribute name=\"SyncReplTimeout\">17500</"
-"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"
-" <name>statefulClustered</name> \n"
-" <!-- So default region would never timeout --"
-">\n"
-" <region name=\"/_default_\">\n"
-" <attribute name=\"maxNodes\">0</attribute>\n"
-" <attribute name=\"timeToIdleSeconds\">0</"
-"attribute>\n"
-" </region>\n"
-" </config>\n"
-" </attribute> \n"
-" \n"
-" <!-- Store passivated sessions to the file system --> \n"
-" <attribute name=\"CacheLoaderConfiguration\"> \n"
-" <config> \n"
-" \n"
-" <passivation>true</passivation> \n"
-" <shared>false</shared> \n"
-" \n"
-" <cacheloader> \n"
-" <class>org.jboss.cache.loader.FileCacheLoader</class> \n"
-" <!-- Passivate to the server data dir --> \n"
-" <properties> \n"
-" location=${jboss.server.data.dir}${/}sfsb \n"
-" </properties> \n"
-" <async>false</async> \n"
-" <fetchPersistentState>true</fetchPersistentState> \n"
-" <ignoreModifications>false</ignoreModifications> \n"
-" </cacheloader> \n"
-" \n"
-" </config> \n"
-" </attribute>\n"
-" </mbean>\n"
-"</server>]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:846
-#, fuzzy, no-c-format
-msgid ""
-"The configuration attributes in this MBean are essentially the same as the "
-"attributes in the standard JBoss Cache <literal>TreeCache</literal> MBean "
-"discussed in <xref linkend=\"jbosscache.chapt\"/>. Again, we omitted the "
-"JGroups configurations in the <literal>ClusterConfig</literal> attribute "
-"(see more in <xref linkend=\"jbosscache-jgroups\"/>). Two noteworthy items:"
-msgstr ""
-"As funções da configuração em MBean <literal>PassivationTreeCache</literal> "
-"são literalmente iguais às funções no modelo MBean de JBoss Cache "
-"<literal>TreeCache</literal> discutidos em <xref linkend=\"jbosscache.chapt"
-"\"/>. Novamente, omitimos as configurações JGroups na função "
-"<literal>ClusterConfig</literal> (veja mais em <xref linkend=\"jbosscache-"
-"jgroups\"/>)."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:851
-#, no-c-format
-msgid ""
-"The cache is configured to support eviction. The EJB3 SFSB container uses "
-"the JBoss Cache eviction mechanism to manage SFSB passivation. When beans "
-"are deployed, the EJB container will programatically add eviction regions to "
-"the cache, one region per bean type."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:855
-#, no-c-format
-msgid ""
-"A JBoss Cache CacheLoader is also configured; again to support SFSB "
-"passivation. When beans are evicted from the cache, the cache loader "
-"passivates them to a persistent store; in this case to the filesystem in the "
-"$JBOSS_HOME/server/all/data/sfsb directory. JBoss Cache supports a variety "
-"of different CacheLoader implementations that know how to store data to "
-"different persistent store types; see the JBoss Cache documentation for "
-"details. However, if you change the CacheLoaderConfiguration, be sure that "
-"you do not use a shared store (e.g., a single schema in a shared database.) "
-"Each node in the cluster must have its own persistent store, otherwise as "
-"nodes independently passivate and activate clustered beans, they will "
-"corrupt each others data."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:865
-#, no-c-format
-msgid "Clustered Entity EJBs"
-msgstr "Entidade em Cluster EJBs"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:866
-#, fuzzy, no-c-format
-msgid ""
-"In a JBoss AS cluster, the entity bean instance caches need to be kept in "
-"sync across all nodes. If an entity bean provides remote services, the "
-"service methods need to be load balanced as well."
-msgstr ""
-"Em um cluster JBoss AS, as instâncias de entidade bean precisam ser "
-"replicadas em todos os nós. Se um bean de entidade oferece serviços remotos, "
-"o método do serviço precisa também ter a carga balanceada."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:868
-#, fuzzy, no-c-format
-msgid ""
-"To use a clustered entity bean, the application does not need to do anything "
-"special, except for looking up EJB 2.x remote bean references from the "
-"clustered HA-JNDI."
-msgstr ""
-"Para utilizar um bean de entidade em cluster, o aplicativo não precisa fazer "
-"nada de especial, exceto consultar as referências do bean de um HA-JNDI em "
-"cluster. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:870
-#, no-c-format
-msgid "Entity Bean in EJB 2.x"
-msgstr "Bean de Entidade em EJB 2.x"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:871
-#, fuzzy, no-c-format
-msgid ""
-"First of all, it is worth noting that clustering 2.x entity beans is a bad "
-"thing to do. Its exposes elements that generally are too fine grained for "
-"use as remote objects to clustered remote objects and introduces data "
-"synchronization problems that are non-trivial. Do NOT use EJB 2.x entity "
-"bean clustering unless you fit into the sepecial case situation of read-"
-"only, or one read-write node with read-only nodes synched with the cache "
-"invalidation services."
-msgstr ""
-"A princípio, vale notar que não é bom fazer um cluster de beans de entidade "
-"2.x. Ele expõe elementos que geralmente são granulados demasiadamente. Eles "
-"são usados como objetos remotos para objetos remotos em cluster e introduz "
-"problemas de sincronização de dados que não sejam triviais. Não use o "
-"cluster de bean de entidade EJB 2.x a não ser que se encaixe em um caso "
-"especial, somente para leitura, ou um nó de leitura e escrita com os nós "
-"somente para leitura sincronizados com os serviços de invalidação do cache. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:873
-#, no-c-format
-msgid ""
-"To cluster EJB 2.x entity beans, you need to add the <literal><"
-"clustered></literal> element to the application's <literal>jboss.xml</"
-"literal> descriptor file. Below is a typical <literal>jboss.xml</literal> "
-"file."
-msgstr ""
-"Para realizar um bean de entidade de cluster EJB 2.x, você precisará "
-"adicionar o elemento <literal><clustered></literal> para o arquivo de "
-"descrição do <literal>jboss.xml</literal> aplicativo. Segue abaixo um "
-"arquivo típico de <literal>jboss.xml</literal>."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:876
-#, no-c-format
-msgid ""
-"<jboss> \n"
-" <enterprise-beans> \n"
-" <entity> \n"
-" <ejb-name>nextgen.EnterpriseEntity</ejb-"
-"name> \n"
-" <jndi-name>nextgen.EnterpriseEntity</jndi-"
-"name> \n"
-" <clustered>True</clustered> \n"
-" <cluster-config> \n"
-" <partition-name>DefaultPartition</partition-"
-"name> \n"
-" <home-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces."
-"RoundRobin \n"
-" </home-load-balance-policy> \n"
-" <bean-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces."
-"FirstAvailable \n"
-" </bean-load-balance-policy> \n"
-" </cluster-config> \n"
-" </entity> \n"
-" </enterprise-beans> \n"
-"</jboss>"
-msgstr ""
-"<jboss> \n"
-" <enterprise-beans> \n"
-" <entity> \n"
-" <ejb-name>nextgen.EnterpriseEntity</ejb-"
-"name> \n"
-" <jndi-name>nextgen.EnterpriseEntity</jndi-"
-"name> \n"
-" <clustered>True</clustered> \n"
-" <cluster-config> \n"
-" <partition-name>DefaultPartition</partition-"
-"name> \n"
-" <home-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces."
-"RoundRobin \n"
-" </home-load-balance-policy> \n"
-" <bean-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces."
-"FirstAvailable \n"
-" </bean-load-balance-policy> \n"
-" </cluster-config> \n"
-" </entity> \n"
-" </enterprise-beans> \n"
-"</jboss>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:877
-#, no-c-format
-msgid ""
-"The EJB 2.x entity beans are clustered for load balanced remote invocations. "
-"All the bean instances are synchronized to have the same contents on all "
-"nodes."
-msgstr ""
-"Os beans de entidade EJB 2.x estão agrupados para as invocações remotas de "
-"cargas balanceadas. Todas as instâncias de bean estão sincronizadas para ter "
-"o mesmo conteúdo em todos os nós. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:879
-#, no-c-format
-msgid ""
-"However, clustered EJB 2.x Entity Beans do not have a distributed locking "
-"mechanism or a distributed cache. They can only be synchronized by using row-"
-"level locking at the database level (see <literal><row-lock></literal> "
-"in the CMP specification) or by setting the Transaction Isolation Level of "
-"your JDBC driver to be <literal>TRANSACTION_SERIALIZABLE</literal>. Because "
-"there is no supported distributed locking mechanism or distributed cache "
-"Entity Beans use Commit Option \"B\" by default (See <literal>standardjboss."
-"xml</literal> and the container configurations Clustered CMP 2.x EntityBean, "
-"Clustered CMP EntityBean, or Clustered BMP EntityBean). It is not "
-"recommended that you use Commit Option \"A\" unless your Entity Bean is read-"
-"only. (There are some design patterns that allow you to use Commit Option \"A"
-"\" with read-mostly beans. You can also take a look at the Seppuku pattern "
-"<ulink url=\"http://dima.dhs.org/misc/readOnlyUpdates.html\"></ulink>. JBoss "
-"may incorporate this pattern into later versions.)"
-msgstr ""
-"No entanto, os Beans de Entidade do EJB 2.x em cluster não possuem um "
-"mecanismo de bloqueio distribuído ou um cache distribuído. Eles só podem ser "
-"sincronizados se utilizar um bloqueio de nível de linha no nível do banco de "
-"dados (veja <literal><row-lock></literal> na especificação CMP) ou "
-"então, se configurar o Nível de Isolamento de Transação do seu driver JDBC "
-"para ser <literal>TRANSACTION_SERIALIZABLE</literal>. Como não existe "
-"mecanismo de bloqueio distribuído com suporte ou Beans de Entidade de cache "
-"distribuído, utilize a Opção Submeter \"B\" como padrão (Veja "
-"<literal>standardjboss.xml</literal> e as configurações do recipiente do "
-"Bean de Entidade em Cluster CMP 2.x, Bean de Entidade CMP em Cluster, ou o "
-"Bean de Entidade BMP em Cluster). Recomenda-se que não utilize a Opção "
-"Submeter \"A\" a não ser que o seu Bean de Entidade seja somente para "
-"leitura. (Existem alguns modelos de esboço que permitem que você utilize a "
-"Opção Submeter \"A\" com a maioria dos beans de leitura. Você também poderá "
-"procurar no modelo Seppuku <ulink url=\"http://dima.dhs.org/misc/"
-"readOnlyUpdates.html\"></ulink>. O JBoss pode incorporar este modelo nas "
-"versões posteriores.)"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:891
-#, no-c-format
-msgid ""
-"If you are using Bean Managed Persistence (BMP), you are going to have to "
-"implement synchronization on your own. The MVCSoft CMP 2.0 persistence "
-"engine (see <ulink url=\"http://www.jboss.org/jbossgroup/partners.jsp\"></"
-"ulink>) provides different kinds of optimistic locking strategies that can "
-"work in a JBoss cluster."
-msgstr ""
-"Se você estiver utilizando a função Persistência Gerenciada de Bean (BMP), "
-"você terá que implementar a sincronização sozinho. O motor de persistência "
-"MVCSoft CMP 2.0 (veja <ulink url=\"http://www.jboss.org/jbossgroup/partners."
-"jsp\"></ulink>) provê tipos distintos de bloqueio otimista que podem "
-"trabalhar em um cluster JBoss. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:897
-#, no-c-format
-msgid "Entity Bean in EJB 3.0"
-msgstr "Bean de Entidade em EJB 3.0"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:899
-#, no-c-format
-msgid ""
-"In EJB 3.0, the entity beans primarily serve as a persistence data model. "
-"They do not provide remote services. Hence, the entity bean clustering "
-"service in EJB 3.0 primarily deals with distributed caching and replication, "
-"instead of load balancing."
-msgstr ""
-"Em EJB 3.0, os beans de entidade servem como um modelo de dados de "
-"persistência. Eles não provêem serviços remotos. Por isso, o serviço de bean "
-"em cluster no EJB 3.0 lida primeiramente com o cache distribuído e "
-"replicação, ao invés do balanceamento de carga."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:905
-#, no-c-format
-msgid "Configure the distributed cache"
-msgstr "Configurar o cache distribuído."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:906
-#, fuzzy, no-c-format
-msgid ""
-"To avoid round trips to the database, you can use a cache for your entities. "
-"JBoss EJB 3.0 entity beans are implemented by Hibernate, which has support "
-"for a second-level cache. The Hibernate setup used for the JBoss EJB 3.0 "
-"implementation uses JBoss Cache as its underlying second-level cache "
-"implementation. The second-level cache provides the following "
-"functionalities."
-msgstr ""
-"Para não retornar ao banco de dados, você poderá usar um cache para suas "
-"entidades. O JBoss EJB 3.0 é implementado pelo Hibernate, que tem suporte "
-"para um cache de segundo nível. O programa de instalação do Hibernate, usado "
-"para a implementação JBoss EJB 3.0 utiliza o Cache JBoss como a "
-"implementação do seu cache subjacente. O cache provê as seguintes funções:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:909
-#, no-c-format
-msgid ""
-"If you persist a cache enabled entity bean instance to the database via the "
-"entity manager the entity will inserted into the cache."
-msgstr ""
-"Se você persistir com uma instância de bean de entidade habilitada de cache "
-"para um banco de dados, através do gerenciador de entidade, a entidade será "
-"inserida no cache. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:913
-#, no-c-format
-msgid ""
-"If you update an entity bean instance and save the changes to the database "
-"via the entity manager the entity will updated in the cache."
-msgstr ""
-"Se você atualizar uma instância de bean de entidade e salvar as mudanças no "
-"banco de dados, através do gerenciador de entidade, esta será atualizada "
-"dentro do cache. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:917
-#, no-c-format
-msgid ""
-"If you remove an entity bean instance from the database via the entity "
-"manager the entity will removed from the cache."
-msgstr ""
-"Caso remova uma instância de bean de entidade de um banco de dados através "
-"de um gerenciador de entidade, esta será removida do cache. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:921
-#, no-c-format
-msgid ""
-"If loading a cached entity from the database via the entity manager, and "
-"that entity does not exist in the database, it will be inserted into the "
-"cache."
-msgstr ""
-"Ao carregar uma entidade em cache a partir do banco de dados através do "
-"gerenciador de entidade e aparecer como inexistente, esta será inserida no "
-"cache. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:925
-#, fuzzy, no-c-format
-msgid ""
-"The JBoss Cache service for EJB 3.0 entity beans is configured in a "
-"<literal>TreeCache</literal> MBean in the <literal>deploy/ejb3-entity-cache-"
-"service.xml</literal> file. The name of the cache MBean service is "
-"<literal>jboss.cache:service=EJB3EntityTreeCache</literal>. Below are the "
-"contents of the <literal>ejb3-entity-cache-service.xml</literal> file in the "
-"standard JBoss distribution. Again, we omitted the JGroups configuration "
-"element <literal>ClusterConfig</literal>."
-msgstr ""
-"O serviço JBoss Cache para os beans de entidade de EJB 3.0, está configurado "
-"no MBean <literal>TreeCache</literal> (veja em <xref linkend=\"jbosscache-"
-"cache\"/>) no arquivo <literal>deploy/ejb3-entity-cache-service.xml</"
-"literal>. O nome do serviço MBean do cache é <literal>jboss.cache: "
-"service=EJB3EntityTreeCache</literal>. Segue abaixo o contexto do arquivo "
-"<literal>ejb3-entity-cache-service.xml</literal> no padrão de distribuição "
-"JBoss. Novamente, omitimos o elemento de configuração JGroups "
-"<literal>ClusterConfig</literal>."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:931
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-" <server>\n"
-" <mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=EJB3EntityTreeCache\">\n"
-" \n"
-" <depends>jboss:service=Naming</depends>\n"
-" <depends>jboss:service=TransactionManager</depends> \n"
-" \n"
-" <!-- Name of cluster. Needs to be the same on all nodes in the clusters, \n"
-" in order to find each other --> \n"
-" <attribute name=\"ClusterName\">\n"
-" ${jboss.partition.name:DefaultPartition}-EntityCache\n"
-" </attribute>\n"
-" \n"
-" <!-- Configure the TransactionManager -->\n"
-" <attribute name=\"TransactionManagerLookupClass\">\n"
-" org.jboss.cache.JBossTransactionManagerLookup\n"
-" </attribute>\n"
-" \n"
-" <attribute name=\"IsolationLevel\">REPEATABLE_READ</attribute>\n"
-" <attribute name=\"CacheMode\">REPL_SYNC</attribute> \n"
-" \n"
-" <!-- Must be true if any entity deployment uses a scoped "
-"classloader --> \n"
-" <attribute name=\"UseRegionBasedMarshalling\">true</attribute> \n"
-" <!-- Must match the value of \"useRegionBasedMarshalling\" --> \n"
-" <attribute name=\"InactiveOnStartup\">true</attribute>\n"
-" \n"
-" <attribute name=\"ClusterConfig\">\n"
-" ... ...\n"
-" </attribute>\n"
-" \n"
-" <attribute name=\"InitialStateRetrievalTimeout\">17500</attribute>\n"
-" <attribute name=\"SyncReplTimeout\">17500</attribute>\n"
-" <attribute name=\"LockAcquisitionTimeout\">15000</attribute>\n"
-" \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"
-" </config>\n"
-" </attribute>\n"
-" </mbean>\n"
-"</server>\n"
-"]]>"
-msgstr ""
-"<![CDATA[ \n"
-" <server>\n"
-" <mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=EJB3EntityTreeCache\">\n"
-" \n"
-" <depends>jboss:service=Naming</depends>\n"
-" <depends>jboss:service=TransactionManager</depends> \n"
-" \n"
-" <!-- Name of cluster. Needs to be the same on all nodes in the clusters, \n"
-" in order to find each other --> \n"
-" <attribute name=\"ClusterName\">\n"
-" ${jboss.partition.name:DefaultPartition}-EntityCache\n"
-" </attribute>\n"
-" \n"
-" <!-- Configure the TransactionManager -->\n"
-" <attribute name=\"TransactionManagerLookupClass\">\n"
-" org.jboss.cache.JBossTransactionManagerLookup\n"
-" </attribute>\n"
-" \n"
-" <attribute name=\"IsolationLevel\">REPEATABLE_READ</attribute>\n"
-" <attribute name=\"CacheMode\">REPL_SYNC</attribute> \n"
-" \n"
-" <!-- Must be true if any entity deployment uses a scoped "
-"classloader --> \n"
-" <attribute name=\"UseRegionBasedMarshalling\">true</attribute> \n"
-" <!-- Must match the value of \"useRegionBasedMarshalling\" --> \n"
-" <attribute name=\"InactiveOnStartup\">true</attribute>\n"
-" \n"
-" <attribute name=\"ClusterConfig\">\n"
-" ... ...\n"
-" </attribute>\n"
-" \n"
-" <attribute name=\"InitialStateRetrievalTimeout\">17500</attribute>\n"
-" <attribute name=\"SyncReplTimeout\">17500</attribute>\n"
-" <attribute name=\"LockAcquisitionTimeout\">15000</attribute>\n"
-" \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"
-" </config>\n"
-" </attribute>\n"
-" </mbean>\n"
-"</server>\n"
-"]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:933
-#, fuzzy, no-c-format
-msgid ""
-"This is a replicated cache, so, if running within a cluster, and the cache "
-"is updated, changes to the entries in one node will be replicated to the "
-"corresponding entries in the other nodes in the cluster."
-msgstr ""
-"Como já discutimos anteriormente em <xref linkend=\"jbosscache-cache\"/>, o "
-"JBoss Cache permite que você especifique o tempo de espera para as entidades "
-"em cache. As entidades que não forem acessadas dentro de um período de "
-"tempo, serão retiradas do cache para economizar memória. Caso o cache seja "
-"atualizado enquanto estiver rodando em um cluster, as mudanças nas entradas "
-"em um nó serão replicadas para as entradas correspondentes nos outros nós em "
-"cluster. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:936
-#, no-c-format
-msgid ""
-"JBoss Cache allows you to specify timeouts to cached entities. Entities not "
-"accessed within a certain amount of time are dropped from the cache in order "
-"to save memory. The above configuration sets up a default configuration "
-"region that says that at most the cache will hold 5000 nodes, after which "
-"nodes will start being evicted from memory, least-recently used nodes last. "
-"Also, if any node has not been accessed within the last 1000 seconds, it "
-"will be evicted from memory. In general, a node in the cache represents a "
-"cached item (entity, collection, or query result set), although there are "
-"also a few other node that are used for internal purposes. If the above "
-"values of 5000 maxNodes and 1000 idle seconds are invalid for your "
-"application(s), you can change the cache-wide defaults. You can also add "
-"separate eviction regions for each of your entities; more on this below."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:940
-#, no-c-format
-msgid ""
-"Now, we have JBoss Cache configured to support distributed caching of EJB "
-"3.0 entity beans. We still have to configure individual entity beans to use "
-"the cache service."
-msgstr ""
-"Agora, temos um JBoss Cache configurado para suportar o cache distribuído ds "
-"beans de entidade EJB 3.0. Ainda temos que configurar os beans de entidade "
-"individual para usar um serviço cache. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:943
-#, no-c-format
-msgid "Configure the entity beans for cache"
-msgstr "Configurar os beans de entidade para cache."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:944
-#, no-c-format
-msgid ""
-"You define your entity bean classes the normal way. Future versions of JBoss "
-"EJB 3.0 will support annotating entities and their relationship collections "
-"as cached, but for now you have to configure the underlying hibernate engine "
-"directly. Take a look at the <literal>persistence.xml</literal> file, which "
-"configures the caching options for hibernate via its optional "
-"<literal>property</literal> elements. The following element in "
-"<literal>persistence.xml</literal> defines that caching should be enabled:"
-msgstr ""
-"Você é quem define suas classes de bean de entidade normalmente. As próximas "
-"versões do JBoss EJB 3.0 darão suporte às entidades de anotação e suas "
-"coleções de relacionamentos como realizado em cache, mas no momento, você "
-"terá que configurar o motor hibernate subjacente diretamente.Verifique no "
-"arquivo <literal>persistence.xml</literal>, que configura as opções de cache "
-"para hibernate através de seus elementos opcionais <literal>property</"
-"literal>. Os seguintes elementos em <literal>persistence.xml</literal>, "
-"definem que o cache deve estar habilitado:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:950
-#, no-c-format
-msgid ""
-"<!-- Clustered cache with TreeCache -->\n"
-"<property name=\"cache.provider_class\">\n"
-" org.jboss.ejb3.entity.TreeCacheProviderHook\n"
-"</property>"
-msgstr ""
-"<!-- Cache em Cluster com o Cache em Árvore -->\n"
-"<property name=\"cache.provider_class\">\n"
-" org.jboss.ejb3.entity.TreeCacheProviderHook\n"
-"</property>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:951
-#, fuzzy, no-c-format
-msgid ""
-"The following property element defines the object name of the cache to be "
-"used, i.e., the name of the TreeCache MBean shown above."
-msgstr ""
-"Os seguintes elementos de propriedade definem o nome do objeto do cache a "
-"ser utilizado, e o nome do MBean."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:952
-#, no-c-format
-msgid ""
-"<property name=\"treecache.mbean.object_name\">\n"
-" jboss.cache:service=EJB3EntityTreeCache\n"
-"</property>"
-msgstr ""
-"<property name=\"treecache.mbean.object_name\">\n"
-" jboss.cache:service=EJB3EntityTreeCache\n"
-"</property>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:953
-#, no-c-format
-msgid ""
-"Finally, you should give a “region_prefix” to this configuration. This "
-"ensures that all cached items associated with this persistence.xml are "
-"properly grouped together in JBoss Cache. The jboss.cache:"
-"service=EJB3EntityTreeCache cache is a shared resource, potentially used by "
-"multiple persistence units. The items cached in that shared cache need to be "
-"properly grouped to allow the cache to properly manage classloading. <"
-"property name=\"hibernate.cache.region_prefix\" value=\"myprefix\"/>"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:957
-#, no-c-format
-msgid ""
-"If you do not provide a region prefix, JBoss will automatically provide one "
-"for you, building it up from the name of the EAR (if any) and the name of "
-"the JAR that includes the persistence.xml. For example, a persistence.xml "
-"packaged in foo.ear, bar.jar would be given “foo_ear,bar_jar” as its region "
-"prefix. This is not a particularly friendly region prefix if you need to use "
-"it to set up specialized eviction regions (see below), so specifying your "
-"own region prefix is recommended."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:965
-#, fuzzy, no-c-format
-msgid ""
-"Next we need to configure what entities be cached. The default is to not "
-"cache anything, even with the settings shown above. We use the <literal>@org."
-"hibernate.annotations.Cache</literal> annotation to tag entity beans that "
-"needs to be cached."
-msgstr ""
-"A seguir, precisaremos configurar qual entidade ficará em cache. A mensagem "
-"padrão diz para não realizar o cache de nada, até mesmo com as configurações "
-"abaixo. Nós utilizamos a anotação <literal>@Cache</literal> para marcar os "
-"beans de entidade que precisam estar em cache. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:966
-#, no-c-format
-msgid ""
-"@Entity \n"
-"@Cache(usage=CacheConcurrencyStrategy.TRANSACTIONAL) \n"
-"public class Account implements Serializable { \n"
-" // ... ... \n"
-"}"
-msgstr ""
-"@Entity \n"
-"@Cache(usage=CacheConcurrencyStrategy.TRANSACTIONAL) \n"
-"public class Account implements Serializable { \n"
-" // ... ... \n"
-"}"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:967
-#, fuzzy, no-c-format
-msgid ""
-"A very simplified rule of thumb is that you will typically want to do "
-"caching for objects that rarely change, and which are frequently read. You "
-"can fine tune the cache for each entity bean in the <literal>ejb3-entity-"
-"cache-service.xml</literal> configuration file. For instance, you can "
-"specify the size of the cache. If there are too many objects in the cache, "
-"the cache could evict oldest objects (or least used objects, depending on "
-"configuration) to make room for new objects. Assuming the region_prefix "
-"specified in <literal>persistence.xml</literal> was myprefix, the default "
-"name of the cache region for the <literal>com.mycompany.entities.Account</"
-"literal> entity bean <literal>/myprefix/com/mycompany/entities/Account</"
-"literal>."
-msgstr ""
-"Como via de regra bastante simplificada, você irá certamente efetuar o cache "
-"para objetos que raramente mudam e que são freqüentemente lidos. Você pode "
-"ajustar o cache para cada bean de entidade no arquivo de configuração "
-"<literal>ejb3-entity-cache-service.xml</literal>. Por exemplo, você pode "
-"especificar o tamanho do cache. Se existirem muitos objetos em cache, ele "
-"pode despejar os objetos mais antigos. ( ou os objetos menos utilizados, "
-"dependendo da configuração) para abrir espaço para novos objetos. O cache "
-"para o bean de entidade <literal>mycompany.Customer</literal> é a área do "
-"cache <literal>/mycompany/Customer</literal>. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:969
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<server> \n"
-" <mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=EJB3EntityTreeCache\"> \n"
-" ... ... \n"
-" <attribute name=\"EvictionPolicyConfig\"> \n"
-" <config> \n"
-" <attribute name=\"wakeUpIntervalSeconds\">5</"
-"attribute> \n"
-" <region name=\"/_default_\"> \n"
-" <attribute name=\"maxNodes\">5000</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">1000</attribute> \n"
-" </region> \n"
-" <!-- Separate eviction rules for Account entities -->\n"
-" <region name=\"/myprefix/com/mycompany/entities/"
-"Account\"> \n"
-" <attribute name=\"maxNodes\">10000</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">5000</attribute> \n"
-" </region> \n"
-" ... ... \n"
-" </config> \n"
-" </attribute> \n"
-" </mbean> \n"
-"</server>]]>"
-msgstr ""
-"<![CDATA[\n"
-"<server> \n"
-" <mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=EJB3EntityTreeCache\"> \n"
-" ... ... \n"
-" <attribute name=\"EvictionPolicyConfig\"> \n"
-" <config> \n"
-" <attribute name=\"wakeUpIntervalSeconds\">5</"
-"attribute> \n"
-" <region name=\"/_default_\"> \n"
-" <attribute name=\"maxNodes\">5000</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">1000</attribute> \n"
-" </region> \n"
-" <!-- Separate eviction rules for Account entities -->\n"
-" <region name=\"/myprefix/com/mycompany/entities/"
-"Account\"> \n"
-" <attribute name=\"maxNodes\">10000</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">5000</attribute> \n"
-" </region> \n"
-" ... ... \n"
-" </config> \n"
-" </attribute> \n"
-" </mbean> \n"
-"</server>]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:972
-#, fuzzy, no-c-format
-msgid ""
-"If you do not specify a cache region for an entity bean class, all instances "
-"of this class will be cached in the <literal>/_default</literal> region as "
-"defined above. The @Cache annotation exposes an optional attribute “region” "
-"that lets you specify the cache region where an entity is to be stored, "
-"rather than having it be automatically be created from the fully-qualified "
-"class name of the entity class."
-msgstr ""
-"Se você não especificar a área do cache para uma classe de bean de entidade, "
-"todas as instâncias da classe ficarão em cache na região <literal>/_default</"
-"literal> como definido acima. O EJB3 <literal>Query</literal> API, oferece "
-"meios de salvar nos resultados de consulta de carga (ou seja, coleções de "
-"beans de entidade) a partir da regiões de cache especificadas. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:975
-#, no-c-format
-msgid ""
-"@Entity \n"
-"@Cache(usage=CacheConcurrencyStrategy.TRANSACTIONAL,\n"
-"region=”Account”) \n"
-"public class Account implements Serializable { \n"
-"// ... ... \n"
-"}"
-msgstr ""
-"@Entity \n"
-"@Cache(usage=CacheConcurrencyStrategy.TRANSACTIONAL,\n"
-"region=”Account”) \n"
-"public class Account implements Serializable { \n"
-"// ... ... \n"
-"}"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:976
-#, no-c-format
-msgid "The eviction configuration would then become:"
-msgstr "A configuração de remoção se tornaria então:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:977
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"<server> \n"
-" <mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=EJB3EntityTreeCache\"> \n"
-" ... ... \n"
-" <attribute name=\"EvictionPolicyConfig\"> \n"
-" <config> \n"
-" <attribute name=\"wakeUpIntervalSeconds\">5</attribute> \n"
-" <region name=\"/_default_\"> \n"
-" <attribute name=\"maxNodes\">5000</attribute> \n"
-" <attribute name=\"timeToLiveSeconds\">1000</attribute> \n"
-" </region> \n"
-" <!-- Separate eviction rules for Account entities -->\n"
-" <region name=\"/myprefix/Account\"> \n"
-" <attribute name=\"maxNodes\">10000</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds\">5000</"
-"attribute> \n"
-" </region> \n"
-" ... ... \n"
-" </config> \n"
-" </attribute> \n"
-" </mbean> \n"
-"</server>]]>"
-msgstr ""
-"<![CDATA[ \n"
-"<server> \n"
-" <mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=EJB3EntityTreeCache\"> \n"
-" ... ... \n"
-" <attribute name=\"EvictionPolicyConfig\"> \n"
-" <config> \n"
-" <attribute name=\"wakeUpIntervalSeconds\">5</attribute> \n"
-" <region name=\"/_default_\"> \n"
-" <attribute name=\"maxNodes\">5000</attribute> \n"
-" <attribute name=\"timeToLiveSeconds\">1000</attribute> \n"
-" </region> \n"
-" <!-- Separate eviction rules for Account entities -->\n"
-" <region name=\"/myprefix/Account\"> \n"
-" <attribute name=\"maxNodes\">10000</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds\">5000</"
-"attribute> \n"
-" </region> \n"
-" ... ... \n"
-" </config> \n"
-" </attribute> \n"
-" </mbean> \n"
-"</server>]]>"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:982
-#, no-c-format
-msgid "Query result caching"
-msgstr "Cache de resultado de pesquisa"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:983
-#, no-c-format
-msgid ""
-"The EJB3 Query API also provides means for you to save in the second-level "
-"cache the results (i.e., collections of primary keys of entity beans, or "
-"collections of scalar values) of specified queries. Here we show a simple "
-"example of annotating a bean with a named query, also providing the "
-"Hibernate-specific hints that tells Hibernate to cache the query."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:986
-#, no-c-format
-msgid "First, in persistence.xml you need to tell Hibernate to enable query caching:"
-msgstr "Primeiro, no persistence.xml você precisa informar ao Hibernate para ativar o cache de consulta:"
-
-#. Tag: screen
-#: Clustering_Guide_Introduction.xml:989
-#, no-c-format
-msgid "<property name=\"hibernate.cache.use_query_cache\" value=\"true\"/>"
-msgstr "<property name=\"hibernate.cache.use_query_cache\" value=\"true\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:990
-#, no-c-format
-msgid ""
-"Next, you create a named query associated with an entity, and tell Hibernate "
-"you want to cache the results of that query:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:993
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"@Entity\n"
-"@Cache (usage=CacheConcurrencyStrategy.TRANSACTIONAL,\n"
-"region=”Account”)\n"
-"@NamedQueries({\n"
-"@NamedQuery(name=\"account.bybranch\",\n"
-"query=\"select acct from Account as acct where acct.branch = ?1\",\n"
-"hints={@QueryHint(name=\"org.hibernate.cacheable\",value=\"true"
-"\")}) \n"
-"})\n"
-"public class Account implements Serializable { \n"
-"// ... ... \n"
-"}]]>"
-msgstr ""
-"<![CDATA[ \n"
-"@Entity\n"
-"@Cache (usage=CacheConcurrencyStrategy.TRANSACTIONAL,\n"
-"region=”Account”)\n"
-"@NamedQueries({\n"
-"@NamedQuery(name=\"account.bybranch\",\n"
-"query=\"select acct from Account as acct where acct.branch = ?1\",\n"
-"hints={@QueryHint(name=\"org.hibernate.cacheable\",value=\"true"
-"\")}) \n"
-"})\n"
-"public class Account implements Serializable { \n"
-"// ... ... \n"
-"}]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:995
-#, no-c-format
-msgid ""
-"The @NamedQueries, @NamedQuery and @QueryHint annotations are all in the "
-"javax.persistence package.See the Hibernate and EJB3 documentation for more "
-"on how to use EJB3 queries and on how to instruct EJB3 to cache queries."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:998
-#, no-c-format
-msgid ""
-"By default, Hibernate stores query results in JBoss Cache in a region named "
-"{region_prefix}/org/hibernate/cache/StandardQueryCache. Based on this, you "
-"can set up separate eviction handling for your query results. So, if the "
-"region prefix were set to myprefix in persistence.xml, you could, for "
-"example, create this sort of eviction handling:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1002
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"<server> \n"
-" <mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=EJB3EntityTreeCache\">\n"
-" ... ... \n"
-" <attribute name=\"EvictionPolicyConfig\"> \n"
-" <config> \n"
-" <attribute name=\"wakeUpIntervalSeconds\">5</"
-"attribute> \n"
-" <region name=\"/_default_\"> \n"
-" <attribute name=\"maxNodes\">5000</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">1000</attribute> \n"
-" </region> \n"
-" <!-- Separate eviction rules for Account "
-"entities -->\n"
-" <region name=\"/myprefix/Account\"> \n"
-" <attribute name=\"maxNodes"
-"\">10000</attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">5000</attribute> \n"
-" </region>\n"
-" <!-- Cache queries for 10 minutes -->\n"
-" <region name=\"/myprefix/org/hibernate/"
-"cache/StandardQueryCache\"> \n"
-" <attribute name=\"maxNodes\">100</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">600</attribute> \n"
-" </region> \n"
-" ... ... \n"
-" </config> \n"
-" </attribute> \n"
-" </mbean> \n"
-"</server>\n"
-" ]]>"
-msgstr ""
-"<![CDATA[ \n"
-"<server> \n"
-" <mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=EJB3EntityTreeCache\">\n"
-" ... ... \n"
-" <attribute name=\"EvictionPolicyConfig\"> \n"
-" <config> \n"
-" <attribute name=\"wakeUpIntervalSeconds\">5</"
-"attribute> \n"
-" <region name=\"/_default_\"> \n"
-" <attribute name=\"maxNodes\">5000</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">1000</attribute> \n"
-" </region> \n"
-" <!-- Separate eviction rules for Account "
-"entities -->\n"
-" <region name=\"/myprefix/Account\"> \n"
-" <attribute name=\"maxNodes"
-"\">10000</attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">5000</attribute> \n"
-" </region>\n"
-" <!-- Cache queries for 10 minutes -->\n"
-" <region name=\"/myprefix/org/hibernate/"
-"cache/StandardQueryCache\"> \n"
-" <attribute name=\"maxNodes\">100</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">600</attribute> \n"
-" </region> \n"
-" ... ... \n"
-" </config> \n"
-" </attribute> \n"
-" </mbean> \n"
-"</server>\n"
-" ]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1004
-#, no-c-format
-msgid ""
-"The @NamedQuery.hints attribute shown above takes an array of vendor-"
-"specific @QueryHints as a value. Hibernate accepts the “org.hibernate."
-"cacheRegion” query hint, where the value is the name of a cache region to "
-"use instead ofthe default /org/hibernate/cache/StandardQueryCache. For "
-"example:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1007
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-" @Entity\n"
-" @Cache (usage=CacheConcurrencyStrategy.TRANSACTIONAL,\n"
-" region=”Account”)\n"
-" @NamedQueries({\n"
-" @NamedQuery(name=\"account.bybranch\",\n"
-" query=\"select acct from Account as acct where acct.branch = ?1\",\n"
-" hints={@QueryHint(name=\"org.hibernate.cacheable\",value=\"true\"),\n"
-" @QueryHint(name=”org.hibernate.cacheRegion,value=”Queries”)\n"
-" }) \n"
-" })\n"
-" public class Account implements Serializable { \n"
-" // ... ... \n"
-" }]]>"
-msgstr ""
-"<![CDATA[\n"
-" @Entity\n"
-" @Cache (usage=CacheConcurrencyStrategy.TRANSACTIONAL,\n"
-" region=”Account”)\n"
-" @NamedQueries({\n"
-" @NamedQuery(name=\"account.bybranch\",\n"
-" query=\"select acct from Account as acct where acct.branch = ?1\",\n"
-" hints={@QueryHint(name=\"org.hibernate.cacheable\",value=\"true\"),\n"
-" @QueryHint(name=”org.hibernate.cacheRegion,value=”Queries”)\n"
-" }) \n"
-" })\n"
-" public class Account implements Serializable { \n"
-" // ... ... \n"
-" }]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1008
-#, no-c-format
-msgid "The related eviction configuration:"
-msgstr "A configuração da remoção relacionada:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1011
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"<server> \n"
-" <mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=EJB3EntityTreeCache\">\n"
-" ... ... \n"
-" <attribute name=\"EvictionPolicyConfig\"> \n"
-" <config> \n"
-" <attribute name=\"wakeUpIntervalSeconds\">5</"
-"attribute> \n"
-" <region name=\"/_default_\"> \n"
-" <attribute name=\"maxNodes\">5000</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">1000</attribute> \n"
-" </region> \n"
-" <!-- Separate eviction rules for Account "
-"entities -->\n"
-" <region name=\"/myprefix/Account\"> \n"
-" <attribute name=\"maxNodes\">10000</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">5000</attribute> \n"
-" </region>\n"
-" <!-- Cache queries for 10 minutes -->\n"
-" <region name=\"/myprefix/Queries\"> \n"
-" <attribute name=\"maxNodes\">100</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">600</attribute> \n"
-" </region> \n"
-" ... ... \n"
-" </config> \n"
-" </attribute> \n"
-" </mbean> \n"
-"</server>]]>"
-msgstr ""
-"<![CDATA[ \n"
-"<server> \n"
-" <mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=EJB3EntityTreeCache\">\n"
-" ... ... \n"
-" <attribute name=\"EvictionPolicyConfig\"> \n"
-" <config> \n"
-" <attribute name=\"wakeUpIntervalSeconds\">5</"
-"attribute> \n"
-" <region name=\"/_default_\"> \n"
-" <attribute name=\"maxNodes\">5000</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">1000</attribute> \n"
-" </region> \n"
-" <!-- Separate eviction rules for Account "
-"entities -->\n"
-" <region name=\"/myprefix/Account\"> \n"
-" <attribute name=\"maxNodes\">10000</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">5000</attribute> \n"
-" </region>\n"
-" <!-- Cache queries for 10 minutes -->\n"
-" <region name=\"/myprefix/Queries\"> \n"
-" <attribute name=\"maxNodes\">100</"
-"attribute> \n"
-" <attribute name=\"timeToLiveSeconds"
-"\">600</attribute> \n"
-" </region> \n"
-" ... ... \n"
-" </config> \n"
-" </attribute> \n"
-" </mbean> \n"
-"</server>]]>"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1044
-#, no-c-format
-msgid "HTTP Services"
-msgstr "Serviços HTTP"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1045
-#, no-c-format
-msgid ""
-"HTTP session replication is used to replicate the state associated with your "
-"web clients on other nodes of a cluster. Thus, in the event one of your node "
-"crashes, another node in the cluster will be able to recover. Two distinct "
-"functions must be performed:"
-msgstr ""
-"A replicação da sessão HTTP é usada para replicar o estado associado com "
-"seus clientes da web nos outros nós de um cluster. Assim, caso um dos seus "
-"nós trave, outro nó no cluster poderá recuperar. Deve-se realizar duas "
-"funções distintas."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1050
-#, no-c-format
-msgid "Session state replication"
-msgstr "Replicação de estado de Sessão"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1053
-#, no-c-format
-msgid "Load-balancing of incoming invocations"
-msgstr "Balanceamento de cargas de Invocações de entrada.recepção."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1056
-#, fuzzy, no-c-format
-msgid ""
-"State replication is directly handled by JBoss. When you run JBoss in the "
-"<literal>all</literal> configuration, session state replication is enabled "
-"by default. Just configure your web application as distributable in its "
-"<filename>web.xml</filename> (see below), deploy it, and its session state "
-"is automtically replicated across all JBoss instances in the cluster."
-msgstr ""
-"Uma replicação de estado é gerenciada diretamente pelo JBoss. Quando você "
-"rodar o JBoss na configuração <literal>all</literal>, a replicação de estado "
-"de sessão estará habilitada como padrão. Simplesmente implemente seu "
-"aplicativo da web e suas sessões de estado serão automaticamente replicadas "
-"em todas as instâncias JBoss no cluster. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1058
-#, fuzzy, no-c-format
-msgid ""
-"However, load-balancing is a different story; it is not handled by JBoss "
-"itself and requires an external load balancer. aThis function could be "
-"provided by specialized hardware switches or routers (Cisco LoadDirector for "
-"example) or by specialized software running on commodity hardware. As a very "
-"common scenario, we will demonstrate how to set up a software load balancer "
-"using Apache httpd and mod_jk."
-msgstr ""
-"No entanto, o balanceamento de carga é um caso diferente, não é gerenciado "
-"pelo próprio JBoss e requer um software adicional. Como acontece "
-"normalmente, demonstraremos como instalar o Apache e mod_jk. Esta atividade "
-"pode ser realizada tanto pelo alternador de hardware especializado ou pelos "
-"roteadores (como por exemplo, o Diretor de Carga da Cisco) ou qualquer outro "
-"software dedicado. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1063
-#, fuzzy, no-c-format
-msgid ""
-"A load-balancer tracks HTTP requests and, depending on the session to which "
-"the request is linked, it dispatches the request to the appropriate node. "
-"This is called load-balancing with sticky-sessions: once a session is "
-"created on a node, every future request will also be processed by that same "
-"node. Using a load-balancer that supports sticky-sessions but not "
-"configuring your web application for session replication allows you to scale "
-"very well by avoiding the cost of session state replication: each query will "
-"always be handled by the same node. But in case a node dies, the state of "
-"all client sessions hosted by this node (the shopping carts, for example) "
-"will be lost and the clients will most probably need to login on another "
-"node and restart with a new session. In many situations, it is acceptable "
-"not to replicate HTTP sessions because all critical state is stored in a "
-"database. In other situations, losing a client session is not acceptable "
-"and, in this case, session state replication is the price one has to pay."
-msgstr ""
-"Um balanceador de carga controla as solicitações HTTP e dependendo da sessão "
-"com a qual ele está ligado, ele despacha a solicitação para o nó mais "
-"apropriado. Isto se chama balanceador de carga com sessões de aderência: uma "
-"vez que a sessão é criada em um nó, todas as solicitações futuras também "
-"serão processados por um mesmo nó. O uso de um balanceador de carga que "
-"oferece suporte às sessões de aderência sem replicá-las, fará com que você "
-"escale muito bem sem o custo da replicação de estado de sessão: cada a "
-"solicitação será sempre gerenciada pelo mesmo nó. Mas no caso de um nó "
-"falhar, o estado de todas as sessões do cliente, hospedadas por este nó, "
-"será perdido (como por exemplo o carrinho de compras) e muito provavelmente, "
-"o cliente irá precisar entrar em outro nó e reiniciar com a nova sessão. Na "
-"maioria dos casos, é aceitável que não se replique as sessões HTTP, pois "
-"todos os estados críticos estão armazenados no banco de dados. Em outros "
-"casos, não é aceitável afastar uma sessão de cliente e neste caso, paga-se o "
-"preço de realizar a replicação do estado de sessão."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1065
-#, no-c-format
-msgid "Configuring load balancing using Apache and mod_jk"
-msgstr "Configurando o balanceamento de cargas usando o Apache e mod_jk"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1067
-#, fuzzy, no-c-format
-msgid ""
-"Apache is a well-known web server which can be extended by plugging in "
-"modules. One of these modules, mod_jk has been specifically designed to "
-"allow the forwarding of requests from Apache to a Servlet container. "
-"Furthermore, it is also able to load-balance HTTP calls to a set of Servlet "
-"containers while maintaining sticky sessions, which is what is most "
-"interesting for us in this section."
-msgstr ""
-"O Apache é um servidor bastante conhecido, o qual poderá ser estendido ao "
-"ligar os módulos. Um destes módulos, mod_jk (e o mais novo mod_jk2) foi "
-"desenhado especificamente para permitir o encaminhamento de solicitações do "
-"Apache para o recipiente Servlet. Além disso, também é possível balancear a "
-"carga das chamadas HTTP para um conjunto de recipientes Servlet enquanto "
-"mantiver as sessões de aderência, e isto na verdade é o que nos interessa. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1072
-#, no-c-format
-msgid "Download the software"
-msgstr "Download do software"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1073
-#, no-c-format
-msgid ""
-"First of all, make sure that you have Apache installed. You can download "
-"Apache directly from Apache web site at <literal>http://httpd.apache.org/</"
-"literal>. Its installation is pretty straightforward and requires no "
-"specific configuration. As several versions of Apache exist, we advise you "
-"to use version 2.0.x. We will consider, for the next sections, that you have "
-"installed Apache in the <literal>APACHE_HOME</literal> directory."
-msgstr ""
-"A princípio, assegure-se de que você tem um Apache instalado. Você poderá "
-"baixar o Apache diretamente do website do Apache em <literal>http://httpd."
-"apache.org/</literal>. Sua instalação é bastante simples e não requer "
-"configurações específicas. Como existem diversas versões do Apache, "
-"recomendamos que utilize a versão 2.0.x. Consideraremos, para as próximas "
-"seções, que Apache já esteja instalado no diretório <literal>APACHE_HOME</"
-"literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1078
-#, no-c-format
-msgid ""
-"Next, download mod_jk binaries. Several versions of mod_jk exist as well. We "
-"strongly advise you to use mod_jk 1.2.x, as both mod_jk and mod_jk2 are "
-"deprecated, unsupported and no further developments are going on in the "
-"community. The mod_jk 1.2.x binary can be downloaded from <literal>http://"
-"www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/</literal>. Rename "
-"the downloaded file to <literal>mod_jk.so</literal> and copy it under "
-"<literal>APACHE_HOME/modules/</literal>."
-msgstr ""
-"Depois disso, baixe o mod_jk binários. Existem também diversas versões do "
-"mod_jk. Recomendamos que você utilize o mod_jk 1.2.x, uma vez que tanto o "
-"mod_jk quanto o mod_jk2 estão condenados, não possuem suporte e nenhum "
-"desenvolvimento está sendo realizado na comunidade. O binário mod_jk 1.2.x "
-"pode ser baixado a partir do <literal>http://www.apache.org/dist/jakarta/"
-"tomcat-connectors/jk/binaries/</literal>. Renomeie o arquivo baixado para "
-"<literal>mod_jk.so</literal> e copie-o para <literal>APACHE_HOME/modules/</"
-"literal>."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1086
-#, no-c-format
-msgid "Configure Apache to load mod_jk"
-msgstr "Configurar o Apache para a carga mod_jk"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1087
-#, no-c-format
-msgid ""
-"Modify APACHE_HOME/conf/httpd.conf and add a single line at the end of the "
-"file:"
-msgstr ""
-"Modificar o APACHE_HOME/conf/http.conf e adicionar somente uma linha no "
-"final do arquivo. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1088
-#, no-c-format
-msgid ""
-"# Include mod_jk's specific configuration file \n"
-"Include conf/mod-jk.conf"
-msgstr ""
-"# Inclui o arquivo específico de configuração do mod_jk \n"
-"Inclui conf/mod-jk.conf"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1089
-#, no-c-format
-msgid ""
-"Next, create a new file named <literal>APACHE_HOME/conf/mod-jk.conf</"
-"literal>:"
-msgstr ""
-"A seguir, crie um novo arquivo chamado <literal>APACHE_HOME/conf/mod-jk."
-"conf</literal>:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1090
-#, no-c-format
-msgid ""
-"# Load mod_jk module\n"
-"# Specify the filename of the mod_jk lib\n"
-"LoadModule jk_module modules/mod_jk.so\n"
-" \n"
-"# Where to find workers.properties\n"
-"JkWorkersFile conf/workers.properties\n"
-"\n"
-"# Where to put jk logs\n"
-"JkLogFile logs/mod_jk.log\n"
-" \n"
-"# Set the jk log level [debug/error/info]\n"
-"JkLogLevel info \n"
-" \n"
-"# Select the log format\n"
-"JkLogStampFormat \"[%a %b %d %H:%M:%S %Y]\"\n"
-" \n"
-"# JkOptions indicates to send SSK KEY SIZE\n"
-"JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories\n"
-" \n"
-"# JkRequestLogFormat\n"
-"JkRequestLogFormat \"%w %V %T\"\n"
-" \n"
-"# Mount your applications\n"
-"JkMount /application/* loadbalancer\n"
-" \n"
-"# You can use external file for mount points.\n"
-"# It will be checked for updates each 60 seconds.\n"
-"# The format of the file is: /url=worker\n"
-"# /examples/*=loadbalancer\n"
-"JkMountFile conf/uriworkermap.properties \n"
-"\n"
-"# Add shared memory.\n"
-"# This directive is present with 1.2.10 and\n"
-"# later versions of mod_jk, and is needed for\n"
-"# for load balancing to work properly\n"
-"JkShmFile logs/jk.shm \n"
-" \n"
-"# Add jkstatus for managing runtime data\n"
-"<Location /jkstatus/>\n"
-" JkMount status\n"
-" Order deny,allow\n"
-" Deny from all\n"
-" Allow from 127.0.0.1\n"
-"</Location>"
-msgstr ""
-"# Carregue o módulo mod_jk\n"
-"# Especifique o nome de arquivo do lib\n"
-"LoadModule jk_module modules/mod_jk.so\n"
-" \n"
-"# Onde encontrar workers.properties\n"
-"JkWorkersFile conf/workers.properties\n"
-"\n"
-"# Onde colocar as entradas jk\n"
-"JkLogFile logs/mod_jk.log\n"
-" \n"
-"# Configurar o nível de entrada do jk [depuração/erro/info]\n"
-"Informação JkLogLevel \n"
-" \n"
-"# Selecione um formato de entrada\n"
-"JkLogStampFormat \"[%a %b %d %H:%M:%S %Y]\"\n"
-" \n"
-"# As opções Jk indicam que envie SSK KEY SIZE\n"
-"JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories\n"
-" \n"
-"# JkRequestLogFormat\n"
-"JkRequestLogFormat \"%w %V %T\"\n"
-" \n"
-"# Monte seu aplicativo\n"
-"MontagemJk /aplicativo/*balanceador de carga\n"
-" \n"
-"# Você poderá usar o arquivo externo para pontos de montagem.\n"
-"# Será atualizado a cada 60 segundos.\n"
-"# O formato do arquivo é: /url=worker\n"
-"# /examples/*=loadbalancer\n"
-"JkMountFile conf/uriworkermap.properties \n"
-"\n"
-"# Adicione uma memória compartilhada.\n"
-"# Esta diretriz está presente com 1.2.10 e\n"
-"# versões posteriores do mod_jk e são necessárias para\n"
-"# para balancear a carga a fim de funcionar propriamente\n"
-"JkShmFile logs/jk.shm \n"
-" \n"
-"# Adicionar o status jkpara gerenciar os dados do tempo de execução\n"
-"<Location /jkstatus/>\n"
-" Status do JkMount\n"
-" Pedir, negar, permitir\n"
-" Negar de todos\n"
-" Permitir a partir do 127.0.0.1\n"
-"</Location>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1091
-#, no-c-format
-msgid "Please note that two settings are very important:"
-msgstr "Observe que as duas configurações são muito importantes. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1094
-#, no-c-format
-msgid ""
-"The <literal>LoadModule</literal> directive must reference the mod_jk "
-"library you have downloaded in the previous section. You must indicate the "
-"exact same name with the \"modules\" file path prefix."
-msgstr ""
-"A diretriz <literal>LoadModule</literal> deve referenciar a biblioteca "
-"mod_jk que você tiver baixado na seção anterior. Você deverá indicar "
-"exatamente o mesmo nome com o prefixo do caminho do arquivo \"modules\". "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1099
-#, no-c-format
-msgid ""
-"The <literal>JkMount</literal> directive tells Apache which URLs it should "
-"forward to the mod_jk module (and, in turn, to the Servlet containers). In "
-"the above file, all requests with URL path <literal>/application/*</literal> "
-"are sent to the mod_jk load-balancer. This way, you can configure Apache to "
-"server static contents (or PHP contents) directly and only use the "
-"loadbalancer for Java applications. If you only use mod_jk as a "
-"loadbalancer, you can also forward all URLs (i.e., <literal>/*</literal>) to "
-"mod_jk."
-msgstr ""
-"A diretriz <literal>JkMount</literal> diz ao Apache quais URLs encaminhar "
-"para o módulo mod_jk (e ao recipiente Servlet). No arquivo acima, todas as "
-"solicitações que possuam caminho URL <literal>/application/*</literal> são "
-"enviadas para o balanceador de cargas mod_jk. Dessa forma, você poderá "
-"configurar o Apache ao conteúdo estático do servidor (ou conteúdo PHP) "
-"diretamente e somente utilizar o balanceador de carga para os aplicativos "
-"Java. Se você utilizar somente o mod_jk como um balanceador de cargas, você "
-"também poderá encaminhar todos os URLs (ou seja, <literal>/*</literal>) para "
-"mod_jk."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1107
-#, no-c-format
-msgid ""
-"In addition to the <literal>JkMount</literal> directive, you can also use "
-"the <literal>JkMountFile</literal> directive to specify a mount points "
-"configuration file, which contains multiple Tomcat forwarding URL mappings. "
-"You just need to create a <literal>uriworkermap.properties</literal> file in "
-"the <literal>APACHE_HOME/conf</literal> directory. The format of the file is "
-"<literal>/url=worker_name</literal>. To get things started, paste the "
-"following example into the file you created:"
-msgstr ""
-"Além da diretriz <literal>JkMount</literal>, você também poderá utilizar a "
-"diretriz <literal>JkMountFile</literal> para especificar o arquivo de "
-"configuração do ponto de montagem, que contém múltiplos mapeamentos URL de "
-"encaminhamento de Tomcat. Você só precisa criar um arquivo "
-"<literal>uriworkermap.properties</literal> no diretório "
-"<literal>APACHE_HOME/conf</literal>. O formato do arquivo é <literal>/"
-"url=worker_name</literal>. Para iniciar, copie o seguinte exemplo no arquivo "
-"que foi criado. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1113
-#, no-c-format
-msgid ""
-"# Simple worker configuration file\n"
-"\n"
-"# Mount the Servlet context to the ajp13 worker\n"
-"/jmx-console=loadbalancer\n"
-"/jmx-console/*=loadbalancer\n"
-"/web-console=loadbalancer\n"
-"/web-console/*=loadbalancer"
-msgstr ""
-"# Arquivo de configuração de trabalho \n"
-"\n"
-"# Montagem do contexto Servlet para o ajp13 worker\n"
-"/jmx-console=loadbalancer\n"
-"/jmx-console/*=loadbalancer\n"
-"/web-console=loadbalancer\n"
-"/web-console/*=loadbalancer"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1114
-#, no-c-format
-msgid ""
-"This will configure mod_jk to forward requests to <literal>/jmx-console</"
-"literal> and <literal>/web-console</literal> to Tomcat."
-msgstr ""
-"Este irá configurar o mod_jk para encaminhar solicitações para o <literal>/"
-"jmx-console</literal> e <literal>/web-console</literal> para o Tomcat. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1116
-#, no-c-format
-msgid ""
-"You will most probably not change the other settings in <literal>mod_jk."
-"conf</literal>. They are used to tell mod_jk where to put its logging file, "
-"which logging level to use and so on."
-msgstr ""
-"É bastante provável que você não precise mudar as outras configurações em "
-"<literal>mod_jk.conf</literal>. Geralmente o mod_jk já recebe informação de "
-"onde colocar seus arquivos de entrada, quais níveis de entrada utilizar etc. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1120
-#, no-c-format
-msgid "Configure worker nodes in mod_jk"
-msgstr "Configurar os nós de worker em mod_jk"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1121
-#, fuzzy, no-c-format
-msgid ""
-"Next, you need to configure mod_jk workers file <literal>conf/workers."
-"properties</literal>. This file specifies where the different Servlet "
-"containers are located and how calls should be load-balanced across them. "
-"The configuration file contains one section for each target servlet "
-"container and one global section. For a two nodes setup, the file could look "
-"like this:"
-msgstr ""
-"A seguir, você precisará configurar os arquivos do worker mod_jk "
-"<literal>conf/workers.properties</literal>. Este arquivo especifica onde "
-"estão localizados os diferentes recipientes de Servlet e como as chamadas "
-"devem ter suas cargas balanceadas nos tais recipientes. O arquivo de "
-"configuração contém uma seção para cada recipiente de servlet alvo e uma "
-"seção global. Para uma configuração de dois nós, o arquivo se pareceria com "
-"o seguinte:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1126
-#, no-c-format
-msgid ""
-"# Define list of workers that will be used\n"
-"# for mapping requests\n"
-"worker.list=loadbalancer,status\n"
-"\n"
-"# Define Node1\n"
-"# modify the host as your host IP or DNS name.\n"
-"worker.node1.port=8009\n"
-"worker.node1.host=node1.mydomain.com \n"
-"worker.node1.type=ajp13\n"
-"worker.node1.lbfactor=1\n"
-"worker.node1.cachesize=10\n"
-"\n"
-"# Define Node2\n"
-"# modify the host as your host IP or DNS name.\n"
-"worker.node2.port=8009\n"
-"worker.node2.host= node2.mydomain.com\n"
-"worker.node2.type=ajp13\n"
-"worker.node2.lbfactor=1\n"
-"worker.node2.cachesize=10\n"
-"\n"
-"# Load-balancing behaviour\n"
-"worker.loadbalancer.type=lb\n"
-"worker.loadbalancer.balance_workers=node1,node2\n"
-"worker.loadbalancer.sticky_session=1\n"
-"#worker.list=loadbalancer\n"
-"\n"
-"# Status worker for managing load balancer\n"
-"worker.status.type=status"
-msgstr ""
-"# Definir as listas dos workers que serão utilizados\n"
-"# para solicitações de mapeamento\n"
-"worker.list=loadbalancer,status\n"
-"\n"
-"# Definir Nó1\n"
-"# modificar o host como seu host IP ou nome do DNS.\n"
-"worker.node1.port=8009\n"
-"worker.node1.host=node1.mydomain.com \n"
-"worker.node1.type=ajp13\n"
-"worker.node1.lbfactor=1\n"
-"worker.node1.cachesize=10\n"
-"\n"
-"# Definir Nó2\n"
-"# modificar o host como seu host IP ou nome do DNS.\n"
-"worker.node2.port=8009\n"
-"worker.node2.host= node2.mydomain.com\n"
-"worker.node2.type=ajp13\n"
-"worker.node2.lbfactor=1\n"
-"worker.node2.cachesize=10\n"
-"\n"
-"# Comportamento de balanceamento de carga\n"
-"worker.loadbalancer.type=lb\n"
-"worker.loadbalancer.balance_workers=node1,node2\n"
-"worker.loadbalancer.sticky_session=1\n"
-"#worker.list=loadbalancer\n"
-"\n"
-"# Status do worker para gerenciar o balanceador de carga\n"
-"worker.status.type=status"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1127
-#, no-c-format
-msgid ""
-"Basically, the above file configures mod_jk to perform weighted round-robin "
-"load balancing with sticky sessions between two servlet containers (JBoss "
-"Tomcat) node1 and node2 listening on port 8009."
-msgstr ""
-"Basicamente, o arquivo acima configura o mod_jk para realizar um "
-"balanceamento de carga round-robin robusto com sessões aderentes entre dois "
-"recipientes (JBoss Tomcat) nó1 e nó2 ouvindo na porta 8009."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1130
-#, fuzzy, no-c-format
-msgid ""
-"In the <literal>works.properties</literal> file, each node is defined using "
-"the <literal>worker.XXX</literal> naming convention where <literal>XXX</"
-"literal> represents an arbitrary name you choose for each of the target "
-"Servlet containers. For each worker, you must specify the host name (or IP "
-"address) and the port number of the AJP13 connector running in the Servlet "
-"container."
-msgstr ""
-"No arquivo <literal>works.properties</literal>, cada nó é definido "
-"utilizando a convenção de nomes onde <literal>XXX</literal> representa um "
-"nome arbitrário que você escolhe para um recipiente Servlet alvo. Para cada "
-"worker, você deve fornecer o nome do host (ou endereço IP) e número da porta "
-"do conector AJP13 no recipiente Servlet."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1135
-#, fuzzy, no-c-format
-msgid ""
-"The <literal>lbfactor</literal> attribute is the load-balancing factor for "
-"this specific worker. It is used to define the priority (or weight) a node "
-"should have over other nodes. The higher this number is for a given worker "
-"relative to the other workers, the more HTTP requests the worker will "
-"receive. This setting can be used to differentiate servers with different "
-"processing power."
-msgstr ""
-"A função <literal>lbfactor</literal> é o fator de balanceamento de carga "
-"para este worker em específico. É utilizado para definir a prioridade (ou "
-"peso) que um nó deve exercer em outros nós. Quanto maior for o número, mais "
-"solicitações HTTP ele receberá. Esta configuração pode ser utilizada para "
-"diferenciar servidores com potência de processamento diferentes. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1137
-#, no-c-format
-msgid ""
-"The <literal>cachesize</literal> attribute defines the size of the thread "
-"pools associated to the Servlet container (i.e. the number of concurrent "
-"requests it will forward to the Servlet container). Make sure this number "
-"does not outnumber the number of threads configured on the AJP13 connector "
-"of the Servlet container. Please review <literal>http://jakarta.apache.org/"
-"tomcat/connectors-doc/config/workers.html</literal> for comments on "
-"<literal>cachesize</literal> for Apache 1.3.x."
-msgstr ""
-"A função <literal>cachesize</literal> define o tamanho do pool de discussão "
-"associado ao recipiente Servlet (ou seja, o número de solicitações "
-"concorrentes que o pool de discussão enviará ao recipiente Servlet). "
-"Assegure-se de que este número não ultrapasse o número de discussões "
-"configurados no conector AJP13 do recipiente Servlet. Por favor, revise o "
-"<literal>http://jakarta.apache.org/tomcat/connectors-doc/config/workers."
-"html</literal> para comentários sobre o <literal>cachesize</literal> para o "
-"Apache 1.3.x."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1143
-#, no-c-format
-msgid ""
-"The last part of the <literal>conf/workers.properties</literal> file defines "
-"the loadbalancer worker. The only thing you must change is the "
-"<literal>worker.loadbalancer.balanced_workers</literal> line: it must list "
-"all workers previously defined in the same file: load-balancing will happen "
-"over these workers."
-msgstr ""
-"A última parte do arquivo <literal>conf/workers.properties</literal> define "
-"o worker do balanceador de carga. A única coisa que você deve mudar é a "
-"linha <literal>worker.loadbalancer.balanced_workers</literal> que deve "
-"listar todos os workers anteriormente definidos no mesmo arquivo: o "
-"balanceamento de carga será efetuado nestes workers. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1147
-#, fuzzy, no-c-format
-msgid ""
-"The <literal>sticky_session</literal> property specifies the cluster "
-"behavior for HTTP sessions. If you specify <literal>worker.loadbalancer."
-"sticky_session=0</literal>, each request will be load balanced between node1 "
-"and node2; i.e., different requests for the same session will go to "
-"different servers. But when a user opens a session on one server, it is "
-"always necessary to always forward this user's requests to the same server, "
-"as long as that server is available. This is called a \"sticky session\", as "
-"the client is always using the same server he reached on his first request. "
-"To enable session stickiness, you need to set <literal>worker.loadbalancer."
-"sticky_session</literal> to 1."
-msgstr ""
-"A propriedade <literal>sticky_session</literal> especifica o comportamento "
-"do cluster para sessões HTTP. Se você especificar <literal>worker."
-"loadbalancer.sticky_session=0</literal>, cada solicitação terá a carga "
-"balanceada entre os nós 1 e 2. No entanto, recomendamos que quando um "
-"usuário abrir uma sessão em um servidor, sempre encaminhe as solicitações "
-"deste usuário para o mesmo servidor. Esta ação se chama \"sticky session\", "
-"pois o cliente sempre utiliza o mesmo servidor que ele encontrou na primeira "
-"solicitação. Do contrário, os dados da sessão do usuário precisariam estar "
-"sincronizados entre os dois servidores (replicação de sessão, veja <xref "
-"linkend=\"clustering-http-state\"/>). Para habilitar a aderência da sessão, "
-"você irá precisar mudar o <literal>worker.loadbalancer.sticky_session</"
-"literal> para 1."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1152
-#, fuzzy, no-c-format
-msgid ""
-"A non-loadbalanced setup with a single node requires a <literal>worker."
-"list=node1</literal> entry."
-msgstr ""
-"Uma configuração sem balanceamento de carga com somente um nó necessita da "
-"entrada <literal>worker.list=node1</literal> antes que o mod_jk possa "
-"funcionar corretamente. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1157
-#, no-c-format
-msgid "Configuring JBoss to work with mod_jk"
-msgstr "Configurando o JBoss para funcionar em mod_jk"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1158
-#, no-c-format
-msgid ""
-"Finally, we must configure the JBoss Tomcat instances on all clustered nodes "
-"so that they can expect requests forwarded from the mod_jk loadbalancer."
-msgstr ""
-"Finalmente, devemos configurar as instâncias do JBoss Tomcat em todos os nós "
-"em cluster para que eles aguardem solicitações encaminhadas a partir do "
-"balanceador de carga do mod_jk."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1160
-#, fuzzy, no-c-format
-msgid ""
-"On each clustered JBoss node, we have to name the node according to the name "
-"specified in <literal>workers.properties</literal>. For instance, on JBoss "
-"instance node1, edit the <literal>JBOSS_HOME/server/all/deploy/jboss-web."
-"deployer/server.xml</literal> file (replace <literal>/all</literal> with "
-"your own server name if necessary). Locate the <literal><Engine></"
-"literal> element and add an attribute <literal>jvmRoute</literal>:"
-msgstr ""
-"Em cada nó JBoss em cluster, temos que nomear um nó de acordo com o nome "
-"especificado em <literal>workers.properties</literal>. Por exemplo, no nó 1 "
-"da instância do JBoss, edite o arquivo <literal>JBOSS_HOME/server/all/deploy/"
-"jbossweb-tomcat50.sar/server.xml</literal> (substitua o <literal>/all</"
-"literal> com seu próprio nome de servidor se necessário). Localize o "
-"elemento <literal><Engine></literal> e adicione uma função "
-"<literal>jvmRoute</literal>:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1165
-#, no-c-format
-msgid ""
-"<Engine name=\"jboss.web\" defaultHost=\"localhost\" jvmRoute=\"node1"
-"\">\n"
-"... ...\n"
-"</Engine>"
-msgstr ""
-"<Engine name=\"jboss.web\" defaultHost=\"localhost\" jvmRoute=\"node1"
-"\">\n"
-"... ...\n"
-"</Engine>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1166
-#, no-c-format
-msgid ""
-"You also need to be sure the AJP connector in server.xml is enabled (i.e., "
-"uncommented). It is enabled by default."
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1168
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"<!-- Define an AJP 1.3 Connector on port 8009 --> \n"
-"<Connector port=\"8009\" address=\"${jboss.bind.address}\" protocol=\"AJP/1.3"
-"\" \n"
-"emptySessionPath=\"true\" enableLookups=\"false\" redirectPort=\"8443\" /> ]]"
-">"
-msgstr ""
-"<![CDATA[ \n"
-"<!-- Define an AJP 1.3 Connector on port 8009 --> \n"
-"<Connector port=\"8009\" address=\"${jboss.bind.address}\" protocol=\"AJP/1.3"
-"\" \n"
-"emptySessionPath=\"true\" enableLookups=\"false\" redirectPort=\"8443\" /> ]]"
-">"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1170
-#, fuzzy, no-c-format
-msgid ""
-"Then, for each JBoss Tomcat instance in the cluster, we need to tell it that "
-"mod_jk is in use, so it can properly manage the <literal>jvmRoute</literal> "
-"appended to its session cookies so that mod_jk can properly route incoming "
-"requests. Edit the <literal>JBOSS_HOME/server/all/deploy/jbossweb-tomcat50."
-"sar/META-INF/jboss-service.xml</literal> file (replace <literal>/all</"
-"literal> with your own server name). Locate the <literal><attribute></"
-"literal> element with a name of <literal>UseJK</literal>, and set its value "
-"to <literal>true</literal>:"
-msgstr ""
-"Então, para cada instância JBoss Tomcat no cluster, precisamos adicionar o "
-"valor <literal>jvmRoute</literal>para seus cookies de sessão, assim o mod_jk "
-"poderá trilhar as solicitações que são recebidas. Edite o arquivo "
-"<literal>JBOSS_HOME/server/all/deploy/jbossweb-tomcat50.sar/META-INF/jboss-"
-"service.xml</literal> (substitua <literal>/all</literal> com seu próprio "
-"nome de servidor). Localize o elemento <literal><attribute></literal> "
-"com o nome do <literal>UseJK</literal> e configure seu valor para "
-"<literal>true</literal>:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1175
-#, no-c-format
-msgid "<attribute name=\"UseJK\">true</attribute>"
-msgstr "<attribute name=\"UseJK\">true</attribute>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1176
-#, no-c-format
-msgid ""
-"At this point, you have a fully working Apache+mod_jk load-balancer setup "
-"that will balance call to the Servlet containers of your cluster while "
-"taking care of session stickiness (clients will always use the same Servlet "
-"container)."
-msgstr ""
-"Neste momento, a instalação do balanceador de carga Apache+mod_jk já estará "
-"funcionando e esta irá balancear as chamadas para os recipientes Servlet do "
-"seu cluster enquanto estiver cuidando da aderência de sessão (clientes "
-"sempre utilizarão o mesmo recipiente Servlet)."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1180
-#, no-c-format
-msgid ""
-"For more updated information on using mod_jk 1.2 with JBoss Tomcat, please "
-"refer to the JBoss wiki page at <literal>http://wiki.jboss.org/wiki/Wiki.jsp?"
-"page=UsingMod_jk1.2WithJBoss</literal>."
-msgstr ""
-"Para informações mais atualizadas utilizando um mod_jk JBoss Tomcat, favor "
-"consultar a página wiki do JBoss em <literal>http://wiki.jboss.org/wiki/Wiki."
-"jsp?page=UsingMod_jk1.2WithJBoss</literal>."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1188
-#, no-c-format
-msgid "Configuring HTTP session state replication"
-msgstr "Configurando a replicação de etado de sessão HTTP"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1189
-#, no-c-format
-msgid ""
-"The preceding discussion has been focused on using mod_jk as a load "
-"balancer. The content of the remainder our discussion of clustering HTTP "
-"services in JBoss AS applies no matter what load balancer is used."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1192
-#, fuzzy, no-c-format
-msgid ""
-"In <xref linkend=\"clustering-http-nodes\"/>, we covered how to use sticky "
-"sessions to make sure that a client in a session always hits the same server "
-"node in order to maintain the session state. However, sticky sessions by "
-"themselves are not an ideal solution. If a node goes down, all its session "
-"data is lost. A better and more reliable solution is to replicate session "
-"data across the nodes in the cluster. This way, the client can hit any "
-"server node and obtain the same session state."
-msgstr ""
-"Em <xref linkend=\"clustering-http-nodes\"/>, já vimos como utilizar as "
-"sessões aderentes para assegurar que um cliente em uma sessão sempre "
-"encontra o mesmo nó de servidor para manter o estado de sessão. No entanto, "
-"esta não é a solução ideal. A carga deve ser distribuída de forma aleatória "
-"para os nós durante um período e caso um nó caia, toda a sessão se perderá. "
-"Uma solução melhor e mais confiável seria replicar dados de sessão em todos "
-"os nós de um cluster. Dessa forma, o cliente pode encontrar qualquer nó de "
-"servidor e obter o mesmo estado de sessão. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1194
-#, fuzzy, no-c-format
-msgid ""
-"The <literal>jboss.cache:service=TomcatClusteringCache</literal> MBean makes "
-"use of JBoss Cache to provide HTTP session replication services to the JBoss "
-"Tomcat cluster. This MBean is defined in the <literal>deploy/jboss-web-"
-"cluster.sar/META-INF/jboss-service.xml file</literal>."
-msgstr ""
-"O MBean <literal>jboss.cache:service=TomcatClusteringCache</literal> utiliza "
-"o JBoss Cache para prover o serviço de replicação de sessão HTTP para o "
-"balanceador de carga HTTP em um cluster de JBoss Tomcat. Este MBean está "
-"definido no arquivo <literal>deploy/tc5-cluster.sar/META-INF/jboss-service."
-"xml</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1197
-#, fuzzy, no-c-format
-msgid ""
-"Before AS 4.2.0, the location of the HTTP session cache configuration file "
-"was <literal>deploy/tc5-cluster.sar/META-INF/jboss-service.xml</literal>. "
-"Prior to AS 4.0.4 CR2, the file was named <literal>deploy/tc5-cluster-"
-"service.xml</literal>."
-msgstr ""
-"Antes do AS 4.0.4 CR2, o arquivo de configuração do cache de sessão HTTP é o "
-"arquivo <literal>deploy/tc5-cluster-service.xml</literal> . Veja a "
-"documentação AS 4.0.3 para obter maiores detalhes. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1199
-#, fuzzy, no-c-format
-msgid ""
-"Below is a typical <literal>deploy/jbossweb-cluster.sar/META-INF/jboss-"
-"service.xml</literal> file. The configuration attributes in the "
-"<literal>TomcatClusteringCache</literal> MBean are very similar to those in "
-"the JBoss AS cache configuration."
-msgstr ""
-"Segue abaixo um arquivo típico de <literal>deploy/tc5-cluster.sar/META-INF/"
-"jboss-service.xml</literal>. As funções de configuração no MBean "
-"<literal>TomcatClusteringCache</literal> são muito semelhantes àquelas em "
-"<xref linkend=\"jbosscache-cache\"/>."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1202
-#, no-c-format
-msgid ""
-"<mbean code=\"org.jboss.cache.aop.TreeCacheAop\"\n"
-" name=\"jboss.cache:service=TomcatClusteringCache\">\n"
-"\n"
-" <depends>jboss:service=Naming</depends>\n"
-" <depends>jboss:service=TransactionManager</depends>\n"
-" <depends>jboss.aop:service=AspectDeployer</depends>\n"
-"\n"
-" <attribute name=\"TransactionManagerLookupClass\">\n"
-" org.jboss.cache.BatchModeTransactionManagerLookup\n"
-" </attribute>\n"
-" \n"
-" <attribute name=\"IsolationLevel\">REPEATABLE_READ</"
-"attribute>\n"
-" \n"
-" <attribute name=\"CacheMode\">REPL_ASYNC</attribute>\n"
-" \n"
-" <attribute name=\"ClusterName\">\n"
-" Tomcat-${jboss.partition.name:Cluster}\n"
-" </attribute>\n"
-" \n"
-" <attribute name=\"UseMarshalling\">false</attribute>\n"
-" \n"
-" <attribute name=\"InactiveOnStartup\">false</attribute>\n"
-" \n"
-" <attribute name=\"ClusterConfig\">\n"
-" ... ...\n"
-" </attribute>\n"
-" \n"
-" \n"
-" <attribute name=\"LockAcquisitionTimeout\">15000</"
-"attribute>\n"
-" <attribute name=\"SyncReplTimeout\">20000</attribute>\n"
-"</mbean>"
-msgstr ""
-"<mbean code=\"org.jboss.cache.aop.TreeCacheAop\"\n"
-" name=\"jboss.cache:service=TomcatClusteringCache\">\n"
-"\n"
-" <depends>jboss:service=Naming</depends>\n"
-" <depends>jboss:service=TransactionManager</depends>\n"
-" <depends>jboss.aop:service=AspectDeployer</depends>\n"
-"\n"
-" <attribute name=\"TransactionManagerLookupClass\">\n"
-" org.jboss.cache.BatchModeTransactionManagerLookup\n"
-" </attribute>\n"
-" \n"
-" <attribute name=\"IsolationLevel\">REPEATABLE_READ</"
-"attribute>\n"
-" \n"
-" <attribute name=\"CacheMode\">REPL_ASYNC</attribute>\n"
-" \n"
-" <attribute name=\"ClusterName\">\n"
-" Tomcat-${jboss.partition.name:Cluster}\n"
-" </attribute>\n"
-" \n"
-" <attribute name=\"UseMarshalling\">false</attribute>\n"
-" \n"
-" <attribute name=\"InactiveOnStartup\">false</attribute>\n"
-" \n"
-" <attribute name=\"ClusterConfig\">\n"
-" ... ...\n"
-" </attribute>\n"
-" \n"
-" \n"
-" <attribute name=\"LockAcquisitionTimeout\">15000</"
-"attribute>\n"
-" <attribute name=\"SyncReplTimeout\">20000</attribute>\n"
-"</mbean>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1204
-#, no-c-format
-msgid ""
-"Note that the value of the mbean element's code attribute is org.jboss.cache."
-"aop.TreeCacheAop, which is different from the other JBoss Cache Mbeans used "
-"in JBoss AS. This is because FIELD granularity HTTP session replication "
-"(covered below) needs the added features of the <literal>TreeCacheAop</"
-"literal> (a.k.a. <literal>PojoCache</literal>) class."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1207
-#, fuzzy, no-c-format
-msgid ""
-"The details of all the configuration options for a TreeCache MBean are "
-"covered in the JBoss Cache documentation. Below, we will just discuss "
-"several attributes that are most relevant to the HTTP cluster session "
-"replication."
-msgstr ""
-"A configuração detalhada para o MBean <literal>TreeCache</literal> pode ser "
-"encontrada na <xref linkend=\"jbosscache-cache\"/>. Abaixo, discutiremos "
-"diversas funções mais relevantes à replicação de sessão cluster HTTP."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1210
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">TransactionManagerLookupClass</emphasis> sets the "
-"transaction manager factory. The default value is <literal>org.jboss.cache."
-"BatchModeTransactionManagerLookup</literal>. It tells the cache NOT to "
-"participate in JTA-specific transactions. Instead, the cache manages its own "
-"transactions. Please do not change this."
-msgstr ""
-"A <emphasis role=\"bold\">TransactionManagerLookupClass</emphasis> instala a "
-"fábrica de gerenciamento de transação. O valor padrão é <literal>org.jboss."
-"cache.BatchModeTransactionManagerLookup</literal>. Ele diz ao cache para não "
-"participar das transações JTA específicas. Ao invés disso, o cache gerencia "
-"sua própria transação para dar suporte às replicações granuladas finas. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1217
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">CacheMode</emphasis> controls how the cache is "
-"replicated. The valid values are <literal>REPL_SYNC</literal> and "
-"<literal>REPL_ASYNC</literal>. With either setting the client request thread "
-"updates the local cache with the current sesssion contents and then sends a "
-"message to the caches on the other members of the cluster, telling them to "
-"make the same change. With REPL_ASYNC (the default) the request thread "
-"returns as soon as the update message has been put on the network. With "
-"REPL_SYNC, the request thread blocks until it gets a reply message from all "
-"cluster members, informing it that the update was successfully applied. "
-"Using synchronous replication makes sure changes are applied aroundthe "
-"cluster before the web request completes. However, synchronous replication "
-"is much slower."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1221
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ClusterName</emphasis> specifies the name of the "
-"cluster that the cache works within. The default cluster name is the the "
-"word \"Tomcat-\" appended by the current JBoss partition name. All the nodes "
-"must use the same cluster name."
-msgstr ""
-"<emphasis role=\"bold\">ClusterName</emphasis> especifica o nome do cluster "
-"no qual o cache funciona. O nome padrão do cluster padrão é a palavra "
-"\"Tomcat-\" complementado pelo nome de partição do JBoss atual. Todos os nós "
-"deveriam utilizar o mesmo nome de cluster. No entanto, a replicação da "
-"sessão pode compartilhar o mesmo canal (endereço multicast e porta) com "
-"outros serviços em cluster no JBoss, a replicação deve ter seu próprio nome "
-"de cluster. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1226
-#, no-c-format
-msgid ""
-"The <emphasis role=\"bold\">UseMarshalling</emphasis> and <emphasis role="
-"\"bold\">InactiveOnStartup</emphasis> attributes must have the same value. "
-"They must be <literal>true</literal> if <literal>FIELD</literal> level "
-"session replication is needed (see later). Otherwise, they are default to "
-"<literal>false</literal>."
-msgstr ""
-"As funções <emphasis role=\"bold\">UseMarshalling</emphasis> e <emphasis "
-"role=\"bold\">InactiveOnStartup</emphasis> devem ter o mesmo valor. Elas "
-"devem ser <literal>true</literal> caso o nível <literal>FIELD</literal> de "
-"replicação de sessão seja necessário (veja mais adiante). Do contrário, eles "
-"serão configurados para o padrão <literal>false</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1231
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ClusterConfig</emphasis> configures the underlying "
-"JGroups stack. Please refer to <xref linkend=\"jbosscache-jgroups\"/> for "
-"more information."
-msgstr ""
-"<emphasis role=\"bold\">ClusterConfig</emphasis> contém a configuração das "
-"pilhas JGroups subjacentes (veja <xref linkend=\"jbosscache-jgroups\"/>)."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1234
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">LockAcquisitionTimeout</emphasis> sets the maximum "
-"number of milliseconds to wait for a lock acquisition when trying to lock a "
-"cache node. The default value is 15000."
-msgstr ""
-"<emphasis role=\"bold\">LockAcquisitionTimeout</emphasis>estabelece o número "
-"máximo de milisegundos para esperar por uma aquisição de bloqueio. O valor "
-"padrão é 15000."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1238
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">SyncReplTimeout</emphasis> sets the maximum number "
-"of milliseconds to wait for a response from all nodes in the cluster when a "
-"synchronous replication message is sent out. The default value is 20000; "
-"should be a few seconds longer than LockAcquisitionTimeout."
-msgstr ""
-"<emphasis role=\"bold\">LockAcquisitionTimeout</emphasis>estabelece o número "
-"máximo de milisegundos para esperar por uma aquisição de bloqueio. O valor "
-"padrão é 15000."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1246
-#, no-c-format
-msgid "Enabling session replication in your application"
-msgstr "Habilitando a replicação de sessão em seu aplicativo."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1247
-#, fuzzy, no-c-format
-msgid ""
-"To enable clustering of your web application you must tag it as "
-"distributable in the <literal>web.xml</literal> descriptor. Here's an "
-"example:"
-msgstr ""
-"Para habilitar agrupamento em seu aplicativo da Web, você deve ajustá-lo "
-"para distribuível no descritor <literal>web.xml</literal>. Segue aqui um "
-"exemplo:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1249
-#, no-c-format
-msgid ""
-"<?xml version=\"1.0\"?> \n"
-"<web-app xmlns=\"http://java.sun.com/xml/ns/j2ee\"\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/web-app_2_4.xsd"
-"\" \n"
-" version=\"2.4\">\n"
-" <emphasis role=\"bold\"><distributable/></emphasis>\n"
-" <!-- ... -->\n"
-"</web-app>"
-msgstr ""
-"<?xml version=\"1.0\"?> \n"
-"<web-app xmlns=\"http://java.sun.com/xml/ns/j2ee\"\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/web-app_2_4.xsd"
-"\" \n"
-" version=\"2.4\">\n"
-" <emphasis role=\"bold\"><distributable/></emphasis>\n"
-" <!-- ... -->\n"
-"</web-app>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1250
-#, no-c-format
-msgid ""
-"You can futher configure session replication using the <literal>replication-"
-"config</literal> element in the <literal>jboss-web.xml</literal> file. Here "
-"is an example:"
-msgstr ""
-"Mais tarde, você poderá configurar a replicação de sessão utilizando o "
-"elemento <literal>replication-config</literal> no arquivo <literal>jboss-"
-"web.xml</literal>. Segue aqui um exemplo:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1252
-#, no-c-format
-msgid ""
-"<jboss-web>\n"
-" <replication-config>\n"
-" <replication-trigger>SET_AND_NON_PRIMITIVE_GET</replication-"
-"trigger>\n"
-" <replication-granularity>SESSION</replication-"
-"granularity>\n"
-" <replication-field-batch-mode>true</replication-field-batch-"
-"mode>\n"
-" </replication-config>\n"
-"</jboss-web>"
-msgstr ""
-"<jboss-web>\n"
-" <replication-config>\n"
-" <replication-trigger>SET_AND_NON_PRIMITIVE_GET</replication-"
-"trigger>\n"
-" <replication-granularity>SESSION</replication-"
-"granularity>\n"
-" <replication-field-batch-mode>true</replication-field-batch-"
-"mode>\n"
-" </replication-config>\n"
-"</jboss-web>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1253
-#, fuzzy, no-c-format
-msgid ""
-"The <literal>replication-trigger</literal> element determines what triggers "
-"a session replication (i.e. when is a session is considered <literal>dirty</"
-"literal> and in need of replication). It has 4 options:"
-msgstr ""
-"O elemento <literal>replication-trigger</literal> determina o que dispara a "
-"replicação de sessão (ou quando uma sessão é considerada suja). Existem 4 "
-"opções: "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1257
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">SET</emphasis>: With this policy, the session is "
-"considered dirty only when an attribute is set in the session (i.e., "
-"HttpSession.setAttribute() is invoked.) If your application always writes "
-"changed values back into the session, this option will be most optimal in "
-"terms of performance. The downside of SET is that if an object is retrieved "
-"from the session and modified without being written back into the session, "
-"the session manager will not know the attribute is dirty and the change to "
-"that object may not be replicated."
-msgstr ""
-"<emphasis role=\"bold\">SET</emphasis>: Com esta política, a sessão é "
-"considerada suja somente quando uma função é instalada na sessão. Se seu "
-"aplicativo sempre escreve um valor modificado ao retornar para a sessão, "
-"esta opção será mais otimizada em relação ao desempenho. Se um objeto for "
-"recuperado da sessão e modificado sem ser salvo de volta à sessão, a mudança "
-"feita neste objeto não será replicada. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1260
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">SET_AND_GET</emphasis>: With this policy, any "
-"attribute that is get or set will be marked as dirty. If an object is "
-"retrieved from the session and modified without being written back into the "
-"session, the change to that object will be replicated. The downside of "
-"SET_AND_GET is that it can have significant performance implications, since "
-"even reading immutable objects from the session (e.g., strings, numbers) "
-"will mark the read attributes as needing to be replicated."
-msgstr ""
-"<emphasis role=\"bold\">SET_AND_GET</emphasis>: Com esta política, qualquer "
-"função que seja set ou get, será marcada como suja. Caso um objeto seja "
-"recuperado da sessão e modificado sem ser salvo novamente na sessão, a "
-"mudança neste objeto será replicada. Esta opção poderá ter sérios problemas "
-"de desempenho."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1263
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">SET_AND_NON_PRIMITIVE_GET</emphasis>: This policy is "
-"similar to the SET_AND_GET policy except that get operationsthat return "
-"attribute values with primitive types do not mark the attribute as dirty. "
-"Primitive system types (i.e., String, Integer, Long, etc.) are immutable, so "
-"there is no reason to mark an attribute with such a type as dirty just "
-"because it has been read. If a get operation returns a value of a non-"
-"primitive type, the session manager has no simple way to know whether the "
-"object is mutable, so it assumes it is an marks the attribute as dirty. This "
-"setting avoids the downside of SET while reducing the performance impact of "
-"SET_AND_GET. It is the default setting."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1266
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ACCESS</emphasis>: This option causes the session to "
-"be marked as dirty whenever it is accessed. Since a the session is accessed "
-"during each HTTP request, it will be replicated with each request. The "
-"purpose of ACCESS is to ensure session last-access timestamps are kept in "
-"sync around the cluster.. Since with the other replication-trigger options "
-"the time stamp may not be updated in other clustering nodes because of no "
-"replication, the session in other nodes may expire before the active node if "
-"the HTTP request does not retrieve or modify any session attributes. When "
-"this option is set, the session timestamps will be synchronized throughout "
-"the cluster nodes. Note that use of this option can have a significant "
-"performance impact, so use it with caution. With the other replication-"
-"trigger options, if a session has gone 80% of its expiration interval "
-"without being replicated, as a safeguard its timestamp will be replicated no "
-"matter what. So, ACCESS is only useful in special circumstances where the "
-"above safeguard is considered inadequate."
-msgstr ""
-"<emphasis role=\"bold\">ACCESS</emphasis>: Esta opção faz com que a sessão "
-"seja marcada como suja, quando for acessada. Como a sessão é acessada "
-"durante cada solicitação HTTP, ela será replicada com cada solicitação. O "
-"carimbo de data e hora de acesso na instância da sessão também será "
-"atualizado. Como o carimbo de data e hora pode não estar atualizado em "
-"outros nós de cluster devido à falta de replicação, a sessão em outros nós "
-"poderá expirar antes de ativar o nó se a solicitação HTTP não recuperar ou "
-"modificar qualquer função de sessão. Quando esta opção for instalada, o "
-"carimbo de data e hora de sessão será sincronizado através dos nós cluster. "
-"Observe que o uso desta opção pode ter um impacto de desempenho bastante "
-"sério, portanto use-a com cuidado. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1269
-#, no-c-format
-msgid ""
-"The <literal>replication-granularity</literal> element controls the size of "
-"the replication units. The supported values are:"
-msgstr ""
-"O elemento <literal>replication-granularity</literal> controla o tamanho das "
-"unidades de replicação. Os valores de suporte são:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1274
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ATTRIBUTE</emphasis>: Replication is only for the "
-"dirty attributes in the session plus some session data, like the last-"
-"accessed timestamp. For sessions that carry large amounts of data, this "
-"option can increase replication performance. However, attributes will be "
-"separately serialized, so if there are any shared references between objects "
-"stored in the attributes, those shared references may be broken on remote "
-"nodes. For example, say a Person object stored under key “husband” has a "
-"reference to an Address, while another Person object stored under key “wife” "
-"has a reference to that same Address object. When the “husband” and “wife” "
-"attributes are separately deserialized on the remote nodes, each Person "
-"object will now have a reference to its own Address object; the Address "
-"object will no longer be shared."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1277
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">SESSION</emphasis>: The entire session object is "
-"replicated if any attribute is dirty. The entire session is serialized in "
-"one unit, so shared object references are maintained on remote nodes. This "
-"is the default setting."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1282
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">FIELD</emphasis>: Replication is only for individual "
-"changed data fields inside session attribute objects. Shared object "
-"references will be preserved across the cluster. Potentially most "
-"performant, but requires changes to your application (this will be discussed "
-"later)."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1285
-#, fuzzy, no-c-format
-msgid ""
-"The <literal>replication-field-batch-mode</literal> element indicates "
-"whether you want all replication messages associated with a request to be "
-"batched into one message. Only applicable if replication-granularity is "
-"FIELD. Default is <literal>true</literal>."
-msgstr ""
-"O elemento <literal>replication-field-batch-mode</literal> indica se você "
-"quer ou não realizar uma atualização de grupo entre cada solicitação http. O "
-"padrão é <literal>true</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1286
-#, fuzzy, no-c-format
-msgid ""
-"If your sessions are generally small, SESSION is the better policy. If your "
-"session is larger and some parts are infrequently accessed, ATTRIBUTE "
-"replication will be more effective. If your application has very big data "
-"objects in session attributes and only fields in those objects are "
-"frequently modified, the FIELD policy would be the best. In the next "
-"section, we will discuss exactly how the FIELD level replication works."
-msgstr ""
-"Se suas sessões são geralmente pequenas, a SESSÃO é a melhor política. Se "
-"sua sessão for maior e algumas partes dela são raramente acessadas, a "
-"replicação da FUNÇÃO será mais efetiva. Se seu aplicativo tiver objetos de "
-"dados muito grandes nas funções de sessão e somente os campos nestes objetos "
-"são modificados freqüentemente, a política CAMPO seria a melhor. Na próxima "
-"seção, iremos discutir como funciona a replicação de nível CAMPO. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1298
-#, no-c-format
-msgid "Using FIELD level replication"
-msgstr "Usando a replicação de nível FIELD."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1299
-#, no-c-format
-msgid ""
-"FIELD-level replication only replicates modified data fields inside objects "
-"stored in the session. Its use could potentially drastically reduce the data "
-"traffic between clustered nodes, and hence improve the performance of the "
-"whole cluster. To use FIELD-level replication, you have to first prepare (i."
-"e., bytecode enhance) your Java class to allow the session cache to detect "
-"when fields in cached objects have been changed and need to be replicated."
-msgstr ""
-"A replicação de nível FIELD, somente replica campos de dados modificados "
-"dentro de objetos armazenados na sessão. Esta ação poderia reduzir o tráfego "
-"de dados drasticamente entre os nós de cluster, e então melhorar o "
-"desempenho de todo o cluster. Para utilizar a replicação do nível de CAMPO, "
-"você precisa preparar primeiro sua classe de Java para indicar quais campos "
-"a serem replicados. Isto é feito através das anotações de estilo JDK 1.4 "
-"incorporado em JavaDocs."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1301
-#, no-c-format
-msgid ""
-"The first step in doing this is to identify the classes that need to be "
-"prepared. This is done via annotations. For example:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1305
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"@org.jboss.cache.aop.AopMarker\n"
-"public class Address \n"
-"{\n"
-"...\n"
-"}]]>"
-msgstr ""
-"<![CDATA[\n"
-"@org.jboss.cache.aop.AopMarker\n"
-"public class Address \n"
-"{\n"
-"...\n"
-"}]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1307
-#, fuzzy, no-c-format
-msgid ""
-"If you annotate a class with InstanceAopMarker instead, then all of its "
-"subclasses will be automatically annotated as well. Similarly, you can "
-"annotate an interface with InstanceofAopMarker and all of its implementing "
-"classes will be annotated. For example:"
-msgstr ""
-"No entanto, se você anotar com <literal>InstanceAopMarker</literal>, então "
-"todos as suas sub-classes também serão anotadas automaticamente. Por "
-"exemplo, "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1310
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"@org.jboss.cache.aop.InstanceOfAopMarker\n"
-"public class Person \n"
-"{\n"
-"...\n"
-"}\n"
-"then when you have a sub-class like\n"
-"public class Student extends Person\n"
-"{\n"
-"...\n"
-"}\n"
-"]]>"
-msgstr ""
-"<![CDATA[\n"
-"@org.jboss.cache.aop.InstanceOfAopMarker\n"
-"public class Person \n"
-"{\n"
-"...\n"
-"}\n"
-"then when you have a sub-class like\n"
-"public class Student extends Person\n"
-"{\n"
-"...\n"
-"}\n"
-"]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1312
-#, no-c-format
-msgid ""
-"There will be no need to annotate <literal>Student</literal>. It will be "
-"annotated automatically because it is a sub-class of <literal>Person</"
-"literal>. Jboss AS 5.0 requires JDK 5 at runtime, but some users may still "
-"need to build their projects using JDK 1.4. In this case, annotating classes "
-"can be done via JDK 1.4 style annotations embedded in JavaDocs. For example:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1317
-#, no-c-format
-msgid ""
-"/*\n"
-" * My usual comments here first.\n"
-" * @@org.jboss.web.tomcat.tc5.session.AopMarker\n"
-" */\n"
-"public class Address \n"
-"{\n"
-"...\n"
-"}"
-msgstr ""
-"/*\n"
-" * Meus comentários comuns aqui primeiro.\n"
-" * @@org.jboss.web.tomcat.tc5.session.AopMarker\n"
-" */\n"
-"Endereço de classe pública \n"
-"{\n"
-"...\n"
-"}"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1320
-#, no-c-format
-msgid "The anologue for <literal>@InstanceAopMarker</literal> is:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1322
-#, no-c-format
-msgid ""
-"/*\n"
-" *\n"
-" * @@org.jboss.web.tomcat.tc5.session.InstanceOfAopMarker\n"
-" */\n"
-"public class Person \n"
-"{\n"
-"...\n"
-"}"
-msgstr ""
-"/*\n"
-" *\n"
-" * @@org.jboss.web.tomcat.tc5.session.InstanceOfAopMarker\n"
-" */\n"
-"Pessoa de classe pública \n"
-"{\n"
-"...\n"
-"}"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1326
-#, fuzzy, no-c-format
-msgid ""
-"Once you have annotated your classes, you will need to perform a pre-"
-"processing step to bytecode enhance your classes for use by TreeCacheAop. "
-"You need to use the JBoss AOP pre-compiler <literal>annotationc</literal> "
-"and post-compiler <literal>aopc</literal> to process the above source code "
-"before and after they are compiled by the Java compiler. The annotationc "
-"step is only need if the JDK 1.4 style annotations are used; if JDK 5 "
-"annotations are used it is not necessary. Here is an example on how to "
-"invoke those commands from command line."
-msgstr ""
-"No entanto, como somente oferecemos suporte de anotação de estilo JDK 1.4 "
-"(oferecido pelo JBoss Aop), será preciso desempenhar a prévia do "
-"processamento. Será necessário utilizar o pré-compilador JBoss AOP "
-"<literal>annotationc</literal> e pós-compilador <literal>aopc</literal> para "
-"processar o código do recurso acima, antes e depois que eles forem "
-"compilados pelo compilador Java. Segue aqui um exemplo de como invocar estes "
-"comandos a partir de uma linha de comando. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1330
-#, no-c-format
-msgid ""
-"$ annotationc [classpath] [source files or directories]\n"
-"$ javac -cp [classpath] [source files or directories]\n"
-"$ aopc [classpath] [class files or directories]"
-msgstr ""
-"$ annotationc [classpath] [source files or directories]\n"
-"$ javac -cp [classpath] [source files or directories]\n"
-"$ aopc [classpath] [class files or directories]"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1332
-#, fuzzy, no-c-format
-msgid ""
-"Please see the JBoss AOP documentation for the usage of the pre- and post-"
-"compiler. The JBoss AOP project also provides easy to use ANT tasks to help "
-"integrate those steps into your application build process."
-msgstr ""
-"Veja na documentação JBoss AOP para o uso do pré e pós compilador. O projeto "
-"JBoss AOP também oferece o uso de tarefas ANT para ajudar a integrar aqueles "
-"passos em seu processo de construção do aplicativo. No próximo lançamento "
-"AS, o suporte de anotação JDK 5.0 será fornecido para maior transparência. "
-"Mas no momento, é importante que realize os passos pré e pós compilação para "
-"seu código fonte. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1336
-#, no-c-format
-msgid ""
-"You can see a complete example on how to build, deploy, and validate a FIELD-"
-"level replicated web application from this page: <ulink url=\"http://wiki."
-"jboss.org/wiki/Wiki.jsp?page=Http_session_field_level_example\"></ulink>. "
-"The example bundles the pre- and post-compile tools so you do not need to "
-"download JBoss AOP separately."
-msgstr ""
-"Você também poderá encontrar um exemplo completo sobre como construir, "
-"implementar e validar um aplicativo da WEB replicado de nível FIELD a partir "
-"desta página: <ulink url=\"http://wiki."
-"jboss.org/wiki/Wiki.jsp?page=Http_session_field_level_example\"></ulink>. O exemplo reune as "
-"ferramentas de pré e pós compilação para que não precise baixar o JBoss AOP "
-"separadamente."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1340
-#, no-c-format
-msgid ""
-"When you deploy the web application into JBoss AS, make sure that the "
-"following configurations are correct:"
-msgstr ""
-"Quando você implementar o aplicativo da WEB no JBoss AS, assegure-se de que "
-"as seguintes configurações estão corretas. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1344
-#, fuzzy, no-c-format
-msgid ""
-"In the server's <literal>deploy/jboss-web-cluster.sar/META-INF/jboss-service."
-"xml</literal> file, the <literal>inactiveOnStartup</literal> and "
-"<literal>useMarshalling</literal> attributes must both be <literal>true</"
-"literal>."
-msgstr ""
-"No arquivo do servidor <literal>deploy/tc5-cluster.sar/META-INF/jboss-"
-"service.xml</literal>, as funções <literal>inactiveOnStartup</literal> e "
-"<literal>useMarshalling</literal> deverão ser <literal>true</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1349
-#, no-c-format
-msgid ""
-"In the application's <literal>jboss-web.xml</literal> file, the "
-"<literal>replication-granularity</literal> attribute must be <literal>FIELD</"
-"literal>."
-msgstr ""
-"Nos aplicativos do arquivo <literal>jboss-web.xml</literal> , a função "
-"<literal>replication-granularity</literal> deverá ser <literal>FIELD</"
-"literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1354
-#, no-c-format
-msgid ""
-"Finally, let's see an example on how to use FIELD-level replication on those "
-"data classes. Notice that there is no need to call <literal>session."
-"setAttribute()</literal> after you make changes to the data object, and all "
-"changes to the fields are automatically replicated across the cluster."
-msgstr ""
-"Finalmente, vejamos um exemplo de como utilizar a replicação de nível FIELD "
-"naquelas classes de dados. Observe que não há necessidade de chamar "
-"<literal>session.setAttribute()</literal> após realizar as mudanças para o "
-"objeto de dados, e todas as modificações nos campos são automaticamente "
-"replicadas no cluster. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1357
-#, no-c-format
-msgid ""
-"// Do this only once. So this can be in init(), e.g.\n"
-"if(firstTime)\n"
-"{\n"
-" Person joe = new Person(\"Joe\", 40);\n"
-" Person mary = new Person(\"Mary\", 30);\n"
-" Address addr = new Address();\n"
-" addr.setZip(94086);\n"
-"\n"
-" joe.setAddress(addr);\n"
-" mary.setAddress(addr); // joe and mary share the same address!\n"
-"\n"
-" session.setAttribute(\"joe\", joe); // that's it.\n"
-" session.setAttribute(\"mary\", mary); // that's it.\n"
-"}\n"
-"\n"
-"Person mary = (Person)session.getAttribute(\"mary\");\n"
-"mary.getAddress().setZip(95123); // this will update and replicate the zip "
-"code."
-msgstr ""
-"// Faça isto somente uma vez e ele estará em init(), e.g.\n"
-"if(firstTime)\n"
-"{\n"
-" Pessoa joe = Pessoa nova(\"Joe\", 40);\n"
-" Pessoa mary = Pessoa nova(\"Mary\", 30);\n"
-" Endereço end. = Endereço novo();\n"
-" addr.setZip(94086);\n"
-"\n"
-" joe.setAddress(addr);\n"
-" mary.setAddress(addr); // joe e mary compartilham o mesmo endereço!\n"
-"\n"
-" session.setAttribute(\"joe\", joe); // Final.\n"
-" session.setAttribute(\"mary\", mary); // Final.\n"
-"}\n"
-"\n"
-"Pessoa mary = (Pessoa)session.getAttribute(\"mary\");\n"
-"mary.getAddress().setZip(95123); // isto irá atualizar e replicar o código "
-"zip."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1358
-#, no-c-format
-msgid ""
-"Besides plain objects, you can also use regular Java collections of those "
-"objects as session attributes. JBoss cache automatically figures out how to "
-"handle those collections and replicate field changes in their member objects."
-msgstr ""
-"Além dos objetos básicos, você também poderá utilizar as coleções de Java "
-"comuns, daqueles objetos, como funções de sessão. O JBoss cache descobre "
-"automaticamente como lidar com aquelas coleções e replicar as mudanças de "
-"campos em seus objetos de membros. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1363
-#, no-c-format
-msgid "Monitoring session replication"
-msgstr "Monitorar replicação de sessão."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1364
-#, no-c-format
-msgid ""
-"If you have deployed and accessed your application, go to the <literal>jboss."
-"cache:service=TomcatClusteringCache</literal> MBean and invoke the "
-"<literal>printDetails</literal> operation. You should see output resembling "
-"the following."
-msgstr ""
-"Se você tiver implementado e acessado seu aplicativo, vá para o MBean "
-"<literal>jboss.cache:service=TomcatClusteringCache</literal> e invoque a "
-"operação <literal>printDetails</literal>. Será exibido um resultado parecido "
-"com o que se segue:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1367
-#, no-c-format
-msgid ""
-"/JSESSION\n"
-"\n"
-"/localhost\n"
-"\n"
-"/quote\n"
-"\n"
-"/FB04767C454BAB3B2E462A27CB571330\n"
-"VERSION: 6\n"
-"FB04767C454BAB3B2E462A27CB571330: org.jboss.invocation."
-"MarshalledValue at 1f13a81c\n"
-"\n"
-"/AxCI8Ovt5VQTfNyYy9Bomw**\n"
-"VERSION: 4\n"
-"AxCI8Ovt5VQTfNyYy9Bomw**: org.jboss.invocation.MarshalledValue at e076e4c8"
-msgstr ""
-"/JSESSION\n"
-"\n"
-"/localhost\n"
-"\n"
-"/quote\n"
-"\n"
-"/FB04767C454BAB3B2E462A27CB571330\n"
-"VERSION: 6\n"
-"FB04767C454BAB3B2E462A27CB571330: org.jboss.invocation."
-"MarshalledValue at 1f13a81c\n"
-"\n"
-"/AxCI8Ovt5VQTfNyYy9Bomw**\n"
-"VERSION: 4\n"
-"AxCI8Ovt5VQTfNyYy9Bomw**: org.jboss.invocation.MarshalledValue at e076e4c8"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1369
-#, fuzzy, no-c-format
-msgid ""
-"This output shows two separate web sessions, in one application named "
-"<emphasis>quote</emphasis>, that are being shared via JBossCache. This "
-"example uses a <literal>replication-granularity</literal> of "
-"<literal>session</literal>. Had <literal>ATTRIBUTE</literal> level "
-"replication been used, there would be additional entries showing each "
-"replicated session attribute. In either case, the replicated values are "
-"stored in an opaque <literal>MarshelledValue</literal> container. There "
-"aren't currently any tools that allow you to inspect the contents of the "
-"replicated session values. If you do not see any output, either the "
-"application was not correctly marked as <literal>distributable</literal> or "
-"you haven't accessed a part of application that places values in the HTTP "
-"session. The <literal>org.jboss.cache</literal> and <literal>org.jboss.web</"
-"literal> logging categories provide additional insight into session "
-"replication useful for debugging purposes."
-msgstr ""
-"Este resultado mostra duas sessões de Web separadas, que estejam sendo "
-"compartilhadas através do Cache JBoss, em um aplicativo chamado "
-"<emphasis>quote</emphasis>. Este exemplo utiliza um <literal>replication-"
-"granularity</literal> de <literal>session</literal>. Se um nível de "
-"replicação <literal>attribute</literal> tivesse sido utilizado, haveriam "
-"entradas adicionais mostrando cada função de sessão replicada. Em ambos os "
-"casos, os valores replicados são armazenados em um recipiente opaco "
-"<literal>MarshelledValue</literal>. Atualmente, não existe nenhuma "
-"ferramenta que permita que você inspecione o conteúdo dos valores de sessão "
-"replicada. Se o resultado não puder ser visualizado, ou o aplicativo não foi "
-"marcado de forma correta como <literal>distributable</literal> ou então "
-"você não acessou uma parte do aplicativo que coloca os valores na sessão "
-"HTTP. As categorias de entrada<literal>org.jboss.cache</literal> e "
-"<literal>org.jboss.web</literal> oferecem insight adicional na replicação de "
-"sessão, úteis para fins de depuração."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1377
-#, fuzzy, no-c-format
-msgid "Using Clustered Single Sign On"
-msgstr "Uso do Single Sign-On"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1379
-#, fuzzy, no-c-format
-msgid ""
-"JBoss supports clustered single sign-on, allowing a user to authenticate to "
-"one web application on a JBoss server and to be recognized on all web "
-"applications, on that same machine or on another node in the cluster, that "
-"are deployed on the same virtual host. Authentication replication is handled "
-"by the same JBoss Cache Mbean that is used by the HTTP session replication "
-"service. Although session replication does not need to be explicitly enabled "
-"for the applications in question, the <literal>jboss-web-cluster.sar</"
-"literal> file needs to be deployed."
-msgstr ""
-"O JBoss oferece suporte para autenticações simples em cluster, permitindo "
-"que um usuário faça a autenticação em um aplicativo do servidor JBoss e que "
-"ele seja reconhecido em todos os aplicativos, na mesma máquina ou em um "
-"outro nó no cluster, que sejam implementados na mesma máquina virtual. A "
-"replicação da autenticação é gerenciada pelo serviço de replicação da sessão "
-"de HTTP. Apesar da replicação da sessão não precisar ser habilitada "
-"explicitamente para as aplicações em questão, o arquivo <literal>tc5-"
-"cluster-service.xml</literal>precisa ser implementado. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1381
-#, no-c-format
-msgid ""
-"To enable single sign-on, you must add the <literal>ClusteredSingleSignOn</"
-"literal> valve to the appropriate <literal>Host</literal> elements of the "
-"tomcat <literal>server.xml</literal> file. The valve configuration is shown "
-"here:"
-msgstr ""
-"Para habilitar o Single Sign-On, é preciso adicionar a válvula para os "
-"elementos <literal>Host</literal> apropriados do arquivo tomcat "
-"<literal>server.xml</literal>. A configuração da válvula está demonstrada "
-"aqui: "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1384
-#, no-c-format
-msgid ""
-"<Valve className=\"org.jboss.web.tomcat.tc5.sso.ClusteredSingleSignOn\" /"
-">"
-msgstr ""
-"<Valve className=\"org.jboss.web.tomcat.tc5.sso.ClusteredSingleSignOn\" /"
-">"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1387
-#, fuzzy, no-c-format
-msgid "Clustered Singleton Services"
-msgstr "Serviços JMS em Cluster"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1388
-#, no-c-format
-msgid ""
-"A clustered singleton service (also known as an HA singleton) is a service "
-"that is deployed on multiple nodes in a cluster, but is providing its "
-"service on only one of the nodes. The node running the singleton service is "
-"typically called the master node. When the master fails or is shut down, "
-"another master is selected from the remaining nodes and the service is "
-"restarted on the new master. Thus, other than a brief interval when one "
-"master has stopped and another has yet to take over, the service is always "
-"being provided by one but only one node."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1391
-#, no-c-format
-msgid "Topology after the Master Node fails"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1399
-#, no-c-format
-msgid ""
-"The JBoss Application Server (AS) provides support for a number of "
-"strategies for helping you deploy clustered singleton services. In this "
-"section we will explore the different strategies. All of the strategies are "
-"built on top of the HAPartition service described in the introduction. They "
-"rely on the <literal>HAPartition</literal> to provide notifications when "
-"different nodes in the cluster start and stop; based on those notifications "
-"each node in the cluster can independently (but consistently) determine if "
-"it is now the master node and needs to begin providing a service."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1404
-#, fuzzy, no-c-format
-msgid "HASingletonDeployer service"
-msgstr "cliente.deployer-service.xml"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1405
-#, no-c-format
-msgid ""
-"The simplest and most commonly used strategy for deploying an HA singleton "
-"is to take an ordinary deployment (war, ear, jar, whatever you would "
-"normally put in deploy) and deploy it in the <literal>$JBOSS_HOME/server/all/"
-"deploy-hasingleton</literal> directory instead of in <literal>deploy</"
-"literal>. The <literal>deploy-hasingleton</literal> directory does not lie "
-"under deploy or farm, so its contents are not automatically deployed when an "
-"AS instance starts. Instead, deploying the contents of this directory is the "
-"responsibility of a special service, the <literal>jboss.ha:"
-"service=HASingletonDeployer</literal> MBean (which itself is deployed via "
-"the deploy/deploy-hasingleton-service.xml file.) The HASingletonDeployer "
-"service is itself an HA Singleton, one whose provided service when it "
-"becomes master is to deploy the contents of deploy-hasingleton and whose "
-"service when it stops being the master (typically at server shutdown) is to "
-"undeploy the contents of <literal>deploy-hasingleton</literal>."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1408
-#, no-c-format
-msgid ""
-"So, by placing your deployments in <literal>deploy-hasingleton</literal> you "
-"know that they will be deployed only on the master node in the cluster. If "
-"the master node cleanly shuts down, they will be cleanly undeployed as part "
-"of shutdown. If the master node fails or is shut down, they will be deployed "
-"on whatever node takes over as master."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1411
-#, no-c-format
-msgid "Using deploy-hasingleton is very simple, but it does have two drawbacks:"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1415
-#, no-c-format
-msgid ""
-"There is no hot-deployment feature for services in <literal>deploy-"
-"hasingleton</literal>. Redeploying a service that has been deployed to "
-"<literal>deploy-hasingleton</literal> requires a server restart."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1420
-#, no-c-format
-msgid ""
-"If the master node fails and another node takes over as master, your "
-"singleton service needs to go through the entire deployment process before "
-"it will be providing services. Depending on how complex the deployment of "
-"your service is and what sorts of startup activities it engages in, this "
-"could take a while, during which time the service is not being provided."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1432
-#, no-c-format
-msgid "Mbean deployments using HASingletonController"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1433
-#, no-c-format
-msgid ""
-"If your service is an Mbean (i.e., not a J2EE deployment like an ear or war "
-"or jar), you can deploy it along with a service called an "
-"HASingletonController in order to turn it into an HA singleton. It is the "
-"job of the HASingletonController to work with the HAPartition service to "
-"monitor the cluster and determine if it is now the master node for its "
-"service. If it determines it has become the master node, it invokes a method "
-"on your service telling it to begin providing service. If it determines it "
-"is no longer the master node, it invokes a method on your service telling it "
-"to stop providing service. Let's walk through an illustration."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1436
-#, no-c-format
-msgid ""
-"First, we have an MBean service that we want to make an HA singleton. The "
-"only thing special about it is it needs to expose in its MBean interface a "
-"method that can be called when it should begin providing service, and "
-"another that can be called when it should stop providing service:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1439
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"public class HASingletonExample\n"
-"implements HASingletonExampleMBean { \n"
-" \n"
-"private boolean isMasterNode = false; \n"
-" \n"
-"public void startSingleton() { \n"
-"isMasterNode = true; \n"
-"} \n"
-". \n"
-"public boolean isMasterNode() { \n"
-"return isMasterNode; \n"
-" } \n"
-" \n"
-" public void stopSingleton() { \n"
-" isMasterNode = false; \n"
-" } \n"
-"} ]]>"
-msgstr ""
-"<![CDATA[ \n"
-"public class HASingletonExample\n"
-"implements HASingletonExampleMBean { \n"
-" \n"
-"private boolean isMasterNode = false; \n"
-" \n"
-"public void startSingleton() { \n"
-"isMasterNode = true; \n"
-"} \n"
-". \n"
-"public boolean isMasterNode() { \n"
-"return isMasterNode; \n"
-" } \n"
-" \n"
-" public void stopSingleton() { \n"
-" isMasterNode = false; \n"
-" } \n"
-"} ]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1441
-#, no-c-format
-msgid ""
-"We used “startSingleton” and “stopSingleton” in the above example, but you "
-"could name the methods anything."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1444
-#, no-c-format
-msgid ""
-"Next, we deploy our service, along with an HASingletonController to control "
-"it, most likely packaged in a .sar file, with the following <literal>META-"
-"INF/jboss-service.xml</literal>:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1447
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-" <server> \n"
-" <!-- This MBean is an example of a clustered singleton --> \n"
-" <mbean code=\"org.jboss.ha.examples.HASingletonExample\" \n"
-" name=“jboss:service=HASingletonExample\"/> \n"
-" \n"
-" <!-- This HASingletonController manages the cluster Singleton --> \n"
-" <mbean code=\"org.jboss.ha.singleton.HASingletonController\" \n"
-" name=\"jboss:service=ExampleHASingletonController\"> \n"
-" \n"
-" <!-- Inject a ref to the HAPartition -->\n"
-" <depends optional-attribute-name=\"ClusterPartition\" proxy-"
-"type=\"attribute\">\n"
-" jboss:service=${jboss.partition.name:"
-"DefaultPartition}\n"
-" </depends> \n"
-" <!-- Inject a ref to the service being controlled -->\n"
-" <depends optional-attribute-name=\"TargetName\">\n"
-" jboss:service=HASingletonExample\n"
-" </depends>\n"
-" <!-- Methods to invoke when become master / stop being "
-"master -->\n"
-" <attribute name=\"TargetStartMethod\">startSingleton</"
-"attribute> \n"
-" <attribute name=\"TargetStopMethod\">stopSingleton</"
-"attribute> \n"
-" </mbean> \n"
-"</server> ]]>"
-msgstr ""
-"<![CDATA[\n"
-" <server> \n"
-" <!-- This MBean is an example of a clustered singleton --> \n"
-" <mbean code=\"org.jboss.ha.examples.HASingletonExample\" \n"
-" name=“jboss:service=HASingletonExample\"/> \n"
-" \n"
-" <!-- This HASingletonController manages the cluster Singleton --> \n"
-" <mbean code=\"org.jboss.ha.singleton.HASingletonController\" \n"
-" name=\"jboss:service=ExampleHASingletonController\"> \n"
-" \n"
-" <!-- Inject a ref to the HAPartition -->\n"
-" <depends optional-attribute-name=\"ClusterPartition\" proxy-"
-"type=\"attribute\">\n"
-" jboss:service=${jboss.partition.name:"
-"DefaultPartition}\n"
-" </depends> \n"
-" <!-- Inject a ref to the service being controlled -->\n"
-" <depends optional-attribute-name=\"TargetName\">\n"
-" jboss:service=HASingletonExample\n"
-" </depends>\n"
-" <!-- Methods to invoke when become master / stop being "
-"master -->\n"
-" <attribute name=\"TargetStartMethod\">startSingleton</"
-"attribute> \n"
-" <attribute name=\"TargetStopMethod\">stopSingleton</"
-"attribute> \n"
-" </mbean> \n"
-"</server> ]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1449
-#, no-c-format
-msgid "Voila! A clustered singleton service."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1451
-#, no-c-format
-msgid ""
-"The obvious downside to this approach is it only works for MBeans. Upsides "
-"are that the above example can be placed in <literal>deploy</literal> or "
-"<literal>farm</literal> and thus can be hot deployed and farmed deployed. "
-"Also, if our example service had complex, time-consuming startup "
-"requirements, those could potentially be implemented in create() or start() "
-"methods. JBoss will invoke create() and start() as soon as the service is "
-"deployed; it doesn't wait until the node becomes the master node. So, the "
-"service could be primed and ready to go, just waiting for the controller to "
-"implement startSingleton() at which point it can immediately provide service."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1454
-#, no-c-format
-msgid ""
-"The jboss.ha:service=HASingletonDeployer service discussed above is itself "
-"an interesting example of using an HASingletonController. Here is its "
-"deployment descriptor (extracted from the <literal>deploy/deploy-hasingleton-"
-"service.xml</literal> file):"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1457
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"<mbean code=\"org.jboss.ha.singleton.HASingletonController\" \n"
-"name=\"jboss.ha:service=HASingletonDeployer\"> \n"
-" <depends optional-attribute-name=\"ClusterPartition\" proxy-type=\"attribute"
-"\">\n"
-" jboss:service=${jboss.partition.name:DefaultPartition}\n"
-" </depends> \n"
-" <depends optional-attributeame=\"TargetName\">\n"
-" jboss.system:service=MainDeployer\n"
-" </depends> \n"
-" <attribute name=\"TargetStartMethod\">deploy</attribute> \n"
-" <attribute name=\"TargetStartMethodArgument\">\n"
-" ${jboss.server.home.url}/deploy-hasingleton\n"
-" </attribute> \n"
-" <attribute name=\"TargetStopMethod\">undeploy</attribute> \n"
-" <attribute name=\"TargetStopMethodArgument\">\n"
-" ${jboss.server.home.url}/deploy-hasingleton\n"
-" </attribute> \n"
-"</mbean> ]]>"
-msgstr ""
-"<![CDATA[ \n"
-"<mbean code=\"org.jboss.ha.singleton.HASingletonController\" \n"
-"name=\"jboss.ha:service=HASingletonDeployer\"> \n"
-" <depends optional-attribute-name=\"ClusterPartition\" proxy-type=\"attribute"
-"\">\n"
-" jboss:service=${jboss.partition.name:DefaultPartition}\n"
-" </depends> \n"
-" <depends optional-attributeame=\"TargetName\">\n"
-" jboss.system:service=MainDeployer\n"
-" </depends> \n"
-" <attribute name=\"TargetStartMethod\">deploy</attribute> \n"
-" <attribute name=\"TargetStartMethodArgument\">\n"
-" ${jboss.server.home.url}/deploy-hasingleton\n"
-" </attribute> \n"
-" <attribute name=\"TargetStopMethod\">undeploy</attribute> \n"
-" <attribute name=\"TargetStopMethodArgument\">\n"
-" ${jboss.server.home.url}/deploy-hasingleton\n"
-" </attribute> \n"
-"</mbean> ]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1459
-#, no-c-format
-msgid ""
-"A few interesting things here. First the service being controlled is the "
-"<literal>MainDeployer</literal> service, which is the core deployment "
-"service in JBoss. That is, it's a service that wasn't written with an intent "
-"that it be controlled by an <literal>HASingletonController</literal>. But it "
-"still works! Second, the target start and stop methods are “deploy” and "
-"“undeploy”. No requirement that they have particular names, or even that "
-"they logically have “start” and “stop” functionality. Here the functionality "
-"of the invoked methods is more like “do” and “undo”. Finally, note the "
-"“<literal>TargetStart(Stop)MethodArgument</literal>” attributes. Your "
-"singleton service's start/stop methods can take an argument, in this case "
-"the location of the directory the <literal>MainDeployer</literal> should "
-"deploy/undeploy."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1467
-#, no-c-format
-msgid "HASingleton deployments using a Barrier"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1468
-#, no-c-format
-msgid ""
-"Services deployed normally inside deploy or farm that want to be started/"
-"stopped whenever the content of deploy-hasingleton gets deployed/undeployed, "
-"(i.e., whenever the current node becomes the master), need only specify a "
-"dependency on the Barrier mbean:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1470
-#, no-c-format
-msgid ""
-"<![CDATA[<depends>jboss.ha:service=HASingletonDeployer,type=Barrier</"
-"depends>]]>"
-msgstr ""
-"<![CDATA[<depends>jboss.ha:service=HASingletonDeployer,type=Barrier</"
-"depends>]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1472
-#, no-c-format
-msgid ""
-"The way it works is that a BarrierController is deployed along with the "
-"jboss.ha:service=HASingletonDeployer MBean and listens for JMX notifications "
-"from it. A BarrierController is a relatively simple Mbean that can subscribe "
-"to receive any JMX notification in the system. It uses the received "
-"notifications to control the lifecycle of a dynamically created Mbean called "
-"the Barrier.The Barrier is instantiated, registered and brought to the "
-"CREATE state when the BarrierController is deployed. After that, the "
-"BarrierController starts and stops the Barrier when matching JMX "
-"notifications are received. Thus, other services need only depend on the "
-"Barrier MBean using the usual <depends> tag, and they will be started "
-"and stopped in tandem with the Barrier. When the BarrierController is "
-"undeployed the Barrier is destroyed too."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1476
-#, no-c-format
-msgid ""
-"This provides an alternative to the deploy-hasingleton approach in that we "
-"can use farming to distribute the service, while content in deploy-"
-"hasingleton must be copied manually on all nodes."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1479
-#, no-c-format
-msgid ""
-"On the other hand, the barrier-dependent service will be instantiated/"
-"created (i.e., any create() method invoked) on all nodes, but only started "
-"on the master node. This is different with the deploy-hasingleton approach "
-"that will only deploy (instantiate/create/start) the contents of the deploy-"
-"hasingleton directory on one of the nodes."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1483
-#, no-c-format
-msgid ""
-"So services depending on the barrier will need to make sure they do minimal "
-"or no work inside their create() step, rather they should use start() to do "
-"the work."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1487
-#, no-c-format
-msgid ""
-"The Barrier controls the start/stop of dependent services, but not their "
-"destruction, which happens only when the <literal>BarrierController</"
-"literal> is itself destroyed/undeployed. Thus using the <literal>Barrier</"
-"literal> to control services that need to be \"destroyed\" as part of their "
-"normal “undeploy” operation (like, for example, an <literal>EJBContainer</"
-"literal>) will not have the desired effect."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1496
-#, no-c-format
-msgid "Determining the master node"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1497
-#, no-c-format
-msgid ""
-"The various clustered singleton management strategies all depend on the fact "
-"that each node in the cluster can independently react to changes in cluster "
-"membership and correctly decide whether it is now the “master node”. How is "
-"this done?"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1500
-#, no-c-format
-msgid ""
-"Prior to JBoss AS 4.2.0, the methodology for this was fixed and simple. For "
-"each member of the cluster, the HAPartition mbean maintains an attribute "
-"called the CurrentView, which is basically an ordered list of the current "
-"members of the cluster. As nodes join and leave the cluster, JGroups ensures "
-"that each surviving member of the cluster gets an updated view. You can see "
-"the current view by going into the JMX console, and looking at the "
-"CurrentView attribute in the <literal>jboss:service=DefaultPartition</"
-"literal> mbean. Every member of the cluster will have the same view, with "
-"the members in the same order."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1503
-#, no-c-format
-msgid ""
-"Let's say, for example, that we have a 4 node cluster, nodes A through D, "
-"and the current view can be expressed as {A, B, C, D}. Generally speaking, "
-"the order of nodes in the view will reflect the order in which they joined "
-"the cluster (although this is not always the case, and should not be assumed "
-"to be the case.)"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1506
-#, no-c-format
-msgid ""
-"To further our example, let's say there is a singleton service (i.e., an "
-"<literal>HASingletonController</literal>) named Foo that's deployed around "
-"the cluster, except, for whatever reason, on B. The <literal>HAPartition</"
-"literal> service maintains across the cluster a registry of what services "
-"are deployed where, in view order. So, on every node in the cluster, the "
-"<literal>HAPartition</literal> service knows that the view with respect to "
-"the Foo service is {A, C, D} (no B)."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1510
-#, no-c-format
-msgid ""
-"Whenever there is a change in the cluster topology of the Foo service, the "
-"<literal>HAPartition</literal> service invokes a callback on Foo notifying "
-"it of the new topology. So, for example, when Foo started on D, the Foo "
-"service running on A, C and D all got callbacks telling them the new view "
-"for Foo was {A, C, D}. That callback gives each node enough information to "
-"independently decide if it is now the master. The Foo service on each node "
-"does this by checking if they are the first member of the view – if they "
-"are, they are the master; if not, they're not. Simple as that."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1514
-#, no-c-format
-msgid ""
-"If A were to fail or shutdown, Foo on C and D would get a callback with a "
-"new view for Foo of {C, D}. C would then become the master. If A restarted, "
-"A, C and D would get a callback with a new view for Foo of {C, D, A}. C "
-"would remain the master – there's nothing magic about A that would cause it "
-"to become the master again just because it was before."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1534
-#, no-c-format
-msgid "Clustered JMS Services"
-msgstr "Serviços JMS em Cluster"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1536
-#, no-c-format
-msgid ""
-"JBoss AS 3.2.4 and above support high availability JMS (HA-JMS) services in "
-"the <literal>all</literal> server configuration. In the current production "
-"release of JBoss AS, the HA-JMS service is implemented as a clustered "
-"singleton fail-over service."
-msgstr ""
-"JBoss AS 3.2.4 e versões posteriores oferecem suporte de serviços JMS (HA-"
-"JMS) de alta disponibilidade na configuração do servidor <literal>all</"
-"literal>. No lançamento da produção atual do JBoss AS, o serviço HA-JMS é "
-"implementado como um serviço fail-over de singleton em cluster."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1541
-#, no-c-format
-msgid ""
-"If you are willing to configure HA-JMS yourself, you can get it to work with "
-"earlier versions of JBoss AS. We have a customer who uses HA-JMS "
-"successfully in JBoss AS 3.0.7. Please contact JBoss support for more "
-"questions."
-msgstr ""
-"Se você mesmo quiser configurar o HA-JMS, poderá conseguir que ele funcione "
-"com as versões anteriores do JBoss AS. Temos um cliente que utiliza o HA-JMS "
-"perfeitamente no JBoss AS 3.0.7. Entre em contato com o suporte JBoss para "
-"maiores informações."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1545
-#, no-c-format
-msgid ""
-"The HA-JMS in JBoss AS 4.2.2 and earlier was based on the JBoss MQ messaging "
-"product. In later releases of the AS, JBoss MQ was replaced by the newer "
-"JBoss Messaging project. JBoss Messaging's clustering implementation is "
-"considerably different from HA-JMS based on JBoss MQ; most notably it is not "
-"based on a singleton service only running on one node in the cluster."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1554
-#, no-c-format
-msgid "High Availability Singleton Fail-over"
-msgstr "Alta disponibilidade do Fail-over Singleton"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1555
-#, fuzzy, no-c-format
-msgid ""
-"The JBoss HA-JMS service (i.e., message queues topics and supporting "
-"services) only runs on a single node (i.e., the master node) in the cluster "
-"at any given time. If that node fails, the cluster simply elects another "
-"node to run the JMS service, and the queues, topics and supporting services "
-"are deployed on that server (fail-over). This setup provides redundancy "
-"against server failures but does not reduce the work load on the JMS server "
-"node."
-msgstr ""
-"O serviço JBoss HA-JMS (ou seja, filas de 'mensagens' e tópicos) somente "
-"roda em um nó simples (ou seja, o nó master) no cluster a qualquer momento. "
-"Se o nó falhar, o cluster simplesmente elege outro nó para rodar o serviço "
-"JMS (fail-over). Esta configuração oferece redundância junto as falhas do "
-"servidor, mas não reduz a carga de trabalho no nó do servidor JMS: "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1557
-#, no-c-format
-msgid ""
-"While you cannot load balance HA-JMS queues (there is only one master node "
-"that runs the queues), you can load balance the MDBs that process messages "
-"from those queues (see <xref linkend=\"clustering-jms-loadbalanced\"/>)."
-msgstr ""
-"Embora você não possa balancear a carga das filas do HA-JMS (existe somente "
-"um nó master que roda as filas) você não pode balancear a carga dos MDBs que "
-"processam as mensagens a partir destas filas (veja <xref linkend="
-"\"clustering-jms-loadbalanced\"/>)."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1562
-#, no-c-format
-msgid "Server Side Configuration"
-msgstr "Configuração do Servidor"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1564
-#, no-c-format
-msgid ""
-"The biggest configuration difference between HA-JMS in the all configuration "
-"and the non-HA version found in the default configuration is the location of "
-"most configuration files. For HA-JMS, most configuration files are found in "
-"the deploy-hasingleton/jms directory, not in deploy/jms. Your queues and "
-"topics must be deployed in deploy-hasingleton (or a subdirectory of it like "
-"deploy-hasingleton/jms.) Application components that act as clients to HA-"
-"JMS (e.g., MDBs and other JMS clients) do not need to be deployed in deploy-"
-"hasingleton. They should only be deployed there if you only want them "
-"running on one node in the cluster at a time."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1567
-#, fuzzy, no-c-format
-msgid ""
-"To use the singleton fail-over HA-JMS service, you must configure JMS "
-"services identically on all nodes in the cluster. That includes all JMS "
-"related service MBeans and all deployed queues and topics. However, "
-"applications that use JMS (e.g., MDBs and other JMS clients) do not need to "
-"be deployed identically across the cluster."
-msgstr ""
-"Para utilizar um serviço HA-JMS failover singleton, você deve configurar os "
-"serviços JMS identicamente em todos os nós no cluster. Isto inclui todos os "
-"serviços MBeans relacionados ao JMS e todos os aplicativos JMS implementados."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1573
-#, fuzzy, no-c-format
-msgid ""
-"The JMS server is configured to persist its data in the <literal>DefaultDS</"
-"literal>. By default, that is the embedded HSQLDB. However, for the HA-JMS "
-"service fail-over to work, the newly started HA-JMS server needs to be able "
-"to find the data persisted by the old server. That's not likely to happen if "
-"the data is persisted in files written by the old servers' HSQLDB. In almost "
-"any cluster environments, all nodes need to persist data against a shared "
-"database. So, the first thing to do before you start clustered JMS is to "
-"setup a shared database for JMS. You need to do the following:"
-msgstr ""
-"O servidor JMS é configurado para continuar com seus dados no "
-"<literal>DefaultDS</literal> como padrão, sendo o HSQLDB incorporado. Na "
-"maioria dos ambientes de cluster, no entanto, todos os nós precisam "
-"continuar com os dados em um banco de dados compartilhado. Portanto, a "
-"primeira coisa a fazer antes de iniciar o JMS em cluster, é instalar um "
-"banco de dados compartilhado para o JMS. Você precisará fazer o seguinte:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1579
-#, no-c-format
-msgid ""
-"Configure <literal>DefaultDS</literal> to point to the database server of "
-"your choice. That is to replace the <literal>deploy/hsqlsb-ds.xml</literal> "
-"file with the <literal>xxx-ds.xml</literal> file in the <literal>docs/"
-"examples/jca</literal> directory, where <literal>xxx</literal> is the name "
-"of the target shared database (e.g., <literal>mysql-ds.xml</literal>)."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1586
-#, no-c-format
-msgid ""
-"Replace the <literal>hsqldb-jdbc2-service.xml</literal> file under the "
-"<literal>server/all/deploy-hasingleton/jms</literal> directory with one "
-"tuned to the specific database. For example if you use MySQL the file is "
-"<literal>mysql-jdbc2-service.xml</literal>. Configuration files for a number "
-"of RDBMS are bundled with the JBoss AS distribution. They can be found under "
-"<literal>docs/examples/jms</literal>."
-msgstr ""
-"Substitua o arquivo <literal>hsqldb-jdbc2-service.xml</literal> sob o "
-"diretório <literal>server/all/deploy-hasingleton/jms</literal> com um "
-"ajustado para o banco de dados específico. Por exemplo: se você utilizar "
-"MySQL, o arquivo será o <literal>mysql-jdbc2-service.xml</literal>. Os "
-"arquivos de configuração para vários RDBMS são reunidos com a distribuição "
-"JBoss AS. Eles podem ser encontrados sob <literal>docs/examples/jms</"
-"literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1595
-#, fuzzy, no-c-format
-msgid ""
-"There is no need to replace the <literal>hsqldb-jdbc-state-service.xml</"
-"literal> file under the <literal>server/all/deploy-hasingleton/jms</literal> "
-"directory. Despite the <literal>hsql</literal> in its name, it works with "
-"all SQL92 compliant databases, including HSQL, MySQL, SQL Server, and more. "
-"It automatically uses the <literal>DefaultDS</literal> for storage, which we "
-"configured above."
-msgstr ""
-"Não há necessidade de substituir o arquivo <literal>hsqldb-jdbc-state-"
-"service.xml</literal> sob o diretório <literal>server/all/deploy-hasingleton/"
-"jms</literal>. Apesar do <literal>hsql</literal> em seu nome, ele funciona "
-"com todos os bancos de dados conforme o SQL92, incluindo os servidores HSQL, "
-"MySQL, SQL entre outros. Ele utiliza automaticamente o <literal>DefaultDS</"
-"literal> para armazenamento, como configurado acima. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1606
-#, fuzzy, no-c-format
-msgid "Non-MDB HA-JMS Clients"
-msgstr "Cliente HA-JMS"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1608
-#, no-c-format
-msgid ""
-"The HA-JMS client is different from regular JMS clients in two important "
-"aspects."
-msgstr "O cliente HA-JMS difere dos clientes JMS comuns em dois aspectos importantes."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1612
-#, no-c-format
-msgid ""
-"The HA-JMS client must look up JMS connection factories as well as queues "
-"and topicsusing HA-JNDI (the default port is 1100). This ensures the factory/"
-"queue/topic can be found no matter which cluster node is running the HA-JMS "
-"server."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1620
-#, no-c-format
-msgid ""
-"If the client is a J2EE component (session bean or web application) running "
-"inside the AS, the lookup via HA-JNDI can be configured using the "
-"component's deployment descriptors: In the standard deployment descriptor "
-"(ejb-jar.xml or web.xml):"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1628
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<resource-ref>\n"
-" <res-ref-name>jms/ConnectionFactory</res-ref-name>\n"
-" <res-type>javax.jms.QueueConnectionFactory</res-type>\n"
-" <res-auth>Container</res-auth>\n"
-"</resource-ref>\n"
-" \n"
-"<resource-ref>\n"
-" <res-ref-name>jms/Queue</res-ref-name>\n"
-" <res-type>javax.jms.Queue</res-type>\n"
-" <res-auth>Container</res-auth>\n"
-"</resource-ref>\n"
-"]]>"
-msgstr ""
-"<![CDATA[\n"
-"<resource-ref>\n"
-" <res-ref-name>jms/ConnectionFactory</res-ref-name>\n"
-" <res-type>javax.jms.QueueConnectionFactory</res-type>\n"
-" <res-auth>Container</res-auth>\n"
-"</resource-ref>\n"
-" \n"
-"<resource-ref>\n"
-" <res-ref-name>jms/Queue</res-ref-name>\n"
-" <res-type>javax.jms.Queue</res-type>\n"
-" <res-auth>Container</res-auth>\n"
-"</resource-ref>\n"
-"]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1630
-#, no-c-format
-msgid "And in the JBoss-specific descriptor (jboss.xml or jboss-web.xml):"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1634
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"<resource-ref>\n"
-" <res-ref-name>jms/ConnectionFactory</res-ref-name>\n"
-" <!-- Use the JMS Resource Adapter, let it deal\n"
-" with knowing where the JMS server is -->\n"
-" <jndi-name>java:/JmsXA</jndi-name>\n"
-" </resource-ref>\n"
-" \n"
-"<resource-ref>\n"
-" <res-ref-name>jms/Queue</res-ref-name>\n"
-" <!-- Use HA-JNDI so we can find the queue on any node -->\n"
-" <jndi-name>jnp://localhost:1100/queue/A</jndi-name>\n"
-"</resource-ref>]]>"
-msgstr ""
-"<![CDATA[ \n"
-"<resource-ref>\n"
-" <res-ref-name>jms/ConnectionFactory</res-ref-name>\n"
-" <!-- Use the JMS Resource Adapter, let it deal\n"
-" with knowing where the JMS server is -->\n"
-" <jndi-name>java:/JmsXA</jndi-name>\n"
-" </resource-ref>\n"
-" \n"
-"<resource-ref>\n"
-" <res-ref-name>jms/Queue</res-ref-name>\n"
-" <!-- Use HA-JNDI so we can find the queue on any node -->\n"
-" <jndi-name>jnp://localhost:1100/queue/A</jndi-name>\n"
-"</resource-ref>]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1639
-#, no-c-format
-msgid ""
-"The HA-JMS client must deal with exceptions that will occur on the JMS "
-"connection if server failover occurs. Unlike, for example, clustered EJB "
-"proxies, the JMS connection object does not include automatic failover "
-"logic. If the HA-JMS service fails over to a different master node, all "
-"client operations on the current connection will fail with a JMSException. "
-"To deal with this:"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1647
-#, no-c-format
-msgid ""
-"If the client is running inside the application server, the client should "
-"obtain the ConnectionFactory by looking up java:/JmsXAin JNDI. This will "
-"find the JBoss JMS Resource Adapter; the resource adapter will handle the "
-"task of detecting server failover and reconnecting to the new server when it "
-"starts."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1651
-#, no-c-format
-msgid ""
-"For clients outside the application server, the best approach is to register "
-"an ExceptionListener with the connection; the listener will get a callback "
-"if there is an exception on the connection. The callback should then handle "
-"the task of closing the old connection and reconnecting. Following is a "
-"example application that continuously sends messages to a queue, handling "
-"any exceptions that occur:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1657
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"package com.test.hajms.client;\n"
-"\n"
-"import javax.naming.InitialContext;\n"
-"import javax.jms.ConnectionFactory;\n"
-"import javax.jms.Destination;\n"
-"import javax.jms.Connection;\n"
-"import javax.jms.Session;\n"
-"import javax.jms.MessageProducer;\n"
-"import javax.jms.Message;\n"
-"import javax.jms.ExceptionListener;\n"
-"import javax.jms.JMSException;\n"
-"import javax.jms.DeliveryMode;\n"
-"\n"
-"import org.apache.commons.logging.Log;\n"
-"import org.apache.commons.logging.LogFactory;\n"
-" \n"
-"public class FailoverJMSClient\n"
-"{\n"
-"private static final Log log = LogFactory.getLog(FailoverJMSClient.class);\n"
-"\n"
-"public static final int NUM_RETRIES = 3;\n"
-"\n"
-"volatile boolean doSend = true;\n"
-"ConnectionFactory connectionFactory;\n"
-"Destination queue;\n"
-"Connection connection;\n"
-"Session session;\n"
-"MessageProducer producer;\n"
-"\n"
-"\n"
-"public static void main(String[] args) throws Exception\n"
-"{\n"
-"FailoverJMSClient jmsClient = new FailoverJMSClient();\n"
-"jmsClient.setUpJMS();\n"
-"jmsClient.sendMessages();\n"
-"}\n"
-"\n"
-"\n"
-"public boolean setUpJMS()\n"
-"{\n"
-"InitialContext ic;\n"
-"try\n"
-"{\n"
-"// assume jndi.properties is configured for HA-JNDI\n"
-"ic = new InitialContext();\n"
-"connectionFactory = (ConnectionFactory)ic.lookup(\"ConnectionFactory\");\n"
-"queue = (Destination)ic.lookup(\"queue/FailoverTestQueue\");\n"
-"connection = connectionFactory.createConnection();\n"
-"try\n"
-"{\n"
-"log.debug(\"Connection created ...\");\n"
-"\n"
-"// KEY - register for exception callbacks\n"
-"connection.setExceptionListener(new ExceptionListenerImpl());\n"
-"\n"
-"session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);\n"
-"log.debug(\"Session created ...\");\n"
-"producer = session.createProducer(queue);\n"
-"\n"
-"producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);\n"
-"log.debug(\"Producer created ...\");\n"
-"\n"
-"return true;\n"
-"}\n"
-"catch (Exception e)\n"
-"{\n"
-"// We failed so close the connection\n"
-"try\n"
-"{\n"
-"connection.close();\n"
-"}\n"
-"catch (JMSException ignored)\n"
-"{\n"
-"// Pointless\n"
-"}\n"
-"// Rethrow the initial problem to where we will log it\n"
-"throw e;\n"
-"} \n"
-"finally\n"
-"{\n"
-"// And close the initial context\n"
-"// We don't want to wait for the garbage collector to close it\n"
-"// otherwise we'll have useless hanging network connections\n"
-"ic.close();\n"
-"}\n"
-"}\n"
-"catch (Exception e)\n"
-"{\n"
-"log.error(\"Error setting up JMS\", e);\n"
-"return false;\n"
-"}\n"
-"}\n"
-"\n"
-"public void sendMessages()\n"
-"{\n"
-"int cnt = 0;\n"
-"while(doSend)\n"
-"{\n"
-"try\n"
-"{\n"
-"Thread.sleep(100);\n"
-"\n"
-"Message m = session.createObjectMessage(new Integer(cnt++));\n"
-"producer.send(m);\n"
-"\n"
-"log.trace(\"message \" + cnt + \" sent\");\n"
-"\n"
-"}\n"
-"catch(Exception e)\n"
-"{\n"
-"cnt--;\n"
-"log.error(e.getMessage());\n"
-"}\n"
-"}\n"
-"}\n"
-"\n"
-"\n"
-"\n"
-"private class ExceptionListenerImpl implements ExceptionListener\n"
-"{\n"
-"public void onException(JMSException e)\n"
-"{\n"
-" \n"
-"for(int i = 0; i < NUM_RETRIES; i++)\n"
-" {\n"
-" log.warn(\"Connection has problems, trying to re-create it, "
-"attempt \" +\n"
-" (i + 1) + \" ...\");\n"
-" \n"
-" try \n"
-" {\n"
-" connection.close(); // unregisters the ExceptionListener\n"
-" }\n"
-" catch(Exception e2) {\n"
-" // I will get an Exception anyway, since the connection to "
-"the \n"
-" //server is broken, but close() frees up resources associated \n"
-" // with the connection\n"
-" }\n"
-" \n"
-" boolean setupOK = setUpJMS();\n"
-" \n"
-" if (setupOK)\n"
-" {\n"
-" log.info(\"Connection re-established\");\n"
-" return;\n"
-" }\n"
-" else\n"
-" {\n"
-" log.warn(\"Re-creating connection failed, retrying ...\");\n"
-" }\n"
-" }\n"
-" \n"
-" log.error(\"Cannot re-establish connection, giving up ...\");\n"
-" doSend = false;\n"
-" }\n"
-" }\n"
-"}\n"
-"]]>"
-msgstr ""
-"<![CDATA[\n"
-"package com.test.hajms.client;\n"
-"\n"
-"import javax.naming.InitialContext;\n"
-"import javax.jms.ConnectionFactory;\n"
-"import javax.jms.Destination;\n"
-"import javax.jms.Connection;\n"
-"import javax.jms.Session;\n"
-"import javax.jms.MessageProducer;\n"
-"import javax.jms.Message;\n"
-"import javax.jms.ExceptionListener;\n"
-"import javax.jms.JMSException;\n"
-"import javax.jms.DeliveryMode;\n"
-"\n"
-"import org.apache.commons.logging.Log;\n"
-"import org.apache.commons.logging.LogFactory;\n"
-" \n"
-"public class FailoverJMSClient\n"
-"{\n"
-"private static final Log log = LogFactory.getLog(FailoverJMSClient.class);\n"
-"\n"
-"public static final int NUM_RETRIES = 3;\n"
-"\n"
-"volatile boolean doSend = true;\n"
-"ConnectionFactory connectionFactory;\n"
-"Destination queue;\n"
-"Connection connection;\n"
-"Session session;\n"
-"MessageProducer producer;\n"
-"\n"
-"\n"
-"public static void main(String[] args) throws Exception\n"
-"{\n"
-"FailoverJMSClient jmsClient = new FailoverJMSClient();\n"
-"jmsClient.setUpJMS();\n"
-"jmsClient.sendMessages();\n"
-"}\n"
-"\n"
-"\n"
-"public boolean setUpJMS()\n"
-"{\n"
-"InitialContext ic;\n"
-"try\n"
-"{\n"
-"// assume jndi.properties is configured for HA-JNDI\n"
-"ic = new InitialContext();\n"
-"connectionFactory = (ConnectionFactory)ic.lookup(\"ConnectionFactory\");\n"
-"queue = (Destination)ic.lookup(\"queue/FailoverTestQueue\");\n"
-"connection = connectionFactory.createConnection();\n"
-"try\n"
-"{\n"
-"log.debug(\"Connection created ...\");\n"
-"\n"
-"// KEY - register for exception callbacks\n"
-"connection.setExceptionListener(new ExceptionListenerImpl());\n"
-"\n"
-"session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);\n"
-"log.debug(\"Session created ...\");\n"
-"producer = session.createProducer(queue);\n"
-"\n"
-"producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);\n"
-"log.debug(\"Producer created ...\");\n"
-"\n"
-"return true;\n"
-"}\n"
-"catch (Exception e)\n"
-"{\n"
-"// We failed so close the connection\n"
-"try\n"
-"{\n"
-"connection.close();\n"
-"}\n"
-"catch (JMSException ignored)\n"
-"{\n"
-"// Pointless\n"
-"}\n"
-"// Rethrow the initial problem to where we will log it\n"
-"throw e;\n"
-"} \n"
-"finally\n"
-"{\n"
-"// And close the initial context\n"
-"// We don't want to wait for the garbage collector to close it\n"
-"// otherwise we'll have useless hanging network connections\n"
-"ic.close();\n"
-"}\n"
-"}\n"
-"catch (Exception e)\n"
-"{\n"
-"log.error(\"Error setting up JMS\", e);\n"
-"return false;\n"
-"}\n"
-"}\n"
-"\n"
-"public void sendMessages()\n"
-"{\n"
-"int cnt = 0;\n"
-"while(doSend)\n"
-"{\n"
-"try\n"
-"{\n"
-"Thread.sleep(100);\n"
-"\n"
-"Message m = session.createObjectMessage(new Integer(cnt++));\n"
-"producer.send(m);\n"
-"\n"
-"log.trace(\"message \" + cnt + \" sent\");\n"
-"\n"
-"}\n"
-"catch(Exception e)\n"
-"{\n"
-"cnt--;\n"
-"log.error(e.getMessage());\n"
-"}\n"
-"}\n"
-"}\n"
-"\n"
-"\n"
-"\n"
-"private class ExceptionListenerImpl implements ExceptionListener\n"
-"{\n"
-"public void onException(JMSException e)\n"
-"{\n"
-" \n"
-"for(int i = 0; i < NUM_RETRIES; i++)\n"
-" {\n"
-" log.warn(\"Connection has problems, trying to re-create it, "
-"attempt \" +\n"
-" (i + 1) + \" ...\");\n"
-" \n"
-" try \n"
-" {\n"
-" connection.close(); // unregisters the ExceptionListener\n"
-" }\n"
-" catch(Exception e2) {\n"
-" // I will get an Exception anyway, since the connection to "
-"the \n"
-" //server is broken, but close() frees up resources associated \n"
-" // with the connection\n"
-" }\n"
-" \n"
-" boolean setupOK = setUpJMS();\n"
-" \n"
-" if (setupOK)\n"
-" {\n"
-" log.info(\"Connection re-established\");\n"
-" return;\n"
-" }\n"
-" else\n"
-" {\n"
-" log.warn(\"Re-creating connection failed, retrying ...\");\n"
-" }\n"
-" }\n"
-" \n"
-" log.error(\"Cannot re-establish connection, giving up ...\");\n"
-" doSend = false;\n"
-" }\n"
-" }\n"
-"}\n"
-"]]>"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1661
-#, no-c-format
-msgid "MDBs and HA-JMS Failover"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1662
-#, no-c-format
-msgid ""
-"When you deploy an MDB in JBoss, JBoss' MDB container handles for you all "
-"issues associated with finding the cluster singleton HA-JMS server and with "
-"reconnecting to it if it fails over."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1672
-#, no-c-format
-msgid "Load Balanced HA-JMS MDBs"
-msgstr "Carga balanceada HA-JMS MDBs"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1673
-#, no-c-format
-msgid ""
-"While the HA-JMS queues and topics only run on a single node at a time, MDBs "
-"on multiple nodes can receive and process messages from the HA-JMS master "
-"node. The contested queues and topics result in load balancing behavior for "
-"MDBs. To enable loading balancing for MDBs, you can specify a receiver for "
-"the queue. The receiver records which node is waiting for a message and in "
-"which order the messages should be processed. JBoss provides three receiver "
-"implementations."
-msgstr ""
-"Embora as filas HA-JMS e tópicos somente rodem em um nó por vez, os MDBs em "
-"nós múltiplos podem receber e processar mensagens recebidas do nó master HA-"
-"JMS. As filas e tópicos disputados, resultam em um comportamento de "
-"balanceamento de carga para MDBs. Para habilitar o balanceamento de carga "
-"para MDBs, você poderá especificar um receptor para esta fila. O receptor "
-"grava qual nó está em espera pela mensagem e em qual ordem as mensagens "
-"devem ser processadas. o JBoss provê três implementações de receptores. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1680
-#, no-c-format
-msgid ""
-"The <literal>org.jboss.mq.server.ReceiversImpl</literal> is the default "
-"implementation using a <literal>HashSet</literal>."
-msgstr ""
-"O <literal>org.jboss.mq.server.ReceiversImpl</literal> é a implementação "
-"padrão, utilizando um <literal>HashSet</literal>. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1684
-#, fuzzy, no-c-format
-msgid ""
-"The <literal>org.jboss.mq.server.ReceiversImplArrayList</literal> is the "
-"implementation using an <literal>ArrayList</literal>."
-msgstr ""
-"O <literal>org.jboss.mq.server.ReceiversImplArrayList</literal> é a "
-"implementação que utiliza um <literal>ArrayList</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1688
-#, no-c-format
-msgid ""
-"The <literal>org.jboss.mq.server.ReceiversImplLinkedList</literal> is the "
-"implementation using a <literal>LinkedList</literal>."
-msgstr ""
-"O <literal>org.jboss.mq.server.ReceiversImplLinkedList</literal> é a "
-"implementação que utiliza um <literal>LinkedList</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1692
-#, no-c-format
-msgid ""
-"You can specify the receiver implementation class name as an attribute in "
-"the MBean that defines the permanent JMS <literal>Queue</literal> or "
-"<literal>DestinationManager</literal> on each node. For best load balancing "
-"performance, we suggest you to use the <literal>ReceiversImplArrayList</"
-"literal> or <literal>ReceiversImplLinkedList</literal> implementations due "
-"to an undesirable implementation detail of <literal>HashSet</literal> in the "
-"JVM."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1704
-#, no-c-format
-msgid "JBossCache and JGroups Services"
-msgstr "JBoss Cache e Serviços JGroups."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1705
-#, fuzzy, 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, HTTP "
-"session replication etc.)."
-msgstr ""
-"JGroups e o Cache JBoss oferecem comunicações subjacentes, replicação de nós "
-"e serviços de cache para clusters de JBoss AS. Estes serviços são "
-"configurados como os MBeans. Existe um conjunto de MBeans de JBossCache e "
-"JGroups para cada tipo de aplicativos em cluster (ex.: a Sessão com Estado "
-"EJBs, a entidade EJBs distribuídas, etc.)."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1709
-#, 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 ""
-"O JBoss AS navega com um conjunto razoável de configurações MBean JGroups e "
-"JBossCache padrão. A maioria dos aplicativos funcionam bem com as "
-"configurações MBean padrão. Você só precisa ajustá-los quando estiver "
-"implementando um aplicativo que possui uma rede de trabalho especial ou "
-"requisição de bom desempenho."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1714
-#, no-c-format
-msgid "JGroups Configuration"
-msgstr "Configuração JGroups"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1715
-#, 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=\"jbosscache-JGroupsStack.fig\"/> shows the protocol "
-"stack in JGroups."
-msgstr ""
-"A moldura do JGroups oferece serviços que possibilitam comunicações ponto a "
-"ponto entre os nós de um cluster. É construído no topo de uma pilha de "
-"protocolos de comunicação de rede de trabalho que provê transporte, "
-"descoberta, confiabilidade e detecção de falhas e serviços de gerenciamento "
-"de propriedade do cluster. <xref linkend=\"jbosscache-JGroupsStack.fig\"/> "
-"mostra a pilha de protocolos em JGroups."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1719
-#, no-c-format
-msgid "Protocol stack in JGroups"
-msgstr "Pilha de prolocolos em JGroups"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1726
-#, 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 ""
-"As configurações geralmente aparecem como funções aninhadas nos serviços "
-"MBean relacionados ao cluster, tais como a função <literal>PartitionConfig</"
-"literal>no Mbean <literal>ClusterPartition</literal> ou a função "
-"<literal>ClusterConfig</literal> no MBean <literal>TreeCache</literal>. Você "
-"pode configurar o comportamente e propriedades de cada protocolo em JGroups "
-"através daquelas funções MBean. Segue abaixo um exemplo de configuração "
-"JGroups no MBean <literal>ClusterPartition</literal>."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1731
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<mbean code=\"org.jboss.ha.framework.server.ClusterPartition\"\n"
-" name=\"jboss:service=${jboss.partition.name:DefaultPartition}\">\n"
-" \n"
-" ... ...\n"
-" \n"
-" <attribute name=\"PartitionConfig\">\n"
-" <Config>\n"
-" \n"
-" <UDP mcast_addr=\"${jboss.partition."
-"udpGroup:228.1.2.3}\" \n"
-" mcast_port=\"${jboss.hapartition."
-"mcast_port:45566}\"\n"
-" tos=\"8\"\n"
-" ucast_recv_buf_size=\"20000000\"\n"
-" ucast_send_buf_size=\"640000\"\n"
-" mcast_recv_buf_size=\"25000000\"\n"
-" mcast_send_buf_size=\"640000\"\n"
-" loopback=\"false\"\n"
-" discard_incompatible_packets=\"true\"\n"
-" enable_bundling=\"false\"\n"
-" max_bundle_size=\"64000\"\n"
-" max_bundle_timeout=\"30\"\n"
-" use_incoming_packet_handler=\"true\"\n"
-" use_outgoing_packet_handler=\"false\"\n"
-" ip_ttl=\"${jgroups.udp.ip_ttl:2}\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>\n"
-" \n"
-" <PING timeout=\"2000\"\n"
-" down_thread=\"false\" up_thread=\"false\" "
-"num_initial_members=\"3\"/>\n"
-" \n"
-" <MERGE2 max_interval=\"100000\"\n"
-" down_thread=\"false\" up_thread=\"false\" "
-"min_interval=\"20000\"/>\n"
-" <FD_SOCK down_thread=\"false\" up_thread=\"false\"/"
-">\n"
-" \n"
-" <FD timeout=\"10000\" max_tries=\"5\" \n"
-" down_thread=\"false\" up_thread=\"false\" shun="
-"\"true\"/>\n"
-" <VERIFY_SUSPECT timeout=\"1500\" down_thread=\"false"
-"\" up_thread=\"false\"/>\n"
-" <pbcast.NAKACK max_xmit_size=\"60000\"\n"
-" use_mcast_xmit=\"false\" gc_lag=\"0"
-"\"\n"
-" retransmit_timeout="
-"\"300,600,1200,2400,4800\"\n"
-" down_thread=\"false\" up_thread="
-"\"false\"\n"
-" discard_delivered_msgs=\"true\"/>\n"
-" <UNICAST timeout=\"300,600,1200,2400,3600\"\n"
-" down_thread=\"false\" up_thread=\"false\"/"
-">\n"
-" <pbcast.STABLE stability_delay=\"1000\" "
-"desired_avg_gossip=\"50000\"\n"
-" down_thread=\"false\" up_thread="
-"\"false\"\n"
-" max_bytes=\"400000\"/>\n"
-" <pbcast.GMS print_local_addr=\"true\" join_timeout="
-"\"3000\"\n"
-" down_thread=\"false\" up_thread=\"false"
-"\"\n"
-" join_retry_timeout=\"2000\" shun=\"true"
-"\"\n"
-" view_bundling=\"true\"/>\n"
-" <FRAG2 frag_size=\"60000\" down_thread=\"false\" "
-"up_thread=\"false\"/>\n"
-" <pbcast.STATE_TRANSFER down_thread=\"false\" \n"
-" up_thread=\"false\" "
-"use_flush=\"false\"/>\n"
-" </Config>\n"
-" </attribute>\n"
-"</mbean> ]]>"
-msgstr ""
-"<![CDATA[\n"
-"<mbean code=\"org.jboss.ha.framework.server.ClusterPartition\"\n"
-" name=\"jboss:service=${jboss.partition.name:DefaultPartition}\">\n"
-" \n"
-" ... ...\n"
-" \n"
-" <attribute name=\"PartitionConfig\">\n"
-" <Config>\n"
-" \n"
-" <UDP mcast_addr=\"${jboss.partition."
-"udpGroup:228.1.2.3}\" \n"
-" mcast_port=\"${jboss.hapartition."
-"mcast_port:45566}\"\n"
-" tos=\"8\"\n"
-" ucast_recv_buf_size=\"20000000\"\n"
-" ucast_send_buf_size=\"640000\"\n"
-" mcast_recv_buf_size=\"25000000\"\n"
-" mcast_send_buf_size=\"640000\"\n"
-" loopback=\"false\"\n"
-" discard_incompatible_packets=\"true\"\n"
-" enable_bundling=\"false\"\n"
-" max_bundle_size=\"64000\"\n"
-" max_bundle_timeout=\"30\"\n"
-" use_incoming_packet_handler=\"true\"\n"
-" use_outgoing_packet_handler=\"false\"\n"
-" ip_ttl=\"${jgroups.udp.ip_ttl:2}\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>\n"
-" \n"
-" <PING timeout=\"2000\"\n"
-" down_thread=\"false\" up_thread=\"false\" "
-"num_initial_members=\"3\"/>\n"
-" \n"
-" <MERGE2 max_interval=\"100000\"\n"
-" down_thread=\"false\" up_thread=\"false\" "
-"min_interval=\"20000\"/>\n"
-" <FD_SOCK down_thread=\"false\" up_thread=\"false\"/"
-">\n"
-" \n"
-" <FD timeout=\"10000\" max_tries=\"5\" \n"
-" down_thread=\"false\" up_thread=\"false\" shun="
-"\"true\"/>\n"
-" <VERIFY_SUSPECT timeout=\"1500\" down_thread=\"false"
-"\" up_thread=\"false\"/>\n"
-" <pbcast.NAKACK max_xmit_size=\"60000\"\n"
-" use_mcast_xmit=\"false\" gc_lag=\"0"
-"\"\n"
-" retransmit_timeout="
-"\"300,600,1200,2400,4800\"\n"
-" down_thread=\"false\" up_thread="
-"\"false\"\n"
-" discard_delivered_msgs=\"true\"/>\n"
-" <UNICAST timeout=\"300,600,1200,2400,3600\"\n"
-" down_thread=\"false\" up_thread=\"false\"/"
-">\n"
-" <pbcast.STABLE stability_delay=\"1000\" "
-"desired_avg_gossip=\"50000\"\n"
-" down_thread=\"false\" up_thread="
-"\"false\"\n"
-" max_bytes=\"400000\"/>\n"
-" <pbcast.GMS print_local_addr=\"true\" join_timeout="
-"\"3000\"\n"
-" down_thread=\"false\" up_thread=\"false"
-"\"\n"
-" join_retry_timeout=\"2000\" shun=\"true"
-"\"\n"
-" view_bundling=\"true\"/>\n"
-" <FRAG2 frag_size=\"60000\" down_thread=\"false\" "
-"up_thread=\"false\"/>\n"
-" <pbcast.STATE_TRANSFER down_thread=\"false\" \n"
-" up_thread=\"false\" "
-"use_flush=\"false\"/>\n"
-" </Config>\n"
-" </attribute>\n"
-"</mbean> ]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1732
-#, no-c-format
-msgid ""
-"All the JGroups configuration data is contained in the <Config> "
-"element under the JGroups config MBean attribute. This information is used "
-"to configure a JGroups Channel; the Channel is conceptually similar to a "
-"socket, and manages communication between peers in a cluster. Each element "
-"inside the <Config> element defines a particular JGroups Protocol; "
-"each Protocol performs one function, and the combination of those functions "
-"is what defines the characteristics of the overall Channel. In the next "
-"several sections, we will dig into the commonly used protocols and their "
-"options and explain exactly what they mean."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1737
-#, fuzzy, no-c-format
-msgid "Common Configuration Properties"
-msgstr "Outras Opções de Configuração"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1738
-#, no-c-format
-msgid ""
-"The following common properties are exposed by all of the JGroups protocols "
-"discussed below:"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1742
-#, no-c-format
-msgid ""
-"<literal>down_thread</literal> whether the protocol should create an "
-"internal queue and a queue processing thread (aka the down_thread) for "
-"messages passed down from higher layers. The higher layer could be another "
-"protocol higher in the stack, or the application itself, if the protocol is "
-"the top one on the stack. If true (the default), when a message is passed "
-"down from a higher layer, the calling thread places the message in the "
-"protocol's queue, and then returns immediately. The protocol's down_thread "
-"is responsible for reading messages off the queue, doing whatever protocol-"
-"specific processing is required, and passing the message on to the next "
-"protocol in the stack."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1746
-#, no-c-format
-msgid ""
-"<literal>up_thread</literal> is conceptually similar to down_thread, but "
-"here the queue and thread are for messages received from lower layers in the "
-"protocol stack."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1750
-#, no-c-format
-msgid ""
-"Generally speaking, <literal>up_thread</literal> and <literal>down_thread</"
-"literal> should be set to false."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1756
-#, no-c-format
-msgid "Transport Protocols"
-msgstr "Protocolos de Transporte"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1757
-#, 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 ""
-"O protocolo de transporte envia mensagens a partir de um nó de cluster para "
-"outro (unicast) ou a partir de um nó de cluster para outros nós em cluster "
-"(multicast). O JGroups oferece suporte para UDP, TCP e TÚNEL como protocolo "
-"de transporte. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1761
-#, 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 ""
-"Os elementos <literal>UDP</literal>, <literal>TCP</literal>, e "
-"<literal>TUNNEL</literal> são exclusivos mutuamente. Você só pode ter um "
-"protocolo de transporte em cada elemento JGroups <literal>Config</literal> ."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1766
-#, no-c-format
-msgid "UDP configuration"
-msgstr "Configuração UDP"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1767
-#, 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 ""
-"Prefere-se o UDP como protocolo para JGroups. Ele utiliza multicast ou "
-"unicasts múltiplos para enviar e receber mensagens. Se você escolher o UDP "
-"como protocolo de transporte para seu serviço de cluster, você irá precisar "
-"configurá-lo no sub-elemento no elemento JGroups <literal>Config</literal> . "
-"Segue aqui um exemplo."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1771
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<UDP mcast_addr=\"${jboss.partition.udpGroup:228.1.2.3}\" \n"
-" mcast_port=\"${jboss.hapartition.mcast_port:45566}\"\n"
-" tos=\"8\"\n"
-" ucast_recv_buf_size=\"20000000\"\n"
-" ucast_send_buf_size=\"640000\"\n"
-" mcast_recv_buf_size=\"25000000\"\n"
-" mcast_send_buf_size=\"640000\"\n"
-" loopback=\"false\"\n"
-" discard_incompatible_packets=\"true\"\n"
-" enable_bundling=\"false\"\n"
-" max_bundle_size=\"64000\"\n"
-" max_bundle_timeout=\"30\"\n"
-" use_incoming_packet_handler=\"true\"\n"
-" use_outgoing_packet_handler=\"false\"\n"
-" ip_ttl=\"${jgroups.udp.ip_ttl:2}\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>]]>"
-msgstr ""
-"<![CDATA[\n"
-"<UDP mcast_addr=\"${jboss.partition.udpGroup:228.1.2.3}\" \n"
-" mcast_port=\"${jboss.hapartition.mcast_port:45566}\"\n"
-" tos=\"8\"\n"
-" ucast_recv_buf_size=\"20000000\"\n"
-" ucast_send_buf_size=\"640000\"\n"
-" mcast_recv_buf_size=\"25000000\"\n"
-" mcast_send_buf_size=\"640000\"\n"
-" loopback=\"false\"\n"
-" discard_incompatible_packets=\"true\"\n"
-" enable_bundling=\"false\"\n"
-" max_bundle_size=\"64000\"\n"
-" max_bundle_timeout=\"30\"\n"
-" use_incoming_packet_handler=\"true\"\n"
-" use_outgoing_packet_handler=\"false\"\n"
-" ip_ttl=\"${jgroups.udp.ip_ttl:2}\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1774
-#, no-c-format
-msgid "The available attributes in the above JGroups configuration are listed below."
-msgstr ""
-"As funções disponíveis na configuração de JGroups acima, estão listadas "
-"abaixo:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1777
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ip_mcast</emphasis> specifies whether or not to use "
-"IP multicasting. The default is <literal>true</literal>. If set to false, it "
-"will send n unicast packets rather than 1 multicast packet. Either way, "
-"packets are UDP datagrams."
-msgstr ""
-"<emphasis role=\"bold\">ip_mcast</emphasis> especifica se irá utilizar ou "
-"não o IP multicasting. O padrão é <literal>true</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1782
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mcast_addr</emphasis> specifies the multicast "
-"address (class D) for joining a group (i.e., the cluster). If omitted, the "
-"default is <literal>228.8.8.8 </literal>."
-msgstr ""
-"<emphasis role=\"bold\">mcast_addr</emphasis> especifica o endereço de "
-"multicast (classe D) para se unir a um grupo (ou seja, ao cluster). O padrão "
-"é <literal>228.8.8.8</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1787
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mcast_port</emphasis> specifies the multicast port "
-"number. If omitted, the default is <literal>45566</literal>."
-msgstr ""
-"<emphasis role=\"bold\">mcast_port</emphasis> especifica o número da porta "
-"multicast. O padrão é <literal>45566</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1791
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">bind_addr</emphasis> specifies the interface on "
-"which to receive and send multicasts (uses the <literal>-Djgroups."
-"bind_address</literal> system property, if present). If you have a "
-"multihomed machine, set the <literal>bind_addr</literal> attribute or system "
-"property to the appropriate NIC IP address. By default, system property "
-"setting takes priority over XML attribute unless -Djgroups.ignore.bind_addr "
-"system property is set."
-msgstr ""
-"<emphasis role=\"bold\">bind_addr</emphasis> especifica a interface a "
-"receber ou enviar multicasts (utiliza a propriedade do sistema <literal>bind."
-"address</literal>, caso esteja presente). Se você tiver uma máquina com "
-"endereços múltiplos, instale a função <literal>bind_addr</literal> para o "
-"endereço NIC IP apropriado. Ignore caso a propriedade <literal>ignore.bind."
-"address</literal> seja verdadeira. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1794
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">receive_on_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> especifica se o nó "
-"deve ser ouvido em todas as interfaces para multicast. O padrão é "
-"<literal>false</literal>. Ele cancela a propriedade <literal>bind_addr</"
-"literal> para receber multicasts. No entanto, <literal>bind_addr</literal> "
-"ainda é utilizado para enviar multicast. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1799
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">send_on_all_interfaces</emphasis> specifies whether "
-"this node send UDP packets via all the NICs if you have a multi NIC machine. "
-"This means that the same multicast message is sent N times, so use with care."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1804
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">receive_interfaces</emphasis> specifies a list of of "
-"interfaces to receive multicasts on. The multicast receive socket will "
-"listen on all of these interfaces. This is a comma-separated list of IP "
-"addresses or interface names. E.g. \"<literal>192.168.5.1,eth1,127.0.0.1</"
-"literal>\"."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1810
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ip_ttl</emphasis> specifies time-to-live for IP "
-"Multicast packets. TTL is the commonly used term in multicast networking, "
-"but is actually something of a misnomer, since the value here refers to how "
-"many network hops a packet will be allowed to travel before networking "
-"equipment will drop it."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1814
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">use_incoming_packet_handler</emphasis> specifies "
-"whether to use a separate thread to process incoming messages. Sometimes "
-"receivers are overloaded (they have to handle de-serialization etc). Packet "
-"handler is a separate thread taking care of de-serialization, receiver thread"
-"(s) simply put packet in queue and return immediately. Setting this to true "
-"adds one more thread. The default is <literal>true</literal>."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1817
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">use_outgoing_packet_handler</emphasis> specifies "
-"whether to use a separate thread to process outgoing messages. The default "
-"is false."
-msgstr ""
-"<emphasis role=\"bold\">use_outgoing_packet_handler</emphasis> especifica "
-"quando utilizar uma discussão separadamente para processar as mensagens "
-"enviadas. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1820
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">enable_bundling</emphasis> specifies whether to "
-"enable message 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> especifica quando "
-"habilitar a união. Caso seja <literal>true</literal>, o nó enfileira "
-"mensagens de saída até que os bytes <literal>max_bundle_size</literal> "
-"tenham-se acumulado, ou os milisegundos <literal>max_bundle_time</literal> "
-"tenham se passado, qualquer um que acontecer primeiro. Depois disso, reúne "
-"as mensagens enfileiradas em uma mensagem grande e as envia. As mensagens "
-"não estão agrupadas no receptor. O padrão é <literal>false</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1828
-#, fuzzy, 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. The default is <literal>false</literal>"
-msgstr ""
-"<emphasis role=\"bold\">loopback</emphasis> especifica quando realizar um "
-"loop nas mensagens de saída e fazer o back up da pilha. No módulo "
-"<literal>unicast</literal>, as mensagens são enviadas para si mesmas. No "
-"módulo <literal>mcast</literal> , é enviado uma cópia da mensagem mcast. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1833
-#, fuzzy, 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. The default is <literal>false</"
-"literal>"
-msgstr ""
-"<emphasis role=\"bold\">discard_incompatibe_packets</emphasis> especifica "
-"quando descartar pacotes de versões JGroups distintas. Cada mensagem no "
-"cluster está marcada com uma versão JGroup. Quando uma mensagem de uma "
-"versão diferente do JGroup for recebida, ela será descartada caso esteja "
-"configurada para verdadeiro, caso contrário aparecerá um aviso. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1839
-#, 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> define, recebe e envia "
-"tamanhos de buffer. Recomenda-se que tenha um tamanho de buffer receptor "
-"grande, para que os pacotes caiam menos, devido ao estouro do buffer. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1845
-#, no-c-format
-msgid ""
-"<literal>tos</literal> specifies traffic class for sending unicast and "
-"multicast datagrams."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1851
-#, 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 ""
-"Nas máquinas com Windows 2000, devido ao media sense ter sido quebrado com "
-"multicast (até mesmo após desabilitar o media sense) você irá precisar "
-"configurar a função de protocolo do UDP <literal>loopback</literal> para "
-"<literal>true</literal>"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1859
-#, no-c-format
-msgid "TCP configuration"
-msgstr "Configuração TCP"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1860
-#, fuzzy, 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. 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 ""
-"Como forma alternativa, um cluster baseado em JGroup, também pode funcionar "
-"com conexões TCP. O TCP. Comparado ao UDP, o TCP gera mais tráfego na rede "
-"de trabalho quando o tamanho do cluster aumenta, mas é mais confiável. O TCP "
-"é um protocolo unicast de origem. Para enviar mensagens multicast, o JGroup "
-"utiliza unicasts TCP múltiplos. Para utilizar o TCP como um protocolo de "
-"transporte, você deve definir um elemento <literal>TCP</literal> no elemento "
-"JGroups <literal>Config</literal> . Segue aqui um exemplo do elemento "
-"<literal>TCP</literal>. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1866
-#, no-c-format
-msgid ""
-"<TCP start_port=\"7800\"\n"
-" bind_addr=\"192.168.5.1\"\n"
-" loopback=\"true\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-msgstr ""
-"<TCP start_port=\"7800\"\n"
-" bind_addr=\"192.168.5.1\"\n"
-" loopback=\"true\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1867
-#, no-c-format
-msgid "Below are the attributes available in the <literal>TCP</literal> element."
-msgstr "Segue abaixo, as funções disponíveis no elemento <literal>TCP</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1870
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">bind_addr</emphasis> specifies the binding address. "
-"It can also be set with the <literal>-Djgroups.bind_address</literal> "
-"command line option at server startup."
-msgstr ""
-"<emphasis role=\"bold\">bind_addr</emphasis> especifica o endereço de "
-"vinculação. Também pode ser configurado com a opção da linha de comando "
-"<literal>-Dbind.address</literal> ao iniciar o servidor. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1875
-#, 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. If no <literal>end_port</literal> is "
-"provided or <literal>end_port < start_port</literal> then there is no "
-"upper limit on the port range. If <literal>start_port == end_port</literal>, "
-"then we force JGroups to use the given port (start fails if port is not "
-"available). The default is 7800. If set to 0, then the operating system will "
-"pick a port. Please, bear in mind that setting it to 0 will work only if we "
-"use MPING or TCPGOSSIP as discovery protocol because <literal>TCCPING</"
-"literal> requires listing the nodes and their corresponding ports."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1881
-#, fuzzy, 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. The default is false."
-msgstr ""
-"<emphasis role=\"bold\">loopback</emphasis> especifica quando realizar um "
-"loop nas mensagens de saída e fazer o back up da pilha. No módulo "
-"<literal>unicast</literal>, as mensagens são enviadas para si mesmas. No "
-"módulo <literal>mcast</literal> , é enviado uma cópia da mensagem mcast. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1886
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">recv_buf_size, send_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> define, recebe e envia "
-"tamanhos de buffer. Recomenda-se que tenha um tamanho de buffer receptor "
-"grande, para que os pacotes caiam menos, devido ao estouro do buffer. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1889
-#, 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> especifica o tempo (em "
-"milisegundos) que a conexão pode ser fechada pelo REAPER caso nenhum tráfego "
-"tenha sido recebido. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1894
-#, fuzzy, 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. By default, "
-"reaper_interval is 0, which means no reaper."
-msgstr ""
-"<emphasis role=\"bold\">reaper_interval</emphasis> especifica o intervalo "
-"(em milisegundos) para rodar o reaper. Caso ambos os valores sejam 0, o "
-"reaping não será realizado. Caso o valor seja > 0, o reaping será "
-"habilitado."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1899
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">sock_conn_timeout</emphasis> specifies max time in "
-"millis for a socket creation. When doing the initial discovery, and a peer "
-"hangs, don't wait forever but go on after the timeout to ping other members. "
-"Reduces chances of *not* finding any members at all. The default is 2000."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1902
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">use_send_queues</emphasis> specifies whether to use "
-"separate send queues for each connection. This prevents blocking on write if "
-"the peer hangs. The default is true."
-msgstr ""
-"<emphasis role=\"bold\">use_incoming_packet_handler</emphasis> especifica "
-"quando utilizar uma discussão separadamente para processar as mensagens "
-"recebidas. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1905
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">external_addr</emphasis> specifies external IP "
-"address to broadcast to other group members (if different to local address). "
-"This is useful when you have use (Network Address Translation) NAT, e.g. a "
-"node on a private network, behind a firewall, but you can only route to it "
-"via an externally visible address, which is different from the local address "
-"it is bound to. Therefore, the node can be configured to broadcast its "
-"external address, while still able to bind to the local one. This avoids "
-"having to use the TUNNEL protocol, (and hence a requirement for a central "
-"gossip router) because nodes outside the firewall can still route to the "
-"node inside the firewall, but only on its external address. Without setting "
-"the external_addr, the node behind the firewall will broadcast its private "
-"address to the other nodes which will not be able to route to it."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1908
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">skip_suspected_members</emphasis> specifies whether "
-"unicast messages should not be sent to suspected members. The default is "
-"true."
-msgstr ""
-"<emphasis role=\"bold\">ip_mcast</emphasis> especifica se irá utilizar ou "
-"não o IP multicasting. O padrão é <literal>true</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1911
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">tcp_nodelay</emphasis> specifies TCP_NODELAY. TCP by "
-"default nagles messages, that is, conceptually, smaller messages are bundled "
-"into larger ones. If we want to invoke synchronous cluster method calls, "
-"then we need to disable nagling in addition to disabling message bundling "
-"(by setting <literal>enable_bundling</literal> to false). Nagling is "
-"disabled by setting <literal>tcp_nodelay</literal> to true. The default is "
-"false."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1923
-#, no-c-format
-msgid "TUNNEL configuration"
-msgstr "Configuração de TÚNEL"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1924
-#, fuzzy, 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 as most firewalls do not permit outside hosts to initiate a TCP "
-"connection to a host inside the firewall. The TUNNEL configuration is "
-"defined in the TUNNEL element in the JGroups Config element. Here is an "
-"example.."
-msgstr ""
-"O protocolo de TÚNEL utiliza um roteador externo para enviar mensagens. O "
-"roteador externo é mais conhecido como um <literal>GossipRouter</literal>. "
-"Cada nó precisa se registrar com o roteador. Todas as mensagens são enviadas "
-"para o roteador e encaminhadas para seus destinos. A abordagem do TÚNEL pode "
-"ser utilizada para estabelecer comunicação entre os nós atrás de firewalls. "
-"Um nó pode estabelecer uma conexão TCP para o GossipRouter através do "
-"firewall ( você pode utilizar a porta 80). A mesma conexão é usada pelo "
-"roteador para enviar mensagens ao nó atrás do firewall. A configuração do "
-"TÚNEL está definida no elemento <literal>TUNNEL</literal> no elemento do "
-"JGroups <literal>Config</literal>. Segue aqui um exemplo:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1929
-#, no-c-format
-msgid ""
-"<TUNNEL router_port=\"12001\"\n"
-" router_host=\"192.168.5.1\"\n"
-" down_thread=\"false\" up_thread=\"false/>"
-msgstr ""
-"<TUNNEL router_port=\"12001\"\n"
-" router_host=\"192.168.5.1\"\n"
-" down_thread=\"false\" up_thread=\"false/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1932
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>TUNNEL</literal> element are listed "
-"below."
-msgstr ""
-"As funções disponíveis no elemento <literal>TUNNEL</literal> estão listadas "
-"abaixo:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1935
-#, 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> especifica a máquina na qual "
-"o GossipRouper está rodando. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1939
-#, 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> especifica a porta na qual o "
-"GossipRouper está rodando. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1943
-#, 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> especifica quando as mensagens "
-"do loop efetuam o backup na pilha."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1954
-#, no-c-format
-msgid "Discovery Protocols"
-msgstr "Protocolos de Descoberta"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1955
-#, fuzzy, no-c-format
-msgid ""
-"The cluster needs 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. Discovery protocols are used to discover active nodes in the "
-"cluster and detect the oldest member of the cluster, which is the "
-"coordinator. 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=\"jbosscache-jgroups-other-"
-"gms\"/>) admits it into the group."
-msgstr ""
-"O cluster precisa sempre manter uma lista dos nós membros atuais, assim o "
-"balanceador de carga e o interceptador do cliente saberão como rotear suas "
-"solicitações. Os protocolos de descoberta são utilizados para descobrir nós "
-"ativos no cluster. Todos os nós iniciais são descobertos quando um cluster "
-"inicia. Quando um novo nó se une ao cluster mais tarde, ele só é descoberto "
-"depois que o protocolo de propriedade do grupo (GMS, veja <xref linkend="
-"\"jbosscache-jgroups-other-gms\"/>) o aceita dentro do grupo. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1959
-#, fuzzy, 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. These are also configured as sub-elements in the JGroups MBean "
-"<literal>Config</literal> element."
-msgstr ""
-"Como os protocolos de descoberta ficam no topo do protocolo de transporte, "
-"você poderá escolher utilizar protocolos de descoberta diferentes em seu "
-"protocolo de transporte. Os protocolos de descoberta são também configurados "
-"como sub-elementos no elemento MBean JGroups <literal>Config</literal>."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1965
-#, no-c-format
-msgid "PING"
-msgstr "PING"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1966
-#, no-c-format
-msgid ""
-"PING is a discovery protocol that works by either multicasting PING requests "
-"to an IP multicast address or connecting to a gossip router. As such, PING "
-"normally sits on top of the UDP or TUNNEL transport protocols. Each node "
-"responds with a packet {C, A}, where C=coordinator's address and A=own "
-"address. After timeout milliseconds or num_initial_members replies, the "
-"joiner determines the coordinator from the responses, and sends a JOIN "
-"request to it (handled by). If nobody responds, we assume we are the first "
-"member of a group."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1969
-#, no-c-format
-msgid "Here is an example PING configuration for IP multicast."
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1973
-#, no-c-format
-msgid ""
-"<PING timeout=\"2000\"\n"
-" num_initial_members=\"2\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-msgstr ""
-"<PING timeout=\"2000\"\n"
-" num_initial_members=\"2\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1974
-#, no-c-format
-msgid "Here is another example PING configuration for contacting a Gossip Router."
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1976
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"<PING gossip_host=\"localhost\"\n"
-" gossip_port=\"1234\"\n"
-" timeout=\"3000\" \n"
-" num_initial_members=\"3\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>]]>"
-msgstr ""
-"<![CDATA[ \n"
-"<PING gossip_host=\"localhost\"\n"
-" gossip_port=\"1234\"\n"
-" timeout=\"3000\" \n"
-" num_initial_members=\"3\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1981
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>PING</literal> element are listed "
-"below."
-msgstr ""
-"As funções disponíveis no elemento <literal>PING</literal> estão listadas "
-"abaixo:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1984
-#: Clustering_Guide_Introduction.xml:2032
-#: Clustering_Guide_Introduction.xml:2061
-#: Clustering_Guide_Introduction.xml:2095
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">timeout</emphasis> specifies the maximum number of "
-"milliseconds to wait for any responses. The default is 3000."
-msgstr ""
-"<emphasis role=\"bold\">timeout</emphasis> especifica o número máximo de "
-"milisegundos para aguardar por qualquer resposta. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1988
-#: Clustering_Guide_Introduction.xml:2036
-#: Clustering_Guide_Introduction.xml:2065
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">num_initial_members</emphasis> specifies the maximum "
-"number of responses to wait for unless timeout has expired. The default is 2."
-msgstr ""
-"<emphasis role=\"bold\">num_initial_members</emphasis> especifica o número "
-"máximo de respostas a receber. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1992
-#, 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> especifica a máquina na qual "
-"o GossipRouter está rodando. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1996
-#, 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> especifica a porta na qual o "
-"GossipRouter está ouvindo. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2000
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">gossip_refresh</emphasis> specifies the interval (in "
-"milliseconds) for the lease from the GossipRouter. The default is 20000."
-msgstr ""
-"<emphasis role=\"bold\">gossip_refresh</emphasis> especifica o intervalo (em "
-"milisegundos) para o empréstimo do GossipRouter. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2004
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">initial_hosts</emphasis> is a comma-seperated list "
-"of addresses (e.g., <literal>host1[12345],host2[23456]</literal>), which are "
-"pinged for discovery."
-msgstr ""
-"<emphasis role=\"bold\">initial_hosts</emphasis> é uma lista de endereços "
-"separada por vírgulas (ex.: <literal>host1[12345],host2[23456]</literal>), "
-"que são feitos pings para a descoberta. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2009
-#, 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 ""
-"Caso ambos os <literal>gossip_host</literal> e <literal>gossip_port</"
-"literal> estejam definidos, o cluster utiliza o GossipRouter para a "
-"descoberta inicial. Se o <literal>initial_hosts</literal> for especificado, "
-"o cluster faz um ping na lista estática de endereço para descoberta. Caso "
-"contrário, o cluster utiliza o multicast IP para descoberta. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2014
-#, 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 ""
-"A fase de descoberta retorna quando o tempo de milisegundos<literal>timeout</"
-"literal> tiver expirado ou quando as respostas <literal>num_initial_members</"
-"literal>tiverem sido recebidas. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2022
-#, no-c-format
-msgid "TCPGOSSIP"
-msgstr "TCPGOSSIP"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2023
-#, 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 ""
-"O Protocolo TCPGOSSIP somente funciona com um GossipRouter. Ele funciona "
-"basicamente da mesma forma que a configuração do protocolo PING com válidos "
-"<literal>gossip_host</literal> e funções <literal>gossip_port</literal>. Ele "
-"funciona em cima tanto do protocolo de transporte UDP quanto do TCP. Segue "
-"aqui um exemplo:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2026
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<TCPGOSSIP timeout=\"2000\"\n"
-" initial_hosts=\"192.168.5.1[12000],192.168.0.2[12000]\"\n"
-" num_initial_members=\"3\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>]]>"
-msgstr ""
-"<![CDATA[\n"
-"<TCPGOSSIP timeout=\"2000\"\n"
-" initial_hosts=\"192.168.5.1[12000],192.168.0.2[12000]\"\n"
-" num_initial_members=\"3\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2029
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>TCPGOSSIP</literal> element are "
-"listed below."
-msgstr ""
-"As funções disponíveis no elemento <literal>TCPGOSSIP</literal> estão "
-"listadas abaixo:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2040
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">initial_hosts</emphasis> is a comma-seperated list "
-"of addresses (e.g., <literal>host1[12345],host2[23456]</literal>) for "
-"GossipRouters to register with."
-msgstr ""
-"<emphasis role=\"bold\">initial_hosts</emphasis> é uma lista de endereços "
-"separada por vírgulas (ex.: <literal>host1[12345],host2[23456]</literal>) "
-"para GossipRouters se registrarem."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2050
-#, no-c-format
-msgid "TCPPING"
-msgstr "TCPPING"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2051
-#, 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 ""
-"O Protocolo TCPPING escolhe um conjunto de membros conhecidos e efetua um "
-"ping neles, para a descoberta. Isto é originalmente uma configuração "
-"estática. Ela funciona sob o TCP. Aqui segue um exemplo de elemento "
-"configuração <literal>TCPPING</literal> no elemento JGroups <literal>Config</"
-"literal>."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2055
-#, no-c-format
-msgid ""
-"<TCPPING timeout=\"2000\"\n"
-" initial_hosts=\"hosta[2300],hostb[3400],hostc[4500]\"\n"
-" port_range=\"3\"\n"
-" num_initial_members=\"3\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-msgstr ""
-"<TCPPING timeout=\"2000\"\n"
-" initial_hosts=\"hosta[2300],hostb[3400],hostc[4500]\"\n"
-" port_range=\"3\"\n"
-" num_initial_members=\"3\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2058
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>TCPPING</literal> element are "
-"listed below."
-msgstr ""
-"As funções disponíveis no elemento <literal>TCPPING</literal> estão listadas "
-"abaixo:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2069
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">initial_hosts</emphasis> is a comma-seperated list "
-"of addresses (e.g., <literal>host1[12345],host2[23456]</literal>) for "
-"pinging."
-msgstr ""
-"<emphasis role=\"bold\">initial_hosts</emphasis> é uma lista de endereços "
-"separada por vírgulas (ex.: <literal>host1[12345],host2[23456]</literal>) "
-"para realizar um ping."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2073
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">port_range</emphasis> specifies the number of "
-"consecutive ports to be probed when getting the initial membership, starting "
-"with the port specified in the initial_hosts parameter. Given the current "
-"values of port_range and initial_hosts above, the TCPPING layer will try to "
-"connect to hosta:2300, hosta:2301, hosta:2302, hostb:3400, hostb:3401, "
-"hostb:3402, hostc:4500, hostc:4501, hostc:4502. The configuration options "
-"allows for multiple nodes on the same host to be pinged."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2084
-#, no-c-format
-msgid "MPING"
-msgstr "MPING "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2085
-#, no-c-format
-msgid ""
-"MPING uses IP multicast to discover the initial membership. It can be used "
-"with all transports, but usually this is used in combination with TCP. TCP "
-"usually requires TCPPING, which has to list all group members explicitly, "
-"but MPING doesn't have this requirement. The typical use case for this is "
-"when we want TCP as transport, but multicasting for discovery so we don't "
-"have to define a static list of initial hosts in TCPPING or require external "
-"Gossip Router."
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2089
-#, 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\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-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\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2092
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>MPING</literal> element are listed "
-"below."
-msgstr ""
-"As funções disponíveis no elemento <literal>MPING</literal> estão listadas "
-"abaixo:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2099
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">num_initial_members</emphasis> specifies the maximum "
-"number of responses to wait for unless timeout has expired. The default is "
-"2.."
-msgstr ""
-"<emphasis role=\"bold\">num_initial_members</emphasis> especifica o número "
-"máximo de respostas a receber. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2103
-#, 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> especifica a interface para "
-"enviar e receber pacotes de multicast."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2107
-#, 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> invalida o "
-"<literal>bind_addr</literal> e utiliza todas as interfaces em nós de "
-"endereços múltiplos."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2111
-#, 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 ""
-"As funções <emphasis role=\"bold\">mcast_addr, mcast_port, ip_ttl</emphasis> "
-"são as mesmas que as funções na configuração do protocolo UDP."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2121
-#, no-c-format
-msgid "Failure Detection Protocols"
-msgstr "Protocolo de Detecção de Falhas."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2122
-#, fuzzy, no-c-format
-msgid ""
-"The failure detection protocols are used to detect failed nodes. Once a "
-"failed node is detected, a suspect verification phase can occur after which, "
-"if the node is still considered dead, 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 ""
-"Os protocolos de detecção de falhas são utilizados para detectar nós falhos. "
-"Uma vez que um nó falho é detectado, o cluster atualiza sua visualização "
-"para que o balanceador de carga e o interceptador do cliente saibam como "
-"evitar o nó falho. Os protocolos de detecção de falha são configurados como "
-"sub-elementos no elemento MBean do JGroups <literal>Config</literal>."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2128
-#, no-c-format
-msgid "<title>FD</title>"
-msgstr "<title>FD</title>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2129
-#, fuzzy, no-c-format
-msgid ""
-"FD is a failure detection protocol based on heartbeat messages. This "
-"protocol requires each node to periodically send are-you-alive messages to "
-"its neighbour. If the neighbour fails to respond, the calling node sends a "
-"SUSPECT message to the cluster. The current group coordinator can optionally "
-"double check whether the suspected node is indeed dead after which, if the "
-"node is still considered dead, updates the cluster's view. Here is an "
-"example FD configuration."
-msgstr ""
-"O protocolo de descoberta FD requer que cada nó envie periódicamente "
-"mensagens para saber se seus vizinhos estão funcionando. Caso seu vizinho "
-"não responda, o nó que está chamando envia uma mensagem de SUSPEITO para o "
-"cluster. O atual coordenador de grupo checa novamente se o nó suspeito está "
-"realmente falho e atualiza a visualização do cluster. Segue aqui um exemplo "
-"de configuração FD."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2133
-#, no-c-format
-msgid ""
-"<FD timeout=\"2000\"\n"
-" max_tries=\"3\"\n"
-" shun=\"true\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-msgstr ""
-"<FD timeout=\"2000\"\n"
-" max_tries=\"3\"\n"
-" shun=\"true\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2136
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>FD</literal> element are listed "
-"below."
-msgstr ""
-"As funções disponíveis no elemento <literal>FD</literal> estão listadas "
-"abaixo:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2139
-#, fuzzy, 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. The "
-"default is 3000."
-msgstr ""
-"<emphasis role=\"bold\">timeout</emphasis> especifica o número máximo de "
-"milisegundos para a espera por respostas às mensagens are-you-alive."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2143
-#, fuzzy, 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. The default "
-"is 2."
-msgstr ""
-"<emphasis role=\"bold\">max_tries</emphasis> especifica o número de "
-"mensagens are-you-alive perdidas de um nó antes dele ser suspeito."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2147
-#, fuzzy, 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. JGroups allows to configure itself such that "
-"shunning leads to automatic rejoins and state transfer, which is the default "
-"behaivour within JBoss Application Server."
-msgstr ""
-"<emphasis role=\"bold\">shun</emphasis> especifica quando um nó falho será "
-"evitado. Uma vez evitado, o nó será expelido do cluster até mesmo se ele for "
-"instalado depois. O nó evitado teria que retornar ao cluster através do "
-"processo de descoberta. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2153
-#, 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 ""
-"O tráfego normal de um nó conta como se estivesse ativo. Portanto, as "
-"mensagens are-you-alive, são enviadas somente quando existir um tráfego "
-"normal para o nó por um certo período de tempo. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2162
-#, no-c-format
-msgid "FD_SOCK"
-msgstr "FD_SOCK"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2163
-#, no-c-format
-msgid ""
-"FD_SOCK is a failure detection protocol based on a ring of TCP sockets "
-"created between group members. Each member in a group connects to its "
-"neighbor (last member connects to first) thus forming a ring. Member B is "
-"suspected when its neighbor A detects abnormally closed TCP socket "
-"(presumably due to a node B crash). However, if a member B is about to leave "
-"gracefully, it lets its neighbor A know, so that it does not become "
-"suspected. 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 ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2167
-#, no-c-format
-msgid "<FD_SOCK_down_thread=\"false\" up_thread=\"false\"/>"
-msgstr "<FD_SOCK_down_thread=\"false\" up_thread=\"false\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2169
-#, fuzzy, no-c-format
-msgid ""
-"There available attributes in the <literal>FD_SOCK</literal> element are "
-"listed below."
-msgstr ""
-"As funções disponíveis no elemento <literal>FD</literal> estão listadas "
-"abaixo:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2172
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">bind_addr</emphasis> specifies the interface to "
-"which the server socket should bind to. If -Djgroups.bind_address system "
-"property is defined, XML value will be ignore. This behaivour can be "
-"reversed setting -Djgroups.ignore.bind_addr=true system property."
-msgstr ""
-"<emphasis role=\"bold\">srv_sock_bind_addr</emphasis> especifica a interface "
-"com o qual o soquete do servidor deve se vincular. Se omitido, será "
-"utilizada a propriedade <literal>-D bind.address</literal> da linha de "
-"comando de inicialização do servidor."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2180
-#, no-c-format
-msgid "VERIFY_SUSPECT"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2181
-#, no-c-format
-msgid ""
-"This protocol verifies whether a suspected member is really dead by pinging "
-"that member once again. This verification is performed by the coordinator of "
-"the cluster. The suspected member is dropped from the cluster group if "
-"confirmed to be dead. The aim of this protocol is to minimize false "
-"suspicions. Here's an example."
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2185
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-"<VERIFY_SUSPECT timeout=\"1500\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>]]>"
-msgstr ""
-"<![CDATA[ \n"
-"<VERIFY_SUSPECT timeout=\"1500\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2187
-#, fuzzy, no-c-format
-msgid "The available attributes in the FD_SOCK element are listed below."
-msgstr ""
-"As funções disponíveis no elemento <literal>FD</literal> estão listadas "
-"abaixo:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2192
-#, no-c-format
-msgid ""
-"timeout specifies how long to wait for a response from the suspected member "
-"before considering it dead."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2203
-#, no-c-format
-msgid "FD versus FD_SOCK"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2204
-#, no-c-format
-msgid ""
-"FD and FD_SOCK, each taken individually, do not provide a solid failure "
-"detection layer. Let's look at the the differences between these failure "
-"detection protocols to understand how they complement each other:"
-msgstr ""
-
-#. Tag: emphasis
-#: Clustering_Guide_Introduction.xml:2208
-#, no-c-format
-msgid "<emphasis>FD</emphasis>"
-msgstr "<emphasis>FD</emphasis>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2213
-#, no-c-format
-msgid "An overloaded machine might be slow in sending are-you-alive responses."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2218
-#, no-c-format
-msgid "A member will be suspected when suspended in a debugger/profiler."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2223
-#, no-c-format
-msgid ""
-"Low timeouts lead to higher probability of false suspicions and higher "
-"network traffic."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2228
-#, no-c-format
-msgid "High timeouts will not detect and remove crashed members for some time."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2235
-#, no-c-format
-msgid "<emphasis>FD_SOCK</emphasis>:"
-msgstr "<emphasis>FD_SOCK</emphasis>:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2241
-#, no-c-format
-msgid ""
-"Suspended in a debugger is no problem because the TCP connection is still "
-"open."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2246
-#, no-c-format
-msgid "High load no problem either for the same reason."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2251
-#, no-c-format
-msgid "Members will only be suspected when TCP connection breaks"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2260
-#, no-c-format
-msgid "So hung members will not be detected."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2265
-#, no-c-format
-msgid ""
-"Also, a crashed switch will not be detected until the connection runs into "
-"the TCP timeout (between 2-20 minutes, depending on TCP/IP stack "
-"implementation)."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2272
-#, no-c-format
-msgid ""
-"The aim of a failure detection layer is to report real failures and "
-"therefore avoid false suspicions. There are two solutions:"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2277
-#, no-c-format
-msgid ""
-"By default, JGroups configures the FD_SOCK socket with KEEP_ALIVE, which "
-"means that TCP sends a heartbeat on socket on which no traffic has been "
-"received in 2 hours. If a host crashed (or an intermediate switch or router "
-"crashed) without closing the TCP connection properly, we would detect this "
-"after 2 hours (plus a few minutes). This is of course better than never "
-"closing the connection (if KEEP_ALIVE is off), but may not be of much help. "
-"So, the first solution would be to lower the timeout value for KEEP_ALIVE. "
-"This can only be done for the entire kernel in most operating systems, so if "
-"this is lowered to 15 minutes, this will affect all TCP sockets."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2282
-#, no-c-format
-msgid ""
-"The second solution is to combine FD_SOCK and FD; the timeout in FD can be "
-"set such that it is much lower than the TCP timeout, and this can be "
-"configured individually per process. FD_SOCK will already generate a suspect "
-"message if the socket was closed abnormally. However, in the case of a "
-"crashed switch or host, FD will make sure the socket is eventually closed "
-"and the suspect message generated. Example:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2287
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<FD_SOCK down_thread=\"false\" up_thread=\"false\"/>\n"
-"<FD timeout=\"10000\" max_tries=\"5\" shun=\"true\" \n"
-"down_thread=\"false\" up_thread=\"false\" /> ]]>"
-msgstr ""
-"<![CDATA[\n"
-"<FD_SOCK down_thread=\"false\" up_thread=\"false\"/>\n"
-"<FD timeout=\"10000\" max_tries=\"5\" shun=\"true\" \n"
-"down_thread=\"false\" up_thread=\"false\" /> ]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2289
-#, no-c-format
-msgid ""
-"This suspects a member when the socket to the neighbor has been closed "
-"abonormally (e.g. process crash, because the OS closes all sockets). "
-"However, f a host or switch crashes, then the sockets won't be closed, "
-"therefore, as a seond line of defense, FD will suspect the neighbor after 50 "
-"seconds. Note that with this example, if you have your system stopped in a "
-"breakpoint in the debugger, the node you're debugging will be suspected "
-"after ca 50 seconds."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2292
-#, no-c-format
-msgid ""
-"A combination of FD and FD_SOCK provides a solid failure detection layer and "
-"for this reason, such technique is used accross JGroups configurations "
-"included within JBoss Application Server."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2301
-#, no-c-format
-msgid "Reliable Delivery Protocols"
-msgstr "Protocolos de Entrega Confiáveis"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2302
-#, fuzzy, no-c-format
-msgid ""
-"Reliable delivery protocols within 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 ""
-"Os protocolos de entrega confiáveis na pilha de JGroup, assegura que os "
-"pacotes de dados estão sendo entregues na ordem correta (FIFO) para o nó de "
-"destino. A base para a entrega de mensagens confiáveis é a confirmação da "
-"entrega positiva e negativa (ACK e NAK). No módulo ACK, o remetente reenvia "
-"a mensagem até que a confirmação seja recebida do remetente. No módulo NAK, "
-"o receptor solicita uma retransmissão quando descobrir uma brecha."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2309
-#, no-c-format
-msgid "UNICAST"
-msgstr "UNICAST"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2310
-#, fuzzy, 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 Config element. If the JGroups "
-"stack is configured with TCP transport protocol, UNICAST is not necessary "
-"because TCP itself guarantees FIFO delivery of unicast messages. Here is an "
-"example configuration for the <literal>UNICAST</literal> protocol."
-msgstr ""
-"O protocolo UNICAST é utilizado para mensagens unicast. Ele utiliza ACK. É "
-"configurado como um sub-elemento sob o elemento JGroups <literal>Config</"
-"literal> . Segue aqui um exemplo de configuração para o protocolo "
-"<literal>UNICAST</literal> ."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2313
-#, no-c-format
-msgid ""
-"<UNICAST timeout=\"100,200,400,800\"\n"
-"down_thread=\"false\" up_thread=\"false\"/>"
-msgstr ""
-"<UNICAST timeout=\"100,200,400,800\"\n"
-"down_thread=\"false\" up_thread=\"false\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2315
-#, no-c-format
-msgid ""
-"There is only one configurable attribute in the <literal>UNICAST</literal> "
-"element."
-msgstr ""
-"Existe somente uma função configurável no elemento <literal>UNICAST</"
-"literal>. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2318
-#, 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> especifica o tempo de espera da "
-"retransmissão (em milisegundos). Por exemplo, se o tempo de espera for "
-"\"100,200,400,800\", o remetente reenvia a mensagem caso não tenha recebido "
-"um ACK após 100ms da primeira vez, na segunda vez ele espera 200ms antes de "
-"reenviar e assim segue. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2328
-#, no-c-format
-msgid "NAKACK"
-msgstr "NAKACK "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2329
-#, 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 ""
-"O protocolo NAKACK é utilizado para mensagens multicast. Ele utiliza o NAK. "
-"Cada mensagem, sob este protocolo, é marcada com um número sequencial. O "
-"receptor mantém o registro dos números seqüenciais e entrega a mensagem "
-"ordenadamente. Quando uma brecha no número de seqüencia for detectada, o "
-"receptor pede ao remetente para retransmitir a mensagem que falta. O "
-"protocolo NAKACK é configurado como um sub-elemento <literal>pbcast.NAKACK</"
-"literal> sob o elemento <literal>Config</literal>. Segue aqui um exemplo de "
-"configuração:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2336
-#, no-c-format
-msgid ""
-"<pbcast.NAKACK max_xmit_size=\"60000\" use_mcast_xmit=\"false\" \n"
-" \n"
-" retransmit_timeout=\"300,600,1200,2400,4800\" gc_lag=\"0\"\n"
-" discard_delivered_msgs=\"true\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-msgstr ""
-"<<pbcast.NAKACK max_xmit_size=\"60000\" use_mcast_xmit=\"false\" \n"
-" \n"
-" retransmit_timeout=\"300,600,1200,2400,4800\" gc_lag=\"0\"\n"
-" discard_delivered_msgs=\"true\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2339
-#, no-c-format
-msgid ""
-"The configurable attributes in the <literal>pbcast.NAKACK</literal> element "
-"are as follows."
-msgstr ""
-"Segue abaixo, exemplo das funções configuráveis no elemento <literal>pbcast."
-"NAKACK</literal>: "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2342
-#, 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> especifica o tempo de "
-"espera da retransmissão (em milisegundos). É o mesmo que a função "
-"<literal>timeout</literal> no protocolo UNICAST."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2347
-#, 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> determina se um remetente "
-"deve enviar uma retransmissão para o cluster todo ou se deve enviar somente "
-"para o nó que estiver solicitando. Isto é muito útil quando o remetente "
-"soltar o pacote, assim não precisamos retransmitir para cada nó. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2353
-#, 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> especifica o tamanho máximo "
-"para uma transmissão agrupada, se pacotes múltiplos forem relatados como "
-"perdidos. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2357
-#, 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> especifica quando "
-"rejeitar mensagens de entrega em nós receptores. Como padrão, salvamos todas "
-"as mensagens entregues. No entanto, se requisitarmos somente para o "
-"remetente reenviar suas mensagens, podemos habilitar esta opção e descartar "
-"mensagens entregues. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2364
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">gc_lag specifies</emphasis> the number of messages "
-"garbage collection lags behind."
-msgstr ""
-"<emphasis role=\"bold\">className</emphasis>: O nome da classe que oferece "
-"a implementação do serviço. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2375
-#, no-c-format
-msgid "Other Configuration Options"
-msgstr "Outras Opções de Configuração"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2376
-#, no-c-format
-msgid ""
-"In addition to the protocol stacks, you can also configure JGroups network "
-"services in the <literal>Config</literal> element."
-msgstr ""
-"Além da pilha de protocolos, você também poderá configurar os serviços da "
-"rede de trabalho JGroups no elemento <literal>Config</literal>. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2380
-#, no-c-format
-msgid "Group Membership"
-msgstr "Propriedade de Grupo"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2381
-#, 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 ""
-"O serviço de propriedade de grupo na pilha de JGroups, mantém um lista de "
-"nós ativos. Ele manipula as solicitações para se unirem ao cluster e depois "
-"deixá-lo. Também manipula as mensagens SUSPEITAS enviadas pelo protocolo de "
-"detecção de falhas. Todos os nós no cluster, assim como o balanceador de "
-"carga e os interceptadores do cliente, são notificados caso a propriedade do "
-"grupo mude. O serviço de propriedade de grupo está configurado no sub-"
-"elemento <literal>pbcast.GMS</literal> sob o elemento "
-"JGroups<literal>Config</literal>. Segue aqui um exemplo de configuração:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2387
-#, no-c-format
-msgid ""
-"<pbcast.GMS print_local_addr=\"true\"\n"
-" join_timeout=\"3000\"\n"
-" down_thread=\"false\" up_thread=\"false\"\n"
-" join_retry_timeout=\"2000\"\n"
-" shun=\"true\"\n"
-" view_bundling=\"true\"/>"
-msgstr ""
-"<pbcast.GMS print_local_addr=\"true\"\n"
-" join_timeout=\"3000\"\n"
-" down_thread=\"false\" up_thread=\"false\"\n"
-" join_retry_timeout=\"2000\"\n"
-" shun=\"true\"\n"
-" view_bundling=\"true\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2391
-#, no-c-format
-msgid ""
-"The configurable attributes in the <literal>pbcast.GMS</literal> element are "
-"as follows."
-msgstr ""
-"As funções configuráveis no elemento <literal>pbcast.GMS</literal> são as "
-"seguintes:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2394
-#, 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> especifica o número máximo "
-"de milisegundos para esperar que um novo nó se junte à solicitação com "
-"sucesso. Tente novamente mais tarde. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2398
-#, 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> especifica o número "
-"máximo de milisegundos para esperar, depois de um JOIN falho, para submetê-"
-"lo novamente."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2402
-#, 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> especifica quando "
-"despejar o endereço próprio do nó na saída, quando iniciado. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2406
-#, 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> especifica quando um nó deve evitar "
-"a si próprio, caso receba a exibição de um cluster que não seja um nó membro."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2410
-#, 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> especifica quando "
-"evitar este nó como coordenador do cluster."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2414
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">view_bundling</emphasis> specifies whether multiple "
-"JOIN or LEAVE request arriving at the same time are bundled and handled "
-"together at the same time, only sending out 1 new view / bundle. This is is "
-"more efficient than handling each request separately."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2423
-#, no-c-format
-msgid "Flow Control"
-msgstr "Controle de Fluxo"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2424
-#, 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 ""
-"O serviço de controle de fluxo tenta adaptar a taxa de dados de envio e "
-"dados de recepção entre os nós. Se um nó remetente for muito rápido, ele "
-"pode sobrepôr o nó receptor e resultar em pacotes soltos que precisarão ser "
-"retransmitidos. No JGroups, o controle de fluxo é implementado através do "
-"sistema baseado em crédito. Os nós remetente e receptor possuem o mesmo "
-"número de créditos (bytes) no início. O remetente subtrai créditos pelo "
-"número de bytes na mensagem que ele envia. O receptor acumula créditos pelos "
-"bytes na mensagem que ele recebe. Quando o crédito de um remetente cai para "
-"um limiar, os receptores enviam alguns créditos para o remetente. Caso o "
-"crédito do remetente seja utilizado, o remetente é bloqueado até que ele "
-"receba créditos de um receptor. O serviço de controle de fluxo é configurado "
-"no sub-elemento <literal>FC</literal> sob o elemento do JGroups "
-"<literal>Config</literal>. Segue aqui um exemplo de configuração."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2435
-#, no-c-format
-msgid ""
-"<FC max_credits=\"1000000\"\n"
-"down_thread=\"false\" up_thread=\"false\" \n"
-" min_threshold=\"0.10\"/>"
-msgstr ""
-"<FC max_credits=\"1000000\"\n"
-"down_thread=\"false\" up_thread=\"false\" \n"
-" min_threshold=\"0.10\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2438
-#: Clustering_Guide_Introduction.xml:2539
-#, no-c-format
-msgid ""
-"The configurable attributes in the <literal>FC</literal> element are as "
-"follows."
-msgstr "As funções configuráveis no elemento <literal>FC</literal> sãos as seguintes:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2441
-#, 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> especifica o número máximo de "
-"créditos (em bytes). Este valor deve ser menor do que o tamanho da pilha do "
-"JVM."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2445
-#, 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> especifica o limite de "
-"crédito no remetente, caso esteja abaixo do limite, o receptor deve enviar "
-"mais créditos. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2449
-#, 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> especifica o valor da "
-"porcentagem do limite. Esta função substitui a função <literal>min_credits</"
-"literal>. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2455
-#, no-c-format
-msgid ""
-"Applications that use synchronous group RPC calls primarily do not require "
-"FC protocol in their JGroups protocol stack because synchronous "
-"communication, where the hread that makes the call blocks waiting for "
-"responses from all the members of the group, already slows overall rate of "
-"calls. Even though TCP provides flow control by itself, FC is still required "
-"in TCP based JGroups stacks because of group communication, where we "
-"essentially have to send group messages at the highest speed the slowest "
-"receiver can keep up with. TCP flow control only takes into account "
-"individual node communications and has not a notion of who's the slowest in "
-"the group, which is why FC is required."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2464
-#, no-c-format
-msgid "Fragmentation"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2465
-#, no-c-format
-msgid ""
-"This protocol fragments messages larger than certain size. Unfragments at "
-"the receiver's side. It works for both unicast and multicast messages. It is "
-"configured in the FRAG2 sub-element under the JGroups Config element. Here "
-"is an example configuration."
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2468
-#, no-c-format
-msgid ""
-"<![CDATA[ \n"
-" <FRAG2 frag_size=\"60000\" down_thread=\"false\" up_thread="
-"\"false\"/>]]>"
-msgstr ""
-"<![CDATA[ \n"
-" <FRAG2 frag_size=\"60000\" down_thread=\"false\" up_thread="
-"\"false\"/>]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2470
-#, fuzzy, no-c-format
-msgid "The configurable attributes in the FRAG2 element are as follows."
-msgstr "As funções configuráveis no elemento <literal>FC</literal> sãos as seguintes:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2475
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">frag_size</emphasis> specifies the max frag size in "
-"bytes. Messages larger than that are fragmented."
-msgstr ""
-"<emphasis role=\"bold\">max_credits</emphasis> especifica o número máximo de "
-"créditos (em bytes). Este valor deve ser menor do que o tamanho da pilha do "
-"JVM."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2479
-#, no-c-format
-msgid ""
-"TCP protocol already provides fragmentation but a fragmentation JGroups "
-"protocol is still needed if FC is used. The reason for this is that if you "
-"send a message larger than FC.max_bytes, FC protocol would block. So, "
-"frag_size within FRAG2 needs to be set to always be less than FC.max_bytes."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2490
-#, no-c-format
-msgid "State Transfer"
-msgstr "Transferência de Estado"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2491
-#, 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 ""
-"O serviço de transferência de estado, transfere o estado de um nó existente "
-"(ou seja, o coordenador do cluster) para um nó recentemente agregado. É "
-"configurado no sub-elemento <literal>pbcast.STATE_TRANSFER</literal> sob o "
-"elemento <literal>Config</literal>. Não possui nenhuma função configurável. "
-"Segue aqui um exemplo de configuração:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2495
-#, no-c-format
-msgid "<pbcast.STATE_TRANSFER down_thread=\"false\" up_thread=\"false\"/>"
-msgstr "<pbcast.STATE_TRANSFER down_thread=\"false\" up_thread=\"false\"/>"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2502
-#, no-c-format
-msgid "Distributed Garbage Collection"
-msgstr "Coletor de Lixo Distribuído"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2503
-#, 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 ""
-"Em um cluster JGroup, todos os nós precisam armazenar todas as mensagens "
-"recebidas para a retransmissão em potencial, caso ocorra falha. No entanto, "
-"se todas as mensagens forem armazenadas para sempre, ficaremos sem memória. "
-"Portanto, o serviço de coletor de lixo distribuído em JGroup, expurga "
-"periódicamente, mensagens vistas por todos os nós da memória em cada nó. O "
-"serviço de coletor de lixo distribuído é configurado no sub-elemento "
-"<literal>pbcast.STABLE</literal> sob o elemento JGroups <literal>Config</"
-"literal> . Segue aqui um exemplo de configuração. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2507
-#, fuzzy, no-c-format
-msgid ""
-"<pbcast.STABLE stability_delay=\"1000\"\n"
-" desired_avg_gossip=\"5000\" \n"
-" down_thread=\"false\" up_thread=\"false\"\n"
-" max_bytes=\"400000\"/>"
-msgstr ""
-"<pbcast.STABLE stability_delay=\"1000\"\n"
-" desired_avg_gossip=\"5000\" \n"
-" down_thread=\"false\"\n"
-" max_bytes=\"250000\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2509
-#, no-c-format
-msgid ""
-"The configurable attributes in the <literal>pbcast.STABLE</literal> element "
-"are as follows."
-msgstr ""
-"As funções configuráveis no elemento <literal>pbcast.STABLE</literal> são as "
-"seguintes:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2512
-#, 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> especifica os "
-"intervalos (em milisegundos) da execução do coletor de lixo. O valor "
-"<literal>0</literal> desabilita este serviço."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2517
-#, 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> especifica o número máximo de "
-"bytes recebidos antes do cluster disparar a execução do coletor de lixo. O "
-"valor <literal>0</literal> desabilita este serviço."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2522
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">stability_delay</emphasis> specifies delay before we "
-"send STABILITY msg (give others a change to send first). If used together "
-"with max_bytes, this attribute should be set to a small number."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2526
-#, no-c-format
-msgid ""
-"Set the <literal>max_bytes</literal> attribute when you have a high traffic "
-"cluster."
-msgstr ""
-"Instalar a função <literal>max_bytes</literal> quando houver um cluster de "
-"tráfego intenso. "
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2531
-#, no-c-format
-msgid "Merging"
-msgstr "Mesclagem"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2532
-#, 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 ""
-"Quando um erro ocorrer na rede de trabalho, o cluster pode ser dividido em "
-"diversas partições diferentes. O JGroups possui um serviço de mesclagem que "
-"permite que os coordenadores nas partições se comuniquem uns com os outros e "
-"formem novamente um cluster só. O serviço de controle de fluxo é configurado "
-"no sub-elemento <literal>MERGE2</literal> sob o elemento JGroups "
-"<literal>Config</literal>. Segue aqui um exemplo de configuração. "
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2536
-#, no-c-format
-msgid ""
-"<MERGE2 max_interval=\"10000\"\n"
-" min_interval=\"2000\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-msgstr ""
-"<MERGE2 max_interval=\"10000\"\n"
-" min_interval=\"2000\"\n"
-" down_thread=\"false\" up_thread=\"false\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2542
-#, 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> especifica o número máximo "
-"de milisegundos para enviar uma mensagem mesclada. "
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2546
-#, 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> especifica o número mínimo "
-"de milisegundos para enviar uma mensagem mesclada."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2550
-#, 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 ""
-"O JGroups escolhe um valor aleatório entre <literal>min_interval</literal> "
-"e<literal>max_interval</literal> para enviar uma mensagem mesclada."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2553
-#, no-c-format
-msgid ""
-"The cluster states are not merged in a merger. This has to be done by the "
-"application. If <literal>MERGE2</literal> is used in conjunction with "
-"TCPPING, the <literal>initial_hosts</literal> attribute must contain all the "
-"nodes that could potentially be merged back, in order for the merge process "
-"to work properly. Otherwise, the merge process would not merge all the nodes "
-"even though shunning is disabled. Alternatively use MPING, which is commonly "
-"used with TCP to provide multicast member discovery capabilities, instead of "
-"TCPPING to avoid having to specify all the nodes."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2559
-#, no-c-format
-msgid "Binding JGroups Channels to a particular interface"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2560
-#, no-c-format
-msgid ""
-"In the Transport Protocols section above, we briefly touched on how the "
-"interface to which JGroups will bind sockets is configured. Let's get into "
-"this topic in more depth:"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2563
-#, no-c-format
-msgid ""
-"First, it's important to understand that the value set in any bind_addr "
-"element in an XML configuration file will be ignored by JGroups if it finds "
-"that system property jgroups.bind_addr (or a deprecated earlier name for the "
-"same thing, <literal>bind.address</literal>) has been set. The system "
-"property trumps XML. If JBoss AS is started with the -b (a.k.a. --host) "
-"switch, the AS will set <literal>jgroups.bind_addr</literal> to the "
-"specified value."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2566
-#, no-c-format
-msgid ""
-"Beginning with AS 4.2.0, for security reasons the JBoss Application Server "
-"binds most services to localhost if -b is not set. The effect of this is "
-"that in most cases users are going to be setting -b and thus jgroups."
-"bind_addr is going to be set and any XML setting will be ignored."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2569
-#, no-c-format
-msgid ""
-"So, what are <emphasis>best practices</emphasis> for managing how JGroups "
-"binds to interfaces?"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2574
-#, no-c-format
-msgid "Binding JGroups to the same interface as other services. Simple, just use -b:"
-msgstr ""
-
-#. Tag: screen
-#: Clustering_Guide_Introduction.xml:2576
-#, no-c-format
-msgid "./run.sh -b 192.168.1.100 -c all"
-msgstr "./run.sh -b 192.168.1.100 -c all"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2580
-#, no-c-format
-msgid ""
-"Binding services (e.g., JBoss Web) to one interface, but use a different one "
-"for JGroups: <screen>./run.sh -b 10.0.0.100 -Djgroups."
-"bind_addr=192.168.1.100 -c all</screen> Specifically setting the system "
-"property overrides the -b value. This is a common usage pattern; put client "
-"traffic on one network, with intra-cluster traffic on another."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2588
-#, no-c-format
-msgid ""
-"Binding services (e.g., JBoss Web) to all interfaces. This can be done like "
-"this: <screen>./run.sh -b 0.0.0.0 -c all</screen> However, doing this will "
-"not cause JGroups to bind to all interfaces! Instead , JGroups will bind to "
-"the machine's default interface. See the Transport Protocols section for how "
-"to tell JGroups to receive or send on all interfaces, if that is what you "
-"really want."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2596
-#, no-c-format
-msgid ""
-"Binding services (e.g., JBoss Web) to all interfaces, but specify the "
-"JGroups interface: <screen>./run.sh -b 0.0.0.0 -Djgroups."
-"bind_addr=192.168.1.100 -c all</screen> Again, specifically setting the "
-"system property overrides the -b value."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2604
-#, no-c-format
-msgid "Using different interfaces for different channels:"
-msgstr ""
-
-#. Tag: screen
-#: Clustering_Guide_Introduction.xml:2606
-#, no-c-format
-msgid "./run.sh -b 10.0.0.100 -Djgroups.ignore.bind_addr=true -c all"
-msgstr "./run.sh -b 10.0.0.100 -Djgroups.ignore.bind_addr=true -c all"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2611
-#, no-c-format
-msgid ""
-"This setting tells JGroups to ignore the <literal>jgroups.bind_addr</"
-"literal> system property, and instead use whatever is specfied in XML. You "
-"would need to edit the various XML configuration files to set the "
-"<literal>bind_addr</literal> to the desired interfaces."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2616
-#, no-c-format
-msgid "Isolating JGroups Channels"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2617
-#, no-c-format
-msgid ""
-"Within JBoss AS, there are a number of services that independently create "
-"JGroups channels -- 3 different JBoss Cache services (used for HttpSession "
-"replication, EJB3 SFSB replication and EJB3 entity replication) along with "
-"the general purpose clustering service called HAPartition that underlies "
-"most other JBossHA services."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2620
-#, no-c-format
-msgid ""
-"It is critical that these channels only communicate with their intended "
-"peers; not with the channels used by other services and not with channels "
-"for the same service opened on machines not meant to be part of the group. "
-"Nodes improperly communicating with each other is one of the most common "
-"issues users have with JBoss AS clustering."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2623
-#, no-c-format
-msgid ""
-"Whom a JGroups channel will communicate with is defined by its group name, "
-"multicast address, and multicast port, so isolating JGroups channels comes "
-"down to ensuring different channels use different values for the group name, "
-"multicast address and multicast port."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2626
-#, no-c-format
-msgid ""
-"To isolate JGroups channels for different services on the same set of AS "
-"instances from each other, you MUST change the group name and the multicast "
-"port. In other words, each channel must have its own set of values."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2629
-#, no-c-format
-msgid ""
-"For example, say we have a production cluster of 3 machines, each of which "
-"has an HAPartition deployed along with a JBoss Cache used for web session "
-"clustering. The HAPartition channels should not communicate with the JBoss "
-"Cache channels. They should use a different group name and multicast port. "
-"They can use the same multicast address, although they don't need to."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2632
-#, no-c-format
-msgid ""
-"To isolate JGroups channels for the same service from other instances of the "
-"service on the network, you MUST change ALL three values. Each channel must "
-"have its own group name, multicast address, and multicast port."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2635
-#, no-c-format
-msgid ""
-"For example, say we have a production cluster of 3 machines, each of which "
-"has an HAPartition deployed. On the same network there is also a QA cluster "
-"of 3 machines, which also has an HAPartition deployed. The HAPartition group "
-"name, multicast address, and multicast port for the production machines must "
-"be different from those used on the QA machines."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2641
-#, no-c-format
-msgid "Changing the Group Name"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2642
-#, no-c-format
-msgid ""
-"The group name for a JGroups channel is configured via the service that "
-"starts the channel. Unfortunately, different services use different "
-"attribute names for configuring this. For HAPartition and related services "
-"configured in the deploy/cluster-service.xml file, this is configured via a "
-"PartitionName attribute. For JBoss Cache services, the name of the attribute "
-"is ClusterName."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2645
-#, no-c-format
-msgid ""
-"Starting with JBoss AS 4.0.4, for the HAPartition and all the standard JBoss "
-"Cache services, we make it easy for you to create unique groups names simply "
-"by using the -g (a.k.a. –partition) switch when starting JBoss: <screen>./"
-"run.sh -g QAPartition -b 192.168.1.100 -c all</screen> This switch sets the "
-"jboss.partition.name system property, which is used as a component in the "
-"configuration of the group name in all the standard clustering configuration "
-"files. For example,"
-msgstr ""
-
-#. Tag: screen
-#: Clustering_Guide_Introduction.xml:2649
-#, no-c-format
-msgid ""
-"<![CDATA[<attribute name=\"ClusterName\">Tomcat-${jboss.partition.name:"
-"Cluster}</attribute>]]>"
-msgstr ""
-"<![CDATA[<attribute name=\"ClusterName\">Tomcat-${jboss.partition.name:"
-"Cluster}</attribute>]]>"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2655
-#, no-c-format
-msgid "Changing the multicast address and port"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2656
-#, no-c-format
-msgid ""
-"The -u (a.k.a. --udp) command line switch may be used to control the "
-"multicast address used by the JGroups channels opened by all standard AS "
-"services. <screen><![CDATA[/run.sh -u 230.1.2.3 -g QAPartition -b "
-"192.168.1.100 -c all]]></screen> This switch sets the jboss.partition."
-"udpGroup system property, which you can see referenced in all of the "
-"standard protocol stack configs in JBoss AS:"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2662
-#, no-c-format
-msgid ""
-"<![CDATA[<Config>\n"
-"<UDP mcast_addr=\"${jboss.partition.udpGroup:228.1.2.3}\"\n"
-" ....]]>"
-msgstr ""
-"<![CDATA[<Config>\n"
-"<UDP mcast_addr=\"${jboss.partition.udpGroup:228.1.2.3}\"\n"
-" ....]]>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2663
-#, no-c-format
-msgid ""
-"Unfortunately, setting the multicast ports is not so simple. As described "
-"above, by default there are four separate JGroups channels in the standard "
-"JBoss AS all configuration, and each should be given a unique port. There "
-"are no command line switches to set these, but the standard configuration "
-"files do use system properties to set them. So, they can be configured from "
-"the command line by using -D. For example,"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2666
-#, no-c-format
-msgid ""
-"/run.sh -u 230.1.2.3 -g QAPartition -Djboss.hapartition.mcast_port=12345 -"
-"Djboss.webpartition.mcast_port=23456 -Djboss.ejb3entitypartition."
-"mcast_port=34567 -Djboss.ejb3sfsbpartition.mcast_port=45678 -b 192.168.1.100 "
-"-c all"
-msgstr ""
-"/run.sh -u 230.1.2.3 -g QAPartition -Djboss.hapartition.mcast_port=12345 -"
-"Djboss.webpartition.mcast_port=23456 -Djboss.ejb3entitypartition."
-"mcast_port=34567 -Djboss.ejb3sfsbpartition.mcast_port=45678 -b 192.168.1.100 "
-"-c all"
-
-#. Tag: emphasis
-#: Clustering_Guide_Introduction.xml:2668
-#, no-c-format
-msgid "Why isn't it sufficient to change the group name?"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2669
-#, no-c-format
-msgid ""
-"If channels with different group names share the same multicast address and "
-"port, the lower level JGroups protocols in each channel will see, process "
-"and eventually discard messages intended for the other group. This will at a "
-"minimum hurt performance and can lead to anomalous behavior."
-msgstr ""
-
-#. Tag: emphasis
-#: Clustering_Guide_Introduction.xml:2673
-#, no-c-format
-msgid "Why do I need to change the multicast port if I change the address?"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2674
-#, no-c-format
-msgid ""
-"It should be sufficient to just change the address, but there is a problem "
-"on several operating systems whereby packets addressed to a particular "
-"multicast port are delivered to all listeners on that port, regardless of "
-"the multicast address they are listening on. So the recommendation is to "
-"change both the address and the port."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2680
-#, no-c-format
-msgid "JGroups Troubleshooting"
-msgstr ""
-
-#. Tag: emphasis
-#: Clustering_Guide_Introduction.xml:2681
-#, no-c-format
-msgid "Nodes do not form a cluster"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2683
-#, no-c-format
-msgid ""
-"Make sure your machine is set up correctly for IP multicast. There are 2 "
-"test programs that can be used to detect this: McastReceiverTest and "
-"McastSenderTest. Go to the <literal>$JBOSS_HOME/server/all/lib</literal> "
-"directory and start McastReceiverTest, for example:"
-msgstr ""
-
-#. Tag: screen
-#: Clustering_Guide_Introduction.xml:2685
-#, no-c-format
-msgid ""
-"java -cp jgroups.jar org.jgroups.tests.McastReceiverTest -mcast_addr "
-"224.10.10.10 -port 5555"
-msgstr ""
-"java -cp jgroups.jar org.jgroups.tests.McastReceiverTest -mcast_addr "
-"224.10.10.10 -port 5555"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2688
-#, no-c-format
-msgid "Then in another window start <literal>McastSenderTest</literal>:"
-msgstr ""
-
-#. Tag: screen
-#: Clustering_Guide_Introduction.xml:2690
-#, no-c-format
-msgid ""
-"java -cp jgroups.jar org.jgroups.tests.McastSenderTest -mcast_addr "
-"224.10.10.10 -port 5555"
-msgstr ""
-"java -cp jgroups.jar org.jgroups.tests.McastSenderTest -mcast_addr "
-"224.10.10.10 -port 5555"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2693
-#, no-c-format
-msgid ""
-"If you want to bind to a specific network interface card (NIC), use "
-"<literal>-bind_addr 192.168.0.2</literal>, where 192.168.0.2 is the IP "
-"address of the NIC to which you want to bind. Use this parameter in both the "
-"sender and the receiver."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2696
-#, no-c-format
-msgid ""
-"You should be able to type in the <literal>McastSenderTest</literal> window "
-"and see the output in the <literal>McastReceiverTest</literal> window. If "
-"not, try to use -ttl 32 in the sender. If this still fails, consult a system "
-"administrator to help you setup IP multicast correctly, and ask the admin to "
-"make sure that multicast will work on the interface you have chosen or, if "
-"the machines have multiple interfaces, ask to be told the correct interface. "
-"Once you know multicast is working properly on each machine in your cluster, "
-"you can repeat the above test to test the network, putting the sender on one "
-"machine and the receiver on another."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2708
-#, no-c-format
-msgid "Causes of missing heartbeats in FD"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2709
-#, no-c-format
-msgid ""
-"Sometimes a member is suspected by FD because a heartbeat ack has not been "
-"received for some time T (defined by timeout and max_tries). This can have "
-"multiple reasons, e.g. in a cluster of A,B,C,D; C can be suspected if (note "
-"that A pings B, B pings C, C pings D and D pings A):"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2715
-#, no-c-format
-msgid ""
-"B or C are running at 100% CPU for more than T seconds. So even if C sends a "
-"heartbeat ack to B, B may not be able to process it because it is at 100%"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2720
-#, no-c-format
-msgid "B or C are garbage collecting, same as above."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2725
-#, no-c-format
-msgid "A combination of the 2 cases above"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2730
-#, no-c-format
-msgid ""
-"The network loses packets. This usually happens when there is a lot of "
-"traffic on the network, and the switch starts dropping packets (usually "
-"broadcasts first, then IP multicasts, TCP packets last)."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2735
-#, no-c-format
-msgid ""
-"B or C are processing a callback. Let's say C received a remote method call "
-"over its channel and takes T+1 seconds to process it. During this time, C "
-"will not process any other messages, including heartbeats, and therefore B "
-"will not receive the heartbeat ack and will suspect C."
-msgstr ""
-
More information about the jboss-cvs-commits
mailing list