[jboss-cvs] JBossAS SVN: r72413 - projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Apr 18 00:54:37 EDT 2008
Author: xhuang at jboss.com
Date: 2008-04-18 00:54:37 -0400 (Fri, 18 Apr 2008)
New Revision: 72413
Modified:
projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po
Log:
update
Modified: projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po 2008-04-18 03:51:02 UTC (rev 72412)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po 2008-04-18 04:54:37 UTC (rev 72413)
@@ -9,7 +9,7 @@
"Project-Id-Version: J2EE_EJBs_On_JBOSS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2007-12-03 00:52+0000\n"
-"PO-Revision-Date: 2008-04-17 11:08+1000\n"
+"PO-Revision-Date: 2008-04-18 14:54+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -5479,7 +5479,6 @@
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1257
#, no-c-format
-#, fuzzy
msgid ""
"<emphasis role=\"bold\">EntitySynchronizationInterceptor</emphasis>: The "
"role of this interceptor is to synchronize the state of the cache with the "
@@ -5492,13 +5491,16 @@
"emphasis>, <emphasis>B</emphasis> and <emphasis>C</emphasis> of the "
"specification are taken care of here as well as the JBoss specific commit-"
"option <emphasis>D</emphasis>."
-msgstr "<emphasis role=\"bold\">EntitySynchronizationInterceptor</emphasis>："
+msgstr ""
+"<emphasis role=\"bold\">EntitySynchronizationInterceptor</emphasis>：这个拦截器的作用是将缓存状态和底层存储同步。它用 EJB 规格的 <literal>ejbLoad</literal> 和 "
+"<literal>ejbStore</literal> 模式来实现这一点。事务开始时它由事务限界（transaction demarcation）触发。它通过 JTA 接口向底层事务监控器注册一个回调方法。如果没有事务，这个策略将存储调用返回的状态。这里考虑了 EJB 规格的同步策略 <emphasis>A</"
+"emphasis>、<emphasis>B</emphasis> 和 <emphasis>C</emphasis>、以及 JBoss 专有的提交选项 <emphasis>D</emphasis>。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1265
#, no-c-format
msgid "Deadlock"
-msgstr ""
+msgstr "死锁"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1266
@@ -5518,12 +5520,16 @@
"are deadlocked waiting for access to the resource already locked by the "
"other thread."
msgstr ""
+"找到并解决死锁问题是本节的主题。我们将讨论什么是 deadlocking MBean、且如何在应用程序里检测并解决死锁问题。当两个或更多线程都拥有对共享资源的锁时，死锁就有可能发生。<xref linkend=\"Deadlock-"
+"Deadlock_definition_example\"/> 演示了一个简单的死锁情景。如图，<literal>Thread 1</literal> 具有对 <literal>Bean A</"
+"literal> 的锁，<literal>Thread 2</literal> 具有对 <literal>Bean B</"
+"literal> 的锁。之后，<literal>Thread 1</literal> 试图锁定 <literal>Bean B</literal> 时会发生堵塞，这是因为 <literal>Thread 2</literal> 已经锁定了它。类似地，当 <literal>Thread 2</literal> 试图锁定 Bean A 时也会堵塞，因为 <literal>Thread 1</literal> 已经锁定了它。此时，两个线程都在等待被已经被对方锁定的资源，这样就发生了死锁。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1270
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Deadlock definition example"
-msgstr "集合例子（Collection example）"
+msgstr "关于死锁定义的例子"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1277
@@ -5536,13 +5542,13 @@
"not careful about ordering the access to them. Various techniques and "
"advanced configurations can be used to avoid deadlocking problems. They are "
"discussed later in this section."
-msgstr ""
+msgstr "JBoss 的缺省锁策略是当调用发生在事务上下文里时，锁定 Entity Bean 直至事务完成。因此，如果有长期运行的并访问多个 Entity Bean 的事务、或者如果没有小心排列访问顺序，我们就很容易遇到死锁。我们将在本节后面进行讨论如何使用不同的技术和高级配置来避免死锁。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1281
#, no-c-format
msgid "Deadlock Detection"
-msgstr ""
+msgstr "死锁检测"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1282
@@ -5556,48 +5562,50 @@
"graph may look like is given in <xref linkend=\"Deadlock_Detection-"
"An_example_blocked_transaction_table\"/>."
msgstr ""
+"幸运的是，JBoss 能够进行死锁检测。JBoss 具有一个全局的包含处于等待状态的事务以及阻塞在哪个事务的内部图表。每当一个线程不能够获得某个 Entity Bean 锁时，它将知道目前是哪个事务持有这个 Bean 的锁并将自己加入到阻塞事务图表里。<xref linkend=\"Deadlock_Detection-"
+"An_example_blocked_transaction_table\"/> 是这个图表的一个例子。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1286
#, no-c-format
msgid "An example blocked transaction table"
-msgstr ""
+msgstr "阻塞的事务表的例子"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1290
#, no-c-format
msgid "Blocking TX"
-msgstr ""
+msgstr "Blocking TX"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1293
#, no-c-format
msgid "Tx that holds needed lock"
-msgstr ""
+msgstr "持有所需锁的事务"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1300 J2EE_EJBs_On_JBOSS.xml:1319
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<entry>Tx1</entry>"
-msgstr "<entry>DB2</entry>"
+msgstr "<entry>Tx1</entry>"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1303
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<entry>Tx2</entry>"
-msgstr "<entry>DB2</entry>"
+msgstr "<entry>Tx2</entry>"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1308
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<entry>Tx3</entry>"
-msgstr "<entry>DB2</entry>"
+msgstr "<entry>Tx3</entry>"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1311 J2EE_EJBs_On_JBOSS.xml:1316
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<entry>Tx4</entry>"
-msgstr "<entry>DB2</entry>"
+msgstr "<entry>Tx4</entry>"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1326
@@ -5610,13 +5618,13 @@
"deadlock and will throw an <literal>ApplicationDeadlockException</literal>. "
"This exception will cause a transaction rollback which will cause all locks "
"that transaction holds to be released."
-msgstr ""
+msgstr "在线程实际阻塞之前，它会试图检测是否存在死锁问题。它通过扫描事务图表来进行检测。它会记录哪些事务处于阻塞状态。如果它在图表里多次发现某个阻塞的节点，它就知道发生了死锁，然后会抛出 <literal>ApplicationDeadlockException</literal>。这个异常件导致事务回滚，因此该事务持有的所有锁都会被释放。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1332
#, no-c-format
msgid "Catching ApplicationDeadlockException"
-msgstr ""
+msgstr "捕获 ApplicationDeadlockException"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1333
@@ -5628,7 +5636,7 @@
"Unfortunately, this exception can be deeply embedded within a "
"<literal>RemoteException</literal>, so you have to search for it in your "
"catch block. For example:"
-msgstr ""
+msgstr "既然 JBoss 可以检测应用程序的死锁，如果某个调用失败是由于 <literal>ApplicationDeadlockException</literal>，你就应该编写自己的代码来重试这个事务。可惜的是，这个异常深嵌在 <literal>RemoteException</literal>，所以你不得不在 catch 代码块里搜索它。例如："
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1336
@@ -5678,7 +5686,7 @@
#: J2EE_EJBs_On_JBOSS.xml:1340
#, no-c-format
msgid "Viewing Lock Information"
-msgstr ""
+msgstr "查看锁信息"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1341
@@ -5688,7 +5696,7 @@
"basic locking statistics as well as printing out the state of the "
"transaction locking table. To enable this monitor uncomment its "
"configuration in the <literal>conf/jboss-service.xml</literal>:"
-msgstr ""
+msgstr "<literal>EntityLockMonitor</literal> MBean 服务允许你查看基本的锁统计信息且输出事务锁表的状态。要启用这个功能，你可以在 <literal>conf/jboss-service.xml</literal> 里取消下列配置的注释："
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1344
@@ -5708,25 +5716,23 @@
msgid ""
"The <literal>EntityLockMonitor</literal> has no configurable attributes. It "
"does have the following read-only attributes:"
-msgstr ""
+msgstr "<literal>EntityLockMonitor</literal> 没有可配置属性。它有下列的只读属性："
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1350
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">MedianWaitTime</emphasis>: The median value of all "
"times threads had to wait to acquire a lock."
-msgstr "<emphasis role=\"bold\">name</emphasis>：参数的变量名，这是必须的。"
+msgstr "<emphasis role=\"bold\">MedianWaitTime</emphasis>：线程等待获取锁的时间的平均值。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1355
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">AverageContenders</emphasis>: The ratio of the total "
"number of contentions to the sum of all threads that had to wait for a lock."
-msgstr ""
-"<emphasis role=\"bold\">num_initial_members</emphasis> 指定等待的最大的应答数"
-"量。"
+msgstr "<emphasis role=\"bold\">AverageContenders</emphasis>：所有争用线程和等待锁的进程总数的比例。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1360
@@ -5736,31 +5742,29 @@
"threads that had to wait to acquire the transaction lock. This happens when "
"a thread attempts to acquire a lock that is associated with another "
"transaction"
-msgstr ""
+msgstr "<emphasis role=\"bold\">TotalContentions</emphasis>：等待获取事务锁的线程的总数。这发生在线程试图获取和其他线程关联的锁的时候。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1365
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">MaxContenders</emphasis>: The maximum number of "
"threads that were waiting to acquire the transaction lock."
-msgstr ""
-"<emphasis role=\"bold\">NumAcceptThreads</emphasis>：用来接受客户联接的线程的"
-"数量。它的缺省值是 1。"
+msgstr "<emphasis role=\"bold\">MaxContenders</emphasis>：等待获取事务锁的线程的最大数目。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1370
-#, fuzzy, no-c-format
+#, no-c-format
msgid "It also has the following operations:"
-msgstr "在以下的表定义中反应了这个映射关系："
+msgstr "它也有下列的操作："
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1375
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">clearMonitor</emphasis>: This operation resets the "
"lock monitor state by zeroing all counters."
-msgstr "<emphasis role=\"bold\">description</emphasis>：构造函数的描述"
+msgstr "<emphasis role=\"bold\">clearMonitor</emphasis>：这个操作通过将所有计数器清零来重置锁监控状态。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1380
@@ -5771,13 +5775,13 @@
"the bean, the total time spent waiting for the lock, the count of times the "
"lock was waited on and the number of transactions that timed out waiting for "
"the lock."
-msgstr ""
+msgstr "<emphasis role=\"bold\">printLockMonitor</emphasis>：这个操作输出所有 EJB 锁的表，它列出 bean 的 <literal>ejbName</literal>、等待锁总共所花费的时间、锁被等待的次数以及等待锁超时的事务的数目。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1390
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Advanced Configurations and Optimizations"
-msgstr "其他配置选项"
+msgstr "高级配置和优化"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1391
@@ -5788,13 +5792,13 @@
"present a huge performance/throughput problem for your application. This "
"section walks through various techniques and configurations that you can use "
"to optimize performance and reduce the possibility of deadlock."
-msgstr ""
+msgstr "Entity Bean 的缺省的锁行为可能导致死锁。既然对 Entity Bean 的访问在事务里锁住了这个 Bean，它也可以避免应用程序的性能/效率问题。本节将介绍不同的技术和配置方法，你可以用它们来优化性能和减低死锁的可能性。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1395
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Short-lived Transactions"
-msgstr "策略：事务缓存（transactional）"
+msgstr "短期的事务"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1396
@@ -5803,13 +5807,13 @@
"Make your transactions as short-lived and fine-grained as possible. The "
"shorter the transaction you have, the less likelihood you will have "
"concurrent access collisions and your application throughput will go up."
-msgstr ""
+msgstr "使你的事务尽可能的短和细颗粒度。事务越短，越不可能有并发访问的冲突，应用程序的效率因此将越高。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1402
#, no-c-format
msgid "Ordered Access"
-msgstr ""
+msgstr "按顺序访问"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1403
@@ -5820,13 +5824,13 @@
"always accessed in the same exact order. In most cases, user applications "
"are just too complicated to use this approach and more advanced "
"configurations are needed."
-msgstr ""
+msgstr "按顺序访问 Entity Bean 可以减少死锁的可能性。这意味着要确保总是按完全相同的顺序访问系统里的 Entity Bean。大多数情况下，用户应用程序通常过于复杂而不能使用这个方法，你需要更高级的配置。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1409
#, no-c-format
msgid "Read-Only Beans"
-msgstr ""
+msgstr "只读的 Bean "
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1410
@@ -5837,23 +5841,21 @@
"transactionally locked. Using commit-option <emphasis>D</emphasis> with this "
"option is sometimes very useful when your read-only bean's data is "
"sometimes updated by an external source."
-msgstr ""
+msgstr "Entity bean 可以标记为只读。当 bean 被标记为只读时，它从不参与事务。这意味着它永远不被事务性地锁定。当有时候外部程序更新你的只读 Bean 的数据事，和提交选项 <emphasis>D</emphasis> 一起使用有时候会非常有用。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1413
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"To mark a bean as read-only, use the <literal>read-only</literal> flag in "
"the <literal>jboss.xml</literal> deployment descriptor."
-msgstr ""
-"你可以用 <literal>jboss-web.xml</literal> 文件里的 <literal>replication-"
-"config</literal> 元素进一步配置会话复制。下面是一个例子："
+msgstr "要把 Bean 标记为只读，你可以使用 <literal>jboss.xml</literal> 部署描述符里的 <literal>read-only</literal> 标记。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1416
#, no-c-format
msgid "Marking an entity bean read-only using jboss.xml"
-msgstr ""
+msgstr "用 jboss.xml 设置只读的 entity bean"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1417
@@ -5889,7 +5891,7 @@
#: J2EE_EJBs_On_JBOSS.xml:1422
#, no-c-format
msgid "Explicitly Defining Read-Only Methods"
-msgstr ""
+msgstr "显性地定义只读方法"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1423
@@ -5905,12 +5907,14 @@
"declaring all getter methods and the <literal>anotherReadOnlyMethod</"
"literal> as read-only."
msgstr ""
+"在理解了 Entity Bean 的缺省的锁行为后，你可能想知道：如果没有修改数据，为什么要锁定 Bean 呢？JBoss 允许你将 Entity Bean 里的某些方法定义为只读，这样当在事务里只调用这些方法时，Bean 并不会被锁住。你可以在 <literal>jboss.xml</literal> 部署描述符里定义这些只读方法。你可以使用通配符。下面是一个声明所有 getter 方法和只读的 <literal>anotherReadOnlyMethod</"
+"literal> 方法的例子。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1426
#, no-c-format
msgid "Defining entity bean methods as read only"
-msgstr ""
+msgstr "定义只读的 entity bean 方法"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1427
@@ -5968,9 +5972,9 @@
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1432
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Instance Per Transaction Policy"
-msgstr "Hibernate 事务属性"
+msgstr "Instance Per Transaction 策略"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1433
@@ -5984,7 +5988,7 @@
"transaction and dropping this instance at the end of the transaction. "
"Because each transaction has its own copy of the bean, there is no need for "
"transaction based locking."
-msgstr ""
+msgstr "Instance Per Transaction 策略是一个高级的配置方法，它可以完全避免 JBoss 的缺省锁策略所引起的死锁和效率问题。缺省的 Entity Bean 锁策略只允许每个 Bean 存在一个活动实例。Instance Per Transaction 策略打破了这个限制，它允许每个事务存在 Bean 的一个新的实例并在事务结束时销毁。因为每个事务都有这个 Bean 的一个拷贝，所以基于事务的锁就不需要了。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1436
@@ -6002,7 +6006,7 @@
"way to go. The JBoss developers are currently exploring ways to allow commit-"
"option <emphasis>A</emphasis> as well (which would allow the use of caching "
"for this option)."
-msgstr ""
+msgstr "这个选项听起来很好但也有一些缺点。首先，这个选项的事务隔离行为和<literal>READ_COMMITTED</literal> 相等。这可能创建不必要的可重复的读。换句话说，事务可能拥有过时的 Bean 的拷贝。其次，这个配置选项目前需要提交选项 <emphasis>B</emphasis> 或 <emphasis>C</emphasis>，既然 ejbLoad 必须在事务开始时执行，这可能导致性能问题。但是，如果你的应用程序本来就需要使用提交选项 <emphasis>B</emphasis> 或 <emphasis>C</emphasis>，那你就可以采用这种方法。JBoss 开发人员目前正在探索新的方法来使用提交选项 <emphasis>A</emphasis>（允许缓存的使用）。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1439
@@ -6015,6 +6019,9 @@
"name of the container configuration to use with your bean in the jboss.xml "
"deployment descriptor as show below."
msgstr ""
+"JBoss 具有在 standardjboss.xml 里定义的、名为 <literal>Instance Per Transaction "
+"CMP 2.x EntityBean</literal> 和 <literal>Instance Per Transaction BMP "
+"EntityBean</literal> 的实现了这个锁策略的容器配置。如下所示，要使用这种配置，你得在 jboss.xml 部署描述符里引用容器配置的名称。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1442
@@ -6162,7 +6169,7 @@
#: J2EE_EJBs_On_JBOSS.xml:1486
#, no-c-format
msgid "IllegalStateException"
-msgstr ""
+msgstr "IllegalStateException"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1487
@@ -6174,12 +6181,15 @@
"key class, or that your primary key class is not implemented correctly for "
"serialization."
msgstr ""
+"带有 \"removing bean lock and it has tx "
+"set!\" 信息的 IllegalStateException 通常表示你没有正确地实现用于自定义/复杂的主键类的 <literal>equals</literal> "
+"和/或 <literal>hashCode</literal> 方法，或者你没有正确地实现主键类的序列化。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1493
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Hangs and Transaction Timeouts"
-msgstr "事务超时"
+msgstr "挂起和事务超时"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1494
@@ -6194,7 +6204,7 @@
"transaction that could hang indefinitely. One common mistake is making "
"connections across the internet or running a web-crawler within a "
"transaction."
-msgstr ""
+msgstr "JBoss 一直以来的一个程序错误就是在事务超时时，这个事务仅仅标记为回滚而实际没有回滚。这被委托给调用线程来实现。但如果调用线程无限期挂起时，此时 Entity Bean 锁等永远都不会被释放，这就会导致严重的问题。解决这个问题的办法很牵强。你实际上只需要避免在事务里做有可能挂起的事情就可以了。在这里，常见的错误就是在事务里连接互联网或运行 web-crawler。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1504
More information about the jboss-cvs-commits
mailing list