[jboss-cvs] JBossAS SVN: r91143 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jul 13 02:55:12 EDT 2009
Author: ldelima at redhat.com
Date: 2009-07-13 02:55:12 -0400 (Mon, 13 Jul 2009)
New Revision: 91143
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_EJBs_On_JBOSS.po
Log:
translation ongoing
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_EJBs_On_JBOSS.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_EJBs_On_JBOSS.po 2009-07-13 06:54:39 UTC (rev 91142)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_EJBs_On_JBOSS.po 2009-07-13 06:55:12 UTC (rev 91143)
@@ -8,7 +8,7 @@
"Project-Id-Version: J2EE_EJBs_On_JBOSS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-07-13 16:48+1000\n"
+"PO-Revision-Date: 2009-07-13 16:54+1000\n"
"Last-Translator: \n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -4745,14 +4745,7 @@
"with caching, data integrity is a problem, so some form of application "
"server level locking is needed for entity beans to provide the transaction "
"isolation properties that you are used to with traditional databases."
-msgstr ""
-"Entity beans are a great way to provide an object-oriented interface to "
-"relational data. Beyond that, they can improve performance by taking the "
-"load off of the database through caching and delaying updates until "
-"absolutely needed so that the database efficiency can be maximized. But, "
-"with caching, data integrity is a problem, so some form of application "
-"server level locking is needed for entity beans to provide the transaction "
-"isolation properties that you are used to with traditional databases."
+msgstr "Os beans de entidades são uma maneira perfeita de fornecer uma interface de objeto-orientado para os dados relacionais. Além disto, eles podem melhorar o desempenho retirando a carga do banco de dados através da realizaçºao do cache e demora na atualização até que seja absolutamente necessário"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1183
@@ -4793,6 +4786,10 @@
"This means that at the start of a new transaction <literal>ejbLoad</literal> "
"must be called."
msgstr ""
+"For commit option <emphasis>B</emphasis>, this instance is cached and used "
+"between transactions, but is marked as dirty at the end of a transaction. "
+"This means that at the start of a new transaction <literal>ejbLoad</literal> "
+"must be called."
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1199
@@ -4802,6 +4799,9 @@
"released from the cache, and marked for passivation at the end of a "
"transaction."
msgstr ""
+"For commit option <emphasis>C</emphasis>, this instance is marked as dirty, "
+"released from the cache, and marked for passivation at the end of a "
+"transaction."
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1204
@@ -4812,6 +4812,10 @@
"cache. Otherwise, this option works in the same way as <emphasis>A</"
"emphasis>."
msgstr ""
+"For commit option <emphasis>D</emphasis>, a background refresh thread "
+"periodically calls <literal>ejbLoad</literal> on stale beans within the "
+"cache. Otherwise, this option works in the same way as <emphasis>A</"
+"emphasis>."
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1209
@@ -4823,6 +4827,11 @@
"pulled out of the passivation queue and reused if the application requests "
"access to a bean of the same primary key."
msgstr ""
+"When a bean is marked for passivation, the bean is placed in a passivation "
+"queue. Each entity bean container has a passivation thread that periodically "
+"passivates beans that have been placed in the passivation queue. A bean is "
+"pulled out of the passivation queue and reused if the application requests "
+"access to a bean of the same primary key."
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1212
@@ -4833,12 +4842,16 @@
"reused by an instance pool. Except for the passivation queue, there is no "
"entity bean instance pooling."
msgstr ""
+"On an exception or transaction rollback, the entity bean instance is thrown "
+"out of cache entirely. It is not put into the passivation queue and is not "
+"reused by an instance pool. Except for the passivation queue, there is no "
+"entity bean instance pooling."
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1218
#, no-c-format
msgid "Default Locking Behavior"
-msgstr ""
+msgstr "Default Locking Behavior"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1219
@@ -4850,6 +4863,11 @@
"one time, JBoss employs two types of locks to ensure data integrity and to "
"conform to the EJB spec."
msgstr ""
+"Entity bean locking is totally decoupled from the entity bean instance. The "
+"logic for locking is totally isolated and managed in a separate lock object. "
+"Because there is only one allowed instance of a given entity bean active at "
+"one time, JBoss employs two types of locks to ensure data integrity and to "
+"conform to the EJB spec."
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1224
@@ -4859,6 +4877,9 @@
"only one thread of execution at a time can invoke on a given Entity Bean. "
"This is required by the EJB spec."
msgstr ""
+"mphasis role=\"bold\">Method Lock</emphasis>: The method lock ensures that "
+"only one thread of execution at a time can invoke on a given Entity Bean. "
+"This is required by the EJB spec."
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1229
@@ -4875,12 +4896,22 @@
"other transaction can have access to this bean until the holding transaction "
"commits or is rolled back."
msgstr ""
+"<emphasis role=\"bold\">Transaction Lock</emphasis>: A transaction lock "
+"ensures that only one transaction at a time has access to a give Entity "
+"Bean. This ensures the ACID properties of transactions at the application "
+"server level. Since, by default, there is only one active instance of any "
+"given Entity Bean at one time, JBoss must protect this instance from dirty "
+"reads and dirty writes. So, the default entity bean locking behavior will "
+"lock an entity bean within a transaction until it completes. This means that "
+"if any method at all is invoked on an entity bean within a transaction, no "
+"other transaction can have access to this bean until the holding transaction "
+"commits or is rolled back."
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1237
#, no-c-format
msgid "Pluggable Interceptors and Locking Policy"
-msgstr ""
+msgstr "Pluggable Interceptors and Locking Policy"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1238
@@ -4892,6 +4923,11 @@
"definition for the <emphasis>Standard CMP 2.x EntityBean</emphasis> "
"configuration."
msgstr ""
+"We saw that the basic entity bean lifecycle and behavior is defined by the "
+"container configuration defined in <literal>standardjboss.xml</literal> "
+"descriptor. Let's look at the <literal>container-interceptors</literal> "
+"definition for the <emphasis>Standard CMP 2.x EntityBean</emphasis> "
+"configuration."
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1241
@@ -4963,6 +4999,9 @@
"Below is an explanation of the interceptors that are relevant to this "
"section."
msgstr ""
+"The interceptors shown above define most of the behavior of the entity bean. "
+"Below is an explanation of the interceptors that are relevant to this "
+"section."
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1247
@@ -4973,6 +5012,10 @@
"the invocation is allowed to proceed. This interceptor is very lightweight "
"and delegates all locking behavior to a pluggable locking policy."
msgstr ""
+"<emphasis role=\"bold\">EntityLockInterceptor</emphasis>: This "
+"interceptor's role is to schedule any locks that must be acquired before "
+"the invocation is allowed to proceed. This interceptor is very lightweight "
+"and delegates all locking behavior to a pluggable locking policy."
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1252
@@ -4983,6 +5026,10 @@
"one. This interceptor also ensures that there is only one active instance of "
"a bean in memory at one time."
msgstr ""
+"<emphasis role=\"bold\">EntityInstanceInterceptor</emphasis>: The job of "
+"this interceptor is to find the entity bean within the cache or create a new "
+"one. This interceptor also ensures that there is only one active instance of "
+"a bean in memory at one time."
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1257
@@ -5000,12 +5047,23 @@
"specification are taken care of here as well as the JBoss specific commit-"
"option <emphasis>D</emphasis>."
msgstr ""
+"<emphasis role=\"bold\">EntitySynchronizationInterceptor</emphasis>: The "
+"role of this interceptor is to synchronize the state of the cache with the "
+"underlying storage. It does this with the <literal>ejbLoad</literal> and "
+"<literal>ejbStore</literal> semantics of the EJB specification. In the "
+"presence of a transaction this is triggered by transaction demarcation. It "
+"registers a callback with the underlying transaction monitor through the JTA "
+"interfaces. If there is no transaction the policy is to store state upon "
+"returning from invocation. The synchronization polices <emphasis>A</"
+"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>."
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1265
#, no-c-format
msgid "Deadlock"
-msgstr ""
+msgstr "Deadlock"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1266
@@ -5025,12 +5083,25 @@
"are deadlocked waiting for access to the resource already locked by the "
"other thread."
msgstr ""
+"Finding deadlock problems and resolving them is the topic of this section. "
+"We will describe what deadlocking MBeans, how you can detect it within your "
+"application, and how you can resolve deadlocks. Deadlock can occur when two "
+"or more threads have locks on shared resources. <xref linkend=\"Deadlock_-"
+"Deadlock_definition_example\"/> illustrates a simple deadlock scenario. "
+"Here, <literal>Thread 1</literal> has the lock for <literal>Bean A</"
+"literal>, and <literal>Thread 2</literal> has the lock for <literal>Bean B</"
+"literal>. At a later time, <literal>Thread 1</literal> tries to lock "
+"<literal>Bean B</literal> and blocks because <literal>Thread 2</literal> has "
+"it. Likewise, as <literal>Thread 2</literal> tries to lock A it also blocks "
+"because <literal>Thread 1</literal> has the lock. At this point both threads "
+"are deadlocked waiting for access to the resource already locked by the "
+"other thread."
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1270
#, no-c-format
msgid "Deadlock definition example"
-msgstr ""
+msgstr "Deadlock definition example"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1277
@@ -5044,12 +5115,19 @@
"advanced configurations can be used to avoid deadlocking problems. They are "
"discussed later in this section."
msgstr ""
+"The default locking policy of JBoss is to lock an Entity bean when an "
+"invocation occurs in the context of a transaction until the transaction "
+"completes. Because of this, it is very easy to encounter deadlock if you "
+"have long running transactions that access many entity beans, or if you are "
+"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."
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1281
#, no-c-format
msgid "Deadlock Detection"
-msgstr ""
+msgstr "Deadlock Detection"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1282
@@ -5063,24 +5141,31 @@
"graph may look like is given in <xref linkend=\"Deadlock_Detection-"
"An_example_blocked_transaction_table\"/>."
msgstr ""
+"Fortunately, JBoss is able to perform deadlock detection. JBoss holds a "
+"global internal graph of waiting transactions and what transactions they are "
+"blocking on. Whenever a thread determines that it cannot acquire an entity "
+"bean lock, it figures out what transaction currently holds the lock on the "
+"bean and add itself to the blocked transaction graph. An example of what the "
+"graph may look like is given in <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 "An example blocked transaction table"
#. 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 "Tx that holds needed lock"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1300 J2EE_EJBs_On_JBOSS.xml:1319
@@ -5118,12 +5203,19 @@
"This exception will cause a transaction rollback which will cause all locks "
"that transaction holds to be released."
msgstr ""
+"Before the thread actually blocks it tries to detect whether there is "
+"deadlock problem. It does this by traversing the block transaction graph. As "
+"it traverses the graph, it keeps track of what transactions are blocked. If "
+"it sees a blocked node more than once in the graph, then it knows there is "
+"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."
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1332
#, no-c-format
msgid "Catching ApplicationDeadlockException"
-msgstr ""
+msgstr "Catching ApplicationDeadlockException"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1333
@@ -5136,6 +5228,12 @@
"<literal>RemoteException</literal>, so you have to search for it in your "
"catch block. For example:"
msgstr ""
+"Since JBoss can detect application deadlock, you should write your "
+"application so that it can retry a transaction if the invocation fails "
+"because of the <literal>ApplicationDeadlockException</literal>. "
+"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:"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1336
@@ -5177,7 +5275,7 @@
#: J2EE_EJBs_On_JBOSS.xml:1340
#, no-c-format
msgid "Viewing Lock Information"
-msgstr ""
+msgstr "Viewing Lock Information"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1341
@@ -5188,6 +5286,10 @@
"transaction locking table. To enable this monitor uncomment its "
"configuration in the <literal>conf/jboss-service.xml</literal>:"
msgstr ""
+"The <literal>EntityLockMonitor</literal> MBean service allows one to view "
+"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>:"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1344
@@ -5206,6 +5308,8 @@
"The <literal>EntityLockMonitor</literal> has no configurable attributes. It "
"does have the following read-only attributes:"
msgstr ""
+"The <literal>EntityLockMonitor</literal> has no configurable attributes. It "
+"does have the following read-only attributes:"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1350
More information about the jboss-cvs-commits
mailing list