[jboss-cvs] JBossAS SVN: r78766 - in projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide: de-DE and 4 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Sep 23 02:24:15 EDT 2008
Author: xhuang at jboss.com
Date: 2008-09-23 02:24:15 -0400 (Tue, 23 Sep 2008)
New Revision: 78766
Added:
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Administration_of_ArjunaTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/JBoss_Transactions_JTA_Administration_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Administration_of_ArjunaTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/JBoss_Transactions_JTA_Administration_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Administration_of_ArjunaTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/JBoss_Transactions_JTA_Administration_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Administration_of_ArjunaTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/JBoss_Transactions_JTA_Administration_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Revision_History.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Administration_of_ArjunaTA.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Author_Group.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Book_Info.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/JBoss_Transactions_JTA_Administration_Guide.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Preface.po
projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Revision_History.po
Log:
merge
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Administration_of_ArjunaTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Administration_of_ArjunaTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Administration_of_ArjunaTA.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,932 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Administration_of_ArjunaTA.xml:6
+#, no-c-format
+msgid "Administration of ArjunaTA"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:9
+#, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the <firstterm>ArjunaTA</"
+"firstterm> software. There are a few points however, that should be made:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:14
+#, no-c-format
+msgid ""
+"The present implementation of the ArjunaTA system provides no security or "
+"protection for data. The objects stored in the ArjunaTA object store are "
+"(typically) owned by the user who ran the application that created them. The "
+"Object Store and Object Manager facilities make no attempt to enforce even "
+"the limited form of protection that Unix/Windows provides. There is no "
+"checking of user or group IDs on access to objects for either reading or "
+"writing."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:19
+#, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"<methodname>StateManager.destroy</methodname> method is invoked on the "
+"object or some application program explicitly deletes them. This means that "
+"the Object Store gradually accumulates garbage (especially during "
+"application development and testing phases). At present we have no automated "
+"garbage collection facility. Further, we have not addressed the problem of "
+"dangling references. That is, a persistent object, A, may have stored a Uid "
+"for another persistent object, B, in its passive representation on disk. "
+"There is nothing to prevent an application from deleting B even though A "
+"still contains a reference to it. When A is next activated and attempts to "
+"access B, a run-time error will occur."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:24
+#, no-c-format
+msgid ""
+"There is presently no support for version control of objects or database "
+"reconfiguration in the event of class structure changes. This is a complex "
+"research area that we have not addressed. At present, if you change the "
+"definition of a class of persistent objects, you are entirely responsible "
+"for ensuring that existing instances of the object in the Object Store are "
+"converted to the new representation. The ArjunaTA software can neither "
+"detect nor correct references to old object state by new operation versions "
+"or vice versa."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:29
+#, no-c-format
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:37
+#, no-c-format
+msgid "ObjectStore management"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:38
+#, no-c-format
+msgid ""
+"Within the transaction service installation, the object store is updated "
+"regularly whenever transactions are created, or when Transactional Objects "
+"for Java is used. In a failure free environment, the only object states "
+"which should reside within the object store are those representing objects "
+"created with the Transactional Objects for Java API. However, if failures "
+"occur, transaction logs may remain in the object store until crash recovery "
+"facilities have resolved the transactions they represent. As such it is very "
+"important that the contents of the object store are not deleted without due "
+"care and attention, as this will make it impossible to resolve in doubt "
+"transactions. In addition, if multiple users share the same object store it "
+"is important that they realise this and do not simply delete the contents of "
+"the object store assuming it is an exclusive resource."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:44
+#, no-c-format
+msgid "ArjunaTA runtime information"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:45
+#, no-c-format
+msgid ""
+"Each module that comprises ArjunaTA possesses a class called Info. These "
+"classes all provide a single toString method that returns an XML document "
+"representing the configuration information for that module. So, for example:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:48
+#, no-c-format
+msgid ""
+"<module-info name=\"arjuna\"><source-identifier>unknown</"
+"source-identifier><build-information>Arjuna Technologies [mlittle] "
+"(Windows 2000 5.0)</build-information><version>unknown</"
+"version><date>2002/06/15 04:06 PM</date><notes></"
+"notes><configuration><properties-file dir=\"null\">arjuna."
+"properties</properties-file><object-store-root>null</object-"
+"store-root></configuration></module-info>"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:52
+#, no-c-format
+msgid "Failure recovery administration"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:53
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of ArjunaTA will ensure that results of a "
+"transaction are applied consistently to all resources affected by the "
+"transaction, even if any of the application processes or the machine hosting "
+"them crash or lose network connectivity. In the case of machine (system) "
+"crash or network failure, the recovery will not take place until the system "
+"or network are restored, but the original application does not need to be "
+"restarted – recovery responsibility is delegated to the Recovery Manager "
+"process (see below). Recovery after failure requires that information about "
+"the transaction and the resources involved survives the failure and is "
+"accessible afterward: this information is held in the ActionStore, which is "
+"part of the ObjectStore."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:57
+#, no-c-format
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:61
+#, no-c-format
+msgid ""
+"Until the recovery procedures are complete, resources affected by a "
+"transaction that was in progress at the time of the failure may be "
+"inaccessible. For database resources, this may be reported as tables or rows "
+"held by <emphasis>in-doubt transactions</emphasis>. For TransactionalObjects "
+"for Java resources, an attempt to activate the Transactional Object (as when "
+"trying to get a lock) will fail."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:65
+#, no-c-format
+msgid "The Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:66
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of ArjunaTA requires that the stand-alone "
+"Recovery Manager process be running for each ObjectStore (typically one for "
+"each node on the network that is running ArjunaTA applications). The "
+"<filename>RecoveryManager</filename> file is located in the "
+"<filename>arjunacore</filename> jar file within the package <package>com."
+"arjuna.ats.arjuna.recovery.RecoveryManager</package>. To start the Recovery "
+"Manager issue the following command:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:70
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:71
+#, no-c-format
+msgid ""
+"If the -test flag is used with the Recovery Manager then it will display a "
+"<emphasis>Ready</emphasis> message when initialised, for instance:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:74
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:76
+#, no-c-format
+msgid "Configuring the Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:77
+#, no-c-format
+msgid ""
+"The RecoveryManager reads the properties defined in the arjuna.properties "
+"file and then also reads the property file RecoveryManager.properties, from "
+"the same directory as it found the arjuna properties file. An entry for a "
+"property in the RecoveryManager properties file will override an entry for "
+"the same property in the main TransactionService properties file. Most of "
+"the entries are specific to the Recovery Manager."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:81
+#, no-c-format
+msgid ""
+"A default version of RecoveryManager.properties is supplied with the "
+"distribution – this can be used without modification, except possibly the "
+"debug tracing fields (see below, Output). The rest of this section discusses "
+"the issues relevant in setting the properties to other values (in the order "
+"of their appearance in the default version of the file)."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:85
+#, no-c-format
+msgid "Output"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:86
+#, no-c-format
+msgid ""
+"It is likely that installations will want to have some form of output from "
+"the RecoveryManager, to provide a record of what recovery activity has taken "
+"place. RecoveryManager uses the logging tracing mechanism provided by the "
+"Arjuna Common Logging Framework (CLF), which provides a high level interface "
+"that hides differences that exist between existing logging APIs such Jakarta "
+"log4j or JDK 1.4 logging API. CLF indirects all logging via the Apache "
+"Commons Logging framework and configuration is assumed to occur through that "
+"framework."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:90
+#, no-c-format
+msgid ""
+"With the CLF applications make logging calls on logger objects. Loggers may "
+"use logging Levels to decide if they are interested in a particular log "
+"message. Each log message has an associated log Level, that gives the "
+"importance and urgency of a log message. The set of possible Log Levels are "
+"DEBUG, INFO, WARN, ERROR and FATAL. Defined Levels are ordered according to "
+"their integer values as follows: DEBUG < INFO < WARN < ERROR < "
+"FATAL."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:93
+#, no-c-format
+msgid ""
+"The CLF provides an extension to filter logging messages according to finer "
+"granularity an application may define. That is, when a log message is "
+"provided to the logger with the DEBUG level, additional conditions can be "
+"specified to determine if the log message is enabled or not."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:97
+#, no-c-format
+msgid ""
+"These conditions are applied if and only the DEBUG level is enabled and the "
+"log request performed by the application specifies debugging granularity."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:101
+#, no-c-format
+msgid "When enabled, Debugging is filtered conditionally on three variables:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:106
+#, no-c-format
+msgid ""
+"Debugging level: this is where the log request with the DEBUG Level is "
+"generated from, for example, constructors or basic methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:111
+#, no-c-format
+msgid ""
+"Visibility level: the visibility of the constructor, method, etc. that "
+"generates the debugging."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:116
+#, no-c-format
+msgid ""
+"Facility code: for instance the package or sub-module within which debugging "
+"is generated, for example, the object store."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:121
+#, no-c-format
+msgid ""
+"According to these variables the CLF defines three interfaces. A particular "
+"product may implement its own classes according to its own finer "
+"granularity. ArjunaTA uses the default Debugging level and the default "
+"Visibility level provided by CLF, but it defines its own Facility Code. "
+"ArjunaTA uses the default level assigned to its logger objects (DEBUG). "
+"However, it uses the finer debugging features to disable or enable debug "
+"messages. Finer debugging values used by the ArjunaTA are defined below:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:124
+#, no-c-format
+msgid ""
+"Debugging level – ArjunaTA uses the default values defined in the class "
+"<classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:129
+#, no-c-format
+msgid "NO_DEBUGGING: No diagnostics."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:132
+#, no-c-format
+msgid "A logger object assigned with this values discard all debug requests"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:137
+#, no-c-format
+msgid "FULL_DEBUGGING: Full diagnostics."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:140
+#, no-c-format
+msgid ""
+"A Logger object assigned with this value allows all debug requests if the "
+"facility code and the visibility level match those allowed by the logger."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:145
+#, no-c-format
+msgid "Additional Debugging Values are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:150
+#, no-c-format
+msgid "CONSTRUCTORS: Diagnostics from constructors."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:155
+#, no-c-format
+msgid "DESTRUCTORS: Diagnostics from finalizers."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:160
+#, no-c-format
+msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:165
+#, no-c-format
+msgid "FUNCTIONS: Diagnostics from functions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:170
+#, no-c-format
+msgid "OPERATORS: Diagnostics from operators, such as equals."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:175
+#, no-c-format
+msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:180
+#, no-c-format
+msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:185
+#, no-c-format
+msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:190
+#, no-c-format
+msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:195
+#, no-c-format
+msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:200
+#, no-c-format
+msgid ""
+"Visibility level – ArjunaTA uses the default values defined in the class "
+"<classname>com.arjuna.common.util.logging.VisibilityLevel</classname>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:205
+#, no-c-format
+msgid "VIS_NONE: No Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:210
+#, no-c-format
+msgid "VIS_PRIVATE: Only from private methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:215
+#, no-c-format
+msgid "VIS_PROTECTED: Only from protected methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:220
+#, no-c-format
+msgid "VIS_PUBLIC: Only from public methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:225
+#, no-c-format
+msgid "VIS_: only from package methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:230
+#, no-c-format
+msgid "VIS_ALL: Full Diagnostic ."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:235
+#, no-c-format
+msgid ""
+"Facility Code – ArjunaTA uses the following values defined in the class "
+"<classname>com.arjuna.common.util.logging.VisibilityLevel</classname>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:240
+#, no-c-format
+msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:245
+#, no-c-format
+msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:250
+#, no-c-format
+msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:255
+#, no-c-format
+msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:260
+#, no-c-format
+msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:265
+#, no-c-format
+msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:270
+#, no-c-format
+msgid "FAC_GENERAL = 0x00000080 (general classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:275
+#, no-c-format
+msgid ""
+"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
+"classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:280
+#, no-c-format
+msgid "FAC_THREADING = 0x00002000 (threading classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:285
+#, no-c-format
+msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:290
+#, no-c-format
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:295
+#, no-c-format
+msgid ""
+"To ensure appropriate output, it is necessary to set some of the finer debug "
+"properties explicitly in the <filename>CommonLogging.xml</filename> file, to "
+"enable logging messages issued by the ArjunaTA module."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:298
+#, no-c-format
+msgid ""
+"Messages describing the start and the periodical behavior made by the "
+"RecoveryManager are output using the INFO level. If other debug tracing is "
+"wanted, the finer debugging level should be set appropriately. For instance, "
+"the following configuration, in the <filename>CommonLogging.xml</filename>, "
+"enables all debug messages related to the Crash Recovery protocol and issued "
+"by the ArjunaTA module."
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:301
+#, no-c-format
+msgid ""
+"<!-- Common logging related properties. -->\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+" value=\"0x00000000\"/>\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+" value=\"0xffffffff\"/>\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+" value=\"0xffffffff\"/>"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:303
+#, no-c-format
+msgid ""
+"Two logger objects are provided, one manages I18N messages and a second does "
+"not."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:307
+#, no-c-format
+msgid ""
+"Setting the normal recovery messages to the INFO level allows the "
+"RecoveryManager producing a moderate level of reporting. If nothing is going "
+"on, it just reports the entry into each module for each periodic pass. To "
+"disable INFO messages produced by the Recovery Manager, the logging level "
+"could be set to the higher level: ERROR. Setting the level to ERROR means "
+"that the RecoveryManager will only produce error, warning or fatal messages."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:311
+#, no-c-format
+msgid "Periodic Recovery"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:312
+#, no-c-format
+msgid ""
+"The RecoveryManager scans the ObjectStore and other locations of "
+"information, looking for transactions and resources that require, or may "
+"require recovery. The scans and recovery processing are performed by "
+"recovery modules, (instances of classes that implement the com.arjuna.ats."
+"arjuna.recovery.RecoveryModule interface), each with responsibility for a "
+"particular category of transaction or resource. The set of recovery modules "
+"used are dynamically loaded, using properties found in the RecoveryManager "
+"property file."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:316
+#, no-c-format
+msgid ""
+"The interface has two methods: <methodname>periodicWorkFirstPass</"
+"methodname> and <methodname>periodicWorkSecondPass</methodname>. At an "
+"interval (defined by property <property>com.arjuna.ats.arjuna.recovery."
+"periodicRecoveryPeriod</property>), the RecoveryManager will call the first "
+"pass method on each property, then wait for a brief period (defined by "
+"property <property>com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</"
+"property>), then call the second pass of each module. Typically, in the "
+"first pass, the module scans (e.g. the relevant part of the ObjectStore) to "
+"find transactions or resources that are in-doubt (i.e. are part way through "
+"the commitment process). On the second pass, if any of the same items are "
+"still in-doubt, it is possible the original application process has crashed "
+"and the item is a candidate for recovery."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:319
+#, no-c-format
+msgid ""
+"An attempt, by the RecoveryManager, to recover a transaction that is still "
+"progressing in the original process(es) is likely to break the consistency. "
+"Accordingly, the recovery modules use a mechanism (implemented in the "
+"<package>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</package> "
+"package) to check to see if the original process is still alive, and if the "
+"transaction is still in progress. The RecoveryManager only proceeds with "
+"recovery if the original process has gone, or, if still alive, the "
+"transaction is completed. (If a server process or machine crashes, but the "
+"transaction-initiating process survives, the transaction will complete, "
+"usually generating a warning. Recovery of such a transaction is the "
+"RecoveryManager’s responsibility)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:322
+#, no-c-format
+msgid ""
+"It is clearly important to set the interval periods appropriately. The total "
+"iteration time will be the sum of the periodicRecoveryPeriod, "
+"recoveryBackoffPeriod and the length of time it takes to scan the stores and "
+"to attempt recovery of any in-doubt transactions found, for all the recovery "
+"modules. The recovery attempt time may include connection timeouts while "
+"trying to communicate with processes or machines that have crashed or are "
+"inaccessible (which is why there are mechanisms in the recovery system to "
+"avoid trying to recover the same transaction for ever). The total iteration "
+"time will affect how long a resource will remain inaccessible after a "
+"failure – periodicRecoveryPeriod should be set accordingly (default is 120 "
+"seconds). The recoveryBackoffPeriod can be comparatively short (default is "
+"10 seconds) – its purpose is mainly to reduce the number of transactions "
+"that are candidates for recovery and which thus require a call to the "
+"original process to see if they are still in progress."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:326
+#, no-c-format
+msgid ""
+"In previous versions of ArjunaCore there was no contact mechanism, and the "
+"backoff period had to be long enough to avoid catching transactions in "
+"flight at all. From 3.0, there is no such risk."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:330
+#, no-c-format
+msgid ""
+"Two recovery modules (implementations of the <interfacename>com.arjuna.ats."
+"arjuna.recovery.RecoveryModule</interfacename> interface) are supplied with "
+"ArjunaTA, supporting various aspects of transaction recovery including JDBC "
+"recovery. It is possible for advanced users to create their own recovery "
+"modules and register them with the Recovery Manager. The recovery modules "
+"are registered with the RecoveryManager using properties that begin with "
+"<property>com.arjuna.ats.arjuna.recovery.RecoveryExtension</property>. These "
+"will be invoked on each pass of the periodic recovery in the sort-order of "
+"the property names – it is thus possible to predict the ordering (but note "
+"that a failure in an application process might occur while a periodic "
+"recovery pass is in progress). The default Recovery Extension settings are:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:333
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = com.arjuna.ats.internal."
+"ts.arjuna.recovery.AtomicActionRecoveryModule\n"
+" \n"
+"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = com.arjuna.ats.txoj."
+"recovery.TORecoveryModule"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:335
+#, no-c-format
+msgid "Expired entry removal"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:336
+#, no-c-format
+msgid ""
+"The operation of the recovery subsystem will cause some entries to be made "
+"in the ObjectStore that will not be removed in normal progress. The "
+"RecoveryManager has a facility for scanning for these and removing items "
+"that are very old. Scans and removals are performed by implementations of "
+"the <interfacename>com.arjuna.ats.arjuna.recovery.ExpiryScanner</"
+"interfacename> interface. Implementations of this interface are loaded by "
+"giving the class name as the value of a property whose name begins with "
+"<property>com.arjuna.ats.arjuna.recovery.expiryScanner</property>. The "
+"RecoveryManager calls the <methodname>scan()</methodname> method on each "
+"loaded Expiry Scanner implementation at an interval determined by the "
+"property <property>com.arjuna.ats.arjuna.recovery.expiryScanInterval</"
+"property>. This value is given in hours – default is 12. An "
+"expiryScanInterval value of zero will suppress any expiry scanning. If the "
+"value as supplied is positive, the first scan is performed when "
+"RecoveryManager starts; if the value is negative, the first scan is delayed "
+"until after the first interval (using the absolute value)"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:340
+#, no-c-format
+msgid "The kinds of item that are scanned for expiry are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:343
+#, no-c-format
+msgid ""
+"TransactionStatusManager items : one of these is created by every "
+"application process that uses ArjunaCore – they contain the information that "
+"allows the RecoveryManager to determine if the process that initiated the "
+"transaction is still alive, and what the transaction status is. The expiry "
+"time for these is set by the property <property>com.arjuna.ats.arjuna."
+"recovery.transactionStatusManagerExpiryTime</property> (in hours – default "
+"is 12, zero means never expire). The expiry time should be greater than the "
+"lifetime of any single ArjunaTA-using process."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:346
+#, no-c-format
+msgid "The Expiry Scanner properties for these are:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:349
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager = com."
+"arjuna.ats.internal.ts.arjuna.recovery.ExpiredTransactionStatusManagerScanner"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:353
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:354
+#, no-c-format
+msgid ""
+"In this section we shall cover the types of errors and exceptions which may "
+"be thrown or reported during a transactional application and give probable "
+"indications of their causes."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:359
+#, no-c-format
+msgid ""
+"NO_MEMORY: the application has run out of memory (thrown an "
+"OutOfMemoryError) and ArjunaTA has attempted to do some cleanup (by running "
+"the garbage collector) before re-throwing the exception. This is probably a "
+"transient problem and retrying the invocation should succeed."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:364
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: an error has occurred which "
+"means that the transaction system must shut down. Prior to this error being "
+"thrown the transaction service will have ensured that all running "
+"transactions have rolled back. If caught, the application should tidy up and "
+"exit. If further work is attempted, application consistency may be violated."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:369
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: an attempt has been made to "
+"use the transaction service in a manner inconsistent with the current "
+"licence. The transaction service will not allow further forward progress for "
+"existing or new transactions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:374
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: an error occurred while "
+"the transaction service attempted to use the object store. Further forward "
+"progress is not possible."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:379
+#, no-c-format
+msgid ""
+"Object store warnings about access problems on states may occur during the "
+"normal execution of crash recovery. This is the result of multiple "
+"concurrent attempts to perform recovery on the same transaction. It can be "
+"safely ignored."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:387
+#, no-c-format
+msgid "Selecting the JTA implementation"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:388
+#, no-c-format
+msgid ""
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:393
+#, no-c-format
+msgid ""
+"A purely local JTA, which only allows non-distributed JTA transactions to be "
+"executed. This is the only version available with the ArjunaTA product."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:398
+#, no-c-format
+msgid ""
+"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
+"executed. This version is only available with the ArjunaJTS product and "
+"requires a supported CORBA ORB."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:404
+#, no-c-format
+msgid ""
+"Both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with ArjunaTA."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:408
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:413
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaTMImplementation</"
+"property> is set to <code>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"TransactionManagerImple</code>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:418
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaUTImplementation</"
+"property> is set to <code>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"UserTransactionImple</code>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:424
+#, no-c-format
+msgid ""
+"These settings are the default values for the properties and do not need to "
+"be specified if the local implementation is required."
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Author_Group.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,20 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Book_Info.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,44 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions JTA Administration Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the administration of Arjuna TA"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/JBoss_Transactions_JTA_Administration_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Preface.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,20 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/de-DE/Revision_History.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,26 @@
+# Language de-DE translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Administration_of_ArjunaTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Administration_of_ArjunaTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Administration_of_ArjunaTA.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,932 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Administration_of_ArjunaTA.xml:6
+#, no-c-format
+msgid "Administration of ArjunaTA"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:9
+#, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the <firstterm>ArjunaTA</"
+"firstterm> software. There are a few points however, that should be made:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:14
+#, no-c-format
+msgid ""
+"The present implementation of the ArjunaTA system provides no security or "
+"protection for data. The objects stored in the ArjunaTA object store are "
+"(typically) owned by the user who ran the application that created them. The "
+"Object Store and Object Manager facilities make no attempt to enforce even "
+"the limited form of protection that Unix/Windows provides. There is no "
+"checking of user or group IDs on access to objects for either reading or "
+"writing."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:19
+#, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"<methodname>StateManager.destroy</methodname> method is invoked on the "
+"object or some application program explicitly deletes them. This means that "
+"the Object Store gradually accumulates garbage (especially during "
+"application development and testing phases). At present we have no automated "
+"garbage collection facility. Further, we have not addressed the problem of "
+"dangling references. That is, a persistent object, A, may have stored a Uid "
+"for another persistent object, B, in its passive representation on disk. "
+"There is nothing to prevent an application from deleting B even though A "
+"still contains a reference to it. When A is next activated and attempts to "
+"access B, a run-time error will occur."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:24
+#, no-c-format
+msgid ""
+"There is presently no support for version control of objects or database "
+"reconfiguration in the event of class structure changes. This is a complex "
+"research area that we have not addressed. At present, if you change the "
+"definition of a class of persistent objects, you are entirely responsible "
+"for ensuring that existing instances of the object in the Object Store are "
+"converted to the new representation. The ArjunaTA software can neither "
+"detect nor correct references to old object state by new operation versions "
+"or vice versa."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:29
+#, no-c-format
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:37
+#, no-c-format
+msgid "ObjectStore management"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:38
+#, no-c-format
+msgid ""
+"Within the transaction service installation, the object store is updated "
+"regularly whenever transactions are created, or when Transactional Objects "
+"for Java is used. In a failure free environment, the only object states "
+"which should reside within the object store are those representing objects "
+"created with the Transactional Objects for Java API. However, if failures "
+"occur, transaction logs may remain in the object store until crash recovery "
+"facilities have resolved the transactions they represent. As such it is very "
+"important that the contents of the object store are not deleted without due "
+"care and attention, as this will make it impossible to resolve in doubt "
+"transactions. In addition, if multiple users share the same object store it "
+"is important that they realise this and do not simply delete the contents of "
+"the object store assuming it is an exclusive resource."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:44
+#, no-c-format
+msgid "ArjunaTA runtime information"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:45
+#, no-c-format
+msgid ""
+"Each module that comprises ArjunaTA possesses a class called Info. These "
+"classes all provide a single toString method that returns an XML document "
+"representing the configuration information for that module. So, for example:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:48
+#, no-c-format
+msgid ""
+"<module-info name=\"arjuna\"><source-identifier>unknown</"
+"source-identifier><build-information>Arjuna Technologies [mlittle] "
+"(Windows 2000 5.0)</build-information><version>unknown</"
+"version><date>2002/06/15 04:06 PM</date><notes></"
+"notes><configuration><properties-file dir=\"null\">arjuna."
+"properties</properties-file><object-store-root>null</object-"
+"store-root></configuration></module-info>"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:52
+#, no-c-format
+msgid "Failure recovery administration"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:53
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of ArjunaTA will ensure that results of a "
+"transaction are applied consistently to all resources affected by the "
+"transaction, even if any of the application processes or the machine hosting "
+"them crash or lose network connectivity. In the case of machine (system) "
+"crash or network failure, the recovery will not take place until the system "
+"or network are restored, but the original application does not need to be "
+"restarted – recovery responsibility is delegated to the Recovery Manager "
+"process (see below). Recovery after failure requires that information about "
+"the transaction and the resources involved survives the failure and is "
+"accessible afterward: this information is held in the ActionStore, which is "
+"part of the ObjectStore."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:57
+#, no-c-format
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:61
+#, no-c-format
+msgid ""
+"Until the recovery procedures are complete, resources affected by a "
+"transaction that was in progress at the time of the failure may be "
+"inaccessible. For database resources, this may be reported as tables or rows "
+"held by <emphasis>in-doubt transactions</emphasis>. For TransactionalObjects "
+"for Java resources, an attempt to activate the Transactional Object (as when "
+"trying to get a lock) will fail."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:65
+#, no-c-format
+msgid "The Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:66
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of ArjunaTA requires that the stand-alone "
+"Recovery Manager process be running for each ObjectStore (typically one for "
+"each node on the network that is running ArjunaTA applications). The "
+"<filename>RecoveryManager</filename> file is located in the "
+"<filename>arjunacore</filename> jar file within the package <package>com."
+"arjuna.ats.arjuna.recovery.RecoveryManager</package>. To start the Recovery "
+"Manager issue the following command:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:70
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:71
+#, no-c-format
+msgid ""
+"If the -test flag is used with the Recovery Manager then it will display a "
+"<emphasis>Ready</emphasis> message when initialised, for instance:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:74
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:76
+#, no-c-format
+msgid "Configuring the Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:77
+#, no-c-format
+msgid ""
+"The RecoveryManager reads the properties defined in the arjuna.properties "
+"file and then also reads the property file RecoveryManager.properties, from "
+"the same directory as it found the arjuna properties file. An entry for a "
+"property in the RecoveryManager properties file will override an entry for "
+"the same property in the main TransactionService properties file. Most of "
+"the entries are specific to the Recovery Manager."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:81
+#, no-c-format
+msgid ""
+"A default version of RecoveryManager.properties is supplied with the "
+"distribution – this can be used without modification, except possibly the "
+"debug tracing fields (see below, Output). The rest of this section discusses "
+"the issues relevant in setting the properties to other values (in the order "
+"of their appearance in the default version of the file)."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:85
+#, no-c-format
+msgid "Output"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:86
+#, no-c-format
+msgid ""
+"It is likely that installations will want to have some form of output from "
+"the RecoveryManager, to provide a record of what recovery activity has taken "
+"place. RecoveryManager uses the logging tracing mechanism provided by the "
+"Arjuna Common Logging Framework (CLF), which provides a high level interface "
+"that hides differences that exist between existing logging APIs such Jakarta "
+"log4j or JDK 1.4 logging API. CLF indirects all logging via the Apache "
+"Commons Logging framework and configuration is assumed to occur through that "
+"framework."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:90
+#, no-c-format
+msgid ""
+"With the CLF applications make logging calls on logger objects. Loggers may "
+"use logging Levels to decide if they are interested in a particular log "
+"message. Each log message has an associated log Level, that gives the "
+"importance and urgency of a log message. The set of possible Log Levels are "
+"DEBUG, INFO, WARN, ERROR and FATAL. Defined Levels are ordered according to "
+"their integer values as follows: DEBUG < INFO < WARN < ERROR < "
+"FATAL."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:93
+#, no-c-format
+msgid ""
+"The CLF provides an extension to filter logging messages according to finer "
+"granularity an application may define. That is, when a log message is "
+"provided to the logger with the DEBUG level, additional conditions can be "
+"specified to determine if the log message is enabled or not."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:97
+#, no-c-format
+msgid ""
+"These conditions are applied if and only the DEBUG level is enabled and the "
+"log request performed by the application specifies debugging granularity."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:101
+#, no-c-format
+msgid "When enabled, Debugging is filtered conditionally on three variables:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:106
+#, no-c-format
+msgid ""
+"Debugging level: this is where the log request with the DEBUG Level is "
+"generated from, for example, constructors or basic methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:111
+#, no-c-format
+msgid ""
+"Visibility level: the visibility of the constructor, method, etc. that "
+"generates the debugging."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:116
+#, no-c-format
+msgid ""
+"Facility code: for instance the package or sub-module within which debugging "
+"is generated, for example, the object store."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:121
+#, no-c-format
+msgid ""
+"According to these variables the CLF defines three interfaces. A particular "
+"product may implement its own classes according to its own finer "
+"granularity. ArjunaTA uses the default Debugging level and the default "
+"Visibility level provided by CLF, but it defines its own Facility Code. "
+"ArjunaTA uses the default level assigned to its logger objects (DEBUG). "
+"However, it uses the finer debugging features to disable or enable debug "
+"messages. Finer debugging values used by the ArjunaTA are defined below:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:124
+#, no-c-format
+msgid ""
+"Debugging level – ArjunaTA uses the default values defined in the class "
+"<classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:129
+#, no-c-format
+msgid "NO_DEBUGGING: No diagnostics."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:132
+#, no-c-format
+msgid "A logger object assigned with this values discard all debug requests"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:137
+#, no-c-format
+msgid "FULL_DEBUGGING: Full diagnostics."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:140
+#, no-c-format
+msgid ""
+"A Logger object assigned with this value allows all debug requests if the "
+"facility code and the visibility level match those allowed by the logger."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:145
+#, no-c-format
+msgid "Additional Debugging Values are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:150
+#, no-c-format
+msgid "CONSTRUCTORS: Diagnostics from constructors."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:155
+#, no-c-format
+msgid "DESTRUCTORS: Diagnostics from finalizers."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:160
+#, no-c-format
+msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:165
+#, no-c-format
+msgid "FUNCTIONS: Diagnostics from functions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:170
+#, no-c-format
+msgid "OPERATORS: Diagnostics from operators, such as equals."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:175
+#, no-c-format
+msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:180
+#, no-c-format
+msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:185
+#, no-c-format
+msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:190
+#, no-c-format
+msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:195
+#, no-c-format
+msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:200
+#, no-c-format
+msgid ""
+"Visibility level – ArjunaTA uses the default values defined in the class "
+"<classname>com.arjuna.common.util.logging.VisibilityLevel</classname>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:205
+#, no-c-format
+msgid "VIS_NONE: No Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:210
+#, no-c-format
+msgid "VIS_PRIVATE: Only from private methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:215
+#, no-c-format
+msgid "VIS_PROTECTED: Only from protected methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:220
+#, no-c-format
+msgid "VIS_PUBLIC: Only from public methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:225
+#, no-c-format
+msgid "VIS_: only from package methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:230
+#, no-c-format
+msgid "VIS_ALL: Full Diagnostic ."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:235
+#, no-c-format
+msgid ""
+"Facility Code – ArjunaTA uses the following values defined in the class "
+"<classname>com.arjuna.common.util.logging.VisibilityLevel</classname>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:240
+#, no-c-format
+msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:245
+#, no-c-format
+msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:250
+#, no-c-format
+msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:255
+#, no-c-format
+msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:260
+#, no-c-format
+msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:265
+#, no-c-format
+msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:270
+#, no-c-format
+msgid "FAC_GENERAL = 0x00000080 (general classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:275
+#, no-c-format
+msgid ""
+"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
+"classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:280
+#, no-c-format
+msgid "FAC_THREADING = 0x00002000 (threading classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:285
+#, no-c-format
+msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:290
+#, no-c-format
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:295
+#, no-c-format
+msgid ""
+"To ensure appropriate output, it is necessary to set some of the finer debug "
+"properties explicitly in the <filename>CommonLogging.xml</filename> file, to "
+"enable logging messages issued by the ArjunaTA module."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:298
+#, no-c-format
+msgid ""
+"Messages describing the start and the periodical behavior made by the "
+"RecoveryManager are output using the INFO level. If other debug tracing is "
+"wanted, the finer debugging level should be set appropriately. For instance, "
+"the following configuration, in the <filename>CommonLogging.xml</filename>, "
+"enables all debug messages related to the Crash Recovery protocol and issued "
+"by the ArjunaTA module."
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:301
+#, no-c-format
+msgid ""
+"<!-- Common logging related properties. -->\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+" value=\"0x00000000\"/>\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+" value=\"0xffffffff\"/>\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+" value=\"0xffffffff\"/>"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:303
+#, no-c-format
+msgid ""
+"Two logger objects are provided, one manages I18N messages and a second does "
+"not."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:307
+#, no-c-format
+msgid ""
+"Setting the normal recovery messages to the INFO level allows the "
+"RecoveryManager producing a moderate level of reporting. If nothing is going "
+"on, it just reports the entry into each module for each periodic pass. To "
+"disable INFO messages produced by the Recovery Manager, the logging level "
+"could be set to the higher level: ERROR. Setting the level to ERROR means "
+"that the RecoveryManager will only produce error, warning or fatal messages."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:311
+#, no-c-format
+msgid "Periodic Recovery"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:312
+#, no-c-format
+msgid ""
+"The RecoveryManager scans the ObjectStore and other locations of "
+"information, looking for transactions and resources that require, or may "
+"require recovery. The scans and recovery processing are performed by "
+"recovery modules, (instances of classes that implement the com.arjuna.ats."
+"arjuna.recovery.RecoveryModule interface), each with responsibility for a "
+"particular category of transaction or resource. The set of recovery modules "
+"used are dynamically loaded, using properties found in the RecoveryManager "
+"property file."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:316
+#, no-c-format
+msgid ""
+"The interface has two methods: <methodname>periodicWorkFirstPass</"
+"methodname> and <methodname>periodicWorkSecondPass</methodname>. At an "
+"interval (defined by property <property>com.arjuna.ats.arjuna.recovery."
+"periodicRecoveryPeriod</property>), the RecoveryManager will call the first "
+"pass method on each property, then wait for a brief period (defined by "
+"property <property>com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</"
+"property>), then call the second pass of each module. Typically, in the "
+"first pass, the module scans (e.g. the relevant part of the ObjectStore) to "
+"find transactions or resources that are in-doubt (i.e. are part way through "
+"the commitment process). On the second pass, if any of the same items are "
+"still in-doubt, it is possible the original application process has crashed "
+"and the item is a candidate for recovery."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:319
+#, no-c-format
+msgid ""
+"An attempt, by the RecoveryManager, to recover a transaction that is still "
+"progressing in the original process(es) is likely to break the consistency. "
+"Accordingly, the recovery modules use a mechanism (implemented in the "
+"<package>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</package> "
+"package) to check to see if the original process is still alive, and if the "
+"transaction is still in progress. The RecoveryManager only proceeds with "
+"recovery if the original process has gone, or, if still alive, the "
+"transaction is completed. (If a server process or machine crashes, but the "
+"transaction-initiating process survives, the transaction will complete, "
+"usually generating a warning. Recovery of such a transaction is the "
+"RecoveryManager’s responsibility)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:322
+#, no-c-format
+msgid ""
+"It is clearly important to set the interval periods appropriately. The total "
+"iteration time will be the sum of the periodicRecoveryPeriod, "
+"recoveryBackoffPeriod and the length of time it takes to scan the stores and "
+"to attempt recovery of any in-doubt transactions found, for all the recovery "
+"modules. The recovery attempt time may include connection timeouts while "
+"trying to communicate with processes or machines that have crashed or are "
+"inaccessible (which is why there are mechanisms in the recovery system to "
+"avoid trying to recover the same transaction for ever). The total iteration "
+"time will affect how long a resource will remain inaccessible after a "
+"failure – periodicRecoveryPeriod should be set accordingly (default is 120 "
+"seconds). The recoveryBackoffPeriod can be comparatively short (default is "
+"10 seconds) – its purpose is mainly to reduce the number of transactions "
+"that are candidates for recovery and which thus require a call to the "
+"original process to see if they are still in progress."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:326
+#, no-c-format
+msgid ""
+"In previous versions of ArjunaCore there was no contact mechanism, and the "
+"backoff period had to be long enough to avoid catching transactions in "
+"flight at all. From 3.0, there is no such risk."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:330
+#, no-c-format
+msgid ""
+"Two recovery modules (implementations of the <interfacename>com.arjuna.ats."
+"arjuna.recovery.RecoveryModule</interfacename> interface) are supplied with "
+"ArjunaTA, supporting various aspects of transaction recovery including JDBC "
+"recovery. It is possible for advanced users to create their own recovery "
+"modules and register them with the Recovery Manager. The recovery modules "
+"are registered with the RecoveryManager using properties that begin with "
+"<property>com.arjuna.ats.arjuna.recovery.RecoveryExtension</property>. These "
+"will be invoked on each pass of the periodic recovery in the sort-order of "
+"the property names – it is thus possible to predict the ordering (but note "
+"that a failure in an application process might occur while a periodic "
+"recovery pass is in progress). The default Recovery Extension settings are:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:333
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = com.arjuna.ats.internal."
+"ts.arjuna.recovery.AtomicActionRecoveryModule\n"
+" \n"
+"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = com.arjuna.ats.txoj."
+"recovery.TORecoveryModule"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:335
+#, no-c-format
+msgid "Expired entry removal"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:336
+#, no-c-format
+msgid ""
+"The operation of the recovery subsystem will cause some entries to be made "
+"in the ObjectStore that will not be removed in normal progress. The "
+"RecoveryManager has a facility for scanning for these and removing items "
+"that are very old. Scans and removals are performed by implementations of "
+"the <interfacename>com.arjuna.ats.arjuna.recovery.ExpiryScanner</"
+"interfacename> interface. Implementations of this interface are loaded by "
+"giving the class name as the value of a property whose name begins with "
+"<property>com.arjuna.ats.arjuna.recovery.expiryScanner</property>. The "
+"RecoveryManager calls the <methodname>scan()</methodname> method on each "
+"loaded Expiry Scanner implementation at an interval determined by the "
+"property <property>com.arjuna.ats.arjuna.recovery.expiryScanInterval</"
+"property>. This value is given in hours – default is 12. An "
+"expiryScanInterval value of zero will suppress any expiry scanning. If the "
+"value as supplied is positive, the first scan is performed when "
+"RecoveryManager starts; if the value is negative, the first scan is delayed "
+"until after the first interval (using the absolute value)"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:340
+#, no-c-format
+msgid "The kinds of item that are scanned for expiry are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:343
+#, no-c-format
+msgid ""
+"TransactionStatusManager items : one of these is created by every "
+"application process that uses ArjunaCore – they contain the information that "
+"allows the RecoveryManager to determine if the process that initiated the "
+"transaction is still alive, and what the transaction status is. The expiry "
+"time for these is set by the property <property>com.arjuna.ats.arjuna."
+"recovery.transactionStatusManagerExpiryTime</property> (in hours – default "
+"is 12, zero means never expire). The expiry time should be greater than the "
+"lifetime of any single ArjunaTA-using process."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:346
+#, no-c-format
+msgid "The Expiry Scanner properties for these are:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:349
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager = com."
+"arjuna.ats.internal.ts.arjuna.recovery.ExpiredTransactionStatusManagerScanner"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:353
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:354
+#, no-c-format
+msgid ""
+"In this section we shall cover the types of errors and exceptions which may "
+"be thrown or reported during a transactional application and give probable "
+"indications of their causes."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:359
+#, no-c-format
+msgid ""
+"NO_MEMORY: the application has run out of memory (thrown an "
+"OutOfMemoryError) and ArjunaTA has attempted to do some cleanup (by running "
+"the garbage collector) before re-throwing the exception. This is probably a "
+"transient problem and retrying the invocation should succeed."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:364
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: an error has occurred which "
+"means that the transaction system must shut down. Prior to this error being "
+"thrown the transaction service will have ensured that all running "
+"transactions have rolled back. If caught, the application should tidy up and "
+"exit. If further work is attempted, application consistency may be violated."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:369
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: an attempt has been made to "
+"use the transaction service in a manner inconsistent with the current "
+"licence. The transaction service will not allow further forward progress for "
+"existing or new transactions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:374
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: an error occurred while "
+"the transaction service attempted to use the object store. Further forward "
+"progress is not possible."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:379
+#, no-c-format
+msgid ""
+"Object store warnings about access problems on states may occur during the "
+"normal execution of crash recovery. This is the result of multiple "
+"concurrent attempts to perform recovery on the same transaction. It can be "
+"safely ignored."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:387
+#, no-c-format
+msgid "Selecting the JTA implementation"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:388
+#, no-c-format
+msgid ""
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:393
+#, no-c-format
+msgid ""
+"A purely local JTA, which only allows non-distributed JTA transactions to be "
+"executed. This is the only version available with the ArjunaTA product."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:398
+#, no-c-format
+msgid ""
+"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
+"executed. This version is only available with the ArjunaJTS product and "
+"requires a supported CORBA ORB."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:404
+#, no-c-format
+msgid ""
+"Both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with ArjunaTA."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:408
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:413
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaTMImplementation</"
+"property> is set to <code>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"TransactionManagerImple</code>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:418
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaUTImplementation</"
+"property> is set to <code>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"UserTransactionImple</code>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:424
+#, no-c-format
+msgid ""
+"These settings are the default values for the properties and do not need to "
+"be specified if the local implementation is required."
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Author_Group.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,20 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Book_Info.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,44 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions JTA Administration Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the administration of Arjuna TA"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/JBoss_Transactions_JTA_Administration_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Preface.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,20 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/es-ES/Revision_History.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,26 @@
+# Language es-ES translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Administration_of_ArjunaTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Administration_of_ArjunaTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Administration_of_ArjunaTA.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,932 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Administration_of_ArjunaTA.xml:6
+#, no-c-format
+msgid "Administration of ArjunaTA"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:9
+#, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the <firstterm>ArjunaTA</"
+"firstterm> software. There are a few points however, that should be made:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:14
+#, no-c-format
+msgid ""
+"The present implementation of the ArjunaTA system provides no security or "
+"protection for data. The objects stored in the ArjunaTA object store are "
+"(typically) owned by the user who ran the application that created them. The "
+"Object Store and Object Manager facilities make no attempt to enforce even "
+"the limited form of protection that Unix/Windows provides. There is no "
+"checking of user or group IDs on access to objects for either reading or "
+"writing."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:19
+#, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"<methodname>StateManager.destroy</methodname> method is invoked on the "
+"object or some application program explicitly deletes them. This means that "
+"the Object Store gradually accumulates garbage (especially during "
+"application development and testing phases). At present we have no automated "
+"garbage collection facility. Further, we have not addressed the problem of "
+"dangling references. That is, a persistent object, A, may have stored a Uid "
+"for another persistent object, B, in its passive representation on disk. "
+"There is nothing to prevent an application from deleting B even though A "
+"still contains a reference to it. When A is next activated and attempts to "
+"access B, a run-time error will occur."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:24
+#, no-c-format
+msgid ""
+"There is presently no support for version control of objects or database "
+"reconfiguration in the event of class structure changes. This is a complex "
+"research area that we have not addressed. At present, if you change the "
+"definition of a class of persistent objects, you are entirely responsible "
+"for ensuring that existing instances of the object in the Object Store are "
+"converted to the new representation. The ArjunaTA software can neither "
+"detect nor correct references to old object state by new operation versions "
+"or vice versa."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:29
+#, no-c-format
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:37
+#, no-c-format
+msgid "ObjectStore management"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:38
+#, no-c-format
+msgid ""
+"Within the transaction service installation, the object store is updated "
+"regularly whenever transactions are created, or when Transactional Objects "
+"for Java is used. In a failure free environment, the only object states "
+"which should reside within the object store are those representing objects "
+"created with the Transactional Objects for Java API. However, if failures "
+"occur, transaction logs may remain in the object store until crash recovery "
+"facilities have resolved the transactions they represent. As such it is very "
+"important that the contents of the object store are not deleted without due "
+"care and attention, as this will make it impossible to resolve in doubt "
+"transactions. In addition, if multiple users share the same object store it "
+"is important that they realise this and do not simply delete the contents of "
+"the object store assuming it is an exclusive resource."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:44
+#, no-c-format
+msgid "ArjunaTA runtime information"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:45
+#, no-c-format
+msgid ""
+"Each module that comprises ArjunaTA possesses a class called Info. These "
+"classes all provide a single toString method that returns an XML document "
+"representing the configuration information for that module. So, for example:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:48
+#, no-c-format
+msgid ""
+"<module-info name=\"arjuna\"><source-identifier>unknown</"
+"source-identifier><build-information>Arjuna Technologies [mlittle] "
+"(Windows 2000 5.0)</build-information><version>unknown</"
+"version><date>2002/06/15 04:06 PM</date><notes></"
+"notes><configuration><properties-file dir=\"null\">arjuna."
+"properties</properties-file><object-store-root>null</object-"
+"store-root></configuration></module-info>"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:52
+#, no-c-format
+msgid "Failure recovery administration"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:53
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of ArjunaTA will ensure that results of a "
+"transaction are applied consistently to all resources affected by the "
+"transaction, even if any of the application processes or the machine hosting "
+"them crash or lose network connectivity. In the case of machine (system) "
+"crash or network failure, the recovery will not take place until the system "
+"or network are restored, but the original application does not need to be "
+"restarted – recovery responsibility is delegated to the Recovery Manager "
+"process (see below). Recovery after failure requires that information about "
+"the transaction and the resources involved survives the failure and is "
+"accessible afterward: this information is held in the ActionStore, which is "
+"part of the ObjectStore."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:57
+#, no-c-format
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:61
+#, no-c-format
+msgid ""
+"Until the recovery procedures are complete, resources affected by a "
+"transaction that was in progress at the time of the failure may be "
+"inaccessible. For database resources, this may be reported as tables or rows "
+"held by <emphasis>in-doubt transactions</emphasis>. For TransactionalObjects "
+"for Java resources, an attempt to activate the Transactional Object (as when "
+"trying to get a lock) will fail."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:65
+#, no-c-format
+msgid "The Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:66
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of ArjunaTA requires that the stand-alone "
+"Recovery Manager process be running for each ObjectStore (typically one for "
+"each node on the network that is running ArjunaTA applications). The "
+"<filename>RecoveryManager</filename> file is located in the "
+"<filename>arjunacore</filename> jar file within the package <package>com."
+"arjuna.ats.arjuna.recovery.RecoveryManager</package>. To start the Recovery "
+"Manager issue the following command:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:70
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:71
+#, no-c-format
+msgid ""
+"If the -test flag is used with the Recovery Manager then it will display a "
+"<emphasis>Ready</emphasis> message when initialised, for instance:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:74
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:76
+#, no-c-format
+msgid "Configuring the Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:77
+#, no-c-format
+msgid ""
+"The RecoveryManager reads the properties defined in the arjuna.properties "
+"file and then also reads the property file RecoveryManager.properties, from "
+"the same directory as it found the arjuna properties file. An entry for a "
+"property in the RecoveryManager properties file will override an entry for "
+"the same property in the main TransactionService properties file. Most of "
+"the entries are specific to the Recovery Manager."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:81
+#, no-c-format
+msgid ""
+"A default version of RecoveryManager.properties is supplied with the "
+"distribution – this can be used without modification, except possibly the "
+"debug tracing fields (see below, Output). The rest of this section discusses "
+"the issues relevant in setting the properties to other values (in the order "
+"of their appearance in the default version of the file)."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:85
+#, no-c-format
+msgid "Output"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:86
+#, no-c-format
+msgid ""
+"It is likely that installations will want to have some form of output from "
+"the RecoveryManager, to provide a record of what recovery activity has taken "
+"place. RecoveryManager uses the logging tracing mechanism provided by the "
+"Arjuna Common Logging Framework (CLF), which provides a high level interface "
+"that hides differences that exist between existing logging APIs such Jakarta "
+"log4j or JDK 1.4 logging API. CLF indirects all logging via the Apache "
+"Commons Logging framework and configuration is assumed to occur through that "
+"framework."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:90
+#, no-c-format
+msgid ""
+"With the CLF applications make logging calls on logger objects. Loggers may "
+"use logging Levels to decide if they are interested in a particular log "
+"message. Each log message has an associated log Level, that gives the "
+"importance and urgency of a log message. The set of possible Log Levels are "
+"DEBUG, INFO, WARN, ERROR and FATAL. Defined Levels are ordered according to "
+"their integer values as follows: DEBUG < INFO < WARN < ERROR < "
+"FATAL."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:93
+#, no-c-format
+msgid ""
+"The CLF provides an extension to filter logging messages according to finer "
+"granularity an application may define. That is, when a log message is "
+"provided to the logger with the DEBUG level, additional conditions can be "
+"specified to determine if the log message is enabled or not."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:97
+#, no-c-format
+msgid ""
+"These conditions are applied if and only the DEBUG level is enabled and the "
+"log request performed by the application specifies debugging granularity."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:101
+#, no-c-format
+msgid "When enabled, Debugging is filtered conditionally on three variables:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:106
+#, no-c-format
+msgid ""
+"Debugging level: this is where the log request with the DEBUG Level is "
+"generated from, for example, constructors or basic methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:111
+#, no-c-format
+msgid ""
+"Visibility level: the visibility of the constructor, method, etc. that "
+"generates the debugging."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:116
+#, no-c-format
+msgid ""
+"Facility code: for instance the package or sub-module within which debugging "
+"is generated, for example, the object store."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:121
+#, no-c-format
+msgid ""
+"According to these variables the CLF defines three interfaces. A particular "
+"product may implement its own classes according to its own finer "
+"granularity. ArjunaTA uses the default Debugging level and the default "
+"Visibility level provided by CLF, but it defines its own Facility Code. "
+"ArjunaTA uses the default level assigned to its logger objects (DEBUG). "
+"However, it uses the finer debugging features to disable or enable debug "
+"messages. Finer debugging values used by the ArjunaTA are defined below:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:124
+#, no-c-format
+msgid ""
+"Debugging level – ArjunaTA uses the default values defined in the class "
+"<classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:129
+#, no-c-format
+msgid "NO_DEBUGGING: No diagnostics."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:132
+#, no-c-format
+msgid "A logger object assigned with this values discard all debug requests"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:137
+#, no-c-format
+msgid "FULL_DEBUGGING: Full diagnostics."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:140
+#, no-c-format
+msgid ""
+"A Logger object assigned with this value allows all debug requests if the "
+"facility code and the visibility level match those allowed by the logger."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:145
+#, no-c-format
+msgid "Additional Debugging Values are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:150
+#, no-c-format
+msgid "CONSTRUCTORS: Diagnostics from constructors."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:155
+#, no-c-format
+msgid "DESTRUCTORS: Diagnostics from finalizers."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:160
+#, no-c-format
+msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:165
+#, no-c-format
+msgid "FUNCTIONS: Diagnostics from functions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:170
+#, no-c-format
+msgid "OPERATORS: Diagnostics from operators, such as equals."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:175
+#, no-c-format
+msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:180
+#, no-c-format
+msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:185
+#, no-c-format
+msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:190
+#, no-c-format
+msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:195
+#, no-c-format
+msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:200
+#, no-c-format
+msgid ""
+"Visibility level – ArjunaTA uses the default values defined in the class "
+"<classname>com.arjuna.common.util.logging.VisibilityLevel</classname>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:205
+#, no-c-format
+msgid "VIS_NONE: No Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:210
+#, no-c-format
+msgid "VIS_PRIVATE: Only from private methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:215
+#, no-c-format
+msgid "VIS_PROTECTED: Only from protected methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:220
+#, no-c-format
+msgid "VIS_PUBLIC: Only from public methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:225
+#, no-c-format
+msgid "VIS_: only from package methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:230
+#, no-c-format
+msgid "VIS_ALL: Full Diagnostic ."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:235
+#, no-c-format
+msgid ""
+"Facility Code – ArjunaTA uses the following values defined in the class "
+"<classname>com.arjuna.common.util.logging.VisibilityLevel</classname>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:240
+#, no-c-format
+msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:245
+#, no-c-format
+msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:250
+#, no-c-format
+msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:255
+#, no-c-format
+msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:260
+#, no-c-format
+msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:265
+#, no-c-format
+msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:270
+#, no-c-format
+msgid "FAC_GENERAL = 0x00000080 (general classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:275
+#, no-c-format
+msgid ""
+"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
+"classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:280
+#, no-c-format
+msgid "FAC_THREADING = 0x00002000 (threading classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:285
+#, no-c-format
+msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:290
+#, no-c-format
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:295
+#, no-c-format
+msgid ""
+"To ensure appropriate output, it is necessary to set some of the finer debug "
+"properties explicitly in the <filename>CommonLogging.xml</filename> file, to "
+"enable logging messages issued by the ArjunaTA module."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:298
+#, no-c-format
+msgid ""
+"Messages describing the start and the periodical behavior made by the "
+"RecoveryManager are output using the INFO level. If other debug tracing is "
+"wanted, the finer debugging level should be set appropriately. For instance, "
+"the following configuration, in the <filename>CommonLogging.xml</filename>, "
+"enables all debug messages related to the Crash Recovery protocol and issued "
+"by the ArjunaTA module."
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:301
+#, no-c-format
+msgid ""
+"<!-- Common logging related properties. -->\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+" value=\"0x00000000\"/>\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+" value=\"0xffffffff\"/>\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+" value=\"0xffffffff\"/>"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:303
+#, no-c-format
+msgid ""
+"Two logger objects are provided, one manages I18N messages and a second does "
+"not."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:307
+#, no-c-format
+msgid ""
+"Setting the normal recovery messages to the INFO level allows the "
+"RecoveryManager producing a moderate level of reporting. If nothing is going "
+"on, it just reports the entry into each module for each periodic pass. To "
+"disable INFO messages produced by the Recovery Manager, the logging level "
+"could be set to the higher level: ERROR. Setting the level to ERROR means "
+"that the RecoveryManager will only produce error, warning or fatal messages."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:311
+#, no-c-format
+msgid "Periodic Recovery"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:312
+#, no-c-format
+msgid ""
+"The RecoveryManager scans the ObjectStore and other locations of "
+"information, looking for transactions and resources that require, or may "
+"require recovery. The scans and recovery processing are performed by "
+"recovery modules, (instances of classes that implement the com.arjuna.ats."
+"arjuna.recovery.RecoveryModule interface), each with responsibility for a "
+"particular category of transaction or resource. The set of recovery modules "
+"used are dynamically loaded, using properties found in the RecoveryManager "
+"property file."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:316
+#, no-c-format
+msgid ""
+"The interface has two methods: <methodname>periodicWorkFirstPass</"
+"methodname> and <methodname>periodicWorkSecondPass</methodname>. At an "
+"interval (defined by property <property>com.arjuna.ats.arjuna.recovery."
+"periodicRecoveryPeriod</property>), the RecoveryManager will call the first "
+"pass method on each property, then wait for a brief period (defined by "
+"property <property>com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</"
+"property>), then call the second pass of each module. Typically, in the "
+"first pass, the module scans (e.g. the relevant part of the ObjectStore) to "
+"find transactions or resources that are in-doubt (i.e. are part way through "
+"the commitment process). On the second pass, if any of the same items are "
+"still in-doubt, it is possible the original application process has crashed "
+"and the item is a candidate for recovery."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:319
+#, no-c-format
+msgid ""
+"An attempt, by the RecoveryManager, to recover a transaction that is still "
+"progressing in the original process(es) is likely to break the consistency. "
+"Accordingly, the recovery modules use a mechanism (implemented in the "
+"<package>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</package> "
+"package) to check to see if the original process is still alive, and if the "
+"transaction is still in progress. The RecoveryManager only proceeds with "
+"recovery if the original process has gone, or, if still alive, the "
+"transaction is completed. (If a server process or machine crashes, but the "
+"transaction-initiating process survives, the transaction will complete, "
+"usually generating a warning. Recovery of such a transaction is the "
+"RecoveryManager’s responsibility)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:322
+#, no-c-format
+msgid ""
+"It is clearly important to set the interval periods appropriately. The total "
+"iteration time will be the sum of the periodicRecoveryPeriod, "
+"recoveryBackoffPeriod and the length of time it takes to scan the stores and "
+"to attempt recovery of any in-doubt transactions found, for all the recovery "
+"modules. The recovery attempt time may include connection timeouts while "
+"trying to communicate with processes or machines that have crashed or are "
+"inaccessible (which is why there are mechanisms in the recovery system to "
+"avoid trying to recover the same transaction for ever). The total iteration "
+"time will affect how long a resource will remain inaccessible after a "
+"failure – periodicRecoveryPeriod should be set accordingly (default is 120 "
+"seconds). The recoveryBackoffPeriod can be comparatively short (default is "
+"10 seconds) – its purpose is mainly to reduce the number of transactions "
+"that are candidates for recovery and which thus require a call to the "
+"original process to see if they are still in progress."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:326
+#, no-c-format
+msgid ""
+"In previous versions of ArjunaCore there was no contact mechanism, and the "
+"backoff period had to be long enough to avoid catching transactions in "
+"flight at all. From 3.0, there is no such risk."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:330
+#, no-c-format
+msgid ""
+"Two recovery modules (implementations of the <interfacename>com.arjuna.ats."
+"arjuna.recovery.RecoveryModule</interfacename> interface) are supplied with "
+"ArjunaTA, supporting various aspects of transaction recovery including JDBC "
+"recovery. It is possible for advanced users to create their own recovery "
+"modules and register them with the Recovery Manager. The recovery modules "
+"are registered with the RecoveryManager using properties that begin with "
+"<property>com.arjuna.ats.arjuna.recovery.RecoveryExtension</property>. These "
+"will be invoked on each pass of the periodic recovery in the sort-order of "
+"the property names – it is thus possible to predict the ordering (but note "
+"that a failure in an application process might occur while a periodic "
+"recovery pass is in progress). The default Recovery Extension settings are:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:333
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = com.arjuna.ats.internal."
+"ts.arjuna.recovery.AtomicActionRecoveryModule\n"
+" \n"
+"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = com.arjuna.ats.txoj."
+"recovery.TORecoveryModule"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:335
+#, no-c-format
+msgid "Expired entry removal"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:336
+#, no-c-format
+msgid ""
+"The operation of the recovery subsystem will cause some entries to be made "
+"in the ObjectStore that will not be removed in normal progress. The "
+"RecoveryManager has a facility for scanning for these and removing items "
+"that are very old. Scans and removals are performed by implementations of "
+"the <interfacename>com.arjuna.ats.arjuna.recovery.ExpiryScanner</"
+"interfacename> interface. Implementations of this interface are loaded by "
+"giving the class name as the value of a property whose name begins with "
+"<property>com.arjuna.ats.arjuna.recovery.expiryScanner</property>. The "
+"RecoveryManager calls the <methodname>scan()</methodname> method on each "
+"loaded Expiry Scanner implementation at an interval determined by the "
+"property <property>com.arjuna.ats.arjuna.recovery.expiryScanInterval</"
+"property>. This value is given in hours – default is 12. An "
+"expiryScanInterval value of zero will suppress any expiry scanning. If the "
+"value as supplied is positive, the first scan is performed when "
+"RecoveryManager starts; if the value is negative, the first scan is delayed "
+"until after the first interval (using the absolute value)"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:340
+#, no-c-format
+msgid "The kinds of item that are scanned for expiry are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:343
+#, no-c-format
+msgid ""
+"TransactionStatusManager items : one of these is created by every "
+"application process that uses ArjunaCore – they contain the information that "
+"allows the RecoveryManager to determine if the process that initiated the "
+"transaction is still alive, and what the transaction status is. The expiry "
+"time for these is set by the property <property>com.arjuna.ats.arjuna."
+"recovery.transactionStatusManagerExpiryTime</property> (in hours – default "
+"is 12, zero means never expire). The expiry time should be greater than the "
+"lifetime of any single ArjunaTA-using process."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:346
+#, no-c-format
+msgid "The Expiry Scanner properties for these are:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:349
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager = com."
+"arjuna.ats.internal.ts.arjuna.recovery.ExpiredTransactionStatusManagerScanner"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:353
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:354
+#, no-c-format
+msgid ""
+"In this section we shall cover the types of errors and exceptions which may "
+"be thrown or reported during a transactional application and give probable "
+"indications of their causes."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:359
+#, no-c-format
+msgid ""
+"NO_MEMORY: the application has run out of memory (thrown an "
+"OutOfMemoryError) and ArjunaTA has attempted to do some cleanup (by running "
+"the garbage collector) before re-throwing the exception. This is probably a "
+"transient problem and retrying the invocation should succeed."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:364
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: an error has occurred which "
+"means that the transaction system must shut down. Prior to this error being "
+"thrown the transaction service will have ensured that all running "
+"transactions have rolled back. If caught, the application should tidy up and "
+"exit. If further work is attempted, application consistency may be violated."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:369
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: an attempt has been made to "
+"use the transaction service in a manner inconsistent with the current "
+"licence. The transaction service will not allow further forward progress for "
+"existing or new transactions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:374
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: an error occurred while "
+"the transaction service attempted to use the object store. Further forward "
+"progress is not possible."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:379
+#, no-c-format
+msgid ""
+"Object store warnings about access problems on states may occur during the "
+"normal execution of crash recovery. This is the result of multiple "
+"concurrent attempts to perform recovery on the same transaction. It can be "
+"safely ignored."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:387
+#, no-c-format
+msgid "Selecting the JTA implementation"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:388
+#, no-c-format
+msgid ""
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:393
+#, no-c-format
+msgid ""
+"A purely local JTA, which only allows non-distributed JTA transactions to be "
+"executed. This is the only version available with the ArjunaTA product."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:398
+#, no-c-format
+msgid ""
+"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
+"executed. This version is only available with the ArjunaJTS product and "
+"requires a supported CORBA ORB."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:404
+#, no-c-format
+msgid ""
+"Both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with ArjunaTA."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:408
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:413
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaTMImplementation</"
+"property> is set to <code>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"TransactionManagerImple</code>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:418
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaUTImplementation</"
+"property> is set to <code>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"UserTransactionImple</code>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:424
+#, no-c-format
+msgid ""
+"These settings are the default values for the properties and do not need to "
+"be specified if the local implementation is required."
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Author_Group.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,20 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Book_Info.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,44 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions JTA Administration Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the administration of Arjuna TA"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/JBoss_Transactions_JTA_Administration_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Preface.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,20 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/fr-FR/Revision_History.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,26 @@
+# Language fr-FR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Administration_of_ArjunaTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Administration_of_ArjunaTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Administration_of_ArjunaTA.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,932 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Administration_of_ArjunaTA.xml:6
+#, no-c-format
+msgid "Administration of ArjunaTA"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:9
+#, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the <firstterm>ArjunaTA</"
+"firstterm> software. There are a few points however, that should be made:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:14
+#, no-c-format
+msgid ""
+"The present implementation of the ArjunaTA system provides no security or "
+"protection for data. The objects stored in the ArjunaTA object store are "
+"(typically) owned by the user who ran the application that created them. The "
+"Object Store and Object Manager facilities make no attempt to enforce even "
+"the limited form of protection that Unix/Windows provides. There is no "
+"checking of user or group IDs on access to objects for either reading or "
+"writing."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:19
+#, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"<methodname>StateManager.destroy</methodname> method is invoked on the "
+"object or some application program explicitly deletes them. This means that "
+"the Object Store gradually accumulates garbage (especially during "
+"application development and testing phases). At present we have no automated "
+"garbage collection facility. Further, we have not addressed the problem of "
+"dangling references. That is, a persistent object, A, may have stored a Uid "
+"for another persistent object, B, in its passive representation on disk. "
+"There is nothing to prevent an application from deleting B even though A "
+"still contains a reference to it. When A is next activated and attempts to "
+"access B, a run-time error will occur."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:24
+#, no-c-format
+msgid ""
+"There is presently no support for version control of objects or database "
+"reconfiguration in the event of class structure changes. This is a complex "
+"research area that we have not addressed. At present, if you change the "
+"definition of a class of persistent objects, you are entirely responsible "
+"for ensuring that existing instances of the object in the Object Store are "
+"converted to the new representation. The ArjunaTA software can neither "
+"detect nor correct references to old object state by new operation versions "
+"or vice versa."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:29
+#, no-c-format
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:37
+#, no-c-format
+msgid "ObjectStore management"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:38
+#, no-c-format
+msgid ""
+"Within the transaction service installation, the object store is updated "
+"regularly whenever transactions are created, or when Transactional Objects "
+"for Java is used. In a failure free environment, the only object states "
+"which should reside within the object store are those representing objects "
+"created with the Transactional Objects for Java API. However, if failures "
+"occur, transaction logs may remain in the object store until crash recovery "
+"facilities have resolved the transactions they represent. As such it is very "
+"important that the contents of the object store are not deleted without due "
+"care and attention, as this will make it impossible to resolve in doubt "
+"transactions. In addition, if multiple users share the same object store it "
+"is important that they realise this and do not simply delete the contents of "
+"the object store assuming it is an exclusive resource."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:44
+#, no-c-format
+msgid "ArjunaTA runtime information"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:45
+#, no-c-format
+msgid ""
+"Each module that comprises ArjunaTA possesses a class called Info. These "
+"classes all provide a single toString method that returns an XML document "
+"representing the configuration information for that module. So, for example:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:48
+#, no-c-format
+msgid ""
+"<module-info name=\"arjuna\"><source-identifier>unknown</"
+"source-identifier><build-information>Arjuna Technologies [mlittle] "
+"(Windows 2000 5.0)</build-information><version>unknown</"
+"version><date>2002/06/15 04:06 PM</date><notes></"
+"notes><configuration><properties-file dir=\"null\">arjuna."
+"properties</properties-file><object-store-root>null</object-"
+"store-root></configuration></module-info>"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:52
+#, no-c-format
+msgid "Failure recovery administration"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:53
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of ArjunaTA will ensure that results of a "
+"transaction are applied consistently to all resources affected by the "
+"transaction, even if any of the application processes or the machine hosting "
+"them crash or lose network connectivity. In the case of machine (system) "
+"crash or network failure, the recovery will not take place until the system "
+"or network are restored, but the original application does not need to be "
+"restarted – recovery responsibility is delegated to the Recovery Manager "
+"process (see below). Recovery after failure requires that information about "
+"the transaction and the resources involved survives the failure and is "
+"accessible afterward: this information is held in the ActionStore, which is "
+"part of the ObjectStore."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:57
+#, no-c-format
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:61
+#, no-c-format
+msgid ""
+"Until the recovery procedures are complete, resources affected by a "
+"transaction that was in progress at the time of the failure may be "
+"inaccessible. For database resources, this may be reported as tables or rows "
+"held by <emphasis>in-doubt transactions</emphasis>. For TransactionalObjects "
+"for Java resources, an attempt to activate the Transactional Object (as when "
+"trying to get a lock) will fail."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:65
+#, no-c-format
+msgid "The Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:66
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of ArjunaTA requires that the stand-alone "
+"Recovery Manager process be running for each ObjectStore (typically one for "
+"each node on the network that is running ArjunaTA applications). The "
+"<filename>RecoveryManager</filename> file is located in the "
+"<filename>arjunacore</filename> jar file within the package <package>com."
+"arjuna.ats.arjuna.recovery.RecoveryManager</package>. To start the Recovery "
+"Manager issue the following command:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:70
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:71
+#, no-c-format
+msgid ""
+"If the -test flag is used with the Recovery Manager then it will display a "
+"<emphasis>Ready</emphasis> message when initialised, for instance:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:74
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:76
+#, no-c-format
+msgid "Configuring the Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:77
+#, no-c-format
+msgid ""
+"The RecoveryManager reads the properties defined in the arjuna.properties "
+"file and then also reads the property file RecoveryManager.properties, from "
+"the same directory as it found the arjuna properties file. An entry for a "
+"property in the RecoveryManager properties file will override an entry for "
+"the same property in the main TransactionService properties file. Most of "
+"the entries are specific to the Recovery Manager."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:81
+#, no-c-format
+msgid ""
+"A default version of RecoveryManager.properties is supplied with the "
+"distribution – this can be used without modification, except possibly the "
+"debug tracing fields (see below, Output). The rest of this section discusses "
+"the issues relevant in setting the properties to other values (in the order "
+"of their appearance in the default version of the file)."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:85
+#, no-c-format
+msgid "Output"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:86
+#, no-c-format
+msgid ""
+"It is likely that installations will want to have some form of output from "
+"the RecoveryManager, to provide a record of what recovery activity has taken "
+"place. RecoveryManager uses the logging tracing mechanism provided by the "
+"Arjuna Common Logging Framework (CLF), which provides a high level interface "
+"that hides differences that exist between existing logging APIs such Jakarta "
+"log4j or JDK 1.4 logging API. CLF indirects all logging via the Apache "
+"Commons Logging framework and configuration is assumed to occur through that "
+"framework."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:90
+#, no-c-format
+msgid ""
+"With the CLF applications make logging calls on logger objects. Loggers may "
+"use logging Levels to decide if they are interested in a particular log "
+"message. Each log message has an associated log Level, that gives the "
+"importance and urgency of a log message. The set of possible Log Levels are "
+"DEBUG, INFO, WARN, ERROR and FATAL. Defined Levels are ordered according to "
+"their integer values as follows: DEBUG < INFO < WARN < ERROR < "
+"FATAL."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:93
+#, no-c-format
+msgid ""
+"The CLF provides an extension to filter logging messages according to finer "
+"granularity an application may define. That is, when a log message is "
+"provided to the logger with the DEBUG level, additional conditions can be "
+"specified to determine if the log message is enabled or not."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:97
+#, no-c-format
+msgid ""
+"These conditions are applied if and only the DEBUG level is enabled and the "
+"log request performed by the application specifies debugging granularity."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:101
+#, no-c-format
+msgid "When enabled, Debugging is filtered conditionally on three variables:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:106
+#, no-c-format
+msgid ""
+"Debugging level: this is where the log request with the DEBUG Level is "
+"generated from, for example, constructors or basic methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:111
+#, no-c-format
+msgid ""
+"Visibility level: the visibility of the constructor, method, etc. that "
+"generates the debugging."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:116
+#, no-c-format
+msgid ""
+"Facility code: for instance the package or sub-module within which debugging "
+"is generated, for example, the object store."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:121
+#, no-c-format
+msgid ""
+"According to these variables the CLF defines three interfaces. A particular "
+"product may implement its own classes according to its own finer "
+"granularity. ArjunaTA uses the default Debugging level and the default "
+"Visibility level provided by CLF, but it defines its own Facility Code. "
+"ArjunaTA uses the default level assigned to its logger objects (DEBUG). "
+"However, it uses the finer debugging features to disable or enable debug "
+"messages. Finer debugging values used by the ArjunaTA are defined below:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:124
+#, no-c-format
+msgid ""
+"Debugging level – ArjunaTA uses the default values defined in the class "
+"<classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:129
+#, no-c-format
+msgid "NO_DEBUGGING: No diagnostics."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:132
+#, no-c-format
+msgid "A logger object assigned with this values discard all debug requests"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:137
+#, no-c-format
+msgid "FULL_DEBUGGING: Full diagnostics."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:140
+#, no-c-format
+msgid ""
+"A Logger object assigned with this value allows all debug requests if the "
+"facility code and the visibility level match those allowed by the logger."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:145
+#, no-c-format
+msgid "Additional Debugging Values are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:150
+#, no-c-format
+msgid "CONSTRUCTORS: Diagnostics from constructors."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:155
+#, no-c-format
+msgid "DESTRUCTORS: Diagnostics from finalizers."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:160
+#, no-c-format
+msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:165
+#, no-c-format
+msgid "FUNCTIONS: Diagnostics from functions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:170
+#, no-c-format
+msgid "OPERATORS: Diagnostics from operators, such as equals."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:175
+#, no-c-format
+msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:180
+#, no-c-format
+msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:185
+#, no-c-format
+msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:190
+#, no-c-format
+msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:195
+#, no-c-format
+msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:200
+#, no-c-format
+msgid ""
+"Visibility level – ArjunaTA uses the default values defined in the class "
+"<classname>com.arjuna.common.util.logging.VisibilityLevel</classname>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:205
+#, no-c-format
+msgid "VIS_NONE: No Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:210
+#, no-c-format
+msgid "VIS_PRIVATE: Only from private methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:215
+#, no-c-format
+msgid "VIS_PROTECTED: Only from protected methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:220
+#, no-c-format
+msgid "VIS_PUBLIC: Only from public methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:225
+#, no-c-format
+msgid "VIS_: only from package methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:230
+#, no-c-format
+msgid "VIS_ALL: Full Diagnostic ."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:235
+#, no-c-format
+msgid ""
+"Facility Code – ArjunaTA uses the following values defined in the class "
+"<classname>com.arjuna.common.util.logging.VisibilityLevel</classname>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:240
+#, no-c-format
+msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:245
+#, no-c-format
+msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:250
+#, no-c-format
+msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:255
+#, no-c-format
+msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:260
+#, no-c-format
+msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:265
+#, no-c-format
+msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:270
+#, no-c-format
+msgid "FAC_GENERAL = 0x00000080 (general classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:275
+#, no-c-format
+msgid ""
+"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
+"classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:280
+#, no-c-format
+msgid "FAC_THREADING = 0x00002000 (threading classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:285
+#, no-c-format
+msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:290
+#, no-c-format
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:295
+#, no-c-format
+msgid ""
+"To ensure appropriate output, it is necessary to set some of the finer debug "
+"properties explicitly in the <filename>CommonLogging.xml</filename> file, to "
+"enable logging messages issued by the ArjunaTA module."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:298
+#, no-c-format
+msgid ""
+"Messages describing the start and the periodical behavior made by the "
+"RecoveryManager are output using the INFO level. If other debug tracing is "
+"wanted, the finer debugging level should be set appropriately. For instance, "
+"the following configuration, in the <filename>CommonLogging.xml</filename>, "
+"enables all debug messages related to the Crash Recovery protocol and issued "
+"by the ArjunaTA module."
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:301
+#, no-c-format
+msgid ""
+"<!-- Common logging related properties. -->\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+" value=\"0x00000000\"/>\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+" value=\"0xffffffff\"/>\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+" value=\"0xffffffff\"/>"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:303
+#, no-c-format
+msgid ""
+"Two logger objects are provided, one manages I18N messages and a second does "
+"not."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:307
+#, no-c-format
+msgid ""
+"Setting the normal recovery messages to the INFO level allows the "
+"RecoveryManager producing a moderate level of reporting. If nothing is going "
+"on, it just reports the entry into each module for each periodic pass. To "
+"disable INFO messages produced by the Recovery Manager, the logging level "
+"could be set to the higher level: ERROR. Setting the level to ERROR means "
+"that the RecoveryManager will only produce error, warning or fatal messages."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:311
+#, no-c-format
+msgid "Periodic Recovery"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:312
+#, no-c-format
+msgid ""
+"The RecoveryManager scans the ObjectStore and other locations of "
+"information, looking for transactions and resources that require, or may "
+"require recovery. The scans and recovery processing are performed by "
+"recovery modules, (instances of classes that implement the com.arjuna.ats."
+"arjuna.recovery.RecoveryModule interface), each with responsibility for a "
+"particular category of transaction or resource. The set of recovery modules "
+"used are dynamically loaded, using properties found in the RecoveryManager "
+"property file."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:316
+#, no-c-format
+msgid ""
+"The interface has two methods: <methodname>periodicWorkFirstPass</"
+"methodname> and <methodname>periodicWorkSecondPass</methodname>. At an "
+"interval (defined by property <property>com.arjuna.ats.arjuna.recovery."
+"periodicRecoveryPeriod</property>), the RecoveryManager will call the first "
+"pass method on each property, then wait for a brief period (defined by "
+"property <property>com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</"
+"property>), then call the second pass of each module. Typically, in the "
+"first pass, the module scans (e.g. the relevant part of the ObjectStore) to "
+"find transactions or resources that are in-doubt (i.e. are part way through "
+"the commitment process). On the second pass, if any of the same items are "
+"still in-doubt, it is possible the original application process has crashed "
+"and the item is a candidate for recovery."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:319
+#, no-c-format
+msgid ""
+"An attempt, by the RecoveryManager, to recover a transaction that is still "
+"progressing in the original process(es) is likely to break the consistency. "
+"Accordingly, the recovery modules use a mechanism (implemented in the "
+"<package>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</package> "
+"package) to check to see if the original process is still alive, and if the "
+"transaction is still in progress. The RecoveryManager only proceeds with "
+"recovery if the original process has gone, or, if still alive, the "
+"transaction is completed. (If a server process or machine crashes, but the "
+"transaction-initiating process survives, the transaction will complete, "
+"usually generating a warning. Recovery of such a transaction is the "
+"RecoveryManager’s responsibility)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:322
+#, no-c-format
+msgid ""
+"It is clearly important to set the interval periods appropriately. The total "
+"iteration time will be the sum of the periodicRecoveryPeriod, "
+"recoveryBackoffPeriod and the length of time it takes to scan the stores and "
+"to attempt recovery of any in-doubt transactions found, for all the recovery "
+"modules. The recovery attempt time may include connection timeouts while "
+"trying to communicate with processes or machines that have crashed or are "
+"inaccessible (which is why there are mechanisms in the recovery system to "
+"avoid trying to recover the same transaction for ever). The total iteration "
+"time will affect how long a resource will remain inaccessible after a "
+"failure – periodicRecoveryPeriod should be set accordingly (default is 120 "
+"seconds). The recoveryBackoffPeriod can be comparatively short (default is "
+"10 seconds) – its purpose is mainly to reduce the number of transactions "
+"that are candidates for recovery and which thus require a call to the "
+"original process to see if they are still in progress."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:326
+#, no-c-format
+msgid ""
+"In previous versions of ArjunaCore there was no contact mechanism, and the "
+"backoff period had to be long enough to avoid catching transactions in "
+"flight at all. From 3.0, there is no such risk."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:330
+#, no-c-format
+msgid ""
+"Two recovery modules (implementations of the <interfacename>com.arjuna.ats."
+"arjuna.recovery.RecoveryModule</interfacename> interface) are supplied with "
+"ArjunaTA, supporting various aspects of transaction recovery including JDBC "
+"recovery. It is possible for advanced users to create their own recovery "
+"modules and register them with the Recovery Manager. The recovery modules "
+"are registered with the RecoveryManager using properties that begin with "
+"<property>com.arjuna.ats.arjuna.recovery.RecoveryExtension</property>. These "
+"will be invoked on each pass of the periodic recovery in the sort-order of "
+"the property names – it is thus possible to predict the ordering (but note "
+"that a failure in an application process might occur while a periodic "
+"recovery pass is in progress). The default Recovery Extension settings are:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:333
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = com.arjuna.ats.internal."
+"ts.arjuna.recovery.AtomicActionRecoveryModule\n"
+" \n"
+"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = com.arjuna.ats.txoj."
+"recovery.TORecoveryModule"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:335
+#, no-c-format
+msgid "Expired entry removal"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:336
+#, no-c-format
+msgid ""
+"The operation of the recovery subsystem will cause some entries to be made "
+"in the ObjectStore that will not be removed in normal progress. The "
+"RecoveryManager has a facility for scanning for these and removing items "
+"that are very old. Scans and removals are performed by implementations of "
+"the <interfacename>com.arjuna.ats.arjuna.recovery.ExpiryScanner</"
+"interfacename> interface. Implementations of this interface are loaded by "
+"giving the class name as the value of a property whose name begins with "
+"<property>com.arjuna.ats.arjuna.recovery.expiryScanner</property>. The "
+"RecoveryManager calls the <methodname>scan()</methodname> method on each "
+"loaded Expiry Scanner implementation at an interval determined by the "
+"property <property>com.arjuna.ats.arjuna.recovery.expiryScanInterval</"
+"property>. This value is given in hours – default is 12. An "
+"expiryScanInterval value of zero will suppress any expiry scanning. If the "
+"value as supplied is positive, the first scan is performed when "
+"RecoveryManager starts; if the value is negative, the first scan is delayed "
+"until after the first interval (using the absolute value)"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:340
+#, no-c-format
+msgid "The kinds of item that are scanned for expiry are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:343
+#, no-c-format
+msgid ""
+"TransactionStatusManager items : one of these is created by every "
+"application process that uses ArjunaCore – they contain the information that "
+"allows the RecoveryManager to determine if the process that initiated the "
+"transaction is still alive, and what the transaction status is. The expiry "
+"time for these is set by the property <property>com.arjuna.ats.arjuna."
+"recovery.transactionStatusManagerExpiryTime</property> (in hours – default "
+"is 12, zero means never expire). The expiry time should be greater than the "
+"lifetime of any single ArjunaTA-using process."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:346
+#, no-c-format
+msgid "The Expiry Scanner properties for these are:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:349
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager = com."
+"arjuna.ats.internal.ts.arjuna.recovery.ExpiredTransactionStatusManagerScanner"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:353
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:354
+#, no-c-format
+msgid ""
+"In this section we shall cover the types of errors and exceptions which may "
+"be thrown or reported during a transactional application and give probable "
+"indications of their causes."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:359
+#, no-c-format
+msgid ""
+"NO_MEMORY: the application has run out of memory (thrown an "
+"OutOfMemoryError) and ArjunaTA has attempted to do some cleanup (by running "
+"the garbage collector) before re-throwing the exception. This is probably a "
+"transient problem and retrying the invocation should succeed."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:364
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: an error has occurred which "
+"means that the transaction system must shut down. Prior to this error being "
+"thrown the transaction service will have ensured that all running "
+"transactions have rolled back. If caught, the application should tidy up and "
+"exit. If further work is attempted, application consistency may be violated."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:369
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: an attempt has been made to "
+"use the transaction service in a manner inconsistent with the current "
+"licence. The transaction service will not allow further forward progress for "
+"existing or new transactions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:374
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: an error occurred while "
+"the transaction service attempted to use the object store. Further forward "
+"progress is not possible."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:379
+#, no-c-format
+msgid ""
+"Object store warnings about access problems on states may occur during the "
+"normal execution of crash recovery. This is the result of multiple "
+"concurrent attempts to perform recovery on the same transaction. It can be "
+"safely ignored."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:387
+#, no-c-format
+msgid "Selecting the JTA implementation"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:388
+#, no-c-format
+msgid ""
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:393
+#, no-c-format
+msgid ""
+"A purely local JTA, which only allows non-distributed JTA transactions to be "
+"executed. This is the only version available with the ArjunaTA product."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:398
+#, no-c-format
+msgid ""
+"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
+"executed. This version is only available with the ArjunaJTS product and "
+"requires a supported CORBA ORB."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:404
+#, no-c-format
+msgid ""
+"Both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with ArjunaTA."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:408
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:413
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaTMImplementation</"
+"property> is set to <code>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"TransactionManagerImple</code>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:418
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaUTImplementation</"
+"property> is set to <code>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"UserTransactionImple</code>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:424
+#, no-c-format
+msgid ""
+"These settings are the default values for the properties and do not need to "
+"be specified if the local implementation is required."
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Author_Group.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,20 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Book_Info.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,44 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions JTA Administration Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the administration of Arjuna TA"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/JBoss_Transactions_JTA_Administration_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Preface.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,20 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/pt-BR/Revision_History.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,26 @@
+# Language pt-BR translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Administration_of_ArjunaTA.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Administration_of_ArjunaTA.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Administration_of_ArjunaTA.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,932 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Administration_of_ArjunaTA.xml:6
+#, no-c-format
+msgid "Administration of ArjunaTA"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:8
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:9
+#, no-c-format
+msgid ""
+"Apart from ensuring that the run-time system is executing normally, there is "
+"little continuous administration needed for the <firstterm>ArjunaTA</"
+"firstterm> software. There are a few points however, that should be made:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:14
+#, no-c-format
+msgid ""
+"The present implementation of the ArjunaTA system provides no security or "
+"protection for data. The objects stored in the ArjunaTA object store are "
+"(typically) owned by the user who ran the application that created them. The "
+"Object Store and Object Manager facilities make no attempt to enforce even "
+"the limited form of protection that Unix/Windows provides. There is no "
+"checking of user or group IDs on access to objects for either reading or "
+"writing."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:19
+#, no-c-format
+msgid ""
+"Persistent objects created in the Object Store never go away unless the "
+"<methodname>StateManager.destroy</methodname> method is invoked on the "
+"object or some application program explicitly deletes them. This means that "
+"the Object Store gradually accumulates garbage (especially during "
+"application development and testing phases). At present we have no automated "
+"garbage collection facility. Further, we have not addressed the problem of "
+"dangling references. That is, a persistent object, A, may have stored a Uid "
+"for another persistent object, B, in its passive representation on disk. "
+"There is nothing to prevent an application from deleting B even though A "
+"still contains a reference to it. When A is next activated and attempts to "
+"access B, a run-time error will occur."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:24
+#, no-c-format
+msgid ""
+"There is presently no support for version control of objects or database "
+"reconfiguration in the event of class structure changes. This is a complex "
+"research area that we have not addressed. At present, if you change the "
+"definition of a class of persistent objects, you are entirely responsible "
+"for ensuring that existing instances of the object in the Object Store are "
+"converted to the new representation. The ArjunaTA software can neither "
+"detect nor correct references to old object state by new operation versions "
+"or vice versa."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:29
+#, no-c-format
+msgid ""
+"Object store management is critically important to the transaction service."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:37
+#, no-c-format
+msgid "ObjectStore management"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:38
+#, no-c-format
+msgid ""
+"Within the transaction service installation, the object store is updated "
+"regularly whenever transactions are created, or when Transactional Objects "
+"for Java is used. In a failure free environment, the only object states "
+"which should reside within the object store are those representing objects "
+"created with the Transactional Objects for Java API. However, if failures "
+"occur, transaction logs may remain in the object store until crash recovery "
+"facilities have resolved the transactions they represent. As such it is very "
+"important that the contents of the object store are not deleted without due "
+"care and attention, as this will make it impossible to resolve in doubt "
+"transactions. In addition, if multiple users share the same object store it "
+"is important that they realise this and do not simply delete the contents of "
+"the object store assuming it is an exclusive resource."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:44
+#, no-c-format
+msgid "ArjunaTA runtime information"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:45
+#, no-c-format
+msgid ""
+"Each module that comprises ArjunaTA possesses a class called Info. These "
+"classes all provide a single toString method that returns an XML document "
+"representing the configuration information for that module. So, for example:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:48
+#, no-c-format
+msgid ""
+"<module-info name=\"arjuna\"><source-identifier>unknown</"
+"source-identifier><build-information>Arjuna Technologies [mlittle] "
+"(Windows 2000 5.0)</build-information><version>unknown</"
+"version><date>2002/06/15 04:06 PM</date><notes></"
+"notes><configuration><properties-file dir=\"null\">arjuna."
+"properties</properties-file><object-store-root>null</object-"
+"store-root></configuration></module-info>"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:52
+#, no-c-format
+msgid "Failure recovery administration"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:53
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of ArjunaTA will ensure that results of a "
+"transaction are applied consistently to all resources affected by the "
+"transaction, even if any of the application processes or the machine hosting "
+"them crash or lose network connectivity. In the case of machine (system) "
+"crash or network failure, the recovery will not take place until the system "
+"or network are restored, but the original application does not need to be "
+"restarted – recovery responsibility is delegated to the Recovery Manager "
+"process (see below). Recovery after failure requires that information about "
+"the transaction and the resources involved survives the failure and is "
+"accessible afterward: this information is held in the ActionStore, which is "
+"part of the ObjectStore."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:57
+#, no-c-format
+msgid ""
+"If the ObjectStore is destroyed or modified, recovery may not be possible."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:61
+#, no-c-format
+msgid ""
+"Until the recovery procedures are complete, resources affected by a "
+"transaction that was in progress at the time of the failure may be "
+"inaccessible. For database resources, this may be reported as tables or rows "
+"held by <emphasis>in-doubt transactions</emphasis>. For TransactionalObjects "
+"for Java resources, an attempt to activate the Transactional Object (as when "
+"trying to get a lock) will fail."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:65
+#, no-c-format
+msgid "The Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:66
+#, no-c-format
+msgid ""
+"The failure recovery subsystem of ArjunaTA requires that the stand-alone "
+"Recovery Manager process be running for each ObjectStore (typically one for "
+"each node on the network that is running ArjunaTA applications). The "
+"<filename>RecoveryManager</filename> file is located in the "
+"<filename>arjunacore</filename> jar file within the package <package>com."
+"arjuna.ats.arjuna.recovery.RecoveryManager</package>. To start the Recovery "
+"Manager issue the following command:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:70
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:71
+#, no-c-format
+msgid ""
+"If the -test flag is used with the Recovery Manager then it will display a "
+"<emphasis>Ready</emphasis> message when initialised, for instance:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:74
+#, no-c-format
+msgid "java com.arjuna.ats.arjuna.recovery.RecoveryManager -test"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:76
+#, no-c-format
+msgid "Configuring the Recovery Manager"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:77
+#, no-c-format
+msgid ""
+"The RecoveryManager reads the properties defined in the arjuna.properties "
+"file and then also reads the property file RecoveryManager.properties, from "
+"the same directory as it found the arjuna properties file. An entry for a "
+"property in the RecoveryManager properties file will override an entry for "
+"the same property in the main TransactionService properties file. Most of "
+"the entries are specific to the Recovery Manager."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:81
+#, no-c-format
+msgid ""
+"A default version of RecoveryManager.properties is supplied with the "
+"distribution – this can be used without modification, except possibly the "
+"debug tracing fields (see below, Output). The rest of this section discusses "
+"the issues relevant in setting the properties to other values (in the order "
+"of their appearance in the default version of the file)."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:85
+#, no-c-format
+msgid "Output"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:86
+#, no-c-format
+msgid ""
+"It is likely that installations will want to have some form of output from "
+"the RecoveryManager, to provide a record of what recovery activity has taken "
+"place. RecoveryManager uses the logging tracing mechanism provided by the "
+"Arjuna Common Logging Framework (CLF), which provides a high level interface "
+"that hides differences that exist between existing logging APIs such Jakarta "
+"log4j or JDK 1.4 logging API. CLF indirects all logging via the Apache "
+"Commons Logging framework and configuration is assumed to occur through that "
+"framework."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:90
+#, no-c-format
+msgid ""
+"With the CLF applications make logging calls on logger objects. Loggers may "
+"use logging Levels to decide if they are interested in a particular log "
+"message. Each log message has an associated log Level, that gives the "
+"importance and urgency of a log message. The set of possible Log Levels are "
+"DEBUG, INFO, WARN, ERROR and FATAL. Defined Levels are ordered according to "
+"their integer values as follows: DEBUG < INFO < WARN < ERROR < "
+"FATAL."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:93
+#, no-c-format
+msgid ""
+"The CLF provides an extension to filter logging messages according to finer "
+"granularity an application may define. That is, when a log message is "
+"provided to the logger with the DEBUG level, additional conditions can be "
+"specified to determine if the log message is enabled or not."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:97
+#, no-c-format
+msgid ""
+"These conditions are applied if and only the DEBUG level is enabled and the "
+"log request performed by the application specifies debugging granularity."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:101
+#, no-c-format
+msgid "When enabled, Debugging is filtered conditionally on three variables:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:106
+#, no-c-format
+msgid ""
+"Debugging level: this is where the log request with the DEBUG Level is "
+"generated from, for example, constructors or basic methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:111
+#, no-c-format
+msgid ""
+"Visibility level: the visibility of the constructor, method, etc. that "
+"generates the debugging."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:116
+#, no-c-format
+msgid ""
+"Facility code: for instance the package or sub-module within which debugging "
+"is generated, for example, the object store."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:121
+#, no-c-format
+msgid ""
+"According to these variables the CLF defines three interfaces. A particular "
+"product may implement its own classes according to its own finer "
+"granularity. ArjunaTA uses the default Debugging level and the default "
+"Visibility level provided by CLF, but it defines its own Facility Code. "
+"ArjunaTA uses the default level assigned to its logger objects (DEBUG). "
+"However, it uses the finer debugging features to disable or enable debug "
+"messages. Finer debugging values used by the ArjunaTA are defined below:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:124
+#, no-c-format
+msgid ""
+"Debugging level – ArjunaTA uses the default values defined in the class "
+"<classname>com.arjuna.common.util.logging.DebugLevel</classname>"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:129
+#, no-c-format
+msgid "NO_DEBUGGING: No diagnostics."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:132
+#, no-c-format
+msgid "A logger object assigned with this values discard all debug requests"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:137
+#, no-c-format
+msgid "FULL_DEBUGGING: Full diagnostics."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:140
+#, no-c-format
+msgid ""
+"A Logger object assigned with this value allows all debug requests if the "
+"facility code and the visibility level match those allowed by the logger."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:145
+#, no-c-format
+msgid "Additional Debugging Values are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:150
+#, no-c-format
+msgid "CONSTRUCTORS: Diagnostics from constructors."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:155
+#, no-c-format
+msgid "DESTRUCTORS: Diagnostics from finalizers."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:160
+#, no-c-format
+msgid "CONSTRUCT_AND_DESTRUCT: Diagnostics from constructors and finalizers."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:165
+#, no-c-format
+msgid "FUNCTIONS: Diagnostics from functions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:170
+#, no-c-format
+msgid "OPERATORS: Diagnostics from operators, such as equals."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:175
+#, no-c-format
+msgid "FUNCS_AND_OPS: Diagnostics from functions and operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:180
+#, no-c-format
+msgid "ALL_NON_TRIVIAL: Diagnostics from all non-trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:185
+#, no-c-format
+msgid "TRIVIAL_FUNCS: Diagnostics from trivial functions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:190
+#, no-c-format
+msgid "TRIVIAL_OPERATORS: Diagnostics from trivial operations, and operators."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:195
+#, no-c-format
+msgid "ALL_TRIVIAL: Diagnostics from all trivial operations."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:200
+#, no-c-format
+msgid ""
+"Visibility level – ArjunaTA uses the default values defined in the class "
+"<classname>com.arjuna.common.util.logging.VisibilityLevel</classname>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:205
+#, no-c-format
+msgid "VIS_NONE: No Diagnostic"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:210
+#, no-c-format
+msgid "VIS_PRIVATE: Only from private methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:215
+#, no-c-format
+msgid "VIS_PROTECTED: Only from protected methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:220
+#, no-c-format
+msgid "VIS_PUBLIC: Only from public methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:225
+#, no-c-format
+msgid "VIS_: only from package methods."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:230
+#, no-c-format
+msgid "VIS_ALL: Full Diagnostic ."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:235
+#, no-c-format
+msgid ""
+"Facility Code – ArjunaTA uses the following values defined in the class "
+"<classname>com.arjuna.common.util.logging.VisibilityLevel</classname>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:240
+#, no-c-format
+msgid "FAC_ATOMIC_ACTION = 0x0000001 (atomic action core module)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:245
+#, no-c-format
+msgid "FAC_BUFFER_MAN = 0x00000004 (state management (buffer) classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:250
+#, no-c-format
+msgid "FAC_ABSTRACT_REC = 0x00000008 (abstract records)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:255
+#, no-c-format
+msgid "FAC_OBJECT_STORE = 0x00000010 (object store implementations)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:260
+#, no-c-format
+msgid "FAC_STATE_MAN = 0x00000020 (state management and StateManager)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:265
+#, no-c-format
+msgid "FAC_SHMEM = 0x00000040 (shared memory implementation classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:270
+#, no-c-format
+msgid "FAC_GENERAL = 0x00000080 (general classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:275
+#, no-c-format
+msgid ""
+"FAC_CRASH_RECOVERY = 0x00000800 (detailed trace of crash recovery module and "
+"classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:280
+#, no-c-format
+msgid "FAC_THREADING = 0x00002000 (threading classes)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:285
+#, no-c-format
+msgid "AC_JDBC = 0x00008000 (JDBC 1.0 and 2.0 support)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:290
+#, no-c-format
+msgid ""
+"FAC_RECOVERY_NORMAL = 0x00040000 (normal output for crash recovery manager)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:295
+#, no-c-format
+msgid ""
+"To ensure appropriate output, it is necessary to set some of the finer debug "
+"properties explicitly in the <filename>CommonLogging.xml</filename> file, to "
+"enable logging messages issued by the ArjunaTA module."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:298
+#, no-c-format
+msgid ""
+"Messages describing the start and the periodical behavior made by the "
+"RecoveryManager are output using the INFO level. If other debug tracing is "
+"wanted, the finer debugging level should be set appropriately. For instance, "
+"the following configuration, in the <filename>CommonLogging.xml</filename>, "
+"enables all debug messages related to the Crash Recovery protocol and issued "
+"by the ArjunaTA module."
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:301
+#, no-c-format
+msgid ""
+"<!-- Common logging related properties. -->\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.DebugLevel\"\n"
+" value=\"0x00000000\"/>\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.FacilityLevel\"\n"
+" value=\"0xffffffff\"/>\n"
+" <property\n"
+" name=\"com.arjuna.common.util.logging.VisibilityLevel\"\n"
+" value=\"0xffffffff\"/>"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:303
+#, no-c-format
+msgid ""
+"Two logger objects are provided, one manages I18N messages and a second does "
+"not."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:307
+#, no-c-format
+msgid ""
+"Setting the normal recovery messages to the INFO level allows the "
+"RecoveryManager producing a moderate level of reporting. If nothing is going "
+"on, it just reports the entry into each module for each periodic pass. To "
+"disable INFO messages produced by the Recovery Manager, the logging level "
+"could be set to the higher level: ERROR. Setting the level to ERROR means "
+"that the RecoveryManager will only produce error, warning or fatal messages."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:311
+#, no-c-format
+msgid "Periodic Recovery"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:312
+#, no-c-format
+msgid ""
+"The RecoveryManager scans the ObjectStore and other locations of "
+"information, looking for transactions and resources that require, or may "
+"require recovery. The scans and recovery processing are performed by "
+"recovery modules, (instances of classes that implement the com.arjuna.ats."
+"arjuna.recovery.RecoveryModule interface), each with responsibility for a "
+"particular category of transaction or resource. The set of recovery modules "
+"used are dynamically loaded, using properties found in the RecoveryManager "
+"property file."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:316
+#, no-c-format
+msgid ""
+"The interface has two methods: <methodname>periodicWorkFirstPass</"
+"methodname> and <methodname>periodicWorkSecondPass</methodname>. At an "
+"interval (defined by property <property>com.arjuna.ats.arjuna.recovery."
+"periodicRecoveryPeriod</property>), the RecoveryManager will call the first "
+"pass method on each property, then wait for a brief period (defined by "
+"property <property>com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod</"
+"property>), then call the second pass of each module. Typically, in the "
+"first pass, the module scans (e.g. the relevant part of the ObjectStore) to "
+"find transactions or resources that are in-doubt (i.e. are part way through "
+"the commitment process). On the second pass, if any of the same items are "
+"still in-doubt, it is possible the original application process has crashed "
+"and the item is a candidate for recovery."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:319
+#, no-c-format
+msgid ""
+"An attempt, by the RecoveryManager, to recover a transaction that is still "
+"progressing in the original process(es) is likely to break the consistency. "
+"Accordingly, the recovery modules use a mechanism (implemented in the "
+"<package>com.arjuna.ats.arjuna.recovery.TransactionStatusManager</package> "
+"package) to check to see if the original process is still alive, and if the "
+"transaction is still in progress. The RecoveryManager only proceeds with "
+"recovery if the original process has gone, or, if still alive, the "
+"transaction is completed. (If a server process or machine crashes, but the "
+"transaction-initiating process survives, the transaction will complete, "
+"usually generating a warning. Recovery of such a transaction is the "
+"RecoveryManager’s responsibility)."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:322
+#, no-c-format
+msgid ""
+"It is clearly important to set the interval periods appropriately. The total "
+"iteration time will be the sum of the periodicRecoveryPeriod, "
+"recoveryBackoffPeriod and the length of time it takes to scan the stores and "
+"to attempt recovery of any in-doubt transactions found, for all the recovery "
+"modules. The recovery attempt time may include connection timeouts while "
+"trying to communicate with processes or machines that have crashed or are "
+"inaccessible (which is why there are mechanisms in the recovery system to "
+"avoid trying to recover the same transaction for ever). The total iteration "
+"time will affect how long a resource will remain inaccessible after a "
+"failure – periodicRecoveryPeriod should be set accordingly (default is 120 "
+"seconds). The recoveryBackoffPeriod can be comparatively short (default is "
+"10 seconds) – its purpose is mainly to reduce the number of transactions "
+"that are candidates for recovery and which thus require a call to the "
+"original process to see if they are still in progress."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:326
+#, no-c-format
+msgid ""
+"In previous versions of ArjunaCore there was no contact mechanism, and the "
+"backoff period had to be long enough to avoid catching transactions in "
+"flight at all. From 3.0, there is no such risk."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:330
+#, no-c-format
+msgid ""
+"Two recovery modules (implementations of the <interfacename>com.arjuna.ats."
+"arjuna.recovery.RecoveryModule</interfacename> interface) are supplied with "
+"ArjunaTA, supporting various aspects of transaction recovery including JDBC "
+"recovery. It is possible for advanced users to create their own recovery "
+"modules and register them with the Recovery Manager. The recovery modules "
+"are registered with the RecoveryManager using properties that begin with "
+"<property>com.arjuna.ats.arjuna.recovery.RecoveryExtension</property>. These "
+"will be invoked on each pass of the periodic recovery in the sort-order of "
+"the property names – it is thus possible to predict the ordering (but note "
+"that a failure in an application process might occur while a periodic "
+"recovery pass is in progress). The default Recovery Extension settings are:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:333
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.recoveryExtension1 = com.arjuna.ats.internal."
+"ts.arjuna.recovery.AtomicActionRecoveryModule\n"
+" \n"
+"com.arjuna.ats.arjuna.recovery.recoveryExtension2 = com.arjuna.ats.txoj."
+"recovery.TORecoveryModule"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:335
+#, no-c-format
+msgid "Expired entry removal"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:336
+#, no-c-format
+msgid ""
+"The operation of the recovery subsystem will cause some entries to be made "
+"in the ObjectStore that will not be removed in normal progress. The "
+"RecoveryManager has a facility for scanning for these and removing items "
+"that are very old. Scans and removals are performed by implementations of "
+"the <interfacename>com.arjuna.ats.arjuna.recovery.ExpiryScanner</"
+"interfacename> interface. Implementations of this interface are loaded by "
+"giving the class name as the value of a property whose name begins with "
+"<property>com.arjuna.ats.arjuna.recovery.expiryScanner</property>. The "
+"RecoveryManager calls the <methodname>scan()</methodname> method on each "
+"loaded Expiry Scanner implementation at an interval determined by the "
+"property <property>com.arjuna.ats.arjuna.recovery.expiryScanInterval</"
+"property>. This value is given in hours – default is 12. An "
+"expiryScanInterval value of zero will suppress any expiry scanning. If the "
+"value as supplied is positive, the first scan is performed when "
+"RecoveryManager starts; if the value is negative, the first scan is delayed "
+"until after the first interval (using the absolute value)"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:340
+#, no-c-format
+msgid "The kinds of item that are scanned for expiry are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:343
+#, no-c-format
+msgid ""
+"TransactionStatusManager items : one of these is created by every "
+"application process that uses ArjunaCore – they contain the information that "
+"allows the RecoveryManager to determine if the process that initiated the "
+"transaction is still alive, and what the transaction status is. The expiry "
+"time for these is set by the property <property>com.arjuna.ats.arjuna."
+"recovery.transactionStatusManagerExpiryTime</property> (in hours – default "
+"is 12, zero means never expire). The expiry time should be greater than the "
+"lifetime of any single ArjunaTA-using process."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:346
+#, no-c-format
+msgid "The Expiry Scanner properties for these are:"
+msgstr ""
+
+#. Tag: screen
+#: Administration_of_ArjunaTA.xml:349
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager = com."
+"arjuna.ats.internal.ts.arjuna.recovery.ExpiredTransactionStatusManagerScanner"
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:353
+#, no-c-format
+msgid "Errors and Exceptions"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:354
+#, no-c-format
+msgid ""
+"In this section we shall cover the types of errors and exceptions which may "
+"be thrown or reported during a transactional application and give probable "
+"indications of their causes."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:359
+#, no-c-format
+msgid ""
+"NO_MEMORY: the application has run out of memory (thrown an "
+"OutOfMemoryError) and ArjunaTA has attempted to do some cleanup (by running "
+"the garbage collector) before re-throwing the exception. This is probably a "
+"transient problem and retrying the invocation should succeed."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:364
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.FatalError: an error has occurred which "
+"means that the transaction system must shut down. Prior to this error being "
+"thrown the transaction service will have ensured that all running "
+"transactions have rolled back. If caught, the application should tidy up and "
+"exit. If further work is attempted, application consistency may be violated."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:369
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.LicenceError: an attempt has been made to "
+"use the transaction service in a manner inconsistent with the current "
+"licence. The transaction service will not allow further forward progress for "
+"existing or new transactions."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:374
+#, no-c-format
+msgid ""
+"com.arjuna.ats.arjuna.exceptions.ObjectStoreError: an error occurred while "
+"the transaction service attempted to use the object store. Further forward "
+"progress is not possible."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:379
+#, no-c-format
+msgid ""
+"Object store warnings about access problems on states may occur during the "
+"normal execution of crash recovery. This is the result of multiple "
+"concurrent attempts to perform recovery on the same transaction. It can be "
+"safely ignored."
+msgstr ""
+
+#. Tag: title
+#: Administration_of_ArjunaTA.xml:387
+#, no-c-format
+msgid "Selecting the JTA implementation"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:388
+#, no-c-format
+msgid ""
+"Two variants of the JTA implementation are now provided and accessible "
+"through the same interface. These are:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:393
+#, no-c-format
+msgid ""
+"A purely local JTA, which only allows non-distributed JTA transactions to be "
+"executed. This is the only version available with the ArjunaTA product."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:398
+#, no-c-format
+msgid ""
+"A remote, CORBA-based JTA, which allows distributed JTA transactions to be "
+"executed. This version is only available with the ArjunaJTS product and "
+"requires a supported CORBA ORB."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:404
+#, no-c-format
+msgid ""
+"Both of these implementations are fully compatible with the transactional "
+"JDBC driver provided with ArjunaTA."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:408
+#, no-c-format
+msgid ""
+"In order to select the local JTA implementation it is necessary to perform "
+"the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:413
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaTMImplementation</"
+"property> is set to <code>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"TransactionManagerImple</code>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:418
+#, no-c-format
+msgid ""
+"make sure the property <property>com.arjuna.ats.jta.jtaUTImplementation</"
+"property> is set to <code>com.arjuna.ats.internal.jta.transaction.arjunacore."
+"UserTransactionImple</code>."
+msgstr ""
+
+#. Tag: para
+#: Administration_of_ArjunaTA.xml:424
+#, no-c-format
+msgid ""
+"These settings are the default values for the properties and do not need to "
+"be specified if the local implementation is required."
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Author_Group.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,20 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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: corpauthor
+#: Author_Group.xml:6
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Book_Info.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,44 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Transactions JTA Administration Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 4.3"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:13
+#, no-c-format
+msgid "This book is about the administration of Arjuna TA"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:20
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:26
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/JBoss_Transactions_JTA_Administration_Guide.po
===================================================================
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Preface.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Preface.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Preface.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,20 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3/Transactions/Transactions_JTA_Administration_Guide/zh-CN/Revision_History.po 2008-09-23 06:24:15 UTC (rev 78766)
@@ -0,0 +1,26 @@
+# Language zh-CN translations for package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2008-09-23 06:22+0000\n"
+"PO-Revision-Date: 2008-09-23 06:22+0000\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
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""
More information about the jboss-cvs-commits
mailing list