[jboss-cvs] JBossAS SVN: r84284 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/de-DE.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Feb 16 19:26:29 EST 2009
Author: xhuang at jboss.com
Date: 2009-02-16 19:26:28 -0500 (Mon, 16 Feb 2009)
New Revision: 84284
Removed:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/de-DE/Clustering_Guide_Introduction.po
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/de-DE/Clustering_Intro.po
Log:
update
Deleted: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/de-DE/Clustering_Guide_Introduction.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/de-DE/Clustering_Guide_Introduction.po 2009-02-17 00:26:09 UTC (rev 84283)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/de-DE/Clustering_Guide_Introduction.po 2009-02-17 00:26:28 UTC (rev 84284)
@@ -1,9648 +0,0 @@
-# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
-# Automatically generated, 2007.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: JBEAP 420\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:5
-#, no-c-format
-msgid "Clustering"
-msgstr "Clustering"
-
-#. Tag: subtitle
-#: Clustering_Guide_Introduction.xml:6
-#, no-c-format
-msgid "High Availability Enterprise Services via JBoss Clusters"
-msgstr "Hohe Verfügbarkeit von Unternehmensleistungen mit JBoss Clusters"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:9
-#, no-c-format
-msgid "Introduction"
-msgstr "Einführung"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:10
-#, fuzzy, 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 ""
-"Mit Clustering (\"Gruppierung\") ist die Ausführung einer Anwendung auf "
-"mehreren parallel laufenden Servern (sog. \"Cluster-Nodes\" oder \"Cluster-"
-"Knoten\") möglich. Die Auslastung wird dabei auf verschiedene Server "
-"verteilt, und selbst falls es zu einer Störung auf einem der Server kommt, "
-"ist die Anwendung über andere Cluster-Nodes nach wie vor zugänglich. "
-"Clustering ist von maßgeblicher Bedeutung für die Anwendungen eines "
-"Unternehmens, da die Leistung ganz bequem durch Hinzufügen weiterer Nodes "
-"(\"Knoten\") zum Cluster erhöht werden kann."
-
-#. 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 ""
-"Der JBoss Applikationsserver (AS) bietet hervorragenden Clustering Support. "
-"Die einfachste Art einen JBoss Server-Cluster zu starten ist, mehrere JBoss "
-"Instanzen auf demselben lokalen Netzwerk mit dem <literal>run -c all</"
-"literal>-Befehl für jede der Instanzen zu starten. Alle in der <literal>all</"
-"literal>-Konfiguration gestarteten Serverinstanzen erkennen einander und "
-"bilden automatisch ein Cluster."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:17
-#, fuzzy, 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 ""
-"Im ersten Kapitel werden die Grundkonzepte der JBoss Clustering-Dienste "
-"erörtert. Es ist wichtig, dass Sie diese verstehen, ehe Sie die übrigen "
-"Kapitel lesen. Clustering-Konfigurationen für spezifische Anwendungstypen "
-"werden nach diesem Abschnitt behandelt."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:23
-#, no-c-format
-msgid "Cluster Definition"
-msgstr "Definition des Begriffs \"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 "Cluster und Server Nodes"
-
-#. 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 ""
-
-#. 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
-#, fuzzy, 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 ""
-"Das folgende Beispiel zeigt die in der Standard JBoss AS Distribution "
-"verpackte MBean-Definition. Falls Sie also JBoss Server mit den Standard "
-"Clustering-Einstellungen auf einem lokalen Netzwerk starten, so erhalten Sie "
-"einen Standard-Cluster mit dem Namen <literal>DefaultPartition</literal>, "
-"der alle Server-Instanzen sowie deren Nodes enthält."
-
-#. 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"
-" <! -- 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>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:63
-#, fuzzy, 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 ""
-"Hier haben wir die detaillierte JGroups Protokoll-Konfiguration für diesen "
-"Cluster weggelassen. JGroups erledigt die zu Grunde liegende Peer-to-Peer-"
-"Kommunikation zwischen Nodes, wobei die betreffende Konfiguration in <xref "
-"linkend=\"jbosscache-jgroups\"/> behandelt wird. Die folgende Liste stellt "
-"die verfügbaren Konfigurationseigenschaften im <literal>ClusterPartition</"
-"literal>-MBean dar."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:68
-#, fuzzy, 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 ""
-"Bei <emphasis role=\"bold\">PartitionName</emphasis> handelt es sich um ein "
-"optionales Merkmal, das den Namen des Clusters festlegt. Der voreingestellte "
-"Wert lautet hier <literal>DefaultPartition</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:72
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">NodeAddress</emphasis> is an optional attribute used "
-"to help generate a unique name for this node."
-msgstr ""
-"Bei <emphasis role=\"bold\">NodeAddress</emphasis> handelt es sich um ein "
-"optionales Merkmal, um die \"Binding-IP-Adresse\" (d.h. die zugewiesene IP-"
-"Adresse) dieses Nodes festzulegen. "
-
-#. 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 ""
-"Bei <emphasis role=\"bold\">DeadlockDetection</emphasis> handelt es sich um "
-"ein optionales boolesches Merkmal, das JGroups mitteilt, dass bei jeder "
-"Anfrage \"Message Deadlock Detection\"-Algorithmen (Deadlockerkennung) "
-"ausgeführt werden sollen. Der voreingestellte Wert lautet hier "
-"<literal>false</literal>."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:80
-#, fuzzy, 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 ""
-"Bei <emphasis role=\"bold\">StateTransferTimeout</emphasis> handelt es sich "
-"um ein optionales Merkmal mit dem der Timeout für die \"State Replication"
-"\" (Statusreplikation) am Cluster (in Millisekunden) festgelegt wird. Der "
-"voreingestellte Wert lautet hier <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 ""
-"Bei <emphasis role=\"bold\">PartitionConfig</emphasis> handelt es sich um "
-"ein Element, das JGroups Konfigurationsoptionen für diesen Cluster (siehe "
-"<xref linkend=\"jbosscache-jgroups\"/>) festlegt."
-
-#. 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
-#, fuzzy, 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 ""
-"Sie können die aktuellen Cluster-Informationen einsehen, indem Sie in Ihrem "
-"Browser die JMX-Konsole einer JBoss Instanz im Cluster aufrufen (z.B. "
-"<literal>http://hostname:8080/jmx-console/</literal>) und dann auf das "
-"<literal>jboss:service=DefaultPartition</literal>-MBean klicken (ändern Sie "
-"den Namen des MBean in den Ihres Clusters, falls dieser Node sich nicht "
-"<literal>DefaultPartition</literal>) anschließt. Eine Liste von IP-Adressen "
-"für die aktuellen Cluster-Members wird im <literal>CurrentView</literal>-"
-"Feld angezeigt."
-
-#. 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
-#, fuzzy, no-c-format
-msgid "Note"
-msgstr "Anmerkungen"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:95
-#, fuzzy, 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 ""
-"Zwar ist es von einem technischen Standpunkt aus betrachtet durchaus "
-"möglich, eine JBoss Server-Instanz gleichzeitig auf mehrere Cluster zu "
-"verteilen, wird aber nicht empfohlen, da es die Verwaltung erschwert."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:101
-#, no-c-format
-msgid "JBoss Cache channels"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:102
-#, fuzzy, 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 ""
-"Beim JBoss Cache handelt es sich um ein vollständig verteiltes Cache-"
-"Framework, das in einer beliebigen Applikationsserver-Umgebung und "
-"eigenständig verwendet werden kann. Es ersetzt schrittweise den "
-"<literal>HASessionState</literal>-Dienst. Der JBoss AS integriert das JBoss "
-"Cache um Cachedienste für HTTP-Sessions, EJB 3.0-Sessions und Entity-Beans "
-"sowie \"Hibernate Persistence Objects\". Jeder dieser Cachedienste ist in "
-"einem separaten MBean definiert. Wir gehen näher auf diese MBeans ein, wenn "
-"wir in den folgenden Abschnitten spezielle Dienste behandeln."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:107
-#, no-c-format
-msgid "Service Architectures"
-msgstr "Service-Architekturen"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:108
-#, fuzzy, 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 ""
-"Die vom <literal>ClusterPartition</literal>-MBean definierte Clustering "
-"Topographie auf den einzelnen Nodes ist in erster Linie für System-"
-"Administratoren von Bedeutung. Für die meisten Anwendungsentwickler ist "
-"jedoch wahrscheinlich die Cluster-Architektur aus Perspektive der Client-"
-"Applikationen wichtiger. JBoss AS unterstützt zwei Arten von Clustering-"
-"Architekturen: Clientbasierte Interceptoren (auch: Proxies oder Stubs) und "
-"Lastverteiler."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:114 Clustering_Guide_Introduction.xml:160
-#, fuzzy, no-c-format
-msgid "Client-side interceptor architecture"
-msgstr "Clientbasierte Interceptoren"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:115
-#, fuzzy, 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 ""
-"Bei den meisten vom JBoss Applikationsserver bereit gestellten Möglichkeiten "
-"der Fernwartung, einschließlich JNDI, EJB, RMI und JBoss Remoting, muss der "
-"Client (etwa durch Look-up und Download) ein Stub (oder Proxy) Objekt "
-"erhalten. Das Stub-Objekt wird vom Server generiert und implementiert die "
-"Unternehmensschnittstelle des Dienstes. Durch den Client erfolgt dann ein "
-"lokaler Methodenaufruf an das Stub-Objekt. Der Aufruf wird automatisch über "
-"das Netzwerk weitergeleitet und gegen vom Server verwaltete Serviceobjekte "
-"abgerufen. In einer Clustering-Umgebung ist das vom Server generierte Stub-"
-"Objekt auch ein Interceptor, der Signale an die Nodes innerhalb des Clusters "
-"weiterleitet. Das Stub-Objekt findet heraus, wie es den passenden Server-"
-"Node findet, ordnet die Aufrufparameter, sortiert die Aufrufergebnisse und "
-"sendet die Ergebnisse zurück an den Client."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:120
-#, fuzzy, 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 ""
-"Die Stub-Interceptoren verfügen über aktualisierte Informationen zum "
-"Cluster. Sie kennen zum Beispiel die IP-Adressen sämtlicher verfügbarer "
-"Server-Nodes, den Algorithmus zur Verteilung der Auslastung auf die Nodes "
-"(siehe nächster Abschnitt) sowie den notwendigen Anfragen-Failover, falls "
-"der Zielnode nicht verfügbar ist. Mit jeder Service-Anfrage aktualisiert der "
-"Server-Node den Stub-Interceptor im Hinblick auf die neuesten Veränderungen "
-"am Cluster. Wenn zum Beispiel einer der Nodes des Clusters ausfällt, wird "
-"jeder Client-Stub-Interceptor mit der neuen Konfiguration aktualisiert und "
-"verbindet sich beim nächsten Mal mit einem aktiven Node im Cluster. Alle "
-"Veränderungen am Service-Stub sind transparent und von der Client-"
-"Applikation erkennbar. Die clientbasierte Clustering-Architektur des "
-"Interceptors ist in <xref linkend=\"clustering-InterceptorArch.fig\"/> "
-"dargestellt."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:123
-#, no-c-format
-msgid "The client-side interceptor (proxy) architecture for clustering"
-msgstr "Die clientbasierte Interceptor (Proxy) Clustering-Architektur"
-
-#. 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 ""
-"beschreibt, wie man den Client Proxy aktiviert, damit er den kompletten "
-"Cluster-Neustart abwickelt."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:136
-#, no-c-format
-msgid "Load balancer"
-msgstr "Der Lastverteiler"
-
-#. 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 ""
-"Andere JBoss Dienste, insbesondere die HTTP-Webdienste, erfordern keine "
-"Downloads durch den Client. Der Client (z.B. ein Webbrowser) schickt "
-"Anfragen und erhält gemäß bestimmter Kommunikationsprotokolle Rückmeldung (z."
-"B. das HTTP-Protokoll) direkt über die Leitung. In diesem Fall wird ein "
-"Lastverteiler benötigt, um alle Anfragen zu bearbeiten und sie an die Server-"
-"Nodes im Cluster zu versenden. Der Lastverteiler ist normalerweise Teil des "
-"Clusters. Er erfasst sowohl die Cluster-Konfiguration als auch die Failover-"
-"Systemrichtlinien. Für den Client ist jedoch lediglich der Lastverteiler von "
-"Interesse. Die Cluster-Architektur des Lastverteilers ist in <xref linkend="
-"\"clustering-BalancerArch.fig\"/> dargestellt."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:141
-#, fuzzy, no-c-format
-msgid "The external load balancer architecture for clustering"
-msgstr "Die Lastverteiler-Architektur für das Clustering"
-
-#. 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 ""
-"Ein potenzielles Problem bei der Lastverteiler-Variante ist die Möglichkeit, "
-"dass der Lastverteiler selbst eine mögliche Fehlerquelle ist. Er sollte "
-"daher genau kontrolliert werden, um sicherzustellen, dass sämtliche Cluster-"
-"Dienste verfügbar sind."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:155
-#, no-c-format
-msgid "Load-Balancing Policies"
-msgstr "Systemrichtlinien der Lastverteilung"
-
-#. 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 ""
-"Sowohl der JBoss clientbasierte Interceptor (Stub) als auch der "
-"Lastverteiler befolgen bei der Lastverteilung Systemrichtlinien, um zu "
-"bestimmen, an welchen Server-Node eine neue Anfrage weitergeleitet wird. In "
-"diesem Abschnitt behandeln wir die Systemrichtlinien der Lastverteilung im "
-"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>): Jede Anfrage wird an einen neuen Node verschickt. Der erste Node "
-"wird zufällig von der Liste ausgewählt."
-
-#. 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>): Jede Anfrage wird an einen neuen Node verschickt. Der erste Node "
-"wird zufällig von der Liste ausgewählt."
-
-#. 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 ""
-"First Available (<literal>org.jboss.ha.framework.interfaces.FirstAvailable</"
-"literal>): Einer der verfügbaren Ziel-Nodes wird als Hauptziel ausgewählt "
-"und für jeden Aufruf verwendet: Das gewählte Element wird zufällig aus der "
-"Liste der Clusterelemente ausgewählt. Wenn die Liste von Ziel-Nodes sich "
-"verändert (weil ein Node hinzukommt oder wegfällt), wird die Richtlinie "
-"(auch: \"Policy\") einen anderen Ziel-Node auswählen, falls der aktuell "
-"gewählte Node nicht doch noch verfügbar ist. Jeder clientbasierte "
-"Interceptor oder Lastverteiler wählt unabhängig von den anderen Proxies "
-"seinen eigenen Ziel-Node."
-
-#. 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 ""
-"Die dritte, neue Möglichkeit der Lastverteilung in JBoss 3.2 ist \"First "
-"AvailableIdenticalAllProxies\" (<literal>org.jboss.ha.framework.interfaces."
-"FirstAvailableIdenticalAllProxies</literal>). Sie folgt denselben Regeln wie "
-"die \"First Available\"-Richtlinie, aber der gewählte Ziel-Node wird von "
-"allen clientbasierten Interceptoren derselben Familie (\"family\") geteilt."
-
-#. 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
-#, fuzzy, no-c-format
-msgid "External load balancer architecture"
-msgstr "Die Lastverteiler-Architektur für das Clustering"
-
-#. 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 "Das Farming-Deployment"
-
-#. 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 ""
-"Das Farming ist in der <literal>all</literal>-Konfiguration von JBoss AS-"
-"Distributionen voreingestellt, so dass Sie es nicht selbst einstellen "
-"müssen. Die Konfigurationsdatei befindet sich im Verzeichnis <literal>deploy/"
-"deploy.last</literal>. Falls Sie das Farming in Ihrer individuellen "
-"Konfiguration aktivieren möchten, erstellen Sie einfach die nachfolgend "
-"dargestellte XML-Datei (nennen Sie diese <literal>farm-service.xml</"
-"literal>), und kopieren Sie sie in das JBoss Deploy-Verzeichnis <literal>"
-"$JBOSS_HOME/server/your_own_config/deploy</literal>. Vergewissern Sie sich, "
-"dass in Ihrer Konfiguration das Clustering aktiviert ist."
-
-#. 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 ""
-"Nachdem Sie <literal>farm-service.xml</literal> eingerichtet haben, kann es "
-"losgehen. Die benötigten <literal>FarmMemberService</literal> MBean-"
-"Attribute zur Konfiguration einer Farm sind nachfolgend aufgeführt."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:232
-#, fuzzy, 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"
-" <attribute name=\"PartitionName\">DefaultPartition</"
-"attribute> \n"
-" <attribute name=\"ScanPeriod\">5000</attribute> \n"
-" <attribute name=\"URLs\">farm/</attribute> \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 ""
-"Bei <emphasis role=\"bold\">PartitionName</emphasis> handelt es sich um ein "
-"optionales Merkmal, das den Namen des Clusters festlegt. Der voreingestellte "
-"Wert lautet hier <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> weist auf das Verzeichnis, in dem "
-"der Deployer das Deployment der Dateien überwacht. Falls es nicht bereits "
-"existiert, so erstellt das MBean dieses Verzeichnis. Auch \".\" bezieht sich "
-"auf das Konfigurationsverzeichnis (d.h. <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 ""
-"Die <emphasis role=\"bold\">ScanPeriod</emphasis> legt den Intervall fest, "
-"in dem der Ordner nach Veränderungen durchsucht wird. Der voreingestellte "
-"Wert beträgt hier <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 ""
-"Beim Farming Service handelt es sich um eine Erweiterung des "
-"<literal>URLDeploymentScanner</literal>, der das <literal>deploy/</literal>-"
-"Verzeichnis nach Hot Deployments durchsucht. Sie können also alle im "
-"<literal>URLDeploymentScanner</literal>-MBean im <literal>FarmMemberService</"
-"literal>-MBean definierten Attribute verwenden. Tatsächlich sind die oben "
-"angeführten <literal>URLs</literal> und <literal>ScanPeriod</literal>-"
-"Attribute vom <literal>URLDeploymentScanner</literal>-MBean übernommen."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:258
-#, no-c-format
-msgid "Distributed state replication services"
-msgstr ""
-"Verteilte Dienste zur Statusreplikation (\"State Replication Services\")"
-
-#. 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 ""
-"In einer geclusterten Serverumgebung ist das verteilte Status-Management "
-"einer der Schlüsseldienste, den der Cluster liefern muss. So muss zum "
-"Beispiel in einer \"Stateful Session Bean\"-Applikation, der Session-Status "
-"aller Bean-Instanzen in sämtlichen Nodes synchronisiert werden, damit die "
-"Client-Applikation denselben Session-Status erreicht, ganz unabhängig davon, "
-"welcher Node die Anfrage bearbeitet. Bei einer Entity-Bean-Applikation ist "
-"es manchmal notwendig, das Bean-Objekt in den Cachespeicher des Clusters "
-"aufzunehmen, um die Auslastung der Datenbank zu reduzieren. Aktuell werden "
-"die Statusreplikation und die verteilten Cachedienste im JBoss AS auf zwei "
-"Arten bereit gestellt: Dem <literal>HASessionState</literal>-MBean und dem "
-"JBoss Cache-Framework."
-
-#. 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 ""
-"Das <literal>HASessionState</literal>-MBean liefert Sessionreplikation und "
-"verteilte Cachedienste für EJB 2.x Stateful Session Beans und HTTP-"
-"Lastverteiler in JBoss 3.x and 4.x. Das MBean ist in der <literal>all/deploy/"
-"cluster-service.xml</literal>-Datei definiert. Die Konfigurationsoptionen "
-"werden später - im Abschnitt zum EJB 2.x Stateful Session Bean - behandelt."
-
-#. 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 "Geclusterte JNDI-Dienste"
-
-#. 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 ""
-
-#. 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 "Und so funktioniert es"
-
-#. 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 ""
-"Der JBoss HA-JNDI (\"High Availability JNDI\") Dienst wartet einen "
-"clusterweiten Context-Tree (\"Context-Verzeichnisbaum\"). Der clusterweite "
-"Tree ist verfügbar, so lange mindestens ein Node im Cluster vorhanden ist. "
-"Jeder JNDI-Node im Cluster besitzt außerdem seinen eigenen lokalen JNDI-"
-"Context. Die serverseitige Anwendung kann ihre Objekte an beide Trees "
-"binden. In diesem Abschnitt erläutern wir die Unterschiede der beiden Trees "
-"und die besten Verfahren bei der Anwendungsentwicklung. Die "
-"Entwurfsprinzipien dieser Architektur lauten wie folgt:"
-
-#. 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 ""
-"Durch Anwendungen, die voraussetzen, dass ihre JNDI-Implementierung lokal "
-"erfolgt, kann es zu Schwierigkeiten bei der Migration kommen. Unser Ziel war "
-"es jedoch, hervorragendes Clustering zu ermöglichen, bei dem nur ein paar "
-"Anpassungen in den Konfigurationsdateien erforderlich sind."
-
-#. 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 ""
-"In einem homogenen Cluster reduziert diese Konfiguration die Menge an "
-"Netzwerkverkehr."
-
-#. 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 ""
-"Aufgrund dieses Entwurfs ist der HA-JNDI Service ein optionaler Dienst, da "
-"alle zu Grunde liegenden Clustercodes einen neuen <literal>InitialContext()</"
-"literal> verwendet, um Bindings zu suchen oder zu erstellen."
-
-#. 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 ""
-"Auf der Serverseite wird der neue <literal>new InitialContext()</literal> in "
-"einen ausschließlich lokalen, nicht clusterweiten JNDI-Context eingebunden "
-"(es handelt sich dabei um elementares JNDI). Sämtliche EJB-Homes werden "
-"nicht in den clusterweiten JNDI-Context eingebunden, sondern jedes Home wird "
-"in die lokale JNDI eingebunden. Wenn ein Remote Client eine Suche mittels HA-"
-"JNDI durchführt, so sendet HA-JNDI zum lokalen JNDI-Context, wenn es das "
-"Objekt im globalen, clusterweiten Context nicht findet. Die genau Lookup-"
-"Regel lautet wie folgt. "
-
-#. 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
-#, fuzzy, no-c-format
-msgid "If the binding is available in the cluster-wide JNDI tree, return it."
-msgstr ""
-"Falls das Binding im clusterweiten JNDI-Tree verfügbar ist und es "
-"beantwortet."
-
-#. 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 ""
-"Falls das Binding im clusterweiten Tree nicht verfügbar ist, sendet es die "
-"Lookup-Anfrage an den lokalen JNDI Dienst und schickt die erhaltene Antwort "
-"(falls verfügbar) zurück."
-
-#. 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 ""
-"Falls keine Antowert verfügbar ist, fragt der HA-JNDI Dienst bei allen "
-"anderen Nodes im Cluster an, ob deren lokaler JNDI-Dienst über ein solches "
-"Binding verfügt und schickt die erhaltene Antwort zurück."
-
-#. 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 ""
-"Falls kein lokaler JNDI-Dienst ein solches Binding besitzt, erscheint "
-"schließlich die Meldung <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 ""
-"Ein EJB-Home-Lookup mittels HA-JNDI wird also immer an die lokale JNDI-"
-"Instanz weitergeleitet. Falls unterschiedliche Beans (auch wenn sie zu "
-"demselben Bean-Typ gehören, jedoch Teil verschiedener Cluster sind) "
-"denselben JNDI-Namen verwenden, so bedeutet dies, dass jeder JNDI-Server "
-"eine andere \"Target\"-Verbindung hat (JNDI an Node 1 besitzt ein Binding "
-"für Bean A und JNDI wird ein Binding desselben Namens an Node 2 für Bean B "
-"besitzen). Wenn folglich ein Client eine HA-JNDI Anfrage für diesen Namen "
-"durchführt, wird diese an einem beliebigen JNDI-Server des Clusters "
-"aufgerufen und zum lokal gebundenen Stub zurückgeschickt. Dennoch ist es "
-"möglich, dass es sich dabei nicht um den korrekten Stub handelt, den der "
-"Client zu erhalten erwartet!"
-
-#. 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 ""
-"Wenn Sie HA-JNDI verwenden möchten, können Sie zur Zeit keine nicht-JNP JNDI "
-"Implementierung (d.h. LDAP) für Ihre lokale JNDI-Implementierung benutzen. "
-"Sie können jedoch JNDI-Federation mit dem <literal>ExternalContext</literal>-"
-"MBean verwenden, um nicht-JBoss JNDI-Trees in den JBoss JNDI-Namespace "
-"(\"Namensraum\") einzubinden. Desweiteren können Sie einen zentralisierten "
-"JNDI-Server für Ihren gesamten Cluster einsetzen und anstelle von HA-JNDI "
-"und JNP verwenden."
-
-#. 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 ""
-"Falls ein Binding nur an wenigen Nodes des Clusters verfügbar ist (z.B. weil "
-"ein Bean nur an einem kleinen Teilsatz von Nodes im Cluster deployt wird), "
-"ist die Wahrscheinlichkeit einen HA-JNDI Server zu finden, der dieses "
-"Binding nicht besitzt höher, und der Lookup wird an alle Nodes im Cluster "
-"weitergeleitet werden müssen. Die Anfrage wird folglich mehr Zeit "
-"beanspruchen als wenn das Binding lokal verfügbar gewesen wäre. Es ist daher "
-"sinnvoll, die Ergebnisse Ihrer JNDI-Anfragen möglichst oft in Ihrem Client "
-"zu speichern."
-
-#. 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 ""
-"Ein EJB-Home-Lookup mittels HA-JNDI wird also immer an die lokale JNDI-"
-"Instanz weitergeleitet. Falls unterschiedliche Beans (auch wenn sie zu "
-"demselben Bean-Typ gehören, jedoch Teil verschiedener Cluster sind) "
-"denselben JNDI-Namen verwenden, so bedeutet dies, dass jeder JNDI-Server "
-"eine andere \"Target\"-Verbindung hat (JNDI an Node 1 besitzt ein Binding "
-"für Bean A und JNDI wird ein Binding desselben Namens an Node 2 für Bean B "
-"besitzen). Wenn folglich ein Client eine HA-JNDI Anfrage für diesen Namen "
-"durchführt, wird diese an einem beliebigen JNDI-Server des Clusters "
-"aufgerufen und zum lokal gebundenen Stub zurückgeschickt. Dennoch ist es "
-"möglich, dass es sich dabei nicht um den korrekten Stub handelt, den der "
-"Client zu erhalten erwartet!"
-
-#. 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 ""
-"Wenn Sie HA-JNDI verwenden möchten, können Sie zur Zeit keine nicht-JNP JNDI "
-"Implementierung (d.h. LDAP) für Ihre lokale JNDI-Implementierung benutzen. "
-"Sie können jedoch JNDI-Federation mit dem <literal>ExternalContext</literal>-"
-"MBean verwenden, um nicht-JBoss JNDI-Trees in den JBoss JNDI-Namespace "
-"(\"Namensraum\") einzubinden. Desweiteren können Sie einen zentralisierten "
-"JNDI-Server für Ihren gesamten Cluster einsetzen und anstelle von HA-JNDI "
-"und JNP verwenden."
-
-#. 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 ""
-"Falls ein Binding nur an wenigen Nodes des Clusters verfügbar ist (z.B. weil "
-"ein Bean nur an einem kleinen Teilsatz von Nodes im Cluster deployt wird), "
-"ist die Wahrscheinlichkeit einen HA-JNDI Server zu finden, der dieses "
-"Binding nicht besitzt höher, und der Lookup wird an alle Nodes im Cluster "
-"weitergeleitet werden müssen. Die Anfrage wird folglich mehr Zeit "
-"beanspruchen als wenn das Binding lokal verfügbar gewesen wäre. Es ist daher "
-"sinnvoll, die Ergebnisse Ihrer JNDI-Anfragen möglichst oft in Ihrem Client "
-"zu speichern."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:447
-#, no-c-format
-msgid "Client configuration"
-msgstr "Die Client-Konfiguration"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:449
-#, no-c-format
-msgid "For clients running inside the application server"
-msgstr ""
-
-#. 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 ""
-"Falls Sie von Serverseite auf HA-JNDI zugreifen möchten, müssen Sie einen "
-"eindeutigen <literal>InitialContext</literal> erhalten, indem Sie JNDI "
-"Eigenschaften einreichen. Der folgende Code zeigt Ihnen, wie Sie auf den HA-"
-"JNDI zugreifen."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:453
-#, fuzzy, 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 ""
-"Die <literal>Context.PROVIDER_URL</literal>-Property zeigt auf den im "
-"<literal>HANamingService</literal>-MBean (siehe <xref linkend=\"clustering-"
-"jndi-jboss\"/>) konfigurierten HA-JNDI-Dienst."
-
-#. 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 ""
-
-#. 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 ""
-"Der JNDI-Client muss Kenntnis vom HA-JNDI Cluster haben. Sie können eine "
-"Auflistung der JNDI-Server (d.h. den Nodes im HA-JNDI Cluster) an "
-"die<literal>java.naming.provider.url</literal> JNDI-Einstellung der "
-"<literal>jndi.properties</literal>-Datei senden. Jeder Server-Node wird "
-"anhand seiner IP-Adresse und der JNDI-Portnummer identifiziert. Die "
-"einzelnen Server-Nodes sind durch Kommas getrennt (siehe <xref linkend="
-"\"clustering-jndi-jboss\"/> zur Konfiguration von Servern und Ports)."
-
-#. 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 ""
-"Bei der Initialisierung versucht der JNP-Client Code mit jedem der "
-"gelisteten Server-Nodes in Verbindung zu treten. Er probiert dies bei einem "
-"nach dem anderen bis er einen der Server erreicht hat. Anschließend lädt er "
-"den HA-JNDI Stub dieses Nodes herunter."
-
-#. 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 ""
-"Beim JNP Client Lookup-Prozess wird keine Lastverteilung verwendet. Die "
-"Providerliste wird einfach durchgegangen und der erste verfügbare Server "
-"benutzt. Die HA-JNDI Providerliste muss lediglich einen Teilsatz von HA-JNDI "
-"Nodes im Cluster enthalten."
-
-#. 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 ""
-"Der heruntergeladene \"Smart-Stub\" beinhaltet die Logik, um im Problemfall "
-"auf andere Server auszuweichen und auch um seine Liste der im Cluster "
-"aktiven Rechner zu aktualisieren. Desweiteren wird jedes Mal wenn ein JNDI-"
-"Aufruf beim Server eingeht die Liste der Targets im Stub-Interceptor "
-"aktualisiert (jedoch nur wenn sich die Liste seit dem letzten Aufruf "
-"verändert hat)."
-
-#. 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 ""
-"Falls der Property String (Eigenschaftswert) <literal>java.naming.provider."
-"url</literal> leer ist oder keiner der aufgeführten Server erreichbar ist, "
-"versucht der JNP-Client mittels Multicast-Call am Netzwerk (Auto-Discovery) "
-"einen Bootstrap HA-JNDI Server zu finden. Zur Konfiguration von Auto-"
-"Discovery auf den JNDI Server-Nodes siehe <xref linkend=\"clustering-jndi-"
-"jboss\"/>. Mit Auto-Discovery ist es möglich, dass der Client einen gültigen "
-"HA-JNDI Server-Node ohne Konfiguration findet. Natürlich muss der Client "
-"sich innerhalb derselben LAN wie der Server-Cluster befinden, damit Auto-"
-"Discovery funktioniert (z.B. die Web-Servlets verwenden die EJB-Server). "
-"Auch muss LAN oder WAN so konfiguriert sein, dass derartige Multicast-"
-"Datagramme fortgepflanzt werden."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:484
-#, fuzzy, no-c-format
-msgid ""
-"By default the auto-discovery feature uses multicast group address 230.0.0.4 "
-"and port1102."
-msgstr ""
-"Das Auto-Discovery Feature verwendet die Multicast-Gruppenadresse "
-"230.0.0.4:1102."
-
-#. 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 ""
-"Neben der <literal>java.naming.provier.url</literal>-Property können Sie "
-"auch einen Satz anderer Properties festlegen. Die folgende Liste zeigt alle "
-"clientbasierten Properties, die Sie bei der Erstellung eines neuen "
-"<literal>InitialContext</literal> festlegen können."
-
-#. 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>: Liefert eine Liste von IP-"
-"Adressen und Portnummern für HA-JNDI Provider-Nodes im Cluster. Der Client "
-"probiert diese Provider einen nach dem anderen ducrh und verwendet den "
-"zuerst reagierenden."
-
-#. 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>: Wenn die Einstellung <literal>true</"
-"literal> vorliegt, deaktiviert diese Property das Automatic-Discovery-"
-"Feature. Der voreingestellte Wert lautet <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>: In einer Umgebung, in der mehrere, an "
-"eindeutige Cluster (d.h. Partitionen) gebundene HA-JNDI-Dienste gestartet "
-"werden, haben Sie mit dieser Property die Möglichkeit zu konfigurieren, "
-"welchen Cluster Sie bei Benutzung des Automatic-Discovery Features aufrufen. "
-"Falls Sie das Automatic-Discovery Feature verwenden (wenn Sie z.B. eine "
-"eindeutige Liste gültiger JNDI-Nodes in <literal>java.naming.provider.url</"
-"literal> eingeben), so wird diese Property nicht benutzt. Diese Property ist "
-"nicht als Standard eingestellt, und Automatic-Discovery wählt den ersten HA-"
-"JNDI Server der reagiert, ganz unabhängig vom Partitionsnamen des Clusters."
-
-#. 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>: Bestimmt, wie lange der Context auf "
-"Antwort auf sein Automatic-Discovery-Packet wartet. Der voreingestellte Wert "
-"ist 5000 ms."
-
-#. 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>: Bestimmt, welche Multicast-"
-"Gruppenadresse für Automatic-Discovery verwendet wird. Der voreingestellte "
-"Wert ist <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>: Bestimmt welcher Multicast-Gruppenport "
-"für Automatic-Discovery verwendet wird. Der voreingestellte Wert ist "
-"<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 "Die JBoss-Konfiguration"
-
-#. 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 ""
-"Die <literal>cluster-service.xml</literal> Datei im <literal>all/deploy</"
-"literal>-Verzeichnis enthält das folgende MBean zur Aktivierung von HA-NDI "
-"Diensten."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:526
-#, fuzzy, 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>jboss:service=DefaultPartition</depends> \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 ""
-"Sie können sehen, dass dieses MBean vom <literal>DefaultPartition</literal>-"
-"MBean, das über ihm definiert ist (wie in einem vorhergehenden Abschnitt "
-"dieses Kapitels erläutert) abhängt. In anderen Konfigurationen können Sie "
-"dieses Element in die <literal>jboss-services.xml</literal>-Datei oder eine "
-"andere JBoss Konfigurationsdatei im <literal>/deploy</literal>-Verzeichnis "
-"ablegen, um HA-JNDI Dienste zu aktivieren. Die verfügbaren Attribute für "
-"dieses MBean sind unten aufgeführt."
-
-#. 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 ""
-"Bei <emphasis role=\"bold\">PartitionName</emphasis> handelt es sich um ein "
-"optionales Merkmal, das den Namen des Clusters festlegt. Der voreingestellte "
-"Wert lautet hier <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 ""
-"Bei <emphasis role=\"bold\">BindAddress</emphasis> handelt es sich um ein "
-"optionales Attribut zur Bestimmung der Adresse mit der sich der HA-JNDI "
-"Server verbindet, während er auf JNP-Clients wartet. Dies ist nur bei "
-"\"Multi-Home\"-Computern sinnvoll."
-
-#. 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 ""
-"Bei <emphasis role=\"bold\">Port</emphasis> handelt es sich um ein "
-"optionales Attribut mit dem der Port festgelegt wird, mit dem sich der HA-"
-"JNDI Server verbindet, während er auf JNP-Clients wartet. Die "
-"Standardeinstellung lautet <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 ""
-"Bei <emphasis role=\"bold\">Backlog</emphasis> handelt es sich um ein "
-"optionales Attribut zur Bestimmung des \"Backlog\"-Werts (auch: "
-"Verarbeitungsrückstandswert), der für das TCP-Server-Socket verwendet wird, "
-"während es auf JNP-Clients wartet. Die Standardeinstellung lautet "
-"<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> bestimmt, welchen Port der Server "
-"bei der Kommunikation mit dem heruntergeladenen Stub verwendet. Dieses "
-"Attribut ist optional. Falls es fehlt, ordnet der Server automatisch einen "
-"RMI-Port zu."
-
-#. 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 ""
-"Bei <emphasis role=\"bold\">DiscoveryDisabled</emphasis> handelt es sich um "
-"ein boolesches Flag, das die Konfiguration des Auto-Discovery Multicast-"
-"Listeners deaktiviert."
-
-#. 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 ""
-"Bei <emphasis role=\"bold\">AutoDiscoveryAddress</emphasis> handelt es sich "
-"um ein optionales Attribut zur Bestimmung der Multicast-Adresse für JNDI-"
-"Automatic-Discovery. Die Standardeinstellung lautet <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 ""
-"Bei <emphasis role=\"bold\">AutoDiscoveryGroup</emphasis> handelt es sich um "
-"ein optionales Attribut zur Bestimmung der Multicast-Gruppe für JNDI-"
-"Automatic-Discovery. Die Standardeinstellung lautet <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> setzt die Auto-"
-"Discovery Bootstrap-Multicast-Bind-Adresse. Falls dieses Attribut nicht "
-"bestimmt ist, jedoch eine <literal>BindAddress</literal> festgelegt wurde, "
-"so wird die <literal>BindAddress</literal> verwendet."
-
-#. 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> bestimmt den Thread-Pool-"
-"Dienst, der für die Steuerung von Bootstrap und Auto-Discovery-Lookups "
-"verwendet wird."
-
-#. 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 ""
-"Die komplette Standardeinstellung des <literal>HANamingService</literal>-"
-"MBeans lautet wie folgt."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:584
-#, fuzzy, 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 ""
-"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
-" name=\"jboss:service=HAJNDI\"> \n"
-" <depends>\n"
-" jboss:service=${jboss.partition.name:DefaultPartition}\n"
-" </depends> \n"
-" <! -- Name of the partition to which the service is linked --> \n"
-" <attribute name=\"PartitionName\">\n"
-" ${jboss.partition.name:DefaultPartition}\n"
-" </attribute> \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. \n"
-" 0 is for 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 \n"
-" auto discovery lookups --> \n"
-" <depends optional-attribute-name=\"LookupPool\" \n"
-" proxy-type=\"attribute\">jboss.system:service=ThreadPool</"
-"depends>\n"
-"\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. --"
-"> \n"
-" <attribute name=\"AutoDiscoveryBindAddress\">\n"
-" ${jboss.bind.address}\n"
-" </attribute> \n"
-" \n"
-" <! -- Multicast Address and group port used for auto-discovery --"
-"> \n"
-" <attribute name=\"AutoDiscoveryAddress\">\n"
-" ${jboss.partition.udpGroup:230.0.0.4}\n"
-" </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"
-"\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 ""
-"Es ist möglich, mehrere HA-JNDI Dienste zu starten, die verschiedene Cluster "
-"verwenden. Diese Option kann zum Beispiel eingesetzt werden, wenn ein Node "
-"Teil mehrerer Cluster ist. In diesem Fall sollten Sie sich vergewissern, "
-"dass die beiden Dienste jeweils verschiedene Ports oder IP-Adressen "
-"verwenden. Wenn Sie etwa HA-JNDI mit dem Beispielcluster verbinden wollen "
-"und den Binding-Port ändern, so würde der MBean-Deskriptor wie folgt "
-"aussehen:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:588
-#, fuzzy, 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 ""
-"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
-" name=\"jboss:service=HAJNDI\"> \n"
-" <depends>jboss:service=MySpecialPartition</depends> \n"
-" <attribute name=\"PartitionName\">MySpecialPartition</"
-"attribute> \n"
-" <attribute name=\"Port\">56789</attribute> \n"
-"</mbean>"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:595
-#, no-c-format
-msgid "Clustered Session EJBs"
-msgstr "Geclusterte Session-EJBs"
-
-#. 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 ""
-"Session-EJBs stellen \"Remote-Invocation\"-Dienste (Fernaufrufdienste) zur "
-"Verfügung. Sie sind auf Grundlage der clientbasierten Interceptor-"
-"Architektur geclustert. Die Client-Anwendung für ein geclustertes Session-"
-"Bean ist - bis auf eine minimale Veränderung in der <literal>java.naming."
-"provier.url</literal>-Systemeigenschaft zur Aktivierung des HA-JNDI Lookup "
-"(siehe vorheriger Abschnitt) - fast identisch mit dem Client für die nicht-"
-"geclusterte Version des Session-Beans. Auf Seite des Clients sind keine Code-"
-"Änderung oder erneute Kompilierung nötig. Werfen wir nun einen Blick auf die "
-"Konfiguration der geclusterten Session-Beans in EJB 2.x bzw. EJB 3.0 Server-"
-"Applikationen."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:603
-#, no-c-format
-msgid "Stateless Session Bean in EJB 2.x"
-msgstr "Das Stateless Session Bean in 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 ""
-"Das Clustern von Stateless Session Beans ist ganz einfach: So lange kein "
-"Status involviert ist, kann die Lastverteilung von Aufrufen an einem "
-"beliebigen teilnehmenden Node des Clusters (d.h. jedem Node der dieses "
-"bestimmte Bean deployt hat) erfolgen. Um ein Bean zu clustern müssen Sie "
-"dessen <literal>jboss.xml</literal>-Deskriptor so verändern, dass er ein "
-"<literal><clustered></literal>-Tag enthält."
-
-#. 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 ""
-"Das <literal><clustered>True</clustered></literal>-Element "
-"fungiert lediglich als Alias für das <literal><configuration-name>"
-"Clustered Stateless SessionBean</configuration-name></literal>-Element."
-
-#. 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 ""
-"In der Bean-Konfiguration ist nur das <literal><clustered></literal>-"
-"Element zwingend erforderlich. Es weist darauf hin, dass das Bean in einem "
-"Cluster wirksam ist. Das <literal><cluster-config></literal>-Element "
-"ist optional, und die Standardwerte seiner Attribute sind in der "
-"Beispielkonfiguration oben dargestellt. Nachfolgend finden Sie eine "
-"Beschreibung der Attribute im <literal><cluster-config></literal>-"
-"Element."
-
-#. 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> bestimmt den Namen des "
-"Clusters, dessen Teil das Bean ist. Der voreingestellte Wert lautet "
-"<literal>DefaultPartition</literal>. Der standardmäßige Partitionsname kann "
-"mittels der <literal>jboss.partition.name</literal>-Systemeigenschaft "
-"ebenfalls eingestellt werden."
-
-#. 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> bezeichnet die "
-"zu verwendende Klasse des Home-Stubs, die bei der Verteilung der Aufrufe auf "
-"die Nodes des Clusters benutzt werden soll. Bei der Standardeinstellung wird "
-"das Proxy Aufrufe nach der <literal>RoundRobin</literal>-Weise verteilen. "
-"Sie können aber auch Ihre eigene Klasse von Lastverteilungsrichtlinien "
-"implementieren oder die Klasse <literal>FirstAvailable</literal> verwenden, "
-"die stets den ersten verfügbaren Node verwendet bis dies fehlschlägt."
-
-#. 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> bezeichnet die "
-"vom Bean-Stub bei der Verteilung der an den Nodes des Clusters gemachten "
-"Aufrufe zu verwendende Klasse. Kommentare für das <literal>home-load-balance-"
-"policy</literal>-Attribute gelten ebenso."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:641
-#, no-c-format
-msgid "Stateful Session Bean in EJB 2.x"
-msgstr "Das Stateful Session Bean in 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 ""
-"Das Clustern von Stateful Session Beans ist komplexer als das der Stateless "
-"Session Beans, da JBoss hier Informationen zu deren Status verwalten muss. "
-"Der Status aller Stateful Session Beans wird repliziert und im gesamten "
-"Cluster synchronisiert, sobald sich der Status eines Beans verändert. Der "
-"JBoss AS verwendet das <literal>HASessionState</literal>-MBean zur "
-"Verwaltung des verteilten Session-Status der geclusterten EJB 2.x Stateful "
-"Session Beans. In diesem Abschnitt werden sowohl die Konfiguration der "
-"Session-Beans als auch die <literal>HASessionState</literal>-MBean-"
-"Konfiguration erläutert."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:649
-#, no-c-format
-msgid "The EJB application configuration"
-msgstr "Die Konfiguration der EJB-Anwendung"
-
-#. 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 ""
-"In der EJB-Anwendung müssen Sie die <literal>jboss.xml</literal> Deskriptor-"
-"Datei für jedes Stateful Session Bean modifizieren und das <literal><"
-"clustered></literal>-Tag hinzufügen."
-
-#. 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 ""
-"In der Bean-Konfiguration ist lediglich das <literal><clustered></"
-"literal>-Tag obligatorisch, um anzuzeigen, dass das Bean Teil eines Clusters "
-"ist. Das <literal><cluster-config></literal>-Element ist optional, und "
-"seine Standard-Attributwerte sind in der vorherigen Beispielkonfiguration "
-"dargestellt."
-
-#. 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 ""
-"Das <literal><session-state-manager-jndi-name></literal>-Tag liefert "
-"den JNDI-Namen des <literal>HASessionState</literal>-Dienstes für dieses "
-"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 ""
-"Die Beschreibung der übrigen Tags ist identisch mit derjenigen des Stateless "
-"Session Beans. Vorgänge am Home-Interface des geclusterten Stateful Session "
-"Bean sind in der Standardeinstellung lastverteilt, \"Round-Robin\". Wenn der "
-"Remote-Stub des Beans für den Client verfügbar ist, so werden Aufrufe nicht "
-"mehr Round-Robin lastverteilt, sondern verbleiben am ersten Node auf der "
-"Liste (man sagt dann auch sie sind \"sticky\")."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:665
-#, no-c-format
-msgid "Optimize state replication"
-msgstr "Optimierung der Statusreplikation"
-
-#. 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 ""
-"Da der Replikationsprozess ein kostspieliger Vorgang ist, können Sie dieses "
-"Verhalten optimieren, indem Sie in Ihrer Bean-Klasse eine Methode mit der "
-"folgenden Signatur implementieren:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:668
-#, no-c-format
-msgid "public boolean isModified ();"
-msgstr "public boolean isModified ();"
-
-#. 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 ""
-"Ehe Sie Ihr Bean replizieren, prüft der Container, ob Ihr Bean diese Methode "
-"implementiert. Falls dies der Fall ist, ruft der Container die "
-"<literal>isModified()</literal>-Methode auf, und das Bean wird nur "
-"repliziert, wenn die Methode mit <literal>true</literal> antwortet. Falls "
-"das Bean nicht modifiziert wurde (oder nicht genug als dass eine Replikation "
-"erforderlich wäre, je nach Ihren persönlichen Wünschen), können Sie mit "
-"<literal>false</literal> antworten und die Replikation findet nicht statt. "
-"Dieses Feature ist nur bei JBoss AS 3.0.1+ verfügbar."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:677
-#, no-c-format
-msgid "The HASessionState service configuration"
-msgstr "Die Konfiguration des \"HASessionState\"-Dienstes"
-
-#. 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
-#, fuzzy, 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 ""
-"<mbean code=\"org.jboss.ha.hasessionstate.server.HASessionStateService\"\n"
-" name=\"jboss:service=HASessionState\">\n"
-" <depends>\n"
-" jboss:service=${jboss.partition.name:DefaultPartition}\n"
-" </depends>\n"
-" <!-- Name of the partition to which the service is linked -->\n"
-" <attribute name=\"PartitionName\">\n"
-" ${jboss.partition.name:DefaultPartition}\n"
-" </attribute>\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 ""
-"Die Konfigurationsattribute des <literal>HASessionState</literal>-MBean sind "
-"unten aufgeführt."
-
-#. 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 ""
-"Bei <emphasis role=\"bold\">PartitionName</emphasis> handelt es sich um ein "
-"optionales Merkmal, das den Namen des Clusters festlegt. Der voreingestellte "
-"Wert lautet hier <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 ""
-"Bei <emphasis role=\"bold\">JndiName</emphasis> handelt es sich um ein "
-"optionales Attribut zur Bestimmung des JNDI-Namens unter dem dieser "
-"<literal>HASessionState</literal>-Dienst gebunden ist. Die "
-"Standardeinstellung lautet <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 ""
-"Bei <emphasis role=\"bold\">BeanCleaningDelay</emphasis> handelt es sich um "
-"ein optionales Attribut zur Bestimmung der Anzahl von Millisekunden nach der "
-"der <literal>HASessionState</literal>-Dienst einen nicht-modifizierten "
-"Status bereinigen kann. Falls ein Node, der über ein Bean verfügt, abstürzt, "
-"so übernimmt sein \"Brother\"-Node dessen Bean. Das Container-Cache des "
-"Brother-Nodes wird darüber jedoch nicht informiert (da es zuvor nie damit zu "
-"tun hatte) und löscht - gemäß der Bereinigungseinstellungen des Beans - nie. "
-"Deshalb ist es notwendig, dass der <literal>HASessionState</literal>-Dienst "
-"gelegentlich diese Bereinigung durchführt. Die Standardeinstellung hierfür "
-"lautet <literal>30*60*1000</literal> Millisekunden (d.h. 30 Minuten)."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:707
-#, fuzzy, no-c-format
-msgid "Handling Cluster Restart"
-msgstr "Vorgehensweise beim Neustart des Clusters"
-
-#. 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 ""
-"Wir haben die HA Smart Client Architektur in <xref linkend=\"clustering-"
-"intro-arch-proxy\"/> behandelt. Ein Failover am HA Smart Proxy Client kann "
-"nur erfolgen, wenn ein Node im Cluster vorhanden ist. Falls es zu einem "
-"vollständigen Cluster-Shutdown kommt, \"verwaist\" das Proxy und verliert "
-"die Informationen zu verfügbaren Nodes im Cluster. Dies lässt sich nicht "
-"rückgängig machen. Das Proxy muss bei Neustart der Nodes in JNDI/HAJNDI "
-"gefunden werden. "
-
-#. 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 ""
-"Die Versionen 3.2.7+/4.0.2+ enthalten einen <literal>RetryInterceptor</"
-"literal>, der zum Proxy des clientbasierten Interceptor-Stack hinzugefügt "
-"werden kann, um eine transparente Wiederherstellung bei einer solchen "
-"Neustartstörung zu ermöglichen. Um dies für ein EJB zu aktivieren, "
-"konfigurieren Sie ein <literal>invoker-proxy-binding</literal> das den "
-"<literal>RetryInterceptor</literal> enthält. Nachfolgend finden Sie ein "
-"Beispiel der <literal>jboss.xml</literal>-Konfiguration."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:714
-#, fuzzy, 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 ""
-"<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 ""
-
-#. 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 ""
-
-#. 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 "Das Stateless Session Bean in 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 ""
-"Um in EJB 3.0 ein Stateless Session Bean zu clustern, müssen Sie nur die "
-"Bean-Klasse mit der <literal>@Cluster</literal>-Annotation versehen. Sie "
-"können die Lastverteilungsrichtlinie und die Cluster-Partition als Parameter "
-"der Annotation eingeben. Die Standard-Lastverteilungsrichtlinie lautet "
-"<literal>org.jboss.ha.framework.interfaces.RandomRobin</literal>, und der "
-"Standard-Cluster ist <literal>DefaultPartition</literal>. Nachfolgend finden "
-"Sie die Definition der <literal>@Cluster</literal>-Annotation."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:766
-#, fuzzy, 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 \"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 ""
-"Dies ist ein Beispiel für die Implementierung eines geclusterten EJB 3.0 "
-"Stateless Session Beans."
-
-#. 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"
-" // Do something cool\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 ""
-
-#. 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 ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:777
-#, fuzzy, no-c-format
-msgid "Stateful Session Beans in EJB 3.0"
-msgstr "Das Stateful Session Bean in 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 ""
-"Um in EJB 3.0 Stateful Session Beans zu clustern, müssen Sie die Bean "
-"Implementierungsklasse mit der <literal>@Cluster</literal>-Annotation "
-"markieren, ganz wie in dem vorherigen Abschnitt zum EJB 3.0 Stateless "
-"Session Bean beschrieben."
-
-#. 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 ""
-
-#. 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
-#, fuzzy, no-c-format
-msgid ""
-"Here is an example of a clustered EJB 3.0 stateful session bean "
-"implementation."
-msgstr ""
-"Dies ist ein Beispiel für die Implementierung eines geclusterten EJB 3.0 "
-"Stateless Session Beans."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:806
-#, fuzzy, 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"
-"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
-#, fuzzy, no-c-format
-msgid ""
-"public interface Optimized {\n"
-"boolean isModified();\n"
-"}"
-msgstr "public boolean isModified ();"
-
-#. 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 ""
-"JBoss Cache liefert den Dienst für die Session-Statusreplikation für EJB 3.0 "
-"Stateful Session Beans. Der zugehörige MBean-Dienst ist in der <literal>ejb3-"
-"clustered-sfsbcache-service.xml</literal>-Datei im <literal>deploy</literal>-"
-"Verzeichnis definiert. Die Inhalte der Datei lauten wie folgt."
-
-#. 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 ""
-
-#. 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 ""
-"Die Konfigurationsattribute im <literal>PassivationTreeCache</literal>-MBean "
-"sind im Wesentlichen dieselben wie die Attribute im Standard JBoss Cache "
-"<literal>TreeCache</literal>-MBean, das in <xref linkend=\"jbosscache.chapt"
-"\"/> behandelt wird. Auch hier wurden die JGroups Konfigurationen im "
-"<literal>ClusterConfig</literal>-Attribut weggelassen (mehr dazu finden Sie "
-"unter <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 "Geclusterte Entity-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 ""
-"In einem JBoss AS Cluster müssen die Instanzen der Entity-Beans über alle "
-"Nodes hinweg repliziert werden. Falls ein Entity Bean für Remote-Dienste "
-"zuständig ist, müssen auch die Service-Methoden lastverteilt werden."
-
-#. 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 ""
-"Um ein geclustertes Entity-Bean zu verwenden, muss die Anwendung lediglich "
-"die Bean-Referenzen der geclusterten HA-JNDI aufsuchen."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:870
-#, no-c-format
-msgid "Entity Bean in EJB 2.x"
-msgstr "Das Entity-Bean in 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 ""
-"Vorab sollte gesagt werden, dass das Clustern von 2.x Entity-Beans keine "
-"gute Idee ist. Es setzt Elemente, die zu feinstufig für den Gebrauch als "
-"Remote-Objekte sind, geclusterten Remote-Objekten aus und bringt nicht zu "
-"unterschätzende Probleme bei der Datensynchronisation mit sich. Verwenden "
-"Sie EJB 2.x Entity-Bean Clustering NICHT, außer bei Ihnen gilt der "
-"Sonderfall von \"read-only\" oder ein \"read-write\"-Node mit \"read-only\"-"
-"Nodes synchron mit Cache-Invalidationsdiensten."
-
-#. 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 ""
-"Um EJB 2.x Entity-Beans zu clustern, müssen Sie das <literal><"
-"clustered></literal>-Element zur <literal>jboss.xml</literal> Deskriptor-"
-"Datei der Anwendung hinzufügen. Nachfolgend sehen Sie eine typische "
-"<literal>jboss.xml</literal>-Datei."
-
-#. 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 ""
-"Die EJB 2.x Entity-Beans werden für lastverteilte Remote-Aufrufe geclustert. "
-"Alle Bean-Instanzen sind synchronisiert, damit sie auf sämtlichen Nodes über "
-"dieselben Inhalten verfügen."
-
-#. 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 ""
-"Geclusterte EJB 2.x Entity-Beans besitzen jedoch keinen verteilten \"Locking"
-"\"-Mechanismus oder ein verteiltes Cache. Sie können nur unter Verwendung "
-"des Row-Level Rocking auf Datenbankebene (siehe <literal><row-lock></"
-"literal> in der CMP-Spezifikation) oder durch Einstellen des \"Transaction "
-"Isolation Levels\" Ihres JDBC-Drivers auf <literal>TRANSACTION_SERIALIZABLE</"
-"literal> synchronisiert werden. Da kein verteilter Locking-Mechanismus oder "
-"verteiltes Cache existieren, müssen Entity-Beans die Commit Option \"B\" als "
-"Standard (siehe <literal>standardjboss.xml</literal> und die Container-"
-"Konfigurationen Clustered CMP 2.x EntityBean, Clustered CMP EntityBean oder "
-"Clustered BMP EntityBean) verwenden. Es wird nicht empfohlen, die \"Commit\"-"
-"Option \"A\" zu benutzen, außer es handelt sich um ein schreibgeschütztes "
-"(\"read-only\") Entity-Bean (Es gibt einige Entwurfsmuster, bei denen Sie "
-"die Commit Option \"A\" mit \"read-mostly\" Beans verwenden können. Sie "
-"können das Seppuku-Muster auch unter <ulink url=\"http://dima.dhs.org/misc/"
-"readOnlyUpdates.html\"></ulink> einsehen. Es ist möglich, dass JBoss diese "
-"in zukünftigen Versionen miteinbezieht)."
-
-#. 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 ""
-"Falls Sie \"Bean Managed Persistence\" (BMP) verwenden, werden Sie die "
-"Synchronisation selbst implementieren müssen. Die MVCSoft CMP 2.0 "
-"Persistence Engine (siehe <ulink url=\"http://www.jboss.org/jbossgroup/"
-"partners.jsp\"></ulink>) bietet unterschiedliche Arten von \"Locking\"-"
-"Strategien, die in einem JBoss-Cluster möglich sind."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:897
-#, no-c-format
-msgid "Entity Bean in EJB 3.0"
-msgstr "Das Entity-Bean in 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 ""
-"Entity-Beans in EJB 3.0 dienen in erster Linie als ein \"Persistence\"-"
-"Datenmodell. Sie bieten keine Remote-Dienste. Der Entity-Bean Clustering "
-"Dienst in EJB 3.0 behandelt demzufolge in erster Linie verteiltes Clustering "
-"sowie Replikation und nicht die Lastverteilung."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:905
-#, no-c-format
-msgid "Configure the distributed cache"
-msgstr "Die Konfiguration des verteilten Caches"
-
-#. 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 ""
-"Um Rundreisen zur Datenbank zu vermeiden, können Sie einen Cachespeicher für "
-"Ihre Entities verwenden. JBoss EJB 3.0 ist durch Hibernate implementiert, "
-"welches Support für ein Cache der zweiten Ebene (\"Second-Level Cache\") "
-"bietet. Der Hibernate Setup, der für die Implementierung von JBoss EJB 3.0 "
-"benutzt wird, verwendet JBoss Cache als seine zu Grunde liegende Cache-"
-"Implementierung. Das Cache bietet die folgenden Funktionalitäten:"
-
-#. 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 ""
-"Wenn eine Cache-aktivierte Entity-Bean-Instanz über den Entity-Manager an "
-"die Datenbank fortbesteht, so wird die Entity dem Cachespeicher zugefügt."
-
-#. 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 ""
-"Wenn Sie eine Bean-Instanz aktualisieren und die Änderungen in der Datenbank "
-"mittels des Entity-Managers speichern, so wird die Entity im Cachespeicher "
-"aktualisiert."
-
-#. 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 ""
-"Wenn Sie eine eine Bean-Instanz aus der Datenbank mittels des Entity-"
-"Managers entfernen, so wird die Entity aus dem Cachespeicher entfernt."
-
-#. 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 ""
-"Wenn Sie eine eine gecachte Entity aus der Datenbank mittels des Entity-"
-"Managers laden und diese bis zu diesem Zeitpunkt in der Datenbank nicht "
-"existiert, so wird sie dem Cachespeicher zugefügt."
-
-#. 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 ""
-"Der JBoss Cache-Dienst für EJB 3.0 Entity-Beans ist in einem "
-"<literal>TreeCache</literal>-MBean (siehe <xref linkend=\"jbosscache-cache\"/"
-">) in der <literal>deploy/ejb3-entity-cache-service.xml</literal>-Datei "
-"konfiguriert. Der Name des MBean Cache-Dienstes lautet <literal>jboss.cache:"
-"service=EJB3EntityTreeCache</literal>. Unten sehen Sie die Inhalte der "
-"<literal>ejb3-entity-cache-service.xml</literal>-Datei in der "
-"standardmäßigen JBoss-Distribution. Auch hier wird das JGroups-"
-"Konfigurationselement <literal>ClusterConfig</literal> weggelassen."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:931
-#, fuzzy, 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 ""
-"<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"
-" <!-- 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"
-" <!--Name of cluster. Needs to be the same for all clusters, \n"
-" in order to find each other -->\n"
-" <attribute name=\"ClusterName\">EJB3-entity-cache</"
-"attribute>\n"
-"\n"
-" <attribute name=\"ClusterConfig\">\n"
-" ... ...\n"
-" </attribute>\n"
-"\n"
-" <attribute name=\"InitialStateRetrievalTimeout\">5000</"
-"attribute>\n"
-" <attribute name=\"SyncReplTimeout\">10000</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>"
-
-#. 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 ""
-"Wie in <xref linkend=\"jbosscache-cache\"/> erläutert, können Sie mit JBoss "
-"Cache Timeouts zu gecachten Entities festlegen. Entities, auf die innerhalb "
-"eines bestimmten zeitlichen Rahmens nicht zugegriffen wird, werden aus dem "
-"Cache entfernt, so dass Speicher gewonnen wird. Falls dies innerhalb eines "
-"Clusters geschieht, werden Eingabeveränderungen innerhalb eines Nodes an "
-"entsprechenden Eingaben in den anderen Nodes des Clusters repliziert."
-
-#. 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 ""
-"Nun ist das JBoss Cache so konfiguriert, dass das verteilte Cachen von EJB "
-"3.0 Entity-Beans unterstützt wird. Es müssen jedoch noch die einzelnen "
-"Entity-Beans konfiguriert werden, die beim Cache-Dienst verwendet werden."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:943
-#, no-c-format
-msgid "Configure the entity beans for cache"
-msgstr "Die Konfiguration der Entity-Beans für das 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 ""
-"Die Klassen des Entity-Beans werden auf reguläre Weise definiert. Zukünftige "
-"Versionen von JBoss EJB 3.0 werden kommentierte Entities und die erfassten "
-"Verbindungen als gecacht unterstützen, aber im Augenblick müssen Sie die zu "
-"Grunde liegende Hibernate-Engine direkt konfigurieren. Werfen Sie einen "
-"Blick auf die <literal>persistence.xml</literal>-Datei, die die Caching-"
-"Optionen für Hibernate mittels seiner optionalen <literal>property</literal>-"
-"Elemente konfiguriert. Das folgende Element in <literal>persistence.xml</"
-"literal> definiert, dass Caching aktiviert werden sollte:"
-
-#. 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 ""
-"<!-- Clustered cache with TreeCache -->\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 ""
-"Das folgende Property-Element definiert den Objektnamen des zu verwendenden "
-"Caches sowie den MBean-Namen."
-
-#. 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 ""
-"Als nächstes muss konfiguriert werden, welche Entities gecacht werden "
-"sollen. In der Standardeinstellung wird selbst mit den oben dargestellten "
-"Einstellungen nichts gecacht. Die <literal>@Cache</literal>-Annotation wird "
-"zur Kennzeichnung von zu cachenden Entity-Beans verwendet."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:966
-#, fuzzy, 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 Customer 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 ""
-"Vereinfacht könnte man sagen, dass in der Regel Objekte gecacht werden, die "
-"sich selten verändern, aber häufig gelesen werden. In der <literal>ejb3-"
-"entity-cache-service.xml</literal>-Konfigurationsdatei können Sie eine "
-"Feinabstimmung des Caches für jedes Entity-Bean vornehmen. So können Sie zum "
-"Beispiel die Größe des Caches festlegen. Falls sich zu viele Objekte im "
-"Cache befinden, kann das Cache die ältesten (oder - je nach Konfiguration - "
-"die am seltensten verwendeten) Objekte ausweisen. Das Cache für das "
-"<literal>mycompany.Customer</literal> Entity-Bean ist der <literal>/"
-"mycompany/Customer</literal> Cache-Bereich."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:969
-#, fuzzy, 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 ""
-"<server> \n"
-" <mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=EJB3EntityTreeCache\"> \n"
-" <depends>jboss:service=Naming \n"
-" <depends>jboss:service=TransactionManager \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"
-" <region name=\"/mycompany/Customer\"> \n"
-" <attribute name=\"maxNodes\">10</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 ""
-"Falls Sie keinen Cache-Bereich für eine Entity-Bean Klasse festlegen, werden "
-"sämtliche Instanzen dieser Klasse - wie oben definiert - im <literal>/"
-"_default</literal>-Bereich gecacht. Die EJB3 <literal>Query</literal>-API "
-"ermöglicht es Ihnen, Anfrageergebnisse (d.h. Auflistungen von Entity-Beans) "
-"von festgelegten Cache-Regionen zu laden/speichern."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:975
-#, fuzzy, 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"
-"public class Customer implements Serializable { \n"
-" // ... ... \n"
-"}"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:976
-#, fuzzy, no-c-format
-msgid "The eviction configuration would then become:"
-msgstr "Die Konfiguration der EJB-Anwendung"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:977
-#, fuzzy, 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 ""
-"<server> \n"
-" <mbean code=\"org.jboss.cache.TreeCache\" \n"
-" name=\"jboss.cache:service=EJB3EntityTreeCache\"> \n"
-" <depends>jboss:service=Naming \n"
-" <depends>jboss:service=TransactionManager \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"
-" <region name=\"/mycompany/Customer\"> \n"
-" <attribute name=\"maxNodes\">10</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 ""
-
-#. 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 ""
-
-#. Tag: screen
-#: Clustering_Guide_Introduction.xml:989
-#, no-c-format
-msgid ""
-"<property name=\"hibernate.cache.use_query_cache\" value=\"true\"/>"
-msgstr ""
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1008
-#, fuzzy, no-c-format
-msgid "The related eviction configuration:"
-msgstr "Die Konfiguration der EJB-Anwendung"
-
-#. 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 ""
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1044
-#, no-c-format
-msgid "HTTP Services"
-msgstr "HTTP-Dienste"
-
-#. 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 ""
-"Die HTTP-Session-Replikation wird verwendet, um den Ihren Web-Clients "
-"zugehörigen Status auf anderen Nodes eines Clusters zu replizieren. Falls "
-"also einer Ihrer Nodes ausfällt, kann ein anderer Node im Cluster "
-"einspringen. Zwei eindeutige Funktionen müssen ausgeführt werden:"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1050
-#, no-c-format
-msgid "Session state replication"
-msgstr "Session-Statusreplikation (\"Session State Replication\")"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1053
-#, fuzzy, no-c-format
-msgid "Load-balancing of incoming invocations"
-msgstr "Lastverteilung eingehender Aufrufe"
-
-#. 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 ""
-"Die Statusreplikation wird direkt von JBoss durchgeführt. Wenn JBoss in der "
-"<literal>all</literal>-Konfiguration läuft, ist die Session-"
-"Statusreplikation standardmäßig aktiviert. Führen Sie einfach Ihre Web-"
-"Applikation aus, und ihr Session-Status ist bereits über sämtlichen JBoss-"
-"Instanzen im Cluster repliziert."
-
-#. 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 ""
-"Die Lastverteilung hingegen wird nicht von JBoss selbst durchgeführt und "
-"benötigt zusätzliche Software. Da es sich um ein sehr gängiges Szenario "
-"handelt, zeigen wir hier den Setup von Apache und mod_jk. Dieser Vorgang "
-"kann entweder durch spezielle Hardware-Switches oder Router (z.B. Cisco "
-"LoadDirector) oder eine andere vergleichbare Software durchgeführt werden."
-
-#. 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 ""
-"Ein Lastverteiler verfolgt die HTTP-Anfragen, und je nachdem welche Session "
-"mit der Anfrage verbunden ist, leitet er diese an den betreffenden Node "
-"weiter. Man spricht in diesem Zusammenhang von einem Lastverteiler mit "
-"\"Sticky Sessions\": Wenn eine Session einmal an einem Node erstellt wurde, "
-"so werden alle zukünftigen Anfragen von demselben Node bearbeitet. Die "
-"Verwendung eines \"Sticky Sessions\" unterstützenden Lastverteilers, bei dem "
-"keine Statusreplikation der Session notwendig ist, ermöglicht eine "
-"unkomplizierte Handhabe, denn jede Anfrage wird stets vom selben Node "
-"bearbeitet. Falls jedoch ein Node ausfällt, so fällt auch der Status "
-"sämtlicher von ihm bearbeiteter Client-Sessions aus (z.B. die Einkaufswagen) "
-"und Kunden werden sich wahrscheinlich auf einem anderen Node neu einloggen "
-"und eine neue Sitzung starten müssen. In vielen Situationen ist es "
-"vertretbar, auf die Replikation von HTTP-Sessions zu verzichten, da alle "
-"wichtigen Statusinformationen in der Datenbank gespeichert werden. In "
-"anderen Situationen hingegen ist es inakzeptabel eine Client-Session zu "
-"verlieren, und es empfiehlt sich, die Session-Statusreplikation anzuwenden."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1065
-#, fuzzy, no-c-format
-msgid "Configuring load balancing using Apache and mod_jk"
-msgstr "Konfiguration von Apache zum Laden von 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 ""
-"Bei Apache handelt es sich um einen bekannten Web-Server, der durch den Plug-"
-"In von Modulen erweiterbar ist. Eines dieser Module, mod_jk (sowie das "
-"aktuelle mod_jk2) wurde speziell dafür entwickelt, Anfragen vom Apache an "
-"einen Servlet-Container weiterzuleiten. Es kann weiterhin die Lastverteilung "
-"von HTTP-Aufrufen an einen Satz von Servlet-Containern übernehmen, während "
-"es \"Sticky Sessions\" aufrecht erhält - und genau das ist es, was uns "
-"interessiert."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1072
-#, no-c-format
-msgid "Download the software"
-msgstr "Download der 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 ""
-"Zunächst einmal sollten Sie sich vergewissern, dass Apache installiert ist. "
-"Falls nicht, können Sie Apache direkt von der Apache-Webseite unter "
-"<literal>http://httpd.apache.org/</literal> herunterladen. Die Installation "
-"ist unkompliziert und erfordert keine spezielle Konfiguration. Da es mehrere "
-"Versionen von Apache gibt, empfehlen wir den Download von Version 2.0.x. In "
-"den folgenden Abschnitten gehen wir davon aus, dass Apache in Ihrem "
-"<literal>APACHE_HOME</literal>-Verzeichnis vorhanden ist."
-
-#. 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 ""
-"Als nächstes laden Sie bitte die mod_jk Binärdateien herunter. Auch von "
-"mod_jk gibt es mehrere Versionen. Hier empfehlen wir dringend den Download "
-"von mod_jk 1.2.x, da sowohl mod_jk als auch mod_jk2 nicht aktuell sind, "
-"keinen Support bieten und auch keine weiteren Entwicklungen innerhalb der "
-"Community durchgeführt werden. Die mod_jk 1.2.x Binärdatei können Sie sich "
-"unter <literal>http://www.apache.org/dist/jakarta/tomcat-connectors/jk/"
-"binaries/</literal> herunterladen. Benennen Sie die heruntergeladene Datei "
-"in <literal>mod_jk.so</literal> um, und legen Sie eine Kopie unter "
-"<literal>APACHE_HOME/modules/</literal> an."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1086
-#, no-c-format
-msgid "Configure Apache to load mod_jk"
-msgstr "Konfiguration von Apache zum Laden von 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 ""
-"Ändern Sie APACHE_HOME/conf/httpd.conf und fügen Sie eine einzelne Zeile am "
-"Ende der Datei hinzu:"
-
-#. 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 ""
-"# Fügen Sie die spezielle Konfigurationsdatei von mod_jk ein \n"
-"Setzen Sie conf/mod-jk.conf ein"
-
-#. 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 ""
-"Anschließend erstellen Sie bitte eine neue Datei mit dem Namen "
-"<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 ""
-"# 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>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1091
-#, no-c-format
-msgid "Please note that two settings are very important:"
-msgstr "Bitte beachten Sie, dass zwei Einstellungen sehr wichtig sind:"
-
-#. 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 ""
-"Die <literal>LoadModule</literal>-\"Directive\" (Übersetzungsanweisung) muss "
-"auf die mod_jk-Bibliothek verweisen, die Sie im vorherigen Abschnitt "
-"heruntergeladen haben. Sie müssen dies durch den identischen Pfadnamen mit "
-"dem \"Modules\" Dateipfad-Präfix anzeigen."
-
-#. 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 ""
-"Die <literal>JkMount</literal>-\"Directive\" (Übersetzungsanweisung) "
-"informiert Apache darüber, welche URLs an das mod_jk-Modul weitergeleitet "
-"werden sollen (und an die Servlet Container). In der Datei oben werden alle "
-"Anfragen mit dem URL-Pfad <literal>/application/*</literal> an den mod_jk-"
-"Lastverteiler weitergeleitet. Auf diese Weise können Sie Apache direkt auf "
-"serverstatische Inhalte (oder PHP-Contents) konfigurieren und den "
-"Lastverteiler ausschließlich für Java-Anwendungen verwenden. Falls Sie "
-"mod_jk nur als Lastverteiler benutzen, können Sie auch alle URLs (d.h. "
-"<literal>/*</literal>) an mod_jk weiterleiten."
-
-#. 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 ""
-"Neben der <literal>JkMount</literal>-Directive können Sie auch die "
-"<literal>JkMountFile</literal>-Directive verwenden, um eine Mountpunkt-"
-"Konfigurationdatei (\"mount points\") zu bestimmen, die mehrere Tomcat "
-"weiterleitende URL Mappings enthält. Sie müssen lediglich eine "
-"<literal>uriworkermap.properties</literal>-Datei im <literal>APACHE_HOME/"
-"conf</literal>-Verzeichnis erstellen. Das Format der Datei lautet <literal>/"
-"url=worker_name</literal>. Für den Anfang fügen Sie einfach das folgende "
-"Beispiel in die erstellte Datei:"
-
-#. 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 ""
-"# 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"
-
-#. 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 ""
-"Dadurch wird mod_jk so konfiguriert, dass Anfragen an <literal>/jmx-console</"
-"literal> und <literal>/web-console</literal> an Tomcat weitergeleitet werden."
-
-#. 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 ""
-"Sie werden die anderen Einstellungen in <literal>mod_jk.conf</literal> "
-"wahrscheinlich nicht ändern. Sie werden benötigt, um mod_jk darüber zu "
-"informieren, wo die Protokolldatei (\"Logfile\") abgelegt werden soll, "
-"welches Logging-Level verwendet werden soll und so weiter."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1120
-#, no-c-format
-msgid "Configure worker nodes in mod_jk"
-msgstr "Die Konfiguration von \"Worker Nodes\" (Arbeitsknoten) in 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 ""
-"Als nächstes muss das mod_jk \"Workers-File\" <literal>conf/workers."
-"properties</literal> konfiguriert werden. Diese Datei bestimmt, wo die "
-"verschiedenen Servlet-Container sich befinden und wie die Lastverteilung von "
-"Aufrufen über diese erfolgt. Die Konfigurationsdatei enthält einen Abschnitt "
-"für jeden Ziel-Servlet-Container sowie einen globalen (modulübergreifenden) "
-"Abschnitt. Für eine Konfiguration mit zwei Nodes könnte die Datei wie folgt "
-"aussehen:"
-
-#. 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 ""
-"# 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"
-
-#. 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 ""
-"Im Wesentlichen konfiguriert die Datei oben mod_jk so, dass eine gewichtete "
-"Round-Robin-Lastverteilung mit Sticky-Sessions zwischen zwei Servlet-"
-"Containern (JBoss Tomcat) - mit node1 und node2 auf Port 8009 ansprechend - "
-"durchgeführt wird."
-
-#. 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 ""
-"In der <literal>works.properties</literal>-Datei ist jeder Node mittels der "
-"<literal>worker.XXX</literal>-Namenskonvention definiert, in der "
-"<literal>XXX</literal> einen arbiträren (beliebigen) Namen repräsentiert, "
-"den Sie für einen der Ziel-Servlet-Container wählen. Für jeden Worker muss "
-"der Host-Name (oder die IP-Adresse) sowie die Portnummer des im Servlet-"
-"Container ausgeführten AJP13-Connectors eingegeben werden."
-
-#. 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 ""
-"Das <literal>lbfactor</literal>-Attribut ist der Lastverteilungsfaktor für "
-"diesen speziellen Worker. Er dient zur Bestimmung der Priorität (oder "
-"Gewichtung), die ein Node im Vergleich zu anderen Nodes hat. Je höher die "
-"Zahl ist, desto mehr HTTP-Anfragen wird er erhalten. Diese Einstellung kann "
-"zur Differenzierung von Servern mit unterschiedlicher Verarbeitungsleistung "
-"verwendet werden."
-
-#. 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 ""
-"Das <literal>cachesize</literal>-Attribut definiert die Größe des mit dem "
-"Servlet-Container verbundenen Thread-Pools (d.h. die Anzahl gleichlaufender "
-"Anfragen, die an den Servlet-Container weitergeleitet wird). Diese Zahl darf "
-"die Anzahl der am AJP13-Connector des Servlet-Container konfigurierten "
-"Threads nicht überschreiten. Sehen Sie hierzu unter <literal>http://jakarta."
-"apache.org/tomcat/connectors-doc/config/workers.html</literal> die "
-"Anmerkungen zu <literal>cachesize</literal> für 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 ""
-"Der letzte Teil der <literal>conf/workers.properties</literal>-Datei "
-"definiert den Lastverteiler-Worker. Das einzige, was Sie hier ändern müssen, "
-"ist die <literal>worker.loadbalancer.balanced_workers</literal>-Zeile: Sie "
-"muss alle zuvor in derselben Datei definierten Worker aufführen: Die "
-"Lastverteilung wird über diese Worker durchgeführt."
-
-#. 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 ""
-"Die <literal>sticky_session</literal>-Property bestimmt das Clusterverhalten "
-"bei HTTP-Sessions. Wenn Sie <literal>worker.loadbalancer.sticky_session=0</"
-"literal> festlegen, wird jede Anfrage zwischen node1 und node2 lastverteilt. "
-"Wenn jedoch ein Benutzer eine Session an einem Server eröffnet, empfiehlt es "
-"sich, die Anfrage des Benutzers immer an denselben Server weiterzuleiten. "
-"Dies wird als \"Sticky Session\" bezeichnet, da der Client stets denselben "
-"Server wie bei seiner ersten Anfrage verwendet. Andernfalls müssen die "
-"Session-Daten des Benutzers zwischen beiden Servern synchronisiert werden "
-"(Sessionreplikation, siehe <xref linkend=\"clustering-http-state\"/>). Um "
-"die \"Session-Stickiness\" zu aktivieren, müssen Sie <literal>worker."
-"loadbalancer.sticky_session</literal> auf 1 setzen."
-
-#. 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 ""
-"Eine nicht-lastverteilte Konfiguration mit einem einzelnen Node bedarf der "
-"<literal>worker.list=node1</literal> Eingabe, ehe mod_jk ordnungsgemäß "
-"funktioniert."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1157
-#, fuzzy, no-c-format
-msgid "Configuring JBoss to work with mod_jk"
-msgstr "Die Konfiguration von \"Worker Nodes\" (Arbeitsknoten) in 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 ""
-"Zum Schluss müssen noch die JBoss Tomcat Instanzen auf allen geclusterten "
-"Nodes konfiguriert werden, damit sie die vom mod_jk-Lastverteiler "
-"weitergeleiteten Anfragen annehmen können."
-
-#. 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 ""
-"An jedem geclusterten JBoss-Node muss der Node entsprechend dem in "
-"<literal>workers.properties</literal> spezifizierten Namen benannt werden. "
-"Ein Beispiel: An JBoss-Instanz node1 ändern Sie die <literal>JBOSS_HOME/"
-"server/all/deploy/jbossweb-tomcat50.sar/server.xml</literal>-Datei (falls "
-"nötig ersetzen Sie <literal>/all</literal> mit Ihrem eigenen Servernamen). "
-"Lokalisieren Sie das <literal><Engine></literal>-Element, und fügen "
-"Sie ein <literal>jvmRoute</literal>-Attribut hinzu:"
-
-#. 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 ""
-
-#. 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 ""
-"Dann muss für jede JBoss Tomcat Instanz im Cluster ein <literal>jvmRoute</"
-"literal>-Wert zu den Session-Cookies hinzugefügt werden, damit mod_jk "
-"eingehende Anfragen weiterleiten kann. Dazu ändern Sie die "
-"<literal>JBOSS_HOME/server/all/deploy/jbossweb-tomcat50.sar/META-INF/jboss-"
-"service.xml</literal> Datei (ersetzen Sie <literal>/all</literal> mit Ihrem "
-"eigenen Servernamen). Lokalisieren Sie das <literal><attribute></"
-"literal>-Element mit Namen <literal>UseJK</literal>, und stellen Sie den "
-"Wert auf <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 ""
-"Nun haben Sie eine voll funktionsfähige Apache+mod_jk "
-"Lastverteilungskonfiguration, die die Aufrufe der Servlet-Container Ihres "
-"Clusters verteilt und außerdem die \"Session Stickiness\" besorgt (d.h. "
-"Clients verwenden stets denselben Servlet-Container)."
-
-#. 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 ""
-"Aktuelle Information zur Benutzung von mod_jk 1.2 mit JBoss Tomcat finden "
-"Sie auf der JBoss Wiki-Seite unter <literal>http://wiki.jboss.org/wiki/Wiki."
-"jsp?page=UsingMod_jk1.2WithJBoss</literal>."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1188
-#, fuzzy, no-c-format
-msgid "Configuring HTTP session state replication"
-msgstr "Die Konfiguration der Statusreplikation von HTTP-Sessions"
-
-#. 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 ""
-"In <xref linkend=\"clustering-http-nodes\"/> wurde erläutert, wie mittels so "
-"genannter \"Sticky Sessions\" ein Client stets an demselben Server-Node "
-"bearbeitet wird, um den Session-Status beizubehalten. Eine ideale Lösung ist "
-"das jedoch nicht. Es ist möglich, dass die Last nach einer gewissen Zeit "
-"ungleichmäßig auf die Nodes verteilt wird und die Daten einer Session "
-"verloren gehen, wenn ein Node ausfällt. Eine bessere und vor allem "
-"zuverlässigere Lösung ist ist, die Session-Daten auf sämtlichen Nodes "
-"innerhalb des Clusters zu replizieren. Auf diese Weise erhält der Client an "
-"allen Server-Nodes denselben Session-Status."
-
-#. 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 ""
-"Das <literal>jboss.cache:service=TomcatClusteringCache</literal>-MBean "
-"benutzt das JBoss Cache um den HTTP-Session Replikationsdienst für den HTTP-"
-"Lastverteiler in einem JBoss Tomcat Cluster zu liefern. Dieses MBean ist in "
-"der <literal>deploy/tc5-cluster.sar/META-INF/jboss-service.xml</literal>-"
-"Datei definiert."
-
-#. 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 ""
-"Vor AS 4.0.4 CR2 ist die HTTP-Session Cache-Konfigurationsdatei die "
-"<literal>deploy/tc5-cluster-service.xml</literal>-Datei. Weitere "
-"Informationen entnehmen Sie bitte der Dokumentation für AS 4.0.3."
-
-#. 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 ""
-"Nachfolgend sehen Sie eine typische <literal>deploy/tc5-cluster.sar/META-INF/"
-"jboss-service.xml</literal>-Datei. Die Konfigurationsattribute im "
-"<literal>TomcatClusteringCache</literal>-MBean ähneln denen in <xref linkend="
-"\"jbosscache-cache\"/> sehr."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1202
-#, fuzzy, 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"
-" <attribute name=\"LockAcquisitionTimeout\">15000</"
-"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 ""
-"Die detaillierte Konfiguration für das <literal>TreeCache</literal>-MBean "
-"wird in <xref linkend=\"jbosscache-cache\"/> erläutert. Nachfolgend "
-"behandeln wir einige Attribute, die von besonderer Bedeutung für die "
-"Replikation der HTTP-Cluster-Session sind."
-
-#. 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 ""
-"<emphasis role=\"bold\">TransactionManagerLookupClass</emphasis> legt die "
-"Factory des Transaktionsmanagers fest. Die Standardeinstellung lautet hier "
-"<literal>org.jboss.cache.BatchModeTransactionManagerLookup</literal>. Dem "
-"Cache wird darin mitgeteilt, NICHT an JTA-spezifischen Transaktionen "
-"teilzunehmen. Statt dessen führt das Cache seinen eigenen "
-"Transaktionssupport, um feinstufige Replikationen zu unterstützen."
-
-#. 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> bestimmt den Clusternamen in "
-"dem das Cache arbeitet. Der Standard-Clustername ist das Wort \"Tomcat-\" "
-"gefolgt vom aktuellen JBoss-Partitionsnamen. Alle Nodes sollten denselben "
-"Clusternamen verwenden. Obwohl die Session-Replikation sich denselben "
-"Channel (Multicast-Adresse und Port) mit anderen geclusterten Diensten in "
-"JBoss teilen kann, sollte die Replikation ihren eigenen Clusternamen "
-"besitzen."
-
-#. 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 ""
-"Die <emphasis role=\"bold\">UseMarshalling</emphasis> und <emphasis role="
-"\"bold\">InactiveOnStartup</emphasis>-Attribute müssen denselben Wert "
-"besitzen. Die Einstellung muss <literal>true</literal> lauten, falls "
-"<literal>FIELD</literal>-Level Session-Replikation benötigt wird (siehe "
-"später). Andernfalls lautet die Standardeinstellung <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> enthält die Konfiguration "
-"des zu Grunde liegenden JGroups Stacks (siehe <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> bestimmt die "
-"maximale Anzahl von Millisekunden, die auf eine \"Lock Acquisition\" "
-"gewartet wird. Der voreinstellte Wert lautet hier 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> bestimmt die "
-"maximale Anzahl von Millisekunden, die auf eine \"Lock Acquisition\" "
-"gewartet wird. Der voreinstellte Wert lautet hier 15000."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1246
-#, no-c-format
-msgid "Enabling session replication in your application"
-msgstr "Die Aktivierung von Session-Replikation in Ihrer Anwendung"
-
-#. 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 ""
-"Um das Clustering Ihrer Webanwendung zu aktivieren, müssen Sie es im "
-"<literal>web.xml</literal>-Deskriptor als verteilbar konfigurieren. "
-"Nachfolgend sehen Sie ein Beispiel:"
-
-#. 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 ""
-"Die Session-Replikation kann mittels des <literal>replication-config</"
-"literal>-Elements in der <literal>jboss-web.xml</literal>-Datei weiter "
-"konfiguriert werden. Hier ist ein Beispiel dazu:"
-
-#. 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 ""
-"Das <literal>replication-trigger</literal>-Element bestimmt, wodurch eine "
-"Session-Replikation ausgelöst wird (oder ob eine Session als \"dirty session"
-"\" gilt, weil Inhalte sich verändert haben). Es besitzt 4 Optionen:"
-
-#. 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>: Mit dieser Richtlinie gilt eine "
-"Session nur als \"dirty\", wenn ein Attribut in der Session festgelegt ist. "
-"Falls Ihre Anwendung immer den veränderten Wert in der Session festhält, ist "
-"dieses hinsichtlich der Performance die wohl beste Option. Wenn ein Objekt "
-"von einer Session abgerufen und modifiziert wird ohne der Session wieder "
-"hinzugefügt zu werden, so wird die Änderung an diesem Objekt nicht "
-"repliziert."
-
-#. 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>: Bei dieser Richtlinie wird "
-"jedes Attribut das geladen oder eingestellt wird als \"dirty\" "
-"gekennzeichnet. Falls ein Objekt der Session aufgerufen und verändert wird, "
-"ohne dass es in die Session zurückgeschrieben wird, so wird die Änderung an "
-"diesem Objekt repliziert. Diese Option kann die Performance stark "
-"beeinflussen."
-
-#. 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>: Bei dieser Option wird eine "
-"Session bei jedem Zugriff als \"dirty\" markiert. Da während jeder HTTP-"
-"Anfrage auf die Session zugegriffen wird, wird sie bei jeder Anfrage "
-"repliziert. Der Zeitstempel (\"Time Stamp\") des Zugriffs in der Session-"
-"Instanz wird ebenfalls aktualisiert.Da der Zeitstempel möglicherweise nicht "
-"in anderen Clustering-Nodes aktualisiert wird, weil keine Replikation "
-"stattfindet kann es sein, dass die Session in anderen Nodes vor dem aktiven "
-"Node abläuft, falls die HTTP-Anfrage keine Attribute der Session abfragt "
-"oder verändert. Wenn diese Option eingestellt ist, werden die Zeitstempel "
-"der Sessions über sämtliche Nodes des Clusters synchronisiert. Bitte "
-"beachten Sie, dass diese Option großen Einfluss auf die Performance haben "
-"kann, und verwenden Sie sie daher mit Vorsicht."
-
-#. 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 ""
-"Das <literal>replication-granularity</literal>-Element steuert die Größe der "
-"Replikationseinheiten (sog. \"replication units\"). Dabei werden die "
-"folgenden Werte unterstützt:"
-
-#. 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 ""
-"Das <literal>replication-field-batch-mode</literal>-Element zeigt an, ob "
-"zwischen jeder http-Anfrage eine Batch-Aktualisierung erfolgt oder nicht. "
-"Der voreingestellte Wert lautet <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 ""
-"Wenn Ihre Sessions in der Regel eher klein sind, so ist SESSION die "
-"geeignetere Richtlinie. Falls Ihre Session größer ist und auf einige Teile "
-"eher selten zugegriffen wird, so ist die ATTRIBUTE-Replikation effektiver. "
-"Falls Ihre Anwendung sehr große Datenobjekte in Session-Attributen besitzt "
-"und nur Felder in diesen Objekten oft verändert werden, dann ist die FIELD-"
-"Richtlinie für Sie am besten geeignet. Im nächsten Abschnitt erläutern wir "
-"genau, wie die Replikation auf FIELD-Ebene funktioniert."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1298
-#, fuzzy, no-c-format
-msgid "Using FIELD level replication"
-msgstr "Die Verwendung der Replikation auf FIELD-Ebene"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1299
-#, fuzzy, 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 ""
-"Die Replikation auf FIELD-Ebene repliziert nur veränderte Datenfelder "
-"innerhalb von Objekten, die in der Session gespeichert werden. Dies könnte "
-"möglicherweise den Datenverkehr zwischen den geclusterten Nodes drastisch "
-"senken und somit die Leistung des Gesamtclusters verbessern. Um die "
-"Replikation auf FIELD-Ebene zu verwenden, müssen Sie Ihre Java-Klasse "
-"vorbereiten, um zu bestimmen, welche Felder repliziert werden sollen. Dies "
-"geschieht mittels Annotationen im JDK 1.4 Stil, die in JavaDocs eingebettet "
-"sind:"
-
-#. 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
-#, fuzzy, no-c-format
-msgid ""
-"<![CDATA[\n"
-"@org.jboss.cache.aop.AopMarker\n"
-"public class Address \n"
-"{\n"
-"...\n"
-"}]]>"
-msgstr ""
-"/*\n"
-" *\n"
-" * @@org.jboss.web.tomcat.tc5.session.InstanceOfAopMarker\n"
-" */\n"
-"public class Person \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 ""
-"Falls Sie sie statt dessen mit <literal>InstanceAopMarker</literal> "
-"annotieren, so werden alle ihre Unterklassen automatisch ebenfalls "
-"annotiert. Zum Beispiel,"
-
-#. 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 ""
-
-#. 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"
-" * My usual comments here first.\n"
-" * @@org.jboss.web.tomcat.tc5.session.AopMarker\n"
-" */\n"
-"public class Address \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"
-"public class Person \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 ""
-"Da wir zur Zeit jedoch nur die Annotation im JDK 1.4 Stil unterstützen (die "
-"von JBoss Aop bereitgestellt wird), werden Sie einen vorbereitenden Schritt "
-"durchführen müssen. Sie werden den JBoss AOP Pre-Compiler (Vorkompilierer) "
-"<literal>annotationc</literal> und Post-Compiler (Nachkompilierer) "
-"<literal>aopc</literal> verwenden müssen, um den Quellcode oben vor und nach "
-"der Kompilierung durch den Java-Compiler zu bearbeiten. Nachfolgend sehen "
-"Sie ein Beispiel dafür, wie Sie Befehle von der Befehlszeile aufrufen."
-
-#. 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 ""
-"Bitte konsultieren Sie die JBoss AOP-Dokumentation zum Gebrauch des Vor- und "
-"Nachkompilierers. Das JBoss AOP-Projekt bietet auch einfach zu benutzende "
-"ANT-Tasks, die Ihnen bei der Integration dieser Schritte beim Aufbauvorgang "
-"Ihrer Anwendung helfen. Bei der nächsten Version des AS wird Support für die "
-"JDK 5.0 Annotation bereit gestellt, um das Ganze transparenter zu gestalten. "
-"Im Moment ist es jedoch wichtig, dass Sie die Vor- und "
-"Nachkompilierungsschritte für Ihren Quellcode durchführen."
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1336
-#, fuzzy, 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 ""
-"Alternativ können Sie sich auch ein vollständiges Beispiel zu Aufbau, "
-"Deployment und Validierung einer auf FIELD-Ebene replizierten Webanwendung "
-"auf der Seite: <literal>http://wiki.jboss.org/wiki/Wiki.jsp?"
-"page=Http_session_field_level_example</literal> ansehen. Das Beispiel "
-"bündelt die Vor- und Nachkompilierungstools, so dass Sie JBoss AOP nicht "
-"separat herunterladen müssen."
-
-#. 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 ""
-"Wenn Sie die Webanwendung im JBoss AS ausführen, vergewissern Sie sich, dass "
-"die folgenden Konfigurationen korrekt sind:"
-
-#. 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 ""
-"In der <literal>deploy/tc5-cluster.sar/META-INF/jboss-service.xml</literal>-"
-"Datei des Servers müssen die <literal>inactiveOnStartup</literal> und "
-"<literal>useMarshalling</literal>-Attribute beide <literal>true</literal> "
-"sein."
-
-#. 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 ""
-"In der <literal>jboss-web.xml</literal>-Datei der Anwendung muss das "
-"<literal>replication-granularity</literal>-Attribut <literal>FIELD</literal> "
-"lauten."
-
-#. 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 ""
-"Im folgenden wird nun noch die Replikation auf FIELD-Ebene an diesen "
-"Datenklassen erläutert. Bitte beachten Sie, dass es nicht nötig ist "
-"<literal>session.setAttribute()</literal> aufzurufen, nachdem Sie die "
-"Änderungen am Datenobjekt vorgenommen haben und dass sämtliche Änderungen in "
-"den Feldern automatisch über den Cluster hinweg repliziert werden."
-
-#. 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 ""
-"// 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."
-
-#. 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 ""
-"Neben Plain Objects können Sie auch reguläre Java Collections dieser Objekte "
-"als Session-Attribute verwenden. Das JBoss Cache weiß automatisch, wie diese "
-"Collections zu behandeln sind und repliziert Feldveränderungen in deren "
-"Mitgliedsobjekten."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1363
-#, no-c-format
-msgid "Monitoring session replication"
-msgstr "Überwachung der Session-Replikation"
-
-#. 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 ""
-"Wenn Sie Ihre Anwendung ausgeführt und aufgerufen haben, gehen Sie in das "
-"<literal>jboss.cache:service=TomcatClusteringCache</literal>-MBean und rufen "
-"Sie die <literal>printDetails</literal>-Funktion auf. Ihre Ausgabe sollte "
-"wie folgt aussehen."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1367
-#, fuzzy, 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"
-"/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 ""
-"Diese Ausgabe zeigt zwei separate Web-Sessions, die mittels JBossCache "
-"geteilt werden und von denen eine den Namen <emphasis>quote</emphasis> "
-"trägt. Das Beispiel verwendet eine <literal>replication-granularity</"
-"literal> von <literal>session</literal>. Wäre eine Replikation auf "
-"<literal>attribute</literal> Ebene verwendet werden, so wären weitere "
-"Eintragungen zu den einzelnen replizierten Session-Attributen vorhanden. In "
-"jedem Falle werden die replizierten Werte in einem nicht einsehbaren "
-"<literal>MarshelledValue</literal>-Container gespeichert. Es gibt derzeit "
-"keine Tools, mit denen Sie die Inhalte der replizierten Sessionwerte "
-"einsehen könnten. Falls Sie keine Ausgabe sehen, war die Anwendung entweder "
-"nicht ordnungsgemäß als <literal>distributable</literal> gekennzeichnet oder "
-"Sie haben keinen Teil der Anwendung aufgerufen, der Werte in der HTTP-"
-"Session ablegt. Die <literal>org.jboss.cache</literal> und <literal>org."
-"jboss.web</literal>-Protokollkategorien bieten zusätzlichen Einblick in die "
-"Replikation der Session, was inbesondere bei der Fehlersuche und -"
-"beseitigung hilfreich sein kann."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1377
-#, fuzzy, no-c-format
-msgid "Using Clustered Single Sign On"
-msgstr "Die Verwendung von \"Single Sign On\" (einmalige Anmeldung)"
-
-#. 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 ""
-"JBoss unterstützt den geclusterten \"Single Sign On\" (einmalige Anmeldung), "
-"bei der ein Benutzer sich bei einer Anwendung des JBoss Servers "
-"authentifiziert und dann von sämtlichen Anwendungen des Geräts oder eines "
-"anderen Nodes im Cluster, die innerhalb desselben virtuellen Hosts "
-"ausgeführt werden, erkannt wird. Die Authentifizierungsreplikation erfolgt "
-"durch den HTTP Session-Replikationsdienst. Obwohl die Session-Replikation "
-"für die betreffenden Anwendungen nicht explizit aktiviert sein muss, muss "
-"die <literal>tc5-cluster-service.xml</literal>-Datei nicht ausgeführt werden."
-
-#. 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 ""
-"Um \"Single Sign-On\" zu aktivieren, müssen Sie den "
-"<literal>ClusteredSingleSignOn</literal>-Valve den entsprechenden "
-"<literal>Host</literal>-Elementen der tomcat <literal>server.xml</literal>-"
-"Datei hinzufügen. Die Konfiguration des Valve sehen Sie hier:"
-
-#. 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 "Geclusterte JMS-Dienste"
-
-#. 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 "client-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 ""
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 "Geclusterte JMS-Dienste"
-
-#. 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 und spätere Versionen unterstützen \"High Availability\"-JMS "
-"(HA-JMS) Dienste in der <literal>all</literal>-Serverkonfiguration. In der "
-"aktuellen Version des JBoss AS, ist der HA-JMS Dienst als geclusterter "
-"Singleton Fail-Over-Dienst implementiert."
-
-#. 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 ""
-"Wenn Sie HA-JMS selbst zu konfigurieren bereit sind, können Sie mit früheren "
-"Versionen des JBoss AS arbeiten. Einer unserer Kunden verwendet HA-JMS "
-"erfolgreich in der JBoss AS 3.0.7 Version. Bitte setzen Sie sich mit dem "
-"JBoss-Support in Verbindung, falls Sie Fragen haben."
-
-#. 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 "Der \"High Availability Singleton Fail-over\""
-
-#. 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 ""
-"Der JBoss HA-JMS Dienst (d.h. Message Queues und Topics) wird zu einem "
-"beliebigen Zeitpunkt stets nur auf einem einzelnen Node (d.h. dem \"Master-"
-"Node\") im Cluster ausgeführt. Falls dieser Node ausfällt, wählt der Cluster "
-"einfach einen anderen Node aus, auf dem der JMS-Dienst ausgeführt wird (Fail-"
-"Over). Diese Konfiguration bietet Redundanz gegen Serverausfälle, senkt "
-"jedoch nicht die Arbeitsbelastung am JMS Server-Node."
-
-#. 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 ""
-"Während Sie bei HA-JMS Queues keine Lastverteilung anwenden können (es "
-"existiert nur ein Master-Node, der die Queues ausführt), können Sie die "
-"MDBs, die die Nachrichten dieser Queues verarbeitet, lastverteilen (siehe "
-"<xref linkend=\"clustering-jms-loadbalanced\"/>)."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1562
-#, no-c-format
-msgid "Server Side Configuration"
-msgstr "Die Konfiguration auf Serverseite"
-
-#. 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 ""
-"Um den Singleton Fail-Over HA-JMS Dienst zu verwenden, müssen Sie die JMS-"
-"Dienste auf sämtlichen Nodes des Clusters identisch konfigurieren. Das "
-"beinhaltet alle JMS bezogenen Service-MBeans und alle deployten JMS-"
-"Anwendungen."
-
-#. 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 ""
-"Der JMS Server ist so konfiguriert, dass er seine Daten im "
-"<literal>DefaultDS</literal> behält. In der Standardeinstellung ist das der "
-"eingebettete (\"embedded\") HSQLDB. In den meisten Clusterumgebungen jedoch "
-"müssen alle Nodes Daten gegen eine gemeinsame Datenbank halten. Ehe Sie also "
-"einen geclusterten JMS starten, müssen Sie eine gemeinsame Datenbank für JMS "
-"einrichten. Hierzu müssen Sie folgendes tun:"
-
-#. 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 ""
-"Ersetzen Sie die <literal>hsqldb-jdbc2-service.xml</literal>-Datei "
-"im<literal>server/all/deploy-hasingleton/jms</literal>-Verzeichnis mit einer "
-"speziell auf Ihre Bedürfnisse abgestimmten. Wenn Sie zum Beispiel MySQL "
-"verwenden, so heißt die Datei <literal>mysql-jdbc2-service.xml</literal>. "
-"Die Konfigurationsdateien für eine Reihe von RDBMS sind mit der JBoss AS "
-"Distribution gebündelt. Sie finden diese unter <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 ""
-"Die <literal>hsqldb-jdbc-state-service.xml</literal>-Datei im "
-"<literal>server/all/deploy-hasingleton/jms</literal>-Verzeichnis muss nicht "
-"ersetzt werden. Trotz des <literal>hsql</literal> in ihrem Namen "
-"funktioniert sie mit allen SQL92-konformen Datenbanken, einschließlich HSQL, "
-"MySQL, SQL-Server und einigen anderen. Zur Speicherung wird automatisch "
-"<literal>DefaultDS</literal> verwendet, wie wir es weiter oben konfiguriert "
-"haben."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1606
-#, fuzzy, no-c-format
-msgid "Non-MDB HA-JMS Clients"
-msgstr "Der HA-JMS Client"
-
-#. 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 ""
-"Der HA-JMS Client unterscheidet sich in zwei wichtigen Aspekten von "
-"regulären JMS-Clients."
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 "Lastverteilte 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 ""
-"Während HA-JMS Queues und Topics jeweils nur an einem einzelnen Node "
-"ausgeführt werden, können MDBs an mehreren Nodes Nachrichten vom HA-JMS "
-"Master-Node empfangen und bearbeiten. Die zweifelhaften Queues und Topics "
-"resultieren im lastverteilten Verhalten der MDBs. Um die Lastverteilung für "
-"MDBs zu aktivieren, können Sie einen Receiver für die Queue bestimmen. Der "
-"Receiver protokolliert welcher Node auf Nachricht wartet und in welcher "
-"Reihenfolge Nachrichten bearbeitet werden sollten. JBoss bietet drei "
-"Receiver-Implementierungen."
-
-#. 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 ""
-"Die Standard-Implementierung ist <literal>org.jboss.mq.server.ReceiversImpl</"
-"literal> unter Verwendung von <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 ""
-"<literal>org.jboss.mq.server.ReceiversImplArrayList</literal> ist die "
-"Implementierung unter Verwendung von <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 ""
-"<literal>org.jboss.mq.server.ReceiversImplLinkedList</literal> ist die "
-"Implementierung unter Verwendung von <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 "Das JBossCache und JGroups-Dienste"
-
-#. 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 und JBossCache liefern die zu Grunde liegende Kommunikation, Node-"
-"Replikation und Caching-Dienste für die JBoss AS Cluster. Diese Dienste sind "
-"als MBeans konfiguriert. Es existiert ein Satz von JBossCache und JGroups "
-"MBeans für jede Art von Clustering-Anwendung (z.B. die Stateful Session "
-"EJBs, die verteilten Entity-EJBs usw.)."
-
-#. 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 ""
-"Der JBoss AS kommt mit einem vernünftigen Satz von voreingestellten JGroups "
-"und JBossCache MBean-Konfigurationen. Die meisten Anwendungen funktionieren "
-"hervorragend mit den voreingestellten MBean-Konfigurationen. Anpassungen "
-"sind nur notwendig, wenn Sie eine Anwendung ausführen, die spezielle "
-"Anforderungen an das Netzwerk oder die Performance stellt."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1714
-#, no-c-format
-msgid "JGroups Configuration"
-msgstr "Die JGroups-Konfiguration"
-
-#. 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 ""
-"Das JGroups Framework liefert die Dienste, die die Peer-to-Peer "
-"Kommunikation zwischen den Nodes eines Clusters ermöglichen. Es basiert auf "
-"einem Stapel (\"stack\") von Netzwerkprotokollen, die Transport, Discovery, "
-"Reliabilty und Failure-Detection sowie Dienste zum Cluster Membership "
-"Management liefern. <xref linkend=\"jbosscache-JGroupsStack.fig\"/> zeigt "
-"das Protokoll-Stack (Protokoll-Stapel) in JGroups."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1719
-#, no-c-format
-msgid "Protocol stack in JGroups"
-msgstr "Protokollstapel in JGroups (\"Protocol Stack\")"
-
-#. 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 ""
-"JGroups Konfigurationen treten oftmals als Attribute innerhalb von "
-"clusterbezogenen MBean-Diensten auf, wie etwa das <literal>PartitionConfig</"
-"literal>-Attribut im <literal>ClusterPartition</literal>-MBean oder das "
-"<literal>ClusterConfig</literal>-Attribut im <literal>TreeCache</literal>-"
-"MBean. Mittels dieser MBean-Attribute können Sie das Verhalten und die "
-"Eigenschaften jedes Protokolls in JGroups konfigurieren. Nachfolgend sehen "
-"Sie ein Beispiel für eine JGroups-Konfiguration im "
-"<literal>ClusterPartition</literal>-MBean."
-
-#. 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 ""
-
-#. 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 "Andere Konfigurationsoptionen"
-
-#. 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 "Transportprotokolle (\"Transport Protocols\")"
-
-#. 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 ""
-"Die Transportprotokolle schicken Nachrichten von einem Cluster-Node an einen "
-"anderen (unicast) oder von Cluster-Node an alle anderen Nodes im Cluster "
-"(mcast). JGroups unterstützt die Transportprotokolle UDP, TCP und TUNNEL."
-
-#. 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 ""
-"Die Elemente <literal>UDP</literal>, <literal>TCP</literal> und "
-"<literal>TUNNEL</literal> sind wechselseitig exklusiv. Für jedes JGroups "
-"<literal>Config</literal>-Element kann es nur ein Transportprotokoll geben."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1766
-#, no-c-format
-msgid "UDP configuration"
-msgstr "Die UDP-Konfiguration"
-
-#. 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 ""
-"UDP ist das bevorzugte Protokoll für JGroups. UDP verwendet Multicast oder "
-"mehrere Unicasts um Nachrichten zu verschicken oder zu empfangen. Falls Sie "
-"UDP als das Transportprotokoll Ihres Cluster-Dienstes wählen, müssen Sie es "
-"im <literal>UDP</literal> Sub-Element im JGroups <literal>Config</literal>-"
-"Element konfigurieren. Nachfolgend sehen Sie ein Beispiel."
-
-#. 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 ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1774
-#, no-c-format
-msgid ""
-"The available attributes in the above JGroups configuration are listed below."
-msgstr ""
-"Die verfügbaren Attribute in der JGroups-Konfiguration oben sind nachfolgend "
-"aufgeführt."
-
-#. 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> bestimmt ob IP-Multicasting "
-"verwendet wird oder nicht. Die Standardeinstellung lautet <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> bestimmt die Multicast-Adresse "
-"(Klasse D) zum Anschluss an eine Gruppe (d.h. den Cluster). Der "
-"voreingestellte Wert ist hier <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> bestimmt die Nummer des "
-"Multicast-Ports. Der voreingestellte Wert ist hier <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> legt das Interface fest, auf "
-"dem Multicasts empfangen und verschickt werden (verwendet die <literal>bind."
-"address</literal> Systemeigenschaft, falls vorhanden). Falls Sie ein "
-"Multihome-Gerät besitzen, stellen Sie das <literal>bind_addr</literal>-"
-"Attribut auf die entsprechende NIC IP-Adresse ein. Dieses wird ignoriert, "
-"falls die <literal>ignore.bind.address</literal>-Property \"true\" ist."
-
-#. 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> legt fest, ob ein "
-"Node auf allen Interfaces auf Multicasts reagiert. Der voreingestellte Wert "
-"lautet hier <literal>false</literal>. Es setzt die <literal>bind_addr</"
-"literal>-Property zum Empfang von Multicasts außer Kraft. Jedoch wird "
-"<literal>bind_addr</literal> (falls eingestellt) nach wie vor zum "
-"Verschicken von Multicasts verwendet."
-
-#. 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> legt fest, ob "
-"ein separater Thread bei der Bearbeitung herausgehender Nachrichten "
-"verwendet wird."
-
-#. 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> legt fest, ob das "
-"\"Bundling\" (Bündelung) aktiviert wird. Falls die Einstellung hier "
-"<literal>true</literal> lautet, erstellt der Node eine Warteschlange der "
-"herausgehenden Nachrichten bis diese <literal>max_bundle_size</literal> "
-"Bytes oder <literal>max_bundle_time</literal> Millisekunden erreicht haben, "
-"je nachdem welcher Wert zuerst erreicht wird. Die in der Warteschlange "
-"befindlichen Nachrichten werden dann zu einer großen Nachricht gebündelt und "
-"verschickt. Diese wird dann vom Receiver entbündelt. Der voreingestellte "
-"Wert lautet <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> legt fest, ob herausgehende "
-"Nachrichten wieder dem Stack zugeführt werden. Im <literal>unicast</literal>-"
-"Modus werden die Nachrichten an sich selbst geschickt. Im <literal>mcast</"
-"literal>-Modus wird eine Kopie der mcast-Nachricht verschickt."
-
-#. 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> legt fest, ob "
-"Pakete unterschiedlicher Versionen von JGroups verworfen werden. Jede "
-"Nachricht im Cluster wird mit einer Version von JGroups markiert. Wenn eine "
-"Nachricht von einer anderen JGroups-Version eingeht, wird diese bei der "
-"Einstellung \"true\" verworfen, andernfalls wird eine Warnung protokolliert."
-
-#. 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> definiert die "
-"Puffergrößen von \"receive\" und \"send\" (empfangen und senden). Es "
-"empfiehlt sich einen großen Puffer (Zwischenspeicher) für den Receiver zu "
-"wählen, damit Pakete nicht aufgrund eines Pufferüberlaufs verloren gehen."
-
-#. 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 ""
-"Bei Windows 2000 Geräten müssen Sie - aufgrund der Außerstandsetzung des "
-"\"Media Sense Features\" durch Multicast (auch nach Deaktivierung von Media "
-"Sense) - beim UDP-Protokoll <literal>loopback</literal> das Attribut auf "
-"<literal>true</literal> setzen."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1859
-#, no-c-format
-msgid "TCP configuration"
-msgstr "Die TCP-Konfiguration"
-
-#. 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 ""
-"Alternativ kann ein auf JGroups basierender Cluster auch über TCP-"
-"Verbindungen laufen. Im Vergleich zu UDP, generiert TCP bei einem Anstieg "
-"der Clustergröße zwar mehr Netzwerkverkehr, ist aber auch verlässlicher. TCP "
-"ist im Wesentlichen ein Unicast-Protokoll. Um Multicast-Nachrichten zu "
-"versenden, verwendet JGroups mehrere TCP-Unicasts. Zur Verwendung von TCP "
-"als Transportprotokoll sollten Sie ein <literal>TCP</literal>-Element im "
-"JGroups <literal>Config</literal>-Element definieren. Nachfolgend sehen Sie "
-"ein Beispiel für das <literal>TCP</literal>-Element."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1866
-#, fuzzy, 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\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1867
-#, no-c-format
-msgid ""
-"Below are the attributes available in the <literal>TCP</literal> element."
-msgstr ""
-"Nachfolgend sehen Sie die im <literal>TCP</literal>-Element verfügbaren "
-"Attribute."
-
-#. 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> legt die Binding-Addresse fest. "
-"Es kann auch mittels der <literal>-Dbind.address</literal>-Befehlszeile bei "
-"Inbetriebnahme des Servers eingestellt werden."
-
-#. 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> legt fest, ob herausgehende "
-"Nachrichten wieder dem Stack zugeführt werden. Im <literal>unicast</literal>-"
-"Modus werden die Nachrichten an sich selbst geschickt. Im <literal>mcast</"
-"literal>-Modus wird eine Kopie der mcast-Nachricht verschickt."
-
-#. 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> definiert die "
-"Puffergrößen von \"receive\" und \"send\" (empfangen und senden). Es "
-"empfiehlt sich einen großen Puffer (Zwischenspeicher) für den Receiver zu "
-"wählen, damit Pakete nicht aufgrund eines Pufferüberlaufs verloren gehen."
-
-#. 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> bestimmt (in "
-"Millisekunden) die Zeit nach der eine Verbindung vom Reaper geschlossen "
-"werden kann, wenn kein Verkehr empfangen wurde."
-
-#. 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> bestimmt in "
-"(Millisekunden) den Intervall in dem der Reaper ausgeführt wird. Wenn beide "
-"Werte \"0\" lauten, findet kein Reaping statt. Wenn einer der beiden Werte "
-"> 0 ist, so ist das Reaping aktiviert."
-
-#. 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> legt fest, ob "
-"ein separater Thread bei der Bearbeitung eingehender Nachrichten verwendet "
-"wird."
-
-#. 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> bestimmt ob IP-Multicasting "
-"verwendet wird oder nicht. Die Standardeinstellung lautet <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 "Die TUNNEL-Konfiguration"
-
-#. 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 ""
-"Das TUNNEL-Protokoll verwendet einen externen Router, um Nachrichten zu "
-"verschicken. Der externe Router ist unter dem Namen <literal>GossipRouter</"
-"literal> bekannt. Jeder Node muss sich beim Router anmelden. Alle "
-"Nachrichten werden an den Router geschickt und an die jeweiligen Ziele "
-"weitergeleitet. Die TUNNEL-Methode kann beim Aufbau der Kommunikation mit "
-"Nodes hinter Firewalls verwendet werden. Ein Node kann eine TCP-Verbindung "
-"zum GossipRouter durch die Firewall herstellen (Sie können Port 80 "
-"verwenden). Diesselbe Verbindung wird vom Router verwendet, um Nachrichten "
-"an Nodes hinter der Firewall zu verschicken. Die TUNNEL-Konfiguration ist im "
-"<literal>TUNNEL</literal>-Element im JGroups <literal>Config</literal>-"
-"Element defieniert. Nachfolgend sehen Sie ein Beispiel:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:1929
-#, fuzzy, 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\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1932
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>TUNNEL</literal> element are listed "
-"below."
-msgstr ""
-"Die verfügbaren Attribute im <literal>TUNNEL</literal>-Element sind unten "
-"aufgeführt."
-
-#. 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> bestimmt den Host, auf dem "
-"der GossipRouter ausgeführt wird."
-
-#. 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> bestimmt den Port, auf den "
-"der GossipRouter reagiert."
-
-#. 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> legt fest, ob Nachrichten zum "
-"\"Stack\" zurückgeführt werden. Der voreingestellte Wert lautet hier "
-"<literal>true</literal>."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:1954
-#, no-c-format
-msgid "Discovery Protocols"
-msgstr "Discovery-Protokolle"
-
-#. 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 ""
-"Der Cluster muss zu jedem beliebigen Zeitpunkt eine Liste der aktuellen "
-"Mitgliedernodes führen, damit Lastverteiler und Client-Interceptor wissen, "
-"wie Anfragen weitergeleitet werden sollen. Die Discovery-Protokolle dienen "
-"dazu, aktive Nodes im Cluster aufzuspüren. Alle vorhandenen Nodes werden "
-"festgestellt, wenn der Cluster startet. Kommt später ein neuer Node hinzu, "
-"so wird er erst aufgespürt, nachdem das Group-Membership-Protocol (GMS, "
-"siehe <xref linkend=\"jbosscache-jgroups-other-gms\"/>) ihn der Gruppe "
-"zuführt."
-
-#. 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 ""
-"Da die Discovery-Protokolle über den Transportprotokollen angesiedelt sind, "
-"können Sie je nach Ihrem eigenen Transportprotokoll unterschiedliche "
-"Discovery-Protokolle verwenden. Die Discovery-Protokolle sind auch als Sub-"
-"Elemente im JGroups MBean <literal>Config</literal>-Element konfiguriert."
-
-#. 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
-#, fuzzy, 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\"/>"
-
-#. 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 ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:1981
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>PING</literal> element are listed "
-"below."
-msgstr ""
-"Die verfügbaren Attribute im <literal>PING</literal>-Element sind unten "
-"aufgeführt."
-
-#. 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> legt die maximale Anzahl von "
-"Millisekunden fest, die auf Rückmeldungen gewartet wird."
-
-#. 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> legt die maximale "
-"Anzahl von Rückmeldungen fest, auf die gewartet wird."
-
-#. 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> bestimmt den Host, auf dem "
-"der GossipRouter ausgeführt wird."
-
-#. 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> bestimmt den Port, auf den "
-"der GossipRouter reagiert."
-
-#. 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> bestimmt (in "
-"Millisekunden) den Intervall der Lease vom 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 ""
-"Bei <emphasis role=\"bold\">initial_hosts</emphasis> handelt es sich um eine "
-"durch Kommas getrennte Adressenliste (z.B. <literal>host1[12345],host2[23456]"
-"</literal>), die für die Discovery angepingt werden."
-
-#. 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 ""
-"Wenn sowohl <literal>gossip_host</literal> als auch <literal>gossip_port</"
-"literal> definiert sind, so verwendet der Cluster den GossipRouter für die "
-"Initial-Discovery. Wenn der <literal>initial_hosts</literal> bestimmt ist, "
-"pingt der Cluster diese statische Adressenliste für die Discovery an. "
-"Andernfalls verwendet der Cluster IP-Multicasting für die Discovery."
-
-#. 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 ""
-"Die Discovery-Phase beginnt erneut, wenn die <literal>timeout</literal> ms "
-"vergangen sind oder die <literal>num_initial_members</literal> Rückmeldungen "
-"empfangen wurden."
-
-#. 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 ""
-"Das TCPGOSSIP-Protokoll hat ausschließlich mit dem GossipRouter zu tun. Es "
-"funktioniert im Wesentlichen auf dieselbe Weise wie die PING-"
-"Protokollkonfiguration mit gültigen <literal>gossip_host</literal> und "
-"<literal>gossip_port</literal> Attributen. Es ist über den UDP- und TCP-"
-"Transportprotokollen angesiedelt. Nachfolgend sehen Sie ein Beispiel:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2026
-#, fuzzy, 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 ""
-"<PING timeout=\"2000\"\n"
-" initial_hosts=\"192.168.5.1[12000],192.168.0.2[12000]\"\n"
-" num_initial_members=\"3\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2029
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>TCPGOSSIP</literal> element are "
-"listed below."
-msgstr ""
-"Die verfügbaren Attribute im <literal>TCPGOSSIP</literal>-Element sind "
-"nachfolgend aufgeführt."
-
-#. 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 ""
-"Bei <emphasis role=\"bold\">initial_hosts</emphasis> handelt es sich um eine "
-"durch Kommas getrennte Adressenliste (z.B. <literal>host1[12345],host2[23456]"
-"</literal>) für die Anmeldung der GossipRouter."
-
-#. 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 ""
-"Das TCPPING-Protokoll übernimmt einen Satz bekannter Mitglieder und pingt "
-"diese für Discovery an. Es handelt sich hierbei im Wesentlichen um eine "
-"statische Konfiguration über dem TCP. Nachfolgend sehen Sie ein Beispiel des "
-"<literal>TCPPING</literal>-Konfigurationselements im JGroups "
-"<literal>Config</literal>-Element."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2055
-#, fuzzy, 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=\"192.168.5.1[7800],192.168.0.2[7800]\"\n"
-" port_range=\"2\"\n"
-" num_initial_members=\"3\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2058
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>TCPPING</literal> element are "
-"listed below."
-msgstr ""
-"Nachfolgend sind die verfügbaren Attribute im <literal>TCPPING</literal>-"
-"Element aufgeführt."
-
-#. 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 ""
-"Bei <emphasis role=\"bold\">initial_hosts</emphasis> handelt es sich um eine "
-"durch Kommas getrennte Adressenliste (z.B. <literal>host1[12345],host2[23456]"
-"</literal>) für das Pingen."
-
-#. 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
-#, fuzzy, 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\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2092
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>MPING</literal> element are listed "
-"below."
-msgstr ""
-"Nachfolgend sind die verfügbaren Attribute im <literal>MPING</literal>-"
-"Element aufgeführt."
-
-#. 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> legt die maximale "
-"Anzahl von Rückmeldungen fest, auf die gewartet wird."
-
-#. 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> bestimmt das Interface, an der "
-"Multicast-Pakete gesendet und empfangen werden."
-
-#. 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> setzt die "
-"<literal>bind_addr</literal> außer Kraft und verwendet alle Interfaces in "
-"Multihome-Nodes."
-
-#. 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 ""
-"Die <emphasis role=\"bold\">mcast_addr, mcast_port, ip_ttl</emphasis>-"
-"Attribute sind dieselben wie die entsprechenden Attribute in der UDP-"
-"Protokollkonfiguration."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2121
-#, no-c-format
-msgid "Failure Detection Protocols"
-msgstr "Protokolle zur Fehlerermittlung (\"Failure Detection Protocols\")"
-
-#. 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 ""
-"Die Protokolle zur Fehlerermittlung helfen beim Auffinden ausgefallener "
-"Nodes. Sobald ein ausgefallener Node ermittelt wurde, wird der Cluster "
-"aktualisiert, so dass Lastverteiler und Client-Interceptoren den "
-"ausgefallenen Node meiden. Die Protokolle zur Fehlerermittlung sind als Sub-"
-"Elemente im JGroups MBean <literal>Config</literal>-Element konfiguriert."
-
-#. 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 ""
-"Beim FD-Discovery-Protokoll schickt jeder Node regelmäßig Zustandsanfrage "
-"(so genannte \"are-you-alive messages\") an seinen Nachbar-Node. Falls "
-"dieser nicht reagiert, wird eine SUSPECT-Nachricht vom anfragenden Node an "
-"den Cluster geschickt. Der aktuelle Gruppenkoordinator (\"group coordinator"
-"\") überprüft noch einmal, ob der verdächtige Node tatsächlich ausgefallen "
-"ist und aktualisiert den Cluster entsprechend. Nachfolgend sehen Sie ein "
-"Beispiel für die FD-Konfiguration."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2133
-#, fuzzy, 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\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2136
-#, no-c-format
-msgid ""
-"The available attributes in the <literal>FD</literal> element are listed "
-"below."
-msgstr ""
-"Die verfügbaren Attribute im <literal>FD</literal>-Element sind nachfolgend "
-"aufgeführt."
-
-#. 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> bestimmt die Anzahl von "
-"Millisekunden, die auf Rückmeldung auf die Zustandsanfrage (die \"are-you-"
-"alive messages\") gewartet wird."
-
-#. 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> Bestimmt die Anzahl verpasster "
-"Zustandsanfragen eines Nodes, ehe von einem Ausfall desselben ausgegangen "
-"wird."
-
-#. 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> bestimmt, ob ein ausgefallener Node "
-"gemieden wird. Falls dies der Fall ist, so wird er vom Cluster "
-"ausgeschlossen selbst wenn er später wieder funktioniert. Der "
-"ausgeschlossene Node wird erst durch den Discovery-Prozess wieder Teil des "
-"Clusters."
-
-#. 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 ""
-"Der reguläre Verkehr eines Nodes zählt als sei dieser aktiv. Die "
-"Zustandsanfragen werden nur verschickt, wenn an einem betreffenden Node eine "
-"Zeit lang kein regulärer Verkehr stattgefunden hat."
-
-#. 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
-#, fuzzy, no-c-format
-msgid "<FD_SOCK_down_thread=\"false\" up_thread=\"false\"/>"
-msgstr ""
-"<pbcast.STATE_TRANSFER \n"
-" down_thread=\"false\"\n"
-" 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 ""
-"Die verfügbaren Attribute im <literal>FD</literal>-Element sind nachfolgend "
-"aufgeführt."
-
-#. 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> legt das Interface "
-"fest, mit dem das Server-Socket sich verbindet. Wird es weggelassen, so wird "
-"die <literal>-D bind.address</literal>-Property von der Server-Startup "
-"Befehlszeile verwendet."
-
-#. 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 ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2187
-#, fuzzy, no-c-format
-msgid "The available attributes in the FD_SOCK element are listed below."
-msgstr ""
-"Die verfügbaren Attribute im <literal>FD</literal>-Element sind nachfolgend "
-"aufgeführt."
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 "Zuverlässige Übertragungsprotokolle (\"Reliable Delivery Protocols\")"
-
-#. 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 ""
-"Die zuverlässigen Übertragungsprotokolle (\"Reliable Delivery Protocols\") "
-"im JGroups Datenstapel (\"Stack\") gewährleisten, dass die Datenpakete den "
-"Ziel-Node in der richtigen Reihenfolge (FIFO) erreichen. Die Grundlage der "
-"zuverlässigen Nachrichtenübermittlung ist die positive bzw. negative "
-"Empfangsbestätigung (ACK und NAK). Im ACK-Modus verschickt der Sender die "
-"Nachricht so lange, bis vom Empfänger (dem \"Receiver\") die Bestätigung "
-"erhalten wird. Im NAK-Modus fordert der Empfänger eine erneute Übertragung "
-"an, wenn er eine Unterbrechung entdeckt."
-
-#. 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 ""
-"Das UNICAST-Protokoll kommt bei Unicast-Messages zum Einsatz und verwendet "
-"ACK. Es ist als Subelement unter dem JGroups <literal>Config</literal>-"
-"Element konfiguriert. Nachfolgend sehen Sie ein Beispiel für das "
-"<literal>UNICAST</literal>-Protokoll."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2313
-#, fuzzy, no-c-format
-msgid ""
-"<UNICAST timeout=\"100,200,400,800\"\n"
-"down_thread=\"false\" up_thread=\"false\"/>"
-msgstr "<UNICAST timeout=\"100,200,400,800\"/>"
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2315
-#, no-c-format
-msgid ""
-"There is only one configurable attribute in the <literal>UNICAST</literal> "
-"element."
-msgstr ""
-"Es existiert nur ein konfigurierbares Attribut im <literal>UNICAST</literal>-"
-"Element."
-
-#. 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> legt (in Millisekunden) den "
-"Timeout für die erneute Übertragung fest. Wenn zum Beispiel der Timeout "
-"\"100,200,400,800\" lautet, so verschickt der Sender bei Nichterhalten einer "
-"ACK die Nachricht nach 100 ms zum ersten Mal erneut. Beim zweiten Mal wartet "
-"er 200 ms bis zum erneuten Senden, usw."
-
-#. 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 ""
-"Das NAKACK-Protokoll kommt bei Multicast-Nachrichten zum Einsatz und "
-"verwendet NAK. Bei diesem Protokoll wird wird jede Nachricht mit einer "
-"laufenden Nummer gekennzeichnet. Der Receiver kontrolliert die laufenden "
-"Nummern und liefert die Nachrichten in ihrer Reihenfolge aus. Wird eine "
-"Lücke in der Laufnummer entdeckt, so fragt der Receiver beim Sender um "
-"erneute Übertragung der vermissten Nachricht an. Das NAKACK-Protokoll ist "
-"als <literal>pbcast.NAKACK</literal>-Subelement unter dem JGroups "
-"<literal>Config</literal>-Element konfiguriert. Nachfolgend sehen Sie eine "
-"Beispielkonfiguration."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2336
-#, fuzzy, 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\n"
-" max_xmit_size=\"8192\"\n"
-" use_mcast_xmit=\"true\" \n"
-" retransmit_timeout=\"600,1200,2400,4800\"/>"
-
-#. 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 ""
-"Die konfigurierbaren Attribute im <literal>pbcast.NAKACK</literal>-Element "
-"lauten wie folgt."
-
-#. 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> legt (in "
-"Millisekunden) den Timeout für die erneute Übertragung fest. Es ist dasselbe "
-"wie das <literal>timeout</literal>-Attribut im UNICAST-Protokoll."
-
-#. 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> bestimmt, ob der Sender "
-"die erneute Übertragung an den gesamten Cluster schickt statt nur an den "
-"anfragenden Node. Dies ist hilfreich damit - falls der Sender das Paket "
-"verliert - nicht für jeden Node erneut Übertragen werden muss."
-
-#. 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> bestimmt die maximale Größe "
-"einer gebündelten, erneuten Übertragung, falls mehrere Pakete als fehlend "
-"gemeldet wurden."
-
-#. 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> legt fest, ob "
-"Übergabe-Meldungen (\"Delivery Messages\") an den Nodes des Receivers "
-"verworfen werden. In der Standardeinstellung werden alle übergebenen "
-"Nachrichten gespeichert. Falls der Sender seine Nachrichten jedoch nur "
-"erneut verschicken soll, so kann diese Option aktiviert und empfangene "
-"Nachrichten verworfen werden."
-
-#. 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>: Der Name der Klasse, die die "
-"Implementierung des Dienstes liefert."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2375
-#, no-c-format
-msgid "Other Configuration Options"
-msgstr "Andere Konfigurationsoptionen"
-
-#. 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 ""
-"Neben den Protokoll-Stacks können auch JGroups Netzwerk-Dienste im "
-"<literal>Config</literal>-Element konfiguriert werden."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2380
-#, no-c-format
-msgid "Group Membership"
-msgstr "Gruppenzugehörigkeit (\"Group Membership\")"
-
-#. 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 ""
-"Der Gruppenzugehörigkeitsdienst (\"Group Membership Service\") im JGroups "
-"Stack führt eine Liste aktiver Nodes. Er bearbeitet auch Anfragen zu "
-"Beitritt und Austritt in den bzw. aus dem Cluster. Auch die von den "
-"Protokollen zur Fehlerermittlung verschickten SUSPECT-Nachrichten werden "
-"hier bearbeitet. Alle Nodes im Cluster, ebenso wie Lastverteiler und "
-"clientbasierte Interceptoren werden benachrichtigt, falls Veränderungen in "
-"der Gruppenzugehörigkeit eintreten. Der Gruppenzugehörigkeitsdienst ist im "
-"<literal>pbcast.GMS</literal>-Subelement unter dem JGroups <literal>Config</"
-"literal>-Element konfiguriert. Nachfolgend sehen Sie eine "
-"Beispielkonfiguration."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2387
-#, fuzzy, 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\" \n"
-" join_retry_timeout=\"2000\"\n"
-" shun=\"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 ""
-"Die konfigurierbaren Attribute im <literal>pbcast.GMS</literal>-Element "
-"lauten wie folgt."
-
-#. 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> legt die maximale Anzahl von "
-"Millisekunden fest, die bei der JOIN-Anfrage eines neuen Nodes gewartet "
-"wird. Anschließend folgt ein erneuter Versuch."
-
-#. 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> legt die maximale "
-"Anzahl von Millisekunden fest, die gewartet wird ehe eine fehlgeschlagene "
-"JOIN-Anfrage erneut eingereicht wird."
-
-#. 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> legt fest, ob beim Start "
-"die eigene Adresse des Nodes in der Ausgabe (\"Output\") angezeigt wird."
-
-#. 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> legt fest, ob ein Node sich selbst "
-"meiden sollte, falls er eine Clusterdarstellung erhält, die kein "
-"Mitgliedsnode ist."
-
-#. 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> legt fest, ob "
-"dieser Node als Cluster-Koordinator fungieren kann."
-
-#. 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 "Flussregelung (\"Flow Control\")"
-
-#. 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 ""
-"Der Flussregelungsdienst (\"Flow Control Service\") versucht die "
-"Übertragungsgeschwindigkeit der gesendeten und der empfangenen Daten "
-"anzupassen. Falls ein Sender-Node zu schnell ist, könnte das den Empfänger-"
-"Node überfordern und zum Verlust von Paketen führen, die dann erneut "
-"übertragen werden müssen. In JGroups ist die Flussregelung mittels eines auf "
-"\"Guthaben\" basierenden Systems implementiert (ein so genanntes \"credit-"
-"based system\"). Sender- und Empfänger-Nodes besitzen zu Beginn diesselbe "
-"Guthabenmenge (Bytes). Der Sender subtrahiert Guthaben je nach der Bytezahl "
-"der von ihm verschickten Nachrichten. Der Empfänger addiert Guthaben je nach "
-"der Bytezahl der von ihm erhaltenen Nachrichten. Wenn das Guthaben des "
-"Senders auf einen bestimmten Grenzwert absinkt, so schickt der Empfänger "
-"Guthaben an den Sender. Falls das Guthaben des Senders aufgebraucht ist, so "
-"blockiert der Sender, bis er Guthaben vom Empfänger erhalten hat. Der "
-"Flussregelungsdienst (\"Flow Control\") ist im <literal>FC</literal>-"
-"Subelement unter dem JGroups <literal>Config</literal>-Element konfiguriert. "
-"Nachfolgend sehen Sie eine Beispielkonfiguration."
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2435
-#, fuzzy, 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\" \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 ""
-"Die konfigurierbaren Attribute im <literal>FC</literal>-Element lauten wie "
-"folgt:"
-
-#. 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> legt die maximale Höhe des "
-"Guthabens (in Bytes) fest. Dieser Wert sollte niedriger sein als der JVM "
-"Heap-Speicher (d.h. der \"Heap Size\")."
-
-#. 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> bestimmt den Grenzwert am "
-"Sender, bei dem der Receiver mit dem Verschicken von Guthaben beginnen "
-"sollte."
-
-#. 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> legt den Prozentwert des "
-"Grenzwerts fest. Er setzt das <literal>min_credits</literal>-Attribut außer "
-"Kraft."
-
-#. 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 ""
-
-#. Tag: para
-#: Clustering_Guide_Introduction.xml:2470
-#, fuzzy, no-c-format
-msgid "The configurable attributes in the FRAG2 element are as follows."
-msgstr ""
-"Die konfigurierbaren Attribute im <literal>FC</literal>-Element lauten wie "
-"folgt:"
-
-#. 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> legt die maximale Höhe des "
-"Guthabens (in Bytes) fest. Dieser Wert sollte niedriger sein als der JVM "
-"Heap-Speicher (d.h. der \"Heap Size\")."
-
-#. 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 "Status-Transfer (\"State Transfer\")"
-
-#. 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 ""
-"Der Status-Transfer-Dienst überträgt den Status von einem bestehenden Node "
-"(d.h. dem Cluster-Koordinator) auf einen neu hinzu kommenden Node. Er ist im "
-"<literal>pbcast.STATE_TRANSFER</literal> -Subelement unter dem JGroups "
-"<literal>Config</literal>-Element konfiguriert. Er besitzt keine "
-"konfigurierbaren Attribute. Nachfolgend sehen Sie eine Beispielkonfiguration:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2495
-#, fuzzy, no-c-format
-msgid ""
-"<pbcast.STATE_TRANSFER down_thread=\"false\" up_thread=\"false\"/>"
-msgstr ""
-"<pbcast.STATE_TRANSFER \n"
-" down_thread=\"false\"\n"
-" up_thread=\"false\"/>"
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2502
-#, no-c-format
-msgid "Distributed Garbage Collection"
-msgstr "Verteilte Speicherbereinigung (\"Distributed Garbage Collection\")"
-
-#. 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 ""
-"In einem JGroups Cluster müssen alle Nodes sämtliche erhaltenen Nachrichten "
-"speichern, um sie gegebenenfalls (bei einem Fehler) erneut zu übertragen. "
-"Werden jedoch alle Nachrichten ohne zeitliche Einschränkung gespeichert, so "
-"ist der Speicher irgendwann voll. Die verteilte Speicherbereinigung "
-"(\"Distributed Garbage Collection\") löscht daher periodisch Nachrichten, "
-"die von sämtlichen Nodes erhalten wurden aus deren Speicher. Die verteilte "
-"Speicherbereinigung ist im <literal>pbcast.STABLE</literal>-Subelement unter "
-"dem JGroups <literal>Config</literal>-Element konfiguriert. Nachfolgend "
-"sehen Sie eine Beispielkonfiguration:"
-
-#. 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 ""
-"Die konfigurierbaren Attribute im <literal>pbcast.STABLE</literal>-Element "
-"lauten wie folgt:"
-
-#. 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> legt in Millisekunden "
-"die Intervalle fest, in denen die Speicherbereinigung durchgeführt wird. Der "
-"Wert <literal>0</literal> deaktiviert diesen Dienst."
-
-#. 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> legt die maximale Anzahl "
-"empfangener Bytes fest, ehe vom Cluster eine Speicherbereinigung ausgelöst "
-"wird. Der Wert <literal>0</literal> deaktiviert diesen Dienst."
-
-#. 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 ""
-"Setzen Sie das <literal>max_bytes</literal>-Attribut, falls es sich bei "
-"Ihrem Cluster um einen Cluster mit viel Verkehr handelt."
-
-#. Tag: title
-#: Clustering_Guide_Introduction.xml:2531
-#, no-c-format
-msgid "Merging"
-msgstr "Zusammenführung (\"Merging\")"
-
-#. 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 ""
-"Im Falle eines Netzwerkfehlers kann der Cluster in mehrere Partitionen "
-"aufgeteilt werden. JGroups bietet einen MERGE-Dienst, mit dem die "
-"Koordinatoren der Partitionen miteinander kommunizieren und sich erneut zu "
-"einem einzelnen Cluster zusammenschließen können. Der Flussregelungsdienst "
-"ist im <literal>MERGE2</literal>-Subelement unter dem JGroups "
-"<literal>Config</literal>-Element konfiguriert. Nachfolgend sehen Sie eine "
-"Beispielkonfiguration:"
-
-#. Tag: programlisting
-#: Clustering_Guide_Introduction.xml:2536
-#, fuzzy, 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\"/>"
-
-#. 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> bestimmt die maximale Anzahl "
-"von Millisekunden bis eine MERGE-Nachricht verschickt wird."
-
-#. 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> bestimmt die minimale Anzahl "
-"von Millisekunden bis eine MERGE-Nachricht verschickt wird."
-
-#. 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 ""
-"JGroups wählt einen zufälligen Wert zwischen <literal>min_interval</literal> "
-"und <literal>max_interval</literal> zum Verschicken der MERGE-Nachricht."
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 ""
-
-#. 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 ""
Deleted: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/de-DE/Clustering_Intro.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/de-DE/Clustering_Intro.po 2009-02-17 00:26:09 UTC (rev 84283)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/de-DE/Clustering_Intro.po 2009-02-17 00:26:28 UTC (rev 84284)
@@ -1,775 +0,0 @@
-# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
-# Automatically generated, 2007.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: JBEAP 420\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#: Clustering_Intro.xml:6
-#, no-c-format
-msgid "Quick Tutorial to Setup a Clustered Web Application"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:7
-#, no-c-format
-msgid ""
-"Web server clustering is to use multiple JBoss AS server instances to serve "
-"the same web address (e.g., http://www.jboss.com/). It is one of the most "
-"common clustering architectures JBoss AS users deploy. In this tutorial, we "
-"discuss the basic architecture of a web cluster and give step-by-step "
-"instructions on how to setup the cluster. A very simple web cluster looks "
-"like <xref linkend=\"Quick_Tutorial_to_Setup_a_Clustered_Web_Application-"
-"A_very_simple_web_cluster\"/>."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:11
-#, no-c-format
-msgid "A very simple web cluster"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:18
-#, no-c-format
-msgid ""
-"A lightweight web server, known as the load balancer, receives all HTTP "
-"requests from that web address and dispatches them to JBoss AS nodes in the "
-"cluster. The JBoss AS node does the heavy lifting of processing the request "
-"and generating the response. All the JBoss AS nodes share the same database "
-"server for persistent data in the application. Notice that each node "
-"contains the entire JBoss AS stack, including the web server, servlet "
-"container, EJB container, persistence manager etc. Breaking the JBoss AS "
-"stack to different physical servers would substantially complicate the "
-"architecture but without much scalability benefit."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:22
-#, no-c-format
-msgid "Setup the simple web cluster"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:23
-#, no-c-format
-msgid ""
-"In our simple cluster depicted in <xref linkend="
-"\"Quick_Tutorial_to_Setup_a_Clustered_Web_Application-"
-"A_very_simple_web_cluster\"/>, every JBoss AS node is independent of each "
-"other. The load balancer \"remembers\" the user sessions and always forwards "
-"requests from the same session to the same JBoss AS node (a.k.a sticky "
-"session). So, each JBoss AS node stores its own set of HTTP session data. "
-"There is no information sharing between JBoss AS nodes, besides the "
-"persistent data in the shared database."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:26
-#, no-c-format
-msgid ""
-"Assuming that the load balancer and the shared database are not performance "
-"bottlenecks, this cluster can scale linearly with the number of JBoss AS "
-"nodes. Of course, the simplicity and scalability has their price. The most "
-"obvious shortcomings of the this simple architecture are the lack of support "
-"for failover and database cache. We will look at solutions for those "
-"problems in <xref linkend=\"Optional_improvements_to_the_simple_cluster-"
-"Database_cache\"/>."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:30
-#, fuzzy, no-c-format
-msgid "Setup the load balancer"
-msgstr "Der Lastverteiler"
-
-#. Tag: para
-#: Clustering_Intro.xml:31
-#, no-c-format
-msgid ""
-"The easiest way to setup a load balancer is to use the Apache web server "
-"with the mod_jk module to interact with JBoss AS. After installing the "
-"Apache web server, you should download the mod_jk 1.2.x binary from <ulink "
-"url=\"http://www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/\"> "
-"http://www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/</ulink>. "
-"Rename the downloaded file to mod_jk.so and copy it under APACHE_HOME/"
-"modules/ directory."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:35
-#, no-c-format
-msgid "Use mod_jk 1.2.x"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:36
-#, no-c-format
-msgid ""
-"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."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:41
-#, no-c-format
-msgid ""
-"Aside from loading balancing, using Apache mod_jk to front JBoss AS servers "
-"have other benefits. The most important one is that Apache serves static "
-"content (e.g., images) much faster than Tomcat (i.e., the embedded servlet "
-"server in JBoss AS). Apache also handles SSL and keep-alive connections much "
-"more efficiently than Tomcat. In addition, Apache provides modules for "
-"access control, URL rewriting, CGI/PHP execution. So, we recommend fronting "
-"JBoss AS with Apache mod_jk even if you have only one JBoss AS node."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:45
-#, no-c-format
-msgid ""
-"To tell the Apache server to use mod_jk, you need to add the following line "
-"to the APACHE_HOME/conf/httpd.conf file."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:48
-#, no-c-format
-msgid "Add this to the httpd.conf file"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Intro.xml:49
-#, fuzzy, no-c-format
-msgid ""
-"# Include mod_jk's specific configuration file\n"
-"Include conf/mod_jk.conf"
-msgstr ""
-"# Fügen Sie die spezielle Konfigurationsdatei von mod_jk ein \n"
-"Setzen Sie conf/mod-jk.conf ein"
-
-#. Tag: para
-#: Clustering_Intro.xml:50
-#, fuzzy, no-c-format
-msgid ""
-"Next, you should configure the interaction between Apache server and mod_jk "
-"by creating the APACHE_HOME/conf/mod_jk.conf file as follows. The LoadModule "
-"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. The JkMount directive tells Apache which URLs it should "
-"forward to the mod_jk module (and, in turn, to the JBoss AS instances). In "
-"the above file, all requests with URL path /application/* 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., /*) to mod_jk."
-msgstr ""
-"Die <literal>JkMount</literal>-\"Directive\" (Übersetzungsanweisung) "
-"informiert Apache darüber, welche URLs an das mod_jk-Modul weitergeleitet "
-"werden sollen (und an die Servlet Container). In der Datei oben werden alle "
-"Anfragen mit dem URL-Pfad <literal>/application/*</literal> an den mod_jk-"
-"Lastverteiler weitergeleitet. Auf diese Weise können Sie Apache direkt auf "
-"serverstatische Inhalte (oder PHP-Contents) konfigurieren und den "
-"Lastverteiler ausschließlich für Java-Anwendungen verwenden. Falls Sie "
-"mod_jk nur als Lastverteiler benutzen, können Sie auch alle URLs (d.h. "
-"<literal>/*</literal>) an mod_jk weiterleiten."
-
-#. Tag: title
-#: Clustering_Intro.xml:53
-#, fuzzy, no-c-format
-msgid "The mod_jk.conf file"
-msgstr "Die context.xml Datei"
-
-#. Tag: programlisting
-#: Clustering_Intro.xml:54
-#, fuzzy, 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"
-"# JkRequestLogFormat\n"
-"JkRequestLogFormat \"%w %V %T\"\n"
-" \n"
-"# Mount your applications\n"
-"JkMount /application/* loadbalancer\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 ""
-"# 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>"
-
-#. Tag: para
-#: Clustering_Intro.xml:55
-#, fuzzy, no-c-format
-msgid ""
-"Then, you need to configure mod_jk itself to load balance the JBoss AS "
-"cluster. The workers file conf/workers.properties specifies the locations of "
-"JBoss AS server nodes and how calls should be load-balanced across them. For "
-"a two nodes setup, the file could look like the following."
-msgstr ""
-"Als nächstes muss das mod_jk \"Workers-File\" <literal>conf/workers."
-"properties</literal> konfiguriert werden. Diese Datei bestimmt, wo die "
-"verschiedenen Servlet-Container sich befinden und wie die Lastverteilung von "
-"Aufrufen über diese erfolgt. Die Konfigurationsdatei enthält einen Abschnitt "
-"für jeden Ziel-Servlet-Container sowie einen globalen (modulübergreifenden) "
-"Abschnitt. Für eine Konfiguration mit zwei Nodes könnte die Datei wie folgt "
-"aussehen:"
-
-#. Tag: title
-#: Clustering_Intro.xml:58
-#, no-c-format
-msgid "The workers.properties file"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Intro.xml:59
-#, 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 ""
-"# 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"
-
-#. Tag: para
-#: Clustering_Intro.xml:60
-#, no-c-format
-msgid ""
-"The above file configures mod_jk to perform weighted round-robin load "
-"balancing between two JBoss AS instances, node1 and node2, listening on port "
-"8009. In the works.properties file, each node is defined using the worker."
-"XXX naming convention where XXX represents an arbitrary name you choose for "
-"one of the target JBoss AS node. For each worker, you must give the host "
-"name (or IP address) and port number of the AJP13 connector (the port 8009 "
-"is default). The lbfactor 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, the more HTTP requests it "
-"will receive. This setting can be used to differentiate servers with "
-"different processing power. The cachesize attribute defines the size of the "
-"thread pools associated to the JBoss AS node (i.e. the number of concurrent "
-"requests it will forward to the node). Make sure this number does not "
-"outnumber the number of threads configured on the AJP13 connector of the "
-"node. The last part of the conf/workers.properties file defines the "
-"loadbalancer worker. The worker.loadbalancer.balanced_workers line must list "
-"all workers previously defined in the same file, and then load-balancing "
-"will happen over these workers."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:64
-#, no-c-format
-msgid "Sticky sessions"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:65
-#, no-c-format
-msgid ""
-"In mod_jk, you almost always configure the load balancer to use \"sticky "
-"sessions\". With sticky sessions, mod_jk forwards requests in the same web "
-"session to the same JBoss AS node. The sticky session ensures that the user "
-"is always served by the JBoss AS instance that has the correct session "
-"state. Sticky session is required for our simple cluster setup."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:72
-#, fuzzy, no-c-format
-msgid "Configure JBoss AS nodes"
-msgstr "Die Konfiguration von JBoss"
-
-#. Tag: para
-#: Clustering_Intro.xml:73
-#, no-c-format
-msgid ""
-"The JBoss AS nodes in the cluster are almost identical to each other. They "
-"must run the same version of JBoss AS, the same applications, and have the "
-"same configuration except for few clustering related configuration options. "
-"In this section, we cover two JBoss AS configuration options required for "
-"the web cluster. One of them is universal for all nodes and the other is "
-"unique for each node."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:77
-#, no-c-format
-msgid "The clustering profile for JBoss AS"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:78
-#, no-c-format
-msgid ""
-"For this simple clustering architecture, you do not even need the "
-"\"clustering\" profile of JBoss AS -- you can just use the default JBoss AS "
-"profile since there is no communication (i.e., clustering) between JBoss AS "
-"nodes."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:82
-#, no-c-format
-msgid ""
-"First, we must configure all JBoss AS nodes to add an \"identifier\" of "
-"itself to all HTTP session IDs it serves. This way, the load balancer would "
-"know which JBoss AS node to forward each request just by checking at the "
-"session ID of the request. To do that, edit the JBOSS_HOME/server/all/deploy/"
-"jboss-web.deploy/META-INF/jboss-service.xml file (replace all with your own "
-"server configuration name). Locate the <attribute> element with a name "
-"of UseJK, and set its value to true as follows."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:85
-#, no-c-format
-msgid ""
-"Configure jboss-service.xml to support JBoss AS node identity in HTTP "
-"session IDs"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Intro.xml:86
-#, no-c-format
-msgid "<attribute name=\"UseJK\">true</attribute>"
-msgstr "<attribute name=\"UseJK\">true</attribute>"
-
-#. Tag: para
-#: Clustering_Intro.xml:87
-#, fuzzy, no-c-format
-msgid ""
-"Second, you need to actually give an identity to each JBoss AS node. On each "
-"clustered JBoss node, you need to name the node according to the name "
-"specified in workers.properties. For instance, on JBoss instance node1, edit "
-"the JBOSS_HOME/server/all/deploy/jboss-web.deployer/server.xml file (replace "
-"all with your own server configuration name if necessary). Locate the <"
-"Engine> element and add an attribute jvmRoute as follows."
-msgstr ""
-"An jedem geclusterten JBoss-Node muss der Node entsprechend dem in "
-"<literal>workers.properties</literal> spezifizierten Namen benannt werden. "
-"Ein Beispiel: An JBoss-Instanz node1 ändern Sie die <literal>JBOSS_HOME/"
-"server/all/deploy/jbossweb-tomcat50.sar/server.xml</literal>-Datei (falls "
-"nötig ersetzen Sie <literal>/all</literal> mit Ihrem eigenen Servernamen). "
-"Lokalisieren Sie das <literal><Engine></literal>-Element, und fügen "
-"Sie ein <literal>jvmRoute</literal>-Attribut hinzu:"
-
-#. Tag: title
-#: Clustering_Intro.xml:90
-#, no-c-format
-msgid "Add node information to the server.xml file"
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Intro.xml:91
-#, fuzzy, no-c-format
-msgid ""
-"<Engine name=\"jboss.web\" \n"
-" defaultHost=\"localhost\" jvmRoute=\"node1\">\n"
-"... ...\n"
-"</Engine>"
-msgstr ""
-"<Engine name=\"jboss.web\" defaultHost=\"localhost\" jvmRoute=\"node1"
-"\">\n"
-"... ...\n"
-"</Engine>"
-
-#. Tag: para
-#: Clustering_Intro.xml:92
-#, no-c-format
-msgid ""
-"Each JBoss AS instance appends its own jvmRoute value to its HTTP session "
-"IDs so that mod_jk can route incoming requests. That's all you need on "
-"the JBoss AS node."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:98
-#, no-c-format
-msgid "Shared Database"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:99
-#, no-c-format
-msgid ""
-"By default, JBoss AS uses an embedded HSQL database for persistence data "
-"storage. For a web cluster to work properly, you must use a shared database "
-"for all server nodes. We recommend you setup a separate MySQL database "
-"server and then configure it as the DataSource for applications deployed on "
-"all nodes. Please see <xref linkend=\"alternative_DBs\"/> for more "
-"information on how to setup external databases as DataSources."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:107
-#, no-c-format
-msgid "Optional improvements to the simple cluster"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:108
-#, no-c-format
-msgid ""
-"The simple web cluster we discussed above is simply a load balanced "
-"architecture for servers that only share information at the database level. "
-"This architecture is highly scalable but it does not provide crucial "
-"clustering features such as failover and distributed caching. With some "
-"simple optional steps, you can easily add those features to your cluster."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:111
-#, no-c-format
-msgid ""
-"Please note that you need to install a clustering enabled JBoss AS profile "
-"(i.e., the all or ejb3-cluster profiles) on all your server nodes for the "
-"optional setups."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:115
-#, no-c-format
-msgid "Failover support"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:116
-#, no-c-format
-msgid ""
-"The simple web cluster does not support failover if one of the server nodes "
-"crashes. Since each JBoss AS node stores its own HTTP session state data -- "
-"the users on the crashed server would lose their sessions when the load "
-"balancer forwards their requests to another node. The solution is for each "
-"node in the cluster to replicate its HTTP session data to other nodes in the "
-"cluster, so that when the node crashes, there is another node node to pick "
-"up all users it left off without any session loss."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:119
-#, no-c-format
-msgid ""
-"When you start multiple clustering enabled JBoss AS instances on the same "
-"network, they automatically form a cluster. Therefore, all you need to do is "
-"to enable HTTP session replication in your web application. That is by "
-"adding a <distributable/> tag in your web.xml file."
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Intro.xml:122
-#, no-c-format
-msgid ""
-"<web-app ...>\n"
-" <distributable/>\n"
-" <!-- ... -->\n"
-"</web-app>"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:123
-#, no-c-format
-msgid ""
-"However, failover does not come free. Since extra object serialization (CPU "
-"intensive) and communication between server nodes (network intensive) are "
-"required, the cluster can no longer scale linearly with the number of nodes. "
-"With the default setup, the HTTP sessions on each node are replicated to all "
-"other nodes in the cluster. So the clustering workload increases "
-"geometrically with the number of server nodes. The cluster would not scale "
-"beyond 8 to 10 servers with the default setup. For a truly scalable failover "
-"solution, we need to setup buddy replication in the cluster so that each "
-"node only replicates its HTTP session data to another \"buddy\" failover "
-"node."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:129
-#, no-c-format
-msgid "Database cache"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:130
-#, no-c-format
-msgid ""
-"Database cache is very useful for improving performance of ORM solutions "
-"like Hibernate and EJB 3.0. It stores frequently accessed data objects in "
-"the application server's memory and hence reduces the round trips to the "
-"database server. However, the challenge is to keep the cache on all server "
-"nodes in sync. For instance, data object O might be cached on both server "
-"nodes A and B. Now, node A updates object O and flushes the change back to "
-"the database. If A and B are not correlated, there is no way for B to know "
-"that object O already has an updated value in the database -- so users on "
-"server B would continue to access the expired value of O and get errors."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:133
-#, no-c-format
-msgid ""
-"The solution here is to use a distributed database cache. The cache is "
-"\"shared\" by all server nodes. So, if one node adds / updates / removes, "
-"any object into / from the cache, all other nodes get the updated cache "
-"instantly as well. Here we give an example configuration for EJB 3.0 entity "
-"bean, which is supported by Hibernate 3.2+."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:136
-#, no-c-format
-msgid ""
-"The distributed database cache is supported out of the box in the ejb3-"
-"cluster profile of JBoss AS. As the case with HTTP session replication, all "
-"you need is to enable this feature in your application. First, you need to "
-"specify JBoss TreeCache as your database cache provider in your persistence."
-"xml file."
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Intro.xml:139
-#, fuzzy, no-c-format
-msgid ""
-"<!-- Clustered cache with TreeCache -->\n"
-"<property name=\"cache.provider_class\">\n"
-" org.jboss.ejb3.entity.TreeCacheProviderHook\n"
-"</property>\n"
-"\n"
-"<property name=\"treecache.mbean.object_name\">\n"
-" jboss.cache:service=EJB3EntityTreeCache\n"
-"</property>"
-msgstr ""
-"<!-- Clustered cache with TreeCache -->\n"
-"<property name=\"cache.provider_class\">\n"
-" org.jboss.ejb3.entity.TreeCacheProviderHook\n"
-"</property>"
-
-#. Tag: para
-#: Clustering_Intro.xml:140
-#, no-c-format
-msgid ""
-"The on each entity bean class you want to cache, add the @Cache annotation."
-msgstr ""
-
-#. Tag: programlisting
-#: Clustering_Intro.xml:143
-#, fuzzy, no-c-format
-msgid ""
-"@Entity \n"
-"@Cache(usage=CacheConcurrencyStrategy.TRANSACTIONAL) \n"
-"public class Product implements Serializable { \n"
-" // ... ... \n"
-"}"
-msgstr ""
-"@Entity \n"
-"@Cache(usage=CacheConcurrencyStrategy.TRANSACTIONAL) \n"
-"public class Customer implements Serializable { \n"
-" // ... ... \n"
-"}"
-
-#. Tag: para
-#: Clustering_Intro.xml:144
-#, no-c-format
-msgid ""
-"That's it. Now the Product data objects are cached in the shared cache "
-"across all JBoss AS server nodes in the cluster."
-msgstr ""
-
-#. Tag: title
-#: Clustering_Intro.xml:152
-#, no-c-format
-msgid "Basic optimization"
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:153
-#, no-c-format
-msgid ""
-"In this section, we will give a few optimization tips to improve the "
-"performance of the cluster. Details of those optimization techniques will be "
-"covered later in this book."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:156
-#, no-c-format
-msgid ""
-"The first tip is to balance the connection pools in JBoss AS server nodes "
-"and the load balancer. The goal is to make the Apache connection poll 80% "
-"the size of the combined connection pools of the JBoss AS nodes. In "
-"addition, to optimize thread performance in the load balancer, we highly "
-"recommend you install the \"worker\" MPM for Apache on Unix / Linux servers "
-"and the \"winnt\" MPM for Windows servers."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:159
-#, no-c-format
-msgid ""
-"Second, we need to understand that HTTP session replication is very "
-"expensive and should be minimized when possible. Choosing the right "
-"replication trigger and granularity is an important step. For instance, "
-"setting the replication trigger to SET might require you to write more code "
-"to push changed data back into the session. But it can drastically reduce "
-"the replication work load for a mostly read-only application. Setting the "
-"granularity level to ATTRIBUTE would be much more efficient than SESSION if "
-"the session size is large. However, setting the granularity level to FIELD "
-"may not have a great benefit due to the AOP overhead associated with dirty "
-"checking on fields."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:162
-#, no-c-format
-msgid ""
-"In addition, as we discussed before, the default \"replicate-to-all-nodes\" "
-"approach for HTTP session replication does scale for large clusters."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:165
-#, no-c-format
-msgid ""
-"At the network level, it is important to make sure that you use an "
-"asynchronous communication mechanism to replicate HTTP sessions. Since the "
-"replicated HTTP sessions are only used when a rare failover happens, it is "
-"not essential for the failover node to always have the exact same state as "
-"the primary node at real time."
-msgstr ""
-
-#. Tag: para
-#: Clustering_Intro.xml:168
-#, no-c-format
-msgid ""
-"It also worth noting that the choice of underlying network protocols for the "
-"inter-node communication also affects performance. In general, on a small "
-"network (i.e., 4 or less nodes) the node-to-node TCP/IP protocol would out "
-"perform the broadcast-based UDP protocol. It is the opposite when the "
-"cluster size grows larger."
-msgstr ""
More information about the jboss-cvs-commits
mailing list