[jboss-cvs] JBossAS SVN: r84107 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Feb 12 00:33:29 EST 2009
Author: xhuang at jboss.com
Date: 2009-02-12 00:33:29 -0500 (Thu, 12 Feb 2009)
New Revision: 84107
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Deploy.po
Log:
update
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po 2009-02-12 04:08:47 UTC (rev 84106)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po 2009-02-12 05:33:29 UTC (rev 84107)
@@ -9,8 +9,8 @@
"Project-Id-Version: Clustering_Guide_JBoss_Cache_JGroups\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-02-11 19:12+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2009-02-12 11:55+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -2594,13 +2594,12 @@
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:956
#, no-c-format
-#, fuzzy
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 "JGroups 的组名定义了它将通信的频道。"
+msgstr "JGroups 的组名、多播地址和多播端口定义了它将通信的频道，所以隔离 JGroups 频道确保了不同的频道根据不同的组名、多播地址和多播端口使用不同的值。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:959
@@ -2609,7 +2608,7 @@
"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 ""
+msgstr "要为相同 AS 实例集合上的不同服务隔离 JGroups 频道，你必须修改组名和多播端口。换句话说，每个频道必须具有一系列自己的值。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:962
@@ -2620,7 +2619,7 @@
"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 ""
+msgstr "例如，假设我们有一个具有 3 台机器的群集，每个节点都有部署了一个 HAPartition 以及一个用于 Web 会话群集的 JBoss Cache。HAPartition 频道不应该和 JBoss Cache 频道通信。它们应该使用不同的组名和多播端口。它们可以使用相同的多播地址，虽然它们并不需要这样做。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:965
@@ -2629,7 +2628,7 @@
"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 ""
+msgstr "要隔离网络里其他实例上的相同服务的 JGroups 频道，这三个值你都必须修改。每个频道必须具有自己的组名、多播地址和端口。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:968
@@ -2640,13 +2639,13 @@
"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 ""
+msgstr "例如，假设我们有一个具有 3 个节点的产品群集，每个都部署了一个 HAPartition。在相同的网络上，也有一个具有 3 个节点的 QA 群集，它们也部署了 HAPartition。产品群集机器的 HAPartition 的组名、多播地址和多播端口必须和 QA 群集机器的不同。"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:974
#, no-c-format
msgid "Changing the Group Name"
-msgstr ""
+msgstr "修改组名"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:975
@@ -2658,7 +2657,7 @@
"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 ""
+msgstr "JGroups 频道的组名是通过启动频道的服务来配置的。可惜的是，不同的服务使用不同的属性名来进行配置。对于 HAPartition 和相关的在 deploy/cluster-service.xml 里配置的服务来说，其组名是通过 PartitionName 属性配置的。但对于 JBoss Cache 服务而言，配置属性是 ClusterName。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:978
@@ -2672,6 +2671,9 @@
"configuration of the group name in all the standard clustering configuration "
"files. For example,"
msgstr ""
+"从 JBoss AS 4.0.4 开始，对于 HAPartition 和其他所有标准的 JBoss "
+"Cache 服务，我们都使你能够轻易地通过在启动 JBoss 时设置 -g（也就是 -partion）选项创建唯一的组名。<screen>./"
+"run.sh -g QAPartition -b 192.168.1.100 -c all</screen> 这个选项设置了 jboss.partition.name system 属性，这个属性被用作所有标准群集配置文件里的组名配置的一个组件。例如："
#. Tag: screen
#: Clustering_Guide_JBoss_Cache_JGroups.xml:982
@@ -2680,12 +2682,14 @@
"<![CDATA[<attribute name=\"ClusterName\">Tomcat-${jboss.partition.name:"
"Cluster}</attribute>]]>"
msgstr ""
+"<![CDATA[<attribute name=\"ClusterName\">Tomcat-${jboss.partition.name:"
+"Cluster}</attribute>]]>"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:988
#, no-c-format
msgid "Changing the multicast address and port"
-msgstr ""
+msgstr "修改多播地址和端口"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:989
@@ -2698,6 +2702,9 @@
"udpGroup system property, which you can see referenced in all of the "
"standard protocol stack configs in JBoss AS:"
msgstr ""
+"我们可以用 -u（也就是 --udp）开关来控制所有标准 AS 服务打开的 JGroups 频道使用多播地址。<screen><![CDATA[/run.sh -u 230.1.2.3 -g QAPartition -b "
+"192.168.1.100 -c all]]></screen> 这个开关设置了 jboss.partition."
+"udpGroup 系统属性，你会看到在 JBoss AS 里所有标准协议栈配置都引用了它："
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:995
@@ -2707,6 +2714,9 @@
"<UDP mcast_addr=\"${jboss.partition.udpGroup:228.1.2.3}\"\n"
" ....]]>"
msgstr ""
+"<![CDATA[<Config>\n"
+"<UDP mcast_addr=\"${jboss.partition.udpGroup:228.1.2.3}\"\n"
+" ....]]>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:996
@@ -2718,7 +2728,7 @@
"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 ""
+msgstr "可惜的是，设置多播端口并非如此简单。如上所述，标准 JBoss AS 的 all 配置在缺省情况下有 4 个独立的 JGroups 频道，每个都应该具有独立的端口。没有命令行选项可以设置这些端口，但标准的配置文件可以使用系统属性来进行设置。所以，它们可以通过命令行选项 -D 来配置。例如，"
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:999
@@ -2729,12 +2739,16 @@
"mcast_port=34567 -Djboss.ejb3sfsbpartition.mcast_port=45678 -b 192.168.1.100 "
"-c all"
msgstr ""
+"/run.sh -u 230.1.2.3 -g QAPartition -Djboss.hapartition.mcast_port=12345 -"
+"Djboss.webpartition.mcast_port=23456 -Djboss.ejb3entitypartition."
+"mcast_port=34567 -Djboss.ejb3sfsbpartition.mcast_port=45678 -b 192.168.1.100 "
+"-c all"
#. Tag: emphasis
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1001
#, no-c-format
msgid "Why isn't it sufficient to change the group name?"
-msgstr ""
+msgstr "为什么只修改组名是不够的？"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1002
@@ -2744,13 +2758,13 @@
"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 ""
+msgstr "如果具有不同组名的频道共享相同的多播地址和端口，每个频道里更底层的 JGroups 协议将查看、处理并最终丢弃送往其他组的消息。这将最小限度地影响性能且会导致反常的行为。"
#. Tag: emphasis
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1006
#, no-c-format
msgid "Why do I need to change the multicast port if I change the address?"
-msgstr ""
+msgstr "如果修改了地址，我们为什么还需要修改多播端口？"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1007
@@ -2761,19 +2775,19 @@
"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 ""
+msgstr "修改地址应该已经足够了，但在有些操作系统里这会出现问题，因为发送到特定多播端口的数据包将被递送给该端口的所有 listener，而不管它们所侦听的多播地址。所以我们推荐你既修改地址也修改端口。"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1013
#, no-c-format
msgid "JGroups Troubleshooting"
-msgstr ""
+msgstr "JGroups 的故障解除"
#. Tag: emphasis
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1014
#, no-c-format
msgid "Nodes do not form a cluster"
-msgstr ""
+msgstr "节点没有组成群集"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1016
@@ -2784,6 +2798,8 @@
"McastSenderTest. Go to the <literal>$JBOSS_HOME/server/all/lib</literal> "
"directory and start McastReceiverTest, for example:"
msgstr ""
+"请确保你的主机正确设置 IP 多点传送。你可以使用两个测试程序来进行检测：McastReceiverTest 和 "
+"McastSenderTest。进入 <literal>$JBOSS_HOME/server/all/lib</literal> 目录并启动 McastReceiverTest，如："
#. Tag: screen
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1018
@@ -2792,12 +2808,14 @@
"java -cp jgroups.jar org.jgroups.tests.McastReceiverTest -mcast_addr "
"224.10.10.10 -port 5555"
msgstr ""
+"java -cp jgroups.jar org.jgroups.tests.McastReceiverTest -mcast_addr "
+"224.10.10.10 -port 5555"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1021
#, no-c-format
msgid "Then in another window start <literal>McastSenderTest</literal>:"
-msgstr ""
+msgstr "然后在另外一个窗口启动 <literal>McastSenderTest</literal>："
#. Tag: screen
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1023
@@ -2806,6 +2824,8 @@
"java -cp jgroups.jar org.jgroups.tests.McastSenderTest -mcast_addr "
"224.10.10.10 -port 5555"
msgstr ""
+"java -cp jgroups.jar org.jgroups.tests.McastSenderTest -mcast_addr "
+"224.10.10.10 -port 5555"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1026
@@ -2815,7 +2835,7 @@
"<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 ""
+msgstr "如果你想绑定到特殊的网络接口卡（NIC），你可以使用 <literal>-bind_addr 192.168.0.2</literal>，这里的 192.168.0.2 是你想绑定的网卡的地址。在发送者和接收者里都使用这个参数。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1029
@@ -2830,13 +2850,13 @@
"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 ""
+msgstr "你应该能够在 <literal>McastSenderTest</literal> 窗口里输入并在 <literal>McastReceiverTest</literal> 窗口里看到输出。如果不行，试一下发送者里的 -ttl 32。如果还不行，请联系系统管理员来帮你设立正确的 IP 多点传送，并请他确保多点传送将工作在你所选的接口上（如果有多个接口）。一旦确认了多点传送在群集里的每台机器上都可以正常工作，把发送者（Sender）放到其中一台主机里而把接收者（Receiver）放到两外一台上。"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1036
#, no-c-format
msgid "Causes of missing heartbeats in FD"
-msgstr ""
+msgstr "FD 里丢失 heartbeat 的原因"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1037
@@ -2846,7 +2866,7 @@
"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 ""
+msgstr "有时候因为在一段时间 T（由 timeout 和 max_tries 定义）内没有接收到 heartbeat ack 回应，FD 会怀疑某个成员。这可能有多个原因，例如在群集 A,B,C,D 里，如果发生下列情况，C 可能会被怀疑（请注意 A pings B，B pings C，C pings D 且 D pings A）："
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1043
@@ -2854,19 +2874,19 @@
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 ""
+msgstr "B 或 C 的 CPU 占用率为 100% 的时间已经超过了 T。所以，即使 C 发送了一个 heartbeat ack 给 B，B 可能也不能够进行处理，因为它的 CPU 占用率已经达到了 100%。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1048
#, no-c-format
msgid "B or C are garbage collecting, same as above."
-msgstr ""
+msgstr "B 或 C 正在进行垃圾收集，情况和上面一样。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1053
#, no-c-format
msgid "A combination of the 2 cases above"
-msgstr ""
+msgstr "A 结合了上面的两种情况"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1058
@@ -2875,7 +2895,7 @@
"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 ""
+msgstr "网络丢失了数据包。当网络里繁忙时，这通常会发生，且交换器开始丢掉数据包（通常首先是广播信息，然后是 IP 多点传送数据包，最后是 TCP 数据包）。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:1063
@@ -2885,5 +2905,5 @@
"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 ""
+msgstr "B 或 C 正在处理回调方法。假设 C 通过其频道接收到一个远程方法调用，它使用了 T+1 秒来进行处理。在这段时间内，C 将不能处理其他消息，包括 heartbeat，因此 B 将不会接收到 heartbeat ack 并怀疑 C。"
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Deploy.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Deploy.po 2009-02-12 04:08:47 UTC (rev 84106)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Deploy.po 2009-02-12 05:33:29 UTC (rev 84107)
@@ -1,24 +1,27 @@
+# translation of Deploy.po to
# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
+# Copyright (C) 2007, 2009 Free Software Foundation, Inc.
+#
# Automatically generated, 2007.
-#
+# Xi HUANG <xhuang at redhat.com>, 2009.
msgid ""
msgstr ""
-"Project-Id-Version: JBEAP 420\n"
+"Project-Id-Version: Deploy\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"
+"PO-Revision-Date: 2009-02-12 13:57+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
#. Tag: title
#: Deploy.xml:6
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Deployment"
-msgstr "Farming 部署"
+msgstr "部署"
#. Tag: para
#: Deploy.xml:8
@@ -31,13 +34,13 @@
"scans the deploy directory to pick up new applications or any changes to "
"existing applications. So, you can \"hot deploy\" application on the fly "
"while JBoss AS is still running."
-msgstr ""
+msgstr "在 JBoss AS 里部署应用程序很容易。你只需要把应用程序复制到 jboss-as/server/production/deploy 目录就可以了。你可以用不同的服务器配置来替代 default 配置，如 all、minimal 或 production。我们将在本章介绍这些内容。JBoss AS 不时扫描 deploy 目录来寻找新的应用程序或对有改动的现有程序。所以，你可以在 JBoss AS 仍然运行时在线“热部署”应用程序。"
#. Tag: title
#: Deploy.xml:11
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Deployable Application Types"
-msgstr "Web 应用程序"
+msgstr "可部署的应用程序类型"
#. Tag: para
#: Deploy.xml:13
@@ -46,6 +49,8 @@
"You can deploy several different types of enterprise applications in JBoss "
"AS:"
msgstr ""
+"你可以在 JBoss "
+"AS 里部署几种不同类型的企业级应用程序："
#. Tag: para
#: Deploy.xml:17
@@ -55,7 +60,7 @@
"application in a JAR file. It contains servlet classes, view pages, "
"libraries, and deployment descriptors such as web.xml, faces-config.xml, and "
"jboss-web.xml etc.."
-msgstr ""
+msgstr "WAR 应用程序归档文件（如 myapp.war）把 Java EE web 程序打包到一个 JAR 文件里。它包含 servlet 类、视图页面、库和部署描述符，如 web.xml、faces-config.xml 和 jboss-web.xml 等。"
#. Tag: para
#: Deploy.xml:19
@@ -381,3 +386,4 @@
"\"alternative_DBs\"/> for more information on how to setup alternative "
"databases for the JBoss AS."
msgstr ""
+
More information about the jboss-cvs-commits
mailing list