[jboss-cvs] JBossAS SVN: r91144 - 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 03:02:00 EDT 2009
Author: ldelima at redhat.com
Date: 2009-07-13 03:02:00 -0400 (Mon, 13 Jul 2009)
New Revision: 91144
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:55:12 UTC (rev 91143)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_EJBs_On_JBOSS.po 2009-07-13 07:02:00 UTC (rev 91144)
@@ -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:54+1000\n"
+"PO-Revision-Date: 2009-07-13 17:01+1000\n"
"Last-Translator: \n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -5313,23 +5313,23 @@
#. 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\">timeout</emphasis> especifica o número máximo de "
-"milisegundos para aguardar por qualquer resposta. "
+"<emphasis role=\"bold\">MedianWaitTime</emphasis>: The median value of all "
+"times threads had to wait to acquire a lock."
#. 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> especifica o número "
-"máximo de respostas a receber. "
+"<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"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1360
@@ -5340,32 +5340,36 @@
"a thread attempts to acquire a lock that is associated with another "
"transaction"
msgstr ""
+"<emphasis role=\"bold\">TotalContentions</emphasis>: The total number of "
+"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"
#. 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\">ReplQueueMaxElements</emphasis> especifica o número "
-"máximo de elementos numa fila de replicação até que a replicação entre. "
+"<emphasis role=\"bold\">MaxContenders</emphasis>: The maximum number of "
+"threads that were waiting to acquire the transaction lock."
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1370
#, no-c-format
msgid "It also has the following operations:"
-msgstr ""
+msgstr "It also has the following operations:"
#. 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\">gossip_port</emphasis> especifica a porta na qual o "
-"GossipRouter está ouvindo. "
+"<emphasis role=\"bold\">clearMonitor</emphasis>: This operation resets the "
+"lock monitor state by zeroing all counters."
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1380
@@ -5377,12 +5381,17 @@
"lock was waited on and the number of transactions that timed out waiting for "
"the lock."
msgstr ""
+"<emphasis role=\"bold\">printLockMonitor</emphasis>: This operation prints "
+"out a table of all EJB locks that lists the <literal>ejbName</literal> of "
+"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."
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1390
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Advanced Configurations and Optimizations"
-msgstr "Outras Opções de Configuração"
+msgstr "Advanced Configurations and Optimizations"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1391
@@ -5394,12 +5403,17 @@
"section walks through various techniques and configurations that you can use "
"to optimize performance and reduce the possibility of deadlock."
msgstr ""
+"The default locking behavior of entity beans can cause deadlock. Since "
+"access to an entity bean locks the bean into the transaction, this also can "
+"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."
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1395
#, no-c-format
msgid "Short-lived Transactions"
-msgstr ""
+msgstr "Short-lived Transactions"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1396
@@ -5409,12 +5423,15 @@
"shorter the transaction you have, the less likelihood you will have "
"concurrent access collisions and your application throughput will go up."
msgstr ""
+"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."
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1402
#, no-c-format
msgid "Ordered Access"
-msgstr ""
+msgstr "Ordered Access"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1403
@@ -5426,12 +5443,17 @@
"are just too complicated to use this approach and more advanced "
"configurations are needed."
msgstr ""
+"Ordering the access to your entity beans can help lessen the likelihood of "
+"deadlock. This means making sure that the entity beans in your system are "
+"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."
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1409
#, no-c-format
msgid "Read-Only Beans"
-msgstr ""
+msgstr "Read-Only Beans"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1410
@@ -5443,23 +5465,27 @@
"option is sometimes very useful when your read-only bean's data is "
"sometimes updated by an external source."
msgstr ""
+"Entity beans can be marked as read-only. When a bean is marked as read-only, "
+"it never takes part in a transaction. This means that it is never "
+"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."
#. 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 ""
-"Mais tarde, você poderá configurar a replicação de sessão utilizando o "
-"elemento <literal>replication-config</literal> no arquivo <literal>jboss-"
-"web.xml</literal>. Segue aqui um exemplo:"
+"To mark a bean as read-only, use the <literal>read-only</literal> flag in "
+"the <literal>jboss.xml</literal> deployment descriptor."
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1416
#, no-c-format
msgid "Marking an entity bean read-only using jboss.xml"
-msgstr ""
+msgstr "Marking an entity bean read-only using jboss.xml"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1417
@@ -5489,7 +5515,7 @@
#: J2EE_EJBs_On_JBOSS.xml:1422
#, no-c-format
msgid "Explicitly Defining Read-Only Methods"
-msgstr ""
+msgstr "Explicitly Defining Read-Only Methods"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1423
@@ -5505,12 +5531,21 @@
"declaring all getter methods and the <literal>anotherReadOnlyMethod</"
"literal> as read-only."
msgstr ""
+"After reading and understanding the default locking behavior of entity "
+"beans, you're probably wondering, \"Why lock the bean if its not "
+"modifying the data?\" JBoss allows you to define what methods on your entity "
+"bean are read only so that it will not lock the bean within the transaction "
+"if only these types of methods are called. You can define these read only "
+"methods within a <literal>jboss.xml</literal> deployment descriptor. "
+"Wildcards are allowed for method names. The following is an example of "
+"declaring all getter methods and the <literal>anotherReadOnlyMethod</"
+"literal> as read-only."
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1426
#, no-c-format
msgid "Defining entity bean methods as read only"
-msgstr ""
+msgstr "Defining entity bean methods as read only"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1427
@@ -5560,7 +5595,7 @@
#: J2EE_EJBs_On_JBOSS.xml:1432
#, no-c-format
msgid "Instance Per Transaction Policy"
-msgstr ""
+msgstr "Instance Per Transaction Policy"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1433
@@ -5575,6 +5610,14 @@
"Because each transaction has its own copy of the bean, there is no need for "
"transaction based locking."
msgstr ""
+"The Instance Per Transaction policy is an advanced configuration that can "
+"totally wipe away deadlock and throughput problems caused by JBoss's "
+"default locking policy. The default Entity Bean locking policy is to only "
+"allow one active instance of a bean. The Instance Per Transaction policy "
+"breaks this requirement by allocating a new instance of a bean per "
+"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."
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1436
More information about the jboss-cvs-commits
mailing list