[jboss-cvs] JBossAS SVN: r95460 - in projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3: pot and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Oct 22 23:44:10 EDT 2009
Author: benlc
Date: 2009-10-22 23:44:09 -0400 (Thu, 22 Oct 2009)
New Revision: 95460
Added:
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/About.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Author_Group.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Book_Info.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Bridge.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/C_Configuration.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Configuration.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Getting_Started.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Installation.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Introduction.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/JBoss_Messaging_User_Guide.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Ordering_Group.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Preface.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Recovery_Configuration.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Revision_History.pot
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Running_Examples.pot
Log:
'committing Messaging pot files"
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/About.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/About.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/About.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,56 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: About.xml:3
+#, no-c-format
+msgid "About JBoss Messaging 1.4"
+msgstr ""
+
+#. Tag: para
+#: About.xml:5
+#, no-c-format
+msgid ""
+"JBoss Messaging is the new enterprise messaging system from JBoss. It is a "
+"complete rewrite of JBossMQ, the legacy JBoss Java Message Service (JMS) "
+"provider."
+msgstr ""
+
+#. Tag: para
+#: About.xml:9
+#, no-c-format
+msgid ""
+"JBoss Messaging is the default JMS provider in JBoss Enterprise Application "
+"Platform version 4.3 or later."
+msgstr ""
+
+#. Tag: para
+#: About.xml:13
+#, no-c-format
+msgid ""
+"JBoss Messaging is integral to Red Hat's messaging strategy. It offers "
+"improvements to performance in both single node and clustered environments, "
+"and features a modular architecture so that we can easily add more features "
+"in the future."
+msgstr ""
+
+#. Tag: para
+#: About.xml:17
+#, no-c-format
+msgid ""
+"This guide shows you how to install, set up, and configure JBoss Messaging "
+"for JBoss Enterprise Application Platform."
+msgstr ""
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Author_Group.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Author_Group.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Author_Group.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,21 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: author
+#: Author_Group.xml:6
+#, no-c-format
+msgid "<firstname>Red Hat Documentation Group</firstname> <surname></surname>"
+msgstr ""
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Book_Info.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Book_Info.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Book_Info.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,47 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Book_Info.xml:6
+#, no-c-format
+msgid "JBoss Messaging User Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform 5.0"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:14
+#, no-c-format
+msgid ""
+"The JBoss Enterprise Application Platform Edition of the JBoss Messaging "
+"version 1.4.3 User Guide."
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:23
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:28
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Bridge.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Bridge.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Bridge.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,665 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Bridge.xml:3
+#, no-c-format
+msgid "JBoss Messaging Message Bridge Configuration"
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:6
+#, no-c-format
+msgid "Message Bridge Overview"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:8
+#, no-c-format
+msgid "JBoss Messaging includes a fully functional message bridge."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:12
+#, no-c-format
+msgid ""
+"The bridge consumes messages from a source queue or topic and sends them to "
+"a target queue or topic, typically on a different server. The source and "
+"target servers need not be in the same cluster, so bridging is a reliable "
+"method of sending messages from one cluster to another (across a WAN, for "
+"example) and where the connection may be unreliable."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:16
+#, no-c-format
+msgid ""
+"A bridge is deployed as a managed bean within any JBoss Application Server "
+"instance. To deploy, simply add the managed bean descriptor into the "
+"<filename>deploy</filename> directory of an Enterprise Application Platform "
+"configuration that contains JBoss Messaging."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:20
+#, no-c-format
+msgid ""
+"The example in <filename>/doc/examples/jboss-messaging-examples/bridge/</"
+"filename> demonstrates a simple bridge deployed in JBoss Application Server "
+"and moving messages from the source to the target destination."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:24
+#, no-c-format
+msgid ""
+"The bridge can also be used to retrieve messages from other non-JBoss "
+"Messaging JMS servers as long as they are JMS 1.1 compliant."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:28
+#, no-c-format
+msgid ""
+"The bridge has built-in resistence to failure, so if the source or target "
+"server connection is lost, the bridge will attempt to reconnect to the "
+"source or target until it comes back online, at which point normal operation "
+"will resume."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:32
+#, no-c-format
+msgid ""
+"The bridge can be configured to consume messages matching a particular JMS "
+"selector."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:36
+#, no-c-format
+msgid ""
+"It can be configured to consume from a queue or a topic. When the bridge "
+"consumes from a topic, it can be configured to consume with a non-durable or "
+"a durable subscription."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:40
+#, no-c-format
+msgid ""
+"The bridge can be configured to bridge messages with one of three "
+"<emphasis>quality of service</emphasis> levels:"
+msgstr ""
+
+#. Tag: literal
+#: Bridge.xml:46
+#, no-c-format
+msgid "QOS_AT_MOST_ONCE"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:48
+#, no-c-format
+msgid ""
+"This mode specifies that messages will arrive at the destination once at the "
+"most. Messages are consumed from the source and acknowledged before they are "
+"sent to the destination. Therefore, if failure occurs between the message "
+"leaving the source and arriving at the destination, messages can be lost. "
+"Messages will therefore be delivered once at most. This mode is available "
+"for both persistent and non-persistent messages."
+msgstr ""
+
+#. Tag: literal
+#: Bridge.xml:54
+#, no-c-format
+msgid "QOS_DUPLICATES_OK"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:56
+#, no-c-format
+msgid ""
+"This mode specifies that messages are consumed from the source and "
+"acknowledged after they have been successfully sent to the destination. "
+"Therefore, if failure occurs between a message arriving at the destination "
+"and being acknowledged by the destination, that message may be sent a second "
+"time when the system recovers, so the destination may receive duplicate "
+"messages. This mode is available for both persistent and non-persistent "
+"messages."
+msgstr ""
+
+#. Tag: literal
+#: Bridge.xml:62
+#, no-c-format
+msgid "QOS_ONCE_AND_ONLY_ONCE"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:64
+#, no-c-format
+msgid ""
+"This mode specifies that messages will arrive exactly once. When the message "
+"source and destination are on the same JBoss Messaging server instance, the "
+"message can be sent and received in the same local transaction. If the "
+"source and destination are on different servers, you can enlist the sending "
+"and consuming sessions in a JTA transaction controlled by JBoss Transactions "
+"JTA implementation, which provides high durability. If JTA is required, both "
+"connection factories must be <literal>XAConnectionFactory</literal> "
+"implementations."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:67
+#, no-c-format
+msgid "This mode is only available for persistent messages."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:70
+#, no-c-format
+msgid ""
+"Because this mode requires logging on both the transaction manager and the "
+"resource side to support recovery, it will likely be the slowest mode. If "
+"you require this level of quality of service, you must enable XA Recovery "
+"with JBoss Transactions."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:74
+#, no-c-format
+msgid "Alternative Methods"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:75
+#, no-c-format
+msgid ""
+"You may be able to apply <emphasis>once and only once</emphasis> semantics "
+"to a specific application without setting <literal>QOS_ONCE_AND_ONLY_ONCE</"
+"literal>. Set <literal>QOS_DUPLICATES_OK</literal> mode, and then check for "
+"and discard duplicate messages at the destination. You may be able to "
+"implement this at the application level by maintaining a cache of received "
+"message IDs on disk and comparing received messages to this cache. Since the "
+"cache would only be valid for a certain period of time, this approach is not "
+"infallible, but can be a useful alternative depending on your application."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:84
+#, no-c-format
+msgid "Bridge deployment"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:86
+#, no-c-format
+msgid ""
+"You can deploy a message bridge by adding a managed bean descriptor into the "
+"<filename>deploy</filename> directory of the JBoss Application Server "
+"installation that contains JBoss Messaging."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:92
+#, no-c-format
+msgid "Bridge Configuration"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:94
+#, no-c-format
+msgid "This section shows you how to configure the message bridge."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:97
+#, no-c-format
+msgid ""
+"The following code is an example configuration of the message bridge, "
+"showing all attributes. Some attributes have been commented out for this "
+"configuration, since not all attributes should be specified at once."
+msgstr ""
+
+#. Tag: programlisting
+#: Bridge.xml:101
+#, no-c-format
+msgid ""
+"<![CDATA[\n"
+"<mbean code=\"org.jboss.jms.server.bridge.BridgeService\"\n"
+" name=\"jboss.messaging:service=Bridge,name=TestBridge\"\n"
+" xmbean-dd=\"xmdesc/Bridge-xmbean.xml\">\n"
+" \n"
+" <!-- The JMS provider loader that is used to lookup the source \n"
+" destination \n"
+" --> \n"
+" <depends optional-attribute-name=\"SourceProviderLoader\">\n"
+" jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>\n"
+" \n"
+" <!-- The JMS provider loader that is used to lookup the target \n"
+" destination \n"
+" -->\n"
+" <depends optional-attribute-name=\"TargetProviderLoader\">\n"
+" jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends> \n"
+" \n"
+" <!-- The JNDI lookup for the source destination -->\n"
+" <attribute name=\"SourceDestinationLookup\">/queue/A</attribute> \n"
+" \n"
+" <!-- The JNDI lookup for the target destination -->\n"
+" <attribute name=\"TargetDestinationLookup\">/queue/B</attribute>\n"
+" \n"
+" <!-- The username to use for the source connection \n"
+" <attribute name=\"SourceUsername\">bob</attribute>\n"
+" -->\n"
+" \n"
+" <!-- The password to use for the source connection\n"
+" <attribute name=\"SourcePassword\">cheesecake</attribute>\n"
+" -->\n"
+" \n"
+" <!-- The username to use for the target connection\n"
+" <attribute name=\"TargetUsername\">mary</attribute>\n"
+" -->\n"
+" \n"
+" <!-- The password to use for the target connection\n"
+" <attribute name=\"TargetPassword\">hotdog</attribute>\n"
+" -->\n"
+" \n"
+" <!-- Optional: The Quality Of Service mode to use, one of:\n"
+" QOS_AT_MOST_ONCE = 0;\n"
+" QOS_DUPLICATES_OK = 1;\n"
+" QOS_ONCE_AND_ONLY_ONCE = 2; \n"
+" -->\n"
+" <attribute name=\"QualityOfServiceMode\">0</attribute>\n"
+" \n"
+" <!-- JMS selector to use for consuming messages from the source\n"
+" <attribute name=\"Selector\">specify jms selector here</attribute>\n"
+" -->\n"
+" \n"
+" <!-- The maximum number of messages to consume from the source\n"
+" before sending to the target \n"
+" -->\n"
+" <attribute name=\"MaxBatchSize\">5</attribute> \n"
+" \n"
+" <!-- The maximum time to wait (in ms) before sending a batch to the\n"
+" target even if MaxBatchSize is not exceeded. -1 means wait forever \n"
+" --> \n"
+" <attribute name=\"MaxBatchTime\">-1</attribute>\n"
+" \n"
+" <!-- If consuming from a durable subscription this is the subscription\n"
+" name\n"
+" <attribute name=\"SubName\">mysub</attribute>\n"
+" -->\n"
+" \n"
+" <!-- If consuming from a durable subscription this is the client ID to\n"
+" use\n"
+" <attribute name=\"ClientID\">myClientID</attribute>\n"
+" -->\n"
+" \n"
+" <!-- The number of ms to wait between connection retrues in the event\n"
+" connections to source or target fail \n"
+" -->\n"
+" <attribute name=\"FailureRetryInterval\">5000</attribute> \n"
+" \n"
+" <!-- The maximum number of connection retries to make in case of failure,\n"
+" before giving up -1 means try forever\n"
+" -->\n"
+" <attribute name=\"MaxRetries\">-1</attribute>\n"
+"\n"
+" <!-- If true then the message ID of the message before bridging will be\n"
+" added as a header to the message so it is available to the \n"
+" receiver. Can then be sent as correlation ID to correlate in a \n"
+" distributed request-response \n"
+" -->\n"
+" <attribute name=\"AddMessageIDInHeader\">false</attribute>\n"
+" \n"
+" </mbean>\n"
+"]]>"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:103
+#, no-c-format
+msgid "The next section discusses these attributes in detail."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:108
+#, no-c-format
+msgid "SourceProviderLoader"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:110
+#, no-c-format
+msgid ""
+"The <literal>JMSProviderLoader</literal> managed bean that the bridge uses "
+"to look up the source connection factory and source destination. By default, "
+"JBoss Application Server ships with one <literal>JMSProviderLoader</"
+"literal>, which is deployed in the <filename>jms-ds.xml</filename> file, and "
+"serves as the default local <literal>JMSProviderLoader</literal>. (A "
+"clustered configuration would use <filename>hajndi-jms-ds.xml</filename>.)"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:113
+#, no-c-format
+msgid ""
+"If your source destination is on a different server, or corresponds to a non-"
+"JBoss JMS Provider, you can deploy another <literal>JMSProviderLoader</"
+"literal> managed bean instance that refers to the remote JMS Provider, and "
+"refer to that destination from the second <literal>JMSProviderLoader</"
+"literal>. The bridge then uses the remote JMS Provider to contact the source "
+"destination."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:116 Bridge.xml:130
+#, no-c-format
+msgid ""
+"If you want to use <emphasis>once and only once</emphasis> delivery and you "
+"are using a remote non-JBoss Messaging source or target, the remote JMS "
+"Provider must provide a fully-functional JMS XA resource implementation that "
+"works remotely from the server."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:122
+#, no-c-format
+msgid "TargetProviderLoader"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:124
+#, no-c-format
+msgid ""
+"The <literal>JMSProviderLoader</literal> managed bean used by the bridge to "
+"lookup the target connection factory and target destination. By default, "
+"JBoss Application Server ships with one <literal>JMSProviderLoader</"
+"literal>, which is deployed in the <filename>jms-ds.xml</filename> file, and "
+"serves as the default local <literal>JMSProviderLoader</literal>. (A "
+"clustered configuration would use <filename>hajndi-jms-ds.xml</filename>.)"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:127
+#, no-c-format
+msgid ""
+"If your target destination is on a different server, or corresponds to a non-"
+"JBoss JMS Provider, you can deploy another <literal>JMSProviderLoader</"
+"literal> managed bean instance that refers to the remote JMS Provider, and "
+"refer to that destination from the second <literal>JMSProviderLoader</"
+"literal>. The bridge then uses the remote JMS Provider to contact the target "
+"destination."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:136
+#, no-c-format
+msgid "SourceDestinationLookup"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:138
+#, no-c-format
+msgid ""
+"The full JNDI lookup for the source destination, via the "
+"<literal>SourceProviderLoader</literal>, such as <filename>/queue/"
+"mySourceQueue</filename>."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:144
+#, no-c-format
+msgid "TargetDestinationLookup"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:146
+#, no-c-format
+msgid ""
+"The full JNDI lookup for the target destination, via the "
+"<literal>TargetProviderLocator</literal>, such as <filename>/topic/"
+"myTargetTopic</filename>."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:152
+#, no-c-format
+msgid "SourceUsername"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:154
+#, no-c-format
+msgid ""
+"An optional attribute that specifies the username used when creating the "
+"source connection."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:160
+#, no-c-format
+msgid "SourcePassword"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:162
+#, no-c-format
+msgid ""
+"An optional attribute that specifies the password used when creating the "
+"source connection."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:168
+#, no-c-format
+msgid "TargetUsername"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:170
+#, no-c-format
+msgid ""
+"An optional attribute that specifies the username used when creating the "
+"raget connection."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:176
+#, no-c-format
+msgid "TargetPassword"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:178
+#, no-c-format
+msgid ""
+"An optional attribute that specifies the password used when creating the "
+"target connection."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:184
+#, no-c-format
+msgid "QualityOfServiceMode"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:186
+#, no-c-format
+msgid ""
+"An integer representing the desired <emphasis>quality of service</emphasis> "
+"mode. The possible values are:"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:191
+#, no-c-format
+msgid "<literal>0</literal> to represent <literal>QOS_AT_MOST_ONCE</literal>"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:196
+#, no-c-format
+msgid "<literal>1</literal> to represent <literal>QOS_DUPLICATES_OK</literal>"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:201
+#, no-c-format
+msgid ""
+"<literal>2</literal> to represent <literal>QOS_ONCE_AND_ONLY_ONCE</literal>"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:206
+#, no-c-format
+msgid ""
+"See <xref linkend=\"bridge.overview\"/> for a complete explanation of these "
+"modes."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:212
+#, no-c-format
+msgid "Selector"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:214
+#, no-c-format
+msgid ""
+"An optional attribute that lets you provide a JMS selector expression when "
+"consuming messages from a source destination. Only messages that match the "
+"selector expression are bridged from the source to the target destination. "
+"The selector expression must follow the JMS selector syntax, specified here: "
+"<ulink url=\"http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html"
+"\"></ulink>."
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:217
+#, no-c-format
+msgid ""
+"For optimal performance, apply source topic subscription selectors to source "
+"queue consumers."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:223
+#, no-c-format
+msgid "MaxBatchSize"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:225
+#, no-c-format
+msgid ""
+"Specifies the maximum number of messages to consume from the source "
+"destination before sending a message batch to the target destination. Its "
+"value must be greater than or equal to <literal>1</literal>."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:231
+#, no-c-format
+msgid "MaxBatchTime"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:233
+#, no-c-format
+msgid ""
+"Specifies the longest period (in milliseconds) to wait before sending a "
+"message batch to the target, even if the <varname>MaxBatchSize</varname> has "
+"not been reached. Its value must be either <literal>-1</literal> (wait "
+"forever) or greater than or equal to <literal>1</literal> to specify a time."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:239
+#, no-c-format
+msgid "SubName"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:241
+#, no-c-format
+msgid ""
+"Represents the name of the durable subscription that will consume from the "
+"source destination topic."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:247
+#, no-c-format
+msgid "ClientID"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:249
+#, no-c-format
+msgid ""
+"Represents the JMS client ID to use when creating or looking up the durable "
+"subscription that will consume from the source destination topic."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:255
+#, no-c-format
+msgid "FailureRetryInterval"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:257
+#, no-c-format
+msgid ""
+"The period of time (in milliseconds) to wait between attempting to recreate "
+"the connection to the source or target server after failure is detected."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:263
+#, no-c-format
+msgid "MaxRetries"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:265
+#, no-c-format
+msgid ""
+"The number of times to attempt to recreate the connection to the source or "
+"target server after failure is detected. The bridge will then stop "
+"attempting to recreate the connection. A value of <literal>-1</literal> "
+"means that the bridge will continue to attempt to reconnect forever."
+msgstr ""
+
+#. Tag: title
+#: Bridge.xml:271
+#, no-c-format
+msgid "AddMessageIDInHeader"
+msgstr ""
+
+#. Tag: para
+#: Bridge.xml:273
+#, no-c-format
+msgid ""
+"When <literal>true</literal>, the original message ID is added to the "
+"<literal>JBossMessage.JBOSS_MESSAGING_BRIDGE_MESSAGE_ID_LIST</literal> "
+"header of the message being sent to the destination. If the message is "
+"bridged multiple times, each message ID is added to the header. This enables "
+"a distributed request-response pattern."
+msgstr ""
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/C_Configuration.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/C_Configuration.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/C_Configuration.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,223 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: C_Configuration.xml:3
+#, no-c-format
+msgid "JBoss Messaging Clustering Notes"
+msgstr ""
+
+#. Tag: title
+#: C_Configuration.xml:6
+#, no-c-format
+msgid "Unique server peer id"
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:8
+#, no-c-format
+msgid ""
+"In most cases, JBoss Messaging works in a clustered environment with no "
+"configuration changes. However, it is crucial that every node is assigned a "
+"unique server ID, as specified in the Installation Guide."
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:11
+#, no-c-format
+msgid ""
+"Every deployed node must have a unique ID, including nodes that form a LAN "
+"cluster and nodes linked by message bridges."
+msgstr ""
+
+#. Tag: title
+#: C_Configuration.xml:17
+#, no-c-format
+msgid "Clustered destinations"
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:19
+#, no-c-format
+msgid ""
+"JBoss Messaging clusters Java Message Service (JMS) queues and topics "
+"transparently across the cluster. Messages sent to a distributed queue or "
+"topic on one node are consumable on other nodes. To make a particular "
+"destination clustered, set the <varname>clustered</varname> attribute in the "
+"destination Deployment Descriptor to <literal>true</literal>."
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:22
+#, no-c-format
+msgid ""
+"JBoss Messaging balances messages between nodes and caters for consumers of "
+"varying speeds so that processing load is distributed efficiently across the "
+"cluster."
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:26
+#, no-c-format
+msgid ""
+"To disable message redistribution between nodes while retaining other "
+"characteristics of clustered destinations, do not specify the "
+"<varname>ClusterPullConnectionFactoryName</varname> attribute on the Server "
+"Peer."
+msgstr ""
+
+#. Tag: title
+#: C_Configuration.xml:32
+#, no-c-format
+msgid "Clustered durable subscriptions"
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:34
+#, no-c-format
+msgid ""
+"It is also possible to cluster JBoss Messaging durable subscriptions such "
+"that multiple subscribers on multiple nodes can consume from one durable "
+"subscription. A durable subscription will be clustered if its topic is "
+"clustered."
+msgstr ""
+
+#. Tag: title
+#: C_Configuration.xml:40
+#, no-c-format
+msgid "Clustered temporary destinations"
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:42
+#, no-c-format
+msgid ""
+"JBoss Messaging supports clustering of temporary topics and queues. All "
+"temporary topics and queues will be clustered if the Post Office is "
+"clustered."
+msgstr ""
+
+#. Tag: title
+#: C_Configuration.xml:48
+#, no-c-format
+msgid "Non-clustered servers"
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:50
+#, no-c-format
+msgid ""
+"Set the <literal>PostOffice</literal>'s <varname>clustered</varname> "
+"attribute to <literal>false</literal> if you do not want all nodes to "
+"participate in a cluster, or if you do not want the server to be clustered."
+msgstr ""
+
+#. Tag: title
+#: C_Configuration.xml:56
+#, no-c-format
+msgid "Message ordering in the cluster"
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:58
+#, no-c-format
+msgid ""
+"To apply strict JMS ordering to messages such that messages are consumed in "
+"the same order they were produced, set the <varname>DefaultPreserveOrdering</"
+"varname> Server Peer attribute to <literal>true</literal>. (The default "
+"value is <literal>false</literal>.) While set to <literal>true</literal>, "
+"messages cannot be distributed as freely around the cluster."
+msgstr ""
+
+#. Tag: title
+#: C_Configuration.xml:64
+#, no-c-format
+msgid "Idempotent operations"
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:66
+#, no-c-format
+msgid ""
+"If the call to send a persistent message to a persistent destination returns "
+"with no exception, then they message has definitely been persisted. However, "
+"if an exception is thrown, you cannot be certain that the message was "
+"<emphasis>not</emphasis> persisted, because failure may have occurred "
+"between the message being persisted and a response being returned to the "
+"caller."
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:70
+#, no-c-format
+msgid ""
+"Your applications must therefore be coded so that its operations are "
+"<emphasis>idempotent</emphasis> — that is, they can be repeated "
+"without causing the system to become inconsistent."
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:74
+#, no-c-format
+msgid ""
+"In a messaging system, you can do this on the application level by checking "
+"for duplicate messages and discarding them if the original message has been "
+"sent successfully. This <emphasis>duplicate checking</emphasis> is a "
+"powerful technique that can remove the need for XA transactions."
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:78
+#, no-c-format
+msgid ""
+"In a clustered environment, JBoss Messaging is configured to perform "
+"duplicate checking by default."
+msgstr ""
+
+#. Tag: title
+#: C_Configuration.xml:84
+#, no-c-format
+msgid "Clustered connection factories"
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:86
+#, no-c-format
+msgid ""
+"When <varname>supportsLoadBalancing</varname> is set to <literal>true</"
+"literal>, consecutive attempts to create connections will round-robin "
+"between available servers. The first node is chosen randomly."
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:90
+#, no-c-format
+msgid ""
+"When <varname>supportsFailover</varname> is set to <literal>true</literal>, "
+"failover will occur transparently and automatically whenever any connection "
+"error is detected."
+msgstr ""
+
+#. Tag: para
+#: C_Configuration.xml:94
+#, no-c-format
+msgid ""
+"If automatic failover is not required, set <varname>supportsFailover</"
+"varname> to <literal>false</literal> and provide a standard JMS "
+"<literal>ExceptionListener</literal> to be called in case of server failure. "
+"Following server failure, you will need to manually close the connection, "
+"lookup a new connection factory from HAJNDI, and create a new connection."
+msgstr ""
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Configuration.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Configuration.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Configuration.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,3842 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Configuration.xml:3
+#, no-c-format
+msgid "Configuration"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:5
+#, no-c-format
+msgid ""
+"The Java Message Service (JMS) API specifies how a messaging client "
+"interacts with a messaging server. How messaging services such as message "
+"destinations and connection factories are defined and implemented depends on "
+"the JMS provider. JBoss Messaging has its own files for service "
+"configuration."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:9
+#, no-c-format
+msgid ""
+"This chapter shows you how to configure various services available in JBoss "
+"Messaging that work together to provide JMS API-level services to client "
+"applications."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:13
+#, no-c-format
+msgid ""
+"JBoss Messaging configuration is divided between several configuration "
+"files. Depending on the type of service provided, configuration information "
+"is divided between <filename>messaging-service.xml</filename>, "
+"<filename>remoting-bisocket-service.xml</filename>, <filename><your "
+"database type>-persistence-service.xml</filename>, <filename>connection-"
+"factories-service.xml</filename> and <filename>destinations-service.xml</"
+"filename>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:17
+#, no-c-format
+msgid ""
+"AOP interceptor stacks can be configured in <filename>aop-messaging-client."
+"xml</filename> (for client-side behavior) and <filename>aop-messaging-server."
+"xml</filename> (for server-side behavior). There is usually no need to "
+"change these files, but some interceptors can be removed to improve "
+"performance if they are not required. Ensure that you have considered the "
+"security implications before removing the security interceptor."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:22
+#, no-c-format
+msgid "Configuring the ServerPeer"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:24
+#, no-c-format
+msgid ""
+"The <literal>ServerPeer</literal> is the heart of the JBoss Messaging JMS "
+"facade. You can configure its behavior by altering <filename>messaging-"
+"service.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:28
+#, no-c-format
+msgid ""
+"All JBoss Messaging services are based in the <literal>ServerPeer</literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:32
+#, no-c-format
+msgid ""
+"An example of a Server Peer configuration is presented below. Note that not "
+"all values for the server peer's attributes are specified in the example"
+msgstr ""
+
+#. Tag: programlisting
+#: Configuration.xml:37
+#, no-c-format
+msgid ""
+"<![CDATA[\n"
+"<!-- ServerPeer MBean configuration\n"
+"============================== -->\n"
+"<mbean code=\"org.jboss.jms.server.ServerPeer\" \n"
+" name=\"jboss.messaging:service=ServerPeer \n"
+" xmbean-dd=\"xmdesc/ServerPeer-xmbean.xml\">\n"
+"\n"
+" <!-- The unique id of the server peer - in a cluster each node \n"
+" MUST have a unique value - must be an integer -->\n"
+"\n"
+" <attribute name=\"ServerPeerID\">0</attribute>\n"
+" \n"
+" <!-- The default JNDI context to use for queues when they are deployed \n"
+" without specifying one --> \n"
+" \n"
+" <attribute name=\"DefaultQueueJNDIContext\">/queue</attribute>\n"
+" \n"
+" <!-- The default JNDI context to use for topics when they are deployed \n"
+" without specifying one --> \n"
+" \n"
+" <attribute name=\"DefaultTopicJNDIContext\">/topic</attribute>\n"
+"\n"
+" <attribute name=\"PostOffice\">\n"
+" jboss.messaging:service=PostOffice\n"
+" </attribute>\n"
+" \n"
+" <!-- The default Dead Letter Queue (DLQ) to use for destinations.\n"
+" This can be overridden on a per destination basis -->\n"
+" \n"
+" <attribute name=\"DefaultDLQ\">\n"
+" jboss.messaging.destination:service=Queue,name=DLQ\n"
+" </attribute>\n"
+" \n"
+" <!-- The default maximum number of times to attempt delivery of a \n"
+" message before sending to the DLQ (if configured). This can be \n"
+" overridden on a per destination basis -->\n"
+" \n"
+" <attribute name=\"DefaultMaxDeliveryAttempts\">10</attribute>\n"
+" \n"
+" <!-- The default Expiry Queue to use for destinations. This can be \n"
+" overridden on a per destination basis -->\n"
+" \n"
+" <attribute name=\"DefaultExpiryQueue\">\n"
+" jboss.messaging.destination:service=Queue,name=ExpiryQueue\n"
+" </attribute>\n"
+" \n"
+" <!-- The default redelivery delay to impose. This can be overridden on \n"
+" a per destination basis -->\n"
+" \n"
+" <attribute name=\"DefaultRedeliveryDelay\">0</attribute>\n"
+" \n"
+" <!-- The periodicity of the message counter manager enquiring on queues \n"
+" for statistics -->\n"
+" \n"
+" <attribute name=\"MessageCounterSamplePeriod\">5000</attribute>\n"
+" \n"
+" <!-- The maximum amount of time for a client to wait for failover to \n"
+" start on the server side after it has detected failure -->\n"
+" \n"
+" <attribute name=\"FailoverStartTimeout\">60000</attribute>\n"
+" \n"
+" <!-- The maximum amount of time for a client to wait for failover to \n"
+" complete on the server side after it has detected failure -->\n"
+" \n"
+" <attribute name=\"FailoverCompleteTimeout\">300000</attribute>\n"
+" \n"
+" <!-- The maximum number of days results to maintain in the message \n"
+" counter history -->\n"
+" \n"
+" <attribute name=\"DefaultMessageCounterHistoryDayLimit\">-1</attribute>\n"
+" \n"
+" <!-- The name of the connection factory to use for creating \n"
+" connections between nodes to pull messages -->\n"
+" \n"
+" <attribute name=\"ClusterPullConnectionFactoryName\">\n"
+" jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory\n"
+" </attribute>\n"
+" \n"
+" <!-- When redistributing messages in the cluster. Do we need to preserve \n"
+" the order of messages received by a particular consumer from a \n"
+" particular producer? -->\n"
+" \n"
+" <attribute name=\"DefaultPreserveOrdering\">false</attribute>\n"
+" \n"
+" <!-- Max. time to hold previously delivered messages back waiting for \n"
+" clients to reconnect after failover -->\n"
+" \n"
+" <attribute name=\"RecoverDeliveriesTimeout\">300000</attribute>\n"
+" \n"
+" <attribute name=\"EnableMessageCounters\">false</attribute>\n"
+" \n"
+" \n"
+" <!-- The password used by the message sucker connections to create \n"
+" connections.\n"
+" THIS SHOULD ALWAYS BE CHANGED AT INSTALL TIME TO SECURE SYSTEM\n"
+" <attribute name=\"SuckerPassword\"></attribute>\n"
+" -->\n"
+"\n"
+" <depends optional-attribute-name=\"PersistenceManager\">\n"
+" jboss.messaging:service=PersistenceManager\n"
+" </depends>\n"
+" \n"
+" <depends optional-attribute-name=\"JMSUserManager\">\n"
+" jboss.messaging:service=JMSUserManager\n"
+" </depends>\n"
+" \n"
+" <depends>jboss.messaging:service=Connector,transport=bisocket</depends>\n"
+" <depends optional-attribute-name=\"SecurityStore\" \n"
+" proxy-type=\"org.jboss.jms.server.SecurityStore\">\n"
+" jboss.messaging:service=SecurityStore\n"
+" </depends>\n"
+" \n"
+"</mbean>\n"
+"]]>"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:39
+#, no-c-format
+msgid "ServerPeer attributes"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:41
+#, no-c-format
+msgid ""
+"This section discusses the <literal>ServerPeer</literal> managed bean "
+"attributes."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:46
+#, no-c-format
+msgid "ServerPeerID"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:48
+#, no-c-format
+msgid ""
+"The unique identifier of the <literal>ServerPeer</literal>. Each node "
+"deployed must have a unique identifier, whether the nodes form a cluster or "
+"are linked by a message bridge. The identifier must be a valid integer."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:54
+#, no-c-format
+msgid "DefaultQueueJNDIContext"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:56
+#, no-c-format
+msgid ""
+"The default JNDI context to be used when binding queues. The default value "
+"is <literal>/queue</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:62
+#, no-c-format
+msgid "DefaultTopicJNDIContext"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:64
+#, no-c-format
+msgid ""
+"The default JNDI context to be used when binding topics. The default value "
+"is <literal>/topic</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:70
+#, no-c-format
+msgid "PostOffice"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:72
+#, no-c-format
+msgid ""
+"The post office used by the <literal>ServerPeer</literal>. You will not "
+"normally need to edit this attribute. The post office routes messages to "
+"queues and maintains the mapping between queues and addresses."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:78
+#, no-c-format
+msgid "DefaultDLQ"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:80
+#, no-c-format
+msgid ""
+"The default DLQ (Dead Letter Queue) that the server uses for destinations. "
+"You can override the DLQ on a per-destination basis. (For more information, "
+"see the configuration information for the destination managed bean.) A DLQ "
+"is a destination for messages that the server has failed to deliver more "
+"than a certain number of times. If the DLQ is not specified, the message "
+"will be removed after the maximum number of delivery attempts. You can "
+"specify a global default for the maximum number of delivery attempts with "
+"the <varname>DefaultMaxDeliveryAttempts</varname> attribute, or set the "
+"maximum individually on a per-destination basis."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:86
+#, no-c-format
+msgid "DefaultMaxDeliveryAttempts"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:88
+#, no-c-format
+msgid ""
+"The global default for the maximum number of times delivery will be "
+"attempted for a message before the message is removed or sent to the DLQ, if "
+"configured. The default value is <literal>10</literal>. You can override "
+"this value on a per-destination basis."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:94
+#, no-c-format
+msgid "DefaultExpiryQueue"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:96
+#, no-c-format
+msgid ""
+"The default expiry queue that the <literal>ServerPeer</literal> will use for "
+"destinations. You can override this value on a per-destination basis, as "
+"seen in the section on destination managed bean configuration. An expiry "
+"queue holds messages that have expired. Message expiry is determined by the "
+"value of <literal>Message::getJMSExpiration()</literal>. If the expiry queue "
+"is not specified, the message will be deleted when it expires."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:102
+#, no-c-format
+msgid "DefaultRedeliveryDelay"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:104
+#, no-c-format
+msgid ""
+"This attribute lets you delay a redelivery attempt, which helps to prevent "
+"thrashing delivery-failure. The default value is <literal>0</literal> (that "
+"is, no delay). You can override this value on a per-destination basis."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:110
+#, no-c-format
+msgid "MessageCounterSamplePeriod"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:112
+#, no-c-format
+msgid ""
+"This attribute defines the period of time between the server's queries to "
+"the queue for queue statistics. The default value is <literal>10000</"
+"literal> milliseconds."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:118
+#, no-c-format
+msgid "FailoverStartTimeout"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:120
+#, no-c-format
+msgid ""
+"The longest period (in milliseconds) that the client will wait for failover "
+"to begin on the server side when a problem is detected. The default value is "
+"<literal>60000</literal> (one minute)."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:126
+#, no-c-format
+msgid "FailoverCompleteTimeout"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:128
+#, no-c-format
+msgid ""
+"The longest period (in milliseconds) that the client will wait for failover "
+"to complete on the server side once failover has been initiated. The default "
+"value is <literal>300000</literal> (five minutes)."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:134
+#, no-c-format
+msgid "DefaultMessageCounterHistoryDayLimit"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:136
+#, no-c-format
+msgid ""
+"JBoss Messaging provides a message counter history, which shows the number "
+"of messages arriving on each queue over a certain number of days. This "
+"attribute represents the maximum number of days for which to store message "
+"counter history. You can override this value on a per-destination."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:142
+#, no-c-format
+msgid "ClusterPullConnectionFactory"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:144
+#, no-c-format
+msgid ""
+"The connection factory used to pull, or suck, messages between queues. You "
+"can omit this attribute to disable message sucking while retaining failover."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:150
+#, no-c-format
+msgid "DefaultPreserveOrdering"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:152
+#, no-c-format
+msgid ""
+"When <literal>true</literal>, JMS ordering is preserved in the cluster. See "
+"the Cluster Configuration section for more detail. The default value is "
+"<literal>false</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:158
+#, no-c-format
+msgid "RecoverDeliveriesTimeout"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:160
+#, no-c-format
+msgid ""
+"When failover occurs, messages that have been delivered will be stored while "
+"the clients reconnect. If the clients do not reconnect (for example, if the "
+"client is dead), these messages will eventually time out and be added to the "
+"queue. This attribute sets the period before timeout in milliseconds. The "
+"default value is <literal>300000</literal> (five minutes)."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:166 Configuration.xml:368
+#, no-c-format
+msgid "EnableMessageCounters"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:168
+#, no-c-format
+msgid ""
+"When set to <literal>true</literal>, enables message counters upon server "
+"start."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:174
+#, no-c-format
+msgid "SuckerPassword"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:176
+#, no-c-format
+msgid ""
+"JBoss Messaging internally creates connections between nodes to redistribute "
+"messages between clustered destinations. These connections are created with "
+"a special, reserved username. This attribute defines the password to use "
+"when creating these connections."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:179
+#, no-c-format
+msgid ""
+"For versions of JBoss Messaging later than 1.4.1.GA, you must define the "
+"<varname>SuckerPassword</varname> on the <literal>SecurityMetadataStore</"
+"literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:183
+#, no-c-format
+msgid ""
+"The <varname>SuckerPassword</varname> must be changed at install time, or "
+"the default password will be used, giving any user who knows the default "
+"password access to any destination on the server."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:190
+#, no-c-format
+msgid "SuckerConnectionRetryTimes"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:192
+#, no-c-format
+msgid ""
+"This is the maximum number of times a sucker's connection is permitted to "
+"retry in the event of a failure. The default value is <literal>-1</literal> "
+"which represents \"retry indefinitely\"."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:198
+#, no-c-format
+msgid "SuckerConnectionRetryInterval"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:200
+#, no-c-format
+msgid ""
+"This is the interval in milliseconds between each retry of the failed "
+"sucker's connection. The default value is <literal>5000</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:205
+#, no-c-format
+msgid "StrictTCK"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:207
+#, no-c-format
+msgid ""
+"To enable strict JMS Technology Compatibility Kit (TCK) semantics, set this "
+"attribute to <literal>true</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:213
+#, no-c-format
+msgid "Destinations"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:215
+#, no-c-format
+msgid ""
+"Returns a list of the destinations (queues and topics) currently deployed."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:221 Configuration.xml:1105
+#, no-c-format
+msgid "MessageCounters"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:223
+#, no-c-format
+msgid "A message counter for a particular queue."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:229
+#, no-c-format
+msgid "MessageStatistics"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:231
+#, no-c-format
+msgid "Statistics about each message counter for each queue."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:237 Configuration.xml:1352
+#, no-c-format
+msgid "SupportsFailover"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:239
+#, no-c-format
+msgid ""
+"When this attribute is <literal>false</literal>, server-side failover does "
+"not occur when a node crashes in a cluster."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:245
+#, no-c-format
+msgid "PersistenceManager"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:247
+#, no-c-format
+msgid ""
+"The persistence manager used by the <literal>ServerPeer</literal>. (You will "
+"not normally need to change this attribute.)"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:253
+#, no-c-format
+msgid "JMSUserManager"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:255
+#, no-c-format
+msgid ""
+"The JMS user manager used by the <literal>ServerPeer</literal>. (You will "
+"not normally need to change this attribute.)"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:261
+#, no-c-format
+msgid "SecurityStore"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:263
+#, no-c-format
+msgid ""
+"The pluggable <literal>SecurityStore</literal>. If you redefine this "
+"attribute, remember that you will need to authenticate the "
+"<literal>MessageSucker</literal> user (<literal>JBM.SUCKER</literal>) with "
+"all special permissions required by clustering."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:269
+#, no-c-format
+msgid "Managed Beans in the ServerPeer"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:272
+#, no-c-format
+msgid "DeployQueue"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:274
+#, no-c-format
+msgid ""
+"Used to programmatically deploy a queue. If the queue exists but is "
+"undeployed, it will be deployed. Otherwise, it is created and deployed."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:277
+#, no-c-format
+msgid "The <varname>name</varname> parameter matches a destination to deploy."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:280
+#, no-c-format
+msgid ""
+"The optional <varname>jndiName</varname> parameter represents the full JNDI "
+"name of the location to which a destination will be bound. If this is not "
+"specified, the destination will be bound in <literal><"
+"DefaultQueueJNDIContext>/<name></literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:283
+#, no-c-format
+msgid ""
+"There are two overloaded versions of this operation. The first deploys the "
+"destination with default paging parameters. The second deploys the "
+"destination with the paging parameters specified. For more information about "
+"paging parameters, see the section on Configuring Destinations."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:289
+#, no-c-format
+msgid "UndeployQueue"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:291
+#, no-c-format
+msgid ""
+"Used to programmatically undeploy a queue. Queues are not removed from "
+"persistent storage. This operation returns <literal>true</literal> if the "
+"queue is successfully undeployed. Otherwise, it returns <literal>false</"
+"literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:297
+#, no-c-format
+msgid "DestroyQueue"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:299
+#, no-c-format
+msgid ""
+"Used to programmatically destroy a queue. Queues are undeployed and all of "
+"their data is removed from the database and destroyed."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:303
+#, no-c-format
+msgid ""
+"Exercise caution when using this method, since it will delete all data for "
+"the queue."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:307
+#, no-c-format
+msgid ""
+"This operation returns <literal>true</literal> if the queue was destroyed "
+"successfully. Otherwise, it returns <literal>false</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:313
+#, no-c-format
+msgid "DeployTopic"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:315
+#, no-c-format
+msgid ""
+"Used to programmatically deploy a topic. There are two overloaded versions "
+"of this operation. The first deploys already existing topics with the "
+"default paging parameters. The second creates and deploys topics with "
+"specified paging parameters. See the section on Configuring Destinations for "
+"more information."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:318
+#, no-c-format
+msgid ""
+"The <varname>name</varname> parameter represents the name of the destination "
+"to deploy."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:321
+#, no-c-format
+msgid ""
+"The <varname>jndiName</varname> represents the full JNDI name of the "
+"location to which the destination will be bound. If this is not specified, "
+"the destination will be bound in <literal><DefaultTopicJNDIContext>/"
+"<name></literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:327
+#, no-c-format
+msgid "UndeployTopic"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:329
+#, no-c-format
+msgid ""
+"Used to programmatically undeploy a topic. Topics are undeployed, but not "
+"removed from persistent storage. This operation returns <literal>true</"
+"literal> if the topic is undeployed successfully. Otherwise, <literal>false</"
+"literal> is returned."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:335
+#, no-c-format
+msgid "DestroyTopic"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:337
+#, no-c-format
+msgid ""
+"Used to programmatically destroy a topic. Topics are undeployed and all data "
+"is removed from the database and destroyed. This operation returns "
+"<literal>true</literal> if the topic is successfully destroyed. Otherwise, "
+"it returns <literal>false</literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:341
+#, no-c-format
+msgid ""
+"Exercise caution when using this method, since it will delete all data for "
+"the topic."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:348
+#, no-c-format
+msgid "ListMessageCountersHTML"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:350
+#, no-c-format
+msgid "Returns message counters in a simply-displayed HTML format."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:356 Configuration.xml:362
+#, no-c-format
+msgid "ResetAllMesageCounters"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:358
+#, no-c-format
+msgid "Resets all message counters to zero."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:364
+#, no-c-format
+msgid "Resets all message counter histories to zero."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:370
+#, no-c-format
+msgid ""
+"Enables all message counters for all destinations. Message counters are "
+"disabled by default."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:374
+#, no-c-format
+msgid "DisableMessageCounters"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:376
+#, no-c-format
+msgid ""
+"Disables all message counters for all destinations. Message counters are "
+"disabled by default."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:380
+#, no-c-format
+msgid "RetrievePreparedTransactions"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:382
+#, no-c-format
+msgid ""
+"Retrieves a list of the XIDs for all transactions currently in a prepared "
+"state on the node."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:386
+#, no-c-format
+msgid "ShowPreparedTransactions"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:388
+#, no-c-format
+msgid ""
+"Retrieves a list of the XIDs for all transactions currently in a prepared "
+"state on the node in an easily-displayed HTML format."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:395
+#, no-c-format
+msgid "Changing the Database"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:397
+#, no-c-format
+msgid ""
+"The Persistence Manager, Post Office and JMS User Manager all interact with "
+"persistent storage. The Persistence Manager handles message-related "
+"persistence. The Post Office handles binding related persistence. The JMS "
+"User Manager handles user-related persistence. All configuration for these "
+"managed beans is handled in the <filename><your database type>-"
+"persistence-service.xml</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:401
+#, no-c-format
+msgid ""
+"Example configuration files for MySQL, Oracle, PostgreSQL, Microsoft SQL "
+"Server or Sybase databases are available in the <filename>jboss-as/docs/"
+"examples/jms</filename> directory of the release bundle."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:405
+#, no-c-format
+msgid ""
+"To enable support for one of these databases, replace the default "
+"<filename>hsqldb-persistence-service.xml</filename> configuration file with "
+"the configuration file specific to your database type and restart the server."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:409
+#, no-c-format
+msgid ""
+"By default, the messaging services relying on a data store reference "
+"<literal>java:/DefaultDS</literal> for the data source. To deploy a data "
+"source with a different JNDI name, you must update all <literal>DataSource</"
+"literal> attributes in the persistence configuration file. We include "
+"example data source configurations in the distribution."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:415
+#, no-c-format
+msgid "Configuring the Post office"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:417
+#, no-c-format
+msgid ""
+"The post office routes messages to their destination or destinations. It "
+"maintains the mappings between the addresses to which a message can be sent, "
+"and the final queue. For example, when sending a message with an address "
+"that represents a JMS queue, the post office routes the message to that JMS "
+"queue. When sending a message with an address that represents a JMS topic, "
+"the post office routes the message to a set of queues — one for each "
+"JMS subscription."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:421
+#, no-c-format
+msgid "The post office also handles the persistence for address mapping."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:423
+#, no-c-format
+msgid ""
+"JBoss Messaging post offices are cluster-aware. In a cluster, they "
+"automatically route and pull messages between nodes in order to provide "
+"fully-distributed JMS queues and topics."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:427
+#, no-c-format
+msgid ""
+"You can configure the post office in your <filename><your database "
+"type>-persistence-service.xml</filename> file. For example:"
+msgstr ""
+
+#. Tag: programlisting
+#: Configuration.xml:432
+#, no-c-format
+msgid ""
+"<![CDATA[\n"
+"<mbean code=\"org.jboss.messaging.core.jmx.MessagingPostOfficeService\"\n"
+" name=\"jboss.messaging:service=PostOffice\"\n"
+" xmbean-dd=\"xmdesc/MessagingPostOffice-xmbean.xml\">\n"
+" \n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" \n"
+" <depends>\n"
+" jboss.jca:service=DataSourceBinding,name=DefaultDS\n"
+" </depends>\n"
+" \n"
+" <depends optional-attribute-name=\"TransactionManager\">\n"
+" jboss:service=TransactionManager\n"
+" </depends>\n"
+" \n"
+" <!-- The name of the post office --> \n"
+" \n"
+" <attribute name=\"PostOfficeName\">JMS post office</attribute>\n"
+" \n"
+" <!-- The datasource used by the post office to access it's \n"
+" binding information --> \n"
+" \n"
+" <attribute name=\"DataSource\">java:/DefaultDS</attribute>\n"
+" \n"
+" <!-- If true will attempt to create tables and indexes on \n"
+" every start-up -->\n"
+" \n"
+" <attribute name=\"CreateTablesOnStartup\">true</attribute>\n"
+" \n"
+" <!-- If true then we will automatically detect and reject \n"
+" duplicate messages sent during failover -->\n"
+" \n"
+" <attribute name=\"DetectDuplicates\">true</attribute>\n"
+" \n"
+" <!-- The size of the id cache to use when detecting duplicate \n"
+" messages -->\n"
+" \n"
+" <attribute name=\"IDCacheSize\">500</attribute>\n"
+" \n"
+" <attribute name=\"SqlProperties\">\n"
+" CREATE_POSTOFFICE_TABLE=CREATE TABLE JBM_POSTOFFICE \n"
+" (POSTOFFICE_NAME VARCHAR(255), \n"
+" NODE_ID INTEGER, QUEUE_NAME VARCHAR(255), COND VARCHAR(1023), \n"
+" SELECTOR VARCHAR(1023), CHANNEL_ID BIGINT, CLUSTERED CHAR(1), \n"
+" ALL_NODES CHAR(1), \n"
+" PRIMARY KEY(POSTOFFICE_NAME, NODE_ID, QUEUE_NAME)) ENGINE = INNODB\n"
+"\n"
+" INSERT_BINDING=INSERT INTO JBM_POSTOFFICE \n"
+" (POSTOFFICE_NAME, NODE_ID, QUEUE_NAME, COND, SELECTOR, \n"
+" CHANNEL_ID, CLUSTERED, ALL_NODES) \n"
+" VALUES (?, ?, ?, ?, ?, ?, ?, ?)\n"
+"\n"
+" DELETE_BINDING=DELETE FROM JBM_POSTOFFICE WHERE \n"
+" POSTOFFICE_NAME=? AND NODE_ID=? AND QUEUE_NAME=?\n"
+"\n"
+" LOAD_BINDINGS=SELECT QUEUE_NAME, COND, SELECTOR, \n"
+" CHANNEL_ID, CLUSTERED, ALL_NODES FROM \n"
+" JBM_POSTOFFICE WHERE POSTOFFICE_NAME=? AND NODE_ID=?\n"
+" </attribute>\n"
+" \n"
+" <!-- This post office is clustered. If you don't want a clustered post \n"
+" office then set to false -->\n"
+" \n"
+" <attribute name=\"Clustered\">true</attribute>\n"
+" \n"
+" <!-- All the remaining properties only have to be specified if the post \n"
+" office is clustered. You can safely comment them out if your post \n"
+" office is non clustered -->\n"
+" \n"
+" <!-- The JGroups group name that the post office will use --> \n"
+" \n"
+" <attribute name=\"GroupName\">\n"
+" ${jboss.messaging.groupname:MessagingPostOffice}\n"
+" </attribute>\n"
+" \n"
+" <!-- Max time to wait for state to arrive when the post office \n"
+" joins the cluster --> \n"
+" \n"
+" <attribute name=\"StateTimeout\">5000</attribute>\n"
+" \n"
+" <!-- Max time to wait for a synchronous call to node members using \n"
+" the MessageDispatcher --> \n"
+" \n"
+" <attribute name=\"CastTimeout\">50000</attribute>\n"
+" \n"
+" <!-- Set this to true if you want failover of connections to occur \n"
+" when a node is shut down -->\n"
+" \n"
+" <attribute name=\"FailoverOnNodeLeave\">false</attribute>\n"
+" \n"
+" <!-- JGroups stack configuration for the data channel - used for sending \n"
+" data across the cluster --> \n"
+" \n"
+" <!-- By default we use the TCP stack for data --> \n"
+" <attribute name=\"DataChannelConfig\">\n"
+" <config>\n"
+" <TCP start_port=\"7900\"\n"
+" loopback=\"true\"\n"
+" recv_buf_size=\"20000000\"\n"
+" send_buf_size=\"640000\"\n"
+" discard_incompatible_packets=\"true\"\n"
+" max_bundle_size=\"64000\"\n"
+" max_bundle_timeout=\"30\"\n"
+" use_incoming_packet_handler=\"true\"\n"
+" use_outgoing_packet_handler=\"false\"\n"
+" down_thread=\"false\" up_thread=\"false\"\n"
+" enable_bundling=\"false\"\n"
+" use_send_queues=\"false\"\n"
+" sock_conn_timeout=\"300\"\n"
+" skip_suspected_members=\"true\"/>\n"
+" <MPING timeout=\"4000\"\n"
+" bind_to_all_interfaces=\"true\"\n"
+" mcast_addr=\"${jboss.messaging.datachanneludpaddress:228.6.6.6}\"\n"
+" mcast_port=\"${jboss.messaging.datachanneludpport:45567}\"\n"
+" ip_ttl=\"8\"\n"
+" num_initial_members=\"2\"\n"
+" num_ping_requests=\"1\"/> \n"
+" <MERGE2 max_interval=\"100000\"\n"
+" down_thread=\"false\" up_thread=\"false\" min_interval=\"20000\"/>\n"
+" <FD_SOCK down_thread=\"false\" up_thread=\"false\"/> \n"
+" <VERIFY_SUSPECT timeout=\"1500\" down_thread=\"false\" \n"
+" up_thread=\"false\"/>\n"
+" <pbcast.NAKACK max_xmit_size=\"60000\"\n"
+" use_mcast_xmit=\"false\" gc_lag=\"0\"\n"
+" retransmit_timeout=\"300,600,1200,2400,4800\"\n"
+" down_thread=\"false\" up_thread=\"false\"\n"
+" discard_delivered_msgs=\"true\"/>\n"
+" <pbcast.STABLE stability_delay=\"1000\" desired_avg_gossip=\"50000\"\n"
+" down_thread=\"false\" up_thread=\"false\"\n"
+" max_bytes=\"400000\"/>\n"
+" <pbcast.GMS print_local_addr=\"true\" join_timeout=\"3000\"\n"
+" down_thread=\"false\" up_thread=\"false\"\n"
+" join_retry_timeout=\"2000\" shun=\"false\"\n"
+" view_bundling=\"true\"/>\n"
+" </config> \n"
+" </attribute>\n"
+" \n"
+" <!-- JGroups stack configuration to use for \n"
+" the control channel - used for control messages --> \n"
+" \n"
+" <!-- We use udp stack for the control channel -->\n"
+" <attribute name=\"ControlChannelConfig\">\n"
+" <config>\n"
+" <UDP\n"
+" mcast_addr=\"${jboss.messaging.controlchanneludpaddress:228.7.7.7}"
+"\"\n"
+" mcast_port=\"${jboss.messaging.controlchanneludpport:45568}\"\n"
+" tos=\"8\"\n"
+" ucast_recv_buf_size=\"20000000\"\n"
+" ucast_send_buf_size=\"640000\"\n"
+" mcast_recv_buf_size=\"25000000\"\n"
+" mcast_send_buf_size=\"640000\"\n"
+" loopback=\"false\"\n"
+" discard_incompatible_packets=\"true\"\n"
+" max_bundle_size=\"64000\"\n"
+" max_bundle_timeout=\"30\"\n"
+" use_incoming_packet_handler=\"true\"\n"
+" use_outgoing_packet_handler=\"false\"\n"
+" ip_ttl=\"2\"\n"
+" down_thread=\"false\" up_thread=\"false\"\n"
+" enable_bundling=\"false\"/>\n"
+" <PING timeout=\"2000\"\n"
+" down_thread=\"false\" up_thread=\"false\" num_initial_members=\"3\"/"
+">\n"
+" <MERGE2 max_interval=\"100000\"\n"
+" down_thread=\"false\" up_thread=\"false\" min_interval=\"20000\"/>\n"
+" <FD_SOCK down_thread=\"false\" up_thread=\"false\"/>\n"
+" <FD timeout=\"10000\" max_tries=\"5\" down_thread=\"false\" \n"
+" up_thread=\"false\" shun=\"true\"/>\n"
+" <VERIFY_SUSPECT timeout=\"1500\" down_thread=\"false\" \n"
+" up_thread=\"false\"/>\n"
+" <pbcast.NAKACK max_xmit_size=\"60000\"\n"
+" use_mcast_xmit=\"false\" gc_lag=\"0\"\n"
+" retransmit_timeout=\"300,600,1200,2400,4800\"\n"
+" down_thread=\"false\" up_thread=\"false\"\n"
+" discard_delivered_msgs=\"true\"/>\n"
+" <UNICAST timeout=\"300,600,1200,2400,3600\"\n"
+" down_thread=\"false\" up_thread=\"false\"/>\n"
+" <pbcast.STABLE stability_delay=\"1000\" desired_avg_gossip=\"50000\"\n"
+" down_thread=\"false\" up_thread=\"false\"\n"
+" max_bytes=\"400000\"/>\n"
+" <pbcast.GMS print_local_addr=\"true\" join_timeout=\"3000\" \n"
+" use_flush=\"true\" flush_timeout=\"3000\"\n"
+" down_thread=\"false\" up_thread=\"false\"\n"
+" join_retry_timeout=\"2000\" shun=\"false\"\n"
+" view_bundling=\"true\"/>\n"
+" <FRAG2 frag_size=\"60000\" down_thread=\"false\" up_thread=\"false\"/"
+">\n"
+" <pbcast.STATE_TRANSFER down_thread=\"false\" up_thread=\"false\" \n"
+" use_flush=\"true\" flush_timeout=\"3000\"/>\n"
+" <pbcast.FLUSH down_thread=\"false\" up_thread=\"false\" timeout=\"20000"
+"\" \n"
+" auto_flush_conf=\"false\"/>\n"
+" </config>\n"
+" </attribute> \n"
+" \n"
+"</mbean>\n"
+"]]>"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:436
+#, no-c-format
+msgid "Post office attributes"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:437
+#, no-c-format
+msgid "In this section, we outline the attributes of the post office."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:441
+#, no-c-format
+msgid "DataSource"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:443
+#, no-c-format
+msgid "The data source used to persist post office mapping data."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:449 Configuration.xml:663 Configuration.xml:722
+#, no-c-format
+msgid "SQLProperties"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:451
+#, no-c-format
+msgid ""
+"Specifies the DDL and DML for a particular database. If this attribute is "
+"not overridden, the default Hypersonic configuration will be used."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:457 Configuration.xml:622 Configuration.xml:706
+#, no-c-format
+msgid "CreateTablesOnStartup"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:459
+#, no-c-format
+msgid ""
+"When set to <literal>true</literal>, the post office will create tables and "
+"indexes on startup. If tables or indexes already exist, a "
+"<exceptionname>SQLException</exceptionname> is thrown by the JDBC driver, "
+"but this is ignored by the Persistence Manager and the operation continues "
+"unhindered. The default value is <literal>true</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:465
+#, no-c-format
+msgid "DetectDuplicates"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:467
+#, no-c-format
+msgid ""
+"When set to <literal>true</literal>, the post office detects duplicate "
+"messages that may be sent when delivery is retried on a new node after "
+"server failure. The default value of this attribute is <literal>true</"
+"literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:473
+#, no-c-format
+msgid "IDCacheSize"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:475
+#, no-c-format
+msgid ""
+"If duplicate detection is enabled, the server remembers the last <literal>n</"
+"literal> message IDs sent, to prevent duplicate messages being sent after "
+"failover occurs. <varname>IDCacheSize</varname> determines the value of "
+"<literal>n</literal>. Its default value is <literal>500</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:480
+#, no-c-format
+msgid "PostOfficeName"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:482
+#, no-c-format
+msgid "The name of the post office."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:486
+#, no-c-format
+msgid "NodeIDView"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:488
+#, no-c-format
+msgid "Returns the node IDs of all nodes in a cluster as a set."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:492
+#, no-c-format
+msgid "GroupName"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:494
+#, no-c-format
+msgid ""
+"Post offices with the same group name will form a cluster together. Match "
+"post office group names to form a cluster with particular post offices."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:500 Configuration.xml:881 Configuration.xml:1090
+#, no-c-format
+msgid "Clustered"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:502
+#, no-c-format
+msgid ""
+"If set to <literal>true</literal>, the post office will join a cluster to "
+"form distributed queues and topics. If set to <literal>false</literal>, all "
+"cluster-related attributes will be ignored."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:508
+#, no-c-format
+msgid "StateTimeout"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:510
+#, no-c-format
+msgid ""
+"The maximum period of time the post office will wait to receive group state "
+"when a node joins a pre-existing cluster. The default value is "
+"<literal>5000</literal> milliseconds."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:516
+#, no-c-format
+msgid "CastTimeout"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:518
+#, no-c-format
+msgid ""
+"The maximum time that the post office will wait for a reply casting message "
+"synchronously. The default value is <literal>5000</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:524
+#, no-c-format
+msgid "FailoverOnNodeLeave"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:526
+#, no-c-format
+msgid ""
+"If set to <literal>true</literal>, when a server node is shut down cleanly, "
+"any connections on that node will failover onto another node. The default "
+"value is <literal>false</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:532
+#, no-c-format
+msgid "MaxConcurrentReplications"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:534
+#, no-c-format
+msgid ""
+"The maximum number of concurrent replication requests to make before "
+"blocking to allow replies to return. This prevents JGroups overloading. "
+"There is rarely a good reason to alter this. The default value is "
+"<literal>50</literal>"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:540
+#, no-c-format
+msgid "ControlChannelConfig"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:542
+#, no-c-format
+msgid ""
+"JBoss Messaging uses JGroups for all group management. This attribute "
+"contains JGroups stack configuration for the control channel, which sends "
+"requests to and receives responses from other nodes in the cluster."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:545 Configuration.xml:556
+#, no-c-format
+msgid ""
+"Standard JGroups configuration is used. For more information, see the "
+"JGroups release documentation or visit <ulink url=\"http://www.jgroups.org"
+"\">http://www.jgroups.org</ulink> or <ulink url=\"http://wiki.jboss.org/wiki/"
+"Wiki.jsp?page=JGroups\">http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroups</"
+"ulink>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:550
+#, no-c-format
+msgid "DataChannelConfig"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:552
+#, no-c-format
+msgid ""
+"JBoss Messaging uses JGroups for all group management. This attribute "
+"contains JGroups stack configuration for the data channel, which sends and "
+"receives messages to and from other nodes in the cluster, and replicates "
+"session data."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:563
+#, no-c-format
+msgid "Configuring the Persistence Manager"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:565
+#, no-c-format
+msgid ""
+"The Persistence Manager manages all message-related persistence. JBoss "
+"Messaging ships with a JDBC Persistence Manager, which handles message data "
+"persistence in a relational database accessed via JDBC. The Persistence "
+"Manager can be plugged into the Messaging server, which lets you provide "
+"additional implementations to persist message data in non-relational stores, "
+"file stores, etc."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:568
+#, no-c-format
+msgid ""
+"Persistent service configuration details are grouped in <filename><your "
+"database type>-persistence-service.xml</filename>. By default, JBoss "
+"Messaging ships with the <filename>hsqldb-persistence-service.xml</filename> "
+"file, which configures the Messaging server to use the Hypersonic database "
+"instance included by default with any JBoss Application Server instance."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:573
+#, no-c-format
+msgid ""
+"Hypersonic should not be used in a production environment, since it has "
+"limited support for transaction isolation and tends to behave erratically "
+"when under high loads."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:582
+#, no-c-format
+msgid ""
+"JBoss Messaging also ships with Persistence Manager configurations for "
+"MySQL, Oracle, PostgreSQL, Sybase, Microsoft SQL Server, and DB2. The "
+"example configuration files (<filename>mysql-persistence-service.xml</"
+"filename>, <filename>ndb-persistence-service.xml</filename>, etc.) are "
+"available from the <filename>jboss-as/docs/examples/jms</filename> directory "
+"of the release bundle."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:586
+#, no-c-format
+msgid ""
+"We encourage users to contribute their own configuration files for thorough "
+"testing and certification for use with JBoss Messaging. The JDBC Persistence "
+"Manager uses standard SQL as its Data Manipulation Language (DML), so "
+"writing a Persistence Manager configuration for another database type is a "
+"matter of changing the configuration's Data Definition Language (DDL), which "
+"usually differs on a per-database basis."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:590
+#, no-c-format
+msgid ""
+"JBoss Messaging also ships with a Null Persistence Manager configuration "
+"option, which can be used when you do not want persistence."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:594
+#, no-c-format
+msgid ""
+"The following code is the default Hypersonic persistence configuration file:"
+msgstr ""
+
+#. Tag: programlisting
+#: Configuration.xml:598
+#, no-c-format
+msgid ""
+"<![CDATA[\n"
+"<mbean code=\"org.jboss.messaging.core.jmx.JDBCPersistenceManagerService\"\n"
+" name=\"jboss.messaging:service=PersistenceManager\"\n"
+" xmbean-dd=\"xmdesc/JDBCPersistenceManager-xmbean.xml\">\n"
+" \n"
+" <depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>\n"
+" \n"
+" <depends optional-attribute-name=\"TransactionManager\">\n"
+" jboss:service=TransactionManager\n"
+" </depends>\n"
+" \n"
+" <!-- The datasource to use for the persistence manager -->\n"
+" \n"
+" <attribute name=\"DataSource\">java:/DefaultDS</attribute>\n"
+" \n"
+" <!-- If true will attempt to create tables and indexes on \n"
+" every start-up -->\n"
+" \n"
+" <attribute name=\"CreateTablesOnStartup\">true</attribute>\n"
+" \n"
+" <!-- If true then will use JDBC batch updates -->\n"
+" \n"
+" <attribute name=\"UsingBatchUpdates\">true</attribute>\n"
+" \n"
+" <attribute name=\"SqlProperties\">\n"
+" CREATE_DUAL=CREATE TABLE JBM_DUAL \n"
+" (DUMMY INTEGER, PRIMARY KEY (DUMMY)) ENGINE = INNODB\n"
+" \n"
+" CREATE_MESSAGE_REFERENCE=CREATE TABLE JBM_MSG_REF \n"
+" (CHANNEL_ID BIGINT, MESSAGE_ID BIGINT, TRANSACTION_ID BIGINT, \n"
+" STATE CHAR(1), ORD BIGINT, PAGE_ORD BIGINT, DELIVERY_COUNT INTEGER, \n"
+" SCHED_DELIVERY BIGINT, PRIMARY KEY(CHANNEL_ID, MESSAGE_ID)) \n"
+" ENGINE = INNODB\n"
+" \n"
+" CREATE_IDX_MESSAGE_REF_TX=CREATE INDEX JBM_MSG_REF_TX \n"
+" ON JBM_MSG_REF (TRANSACTION_ID)\n"
+" \n"
+" CREATE_IDX_MESSAGE_REF_ORD=CREATE INDEX JBM_MSG_REF_ORD \n"
+" ON JBM_MSG_REF (ORD)\n"
+" \n"
+" CREATE_IDX_MESSAGE_REF_PAGE_ORD=CREATE INDEX JBM_MSG_REF_PAGE_ORD \n"
+" ON JBM_MSG_REF (PAGE_ORD)\n"
+" \n"
+" CREATE_IDX_MESSAGE_REF_MESSAGE_ID=\n"
+" CREATE INDEX JBM_MSG_REF_MESSAGE_ID ON JBM_MSG_REF (MESSAGE_ID)\n"
+" \n"
+" CREATE_IDX_MESSAGE_REF_SCHED_DELIVERY=\n"
+" CREATE INDEX JBM_MSG_REF_SCHED_DELIVERY \n"
+" ON JBM_MSG_REF (SCHED_DELIVERY)\n"
+" \n"
+" CREATE_MESSAGE=CREATE TABLE JBM_MSG (MESSAGE_ID BIGINT, \n"
+" RELIABLE CHAR(1), EXPIRATION BIGINT, TIMESTAMP BIGINT, \n"
+" PRIORITY TINYINT, TYPE TINYINT, HEADERS MEDIUMBLOB, \n"
+" PAYLOAD LONGBLOB, PRIMARY KEY (MESSAGE_ID)) ENGINE = INNODB\n"
+" \n"
+" CREATE_IDX_MESSAGE_TIMESTAMP=CREATE INDEX JBM_MSG_REF_TIMESTAMP \n"
+" ON JBM_MSG (TIMESTAMP)\n"
+" \n"
+" CREATE_TRANSACTION=CREATE TABLE JBM_TX (NODE_ID INTEGER, \n"
+" TRANSACTION_ID BIGINT, BRANCH_QUAL VARBINARY(254), \n"
+" FORMAT_ID INTEGER, GLOBAL_TXID VARBINARY(254), \n"
+" PRIMARY KEY (TRANSACTION_ID)) ENGINE = INNODB\n"
+" \n"
+" CREATE_COUNTER=CREATE TABLE JBM_COUNTER (NAME VARCHAR(255), \n"
+" NEXT_ID BIGINT, PRIMARY KEY(NAME)) ENGINE = INNODB\n"
+" \n"
+" INSERT_DUAL=INSERT INTO JBM_DUAL VALUES (1)\n"
+" \n"
+" CHECK_DUAL=SELECT 1 FROM JBM_DUAL\n"
+" \n"
+" INSERT_MESSAGE_REF=INSERT INTO JBM_MSG_REF (CHANNEL_ID, MESSAGE_ID,\n"
+" TRANSACTION_ID, STATE, ORD, PAGE_ORD, DELIVERY_COUNT, \n"
+" SCHED_DELIVERY) VALUES (?, ?, ?, ?, ?, ?, ?, ?)\n"
+" \n"
+" DELETE_MESSAGE_REF=DELETE FROM JBM_MSG_REF WHERE MESSAGE_ID=? \n"
+" AND CHANNEL_ID=? AND STATE='C'\n"
+" \n"
+" UPDATE_MESSAGE_REF=UPDATE JBM_MSG_REF SET TRANSACTION_ID=?, STATE='-' \n"
+" WHERE MESSAGE_ID=? AND CHANNEL_ID=? AND STATE='C'\n"
+" \n"
+" UPDATE_PAGE_ORDER=UPDATE JBM_MSG_REF SET PAGE_ORD = ? \n"
+" WHERE MESSAGE_ID=? AND CHANNEL_ID=?\n"
+" \n"
+" COMMIT_MESSAGE_REF1=UPDATE JBM_MSG_REF SET STATE='C', \n"
+" TRANSACTION_ID = NULL WHERE TRANSACTION_ID=? AND STATE='+'\n"
+" \n"
+" COMMIT_MESSAGE_REF2=DELETE FROM JBM_MSG_REF WHERE TRANSACTION_ID=? \n"
+" AND STATE='-'\n"
+" \n"
+" ROLLBACK_MESSAGE_REF1=DELETE FROM JBM_MSG_REF WHERE TRANSACTION_ID=? \n"
+" AND STATE='+'\n"
+" \n"
+" ROLLBACK_MESSAGE_REF2=UPDATE JBM_MSG_REF SET STATE='C', \n"
+" TRANSACTION_ID = NULL WHERE TRANSACTION_ID=? AND STATE='-'\n"
+" \n"
+" LOAD_PAGED_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, PAGE_ORD, \n"
+" SCHED_DELIVERY FROM JBM_MSG_REF WHERE CHANNEL_ID = ? AND PAGE_ORD \n"
+" BETWEEN ? AND ? ORDER BY PAGE_ORD\n"
+" \n"
+" LOAD_UNPAGED_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, SCHED_DELIVERY \n"
+" FROM JBM_MSG_REF WHERE STATE = 'C' AND CHANNEL_ID = ? AND PAGE_ORD \n"
+" IS NULL ORDER BY ORD\n"
+" \n"
+" LOAD_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, SCHED_DELIVERY \n"
+" FROM JBM_MSG_REF WHERE STATE = 'C' AND CHANNEL_ID = ? ORDER BY ORD\n"
+" \n"
+" UPDATE_REFS_NOT_PAGED=UPDATE JBM_MSG_REF SET PAGE_ORD = NULL WHERE \n"
+" PAGE_ORD BETWEEN ? AND ? AND CHANNEL_ID=?\n"
+" \n"
+" SELECT_MIN_MAX_PAGE_ORD=SELECT MIN(PAGE_ORD), MAX(PAGE_ORD) \n"
+" FROM JBM_MSG_REF WHERE CHANNEL_ID = ?\n"
+" \n"
+" SELECT_EXISTS_REF_MESSAGE_ID=SELECT MESSAGE_ID FROM JBM_MSG_REF \n"
+" WHERE MESSAGE_ID = ?\n"
+" \n"
+" UPDATE_DELIVERY_COUNT=UPDATE JBM_MSG_REF SET DELIVERY_COUNT = ? \n"
+" WHERE CHANNEL_ID = ? AND MESSAGE_ID = ?\n"
+" \n"
+" UPDATE_CHANNEL_ID=UPDATE JBM_MSG_REF SET CHANNEL_ID = ? \n"
+" WHERE CHANNEL_ID = ?\n"
+" \n"
+" LOAD_MESSAGES=SELECT MESSAGE_ID, RELIABLE, EXPIRATION, TIMESTAMP, \n"
+" PRIORITY, HEADERS, PAYLOAD, TYPE FROM JBM_MSG\n"
+" \n"
+" INSERT_MESSAGE=INSERT INTO JBM_MSG (MESSAGE_ID, RELIABLE, EXPIRATION,\n"
+" TIMESTAMP, PRIORITY, TYPE, HEADERS, PAYLOAD) \n"
+" VALUES (?, ?, ?, ?, ?, ?, ?, ?)\n"
+" \n"
+" INSERT_MESSAGE_CONDITIONAL=INSERT INTO JBM_MSG (MESSAGE_ID, RELIABLE, \n"
+" EXPIRATION, TIMESTAMP, PRIORITY, TYPE, INST_TIME) \n"
+" SELECT ?, ?, ?, ?, ?, ?, ? FROM JBM_DUAL WHERE NOT EXISTS \n"
+" (SELECT MESSAGE_ID FROM JBM_MSG WHERE MESSAGE_ID = ?)\n"
+" \n"
+" UPDATE_MESSAGE_4CONDITIONAL=UPDATE JBM_MSG SET HEADERS=?, PAYLOAD=? \n"
+" WHERE MESSAGE_ID=?\n"
+" \n"
+" INSERT_MESSAGE_CONDITIONAL_FULL=INSERT INTO JBM_MSG (MESSAGE_ID, \n"
+" RELIABLE, EXPIRATION, TIMESTAMP, PRIORITY, TYPE, HEADERS, PAYLOAD) \n"
+" SELECT ?, ?, ?, ?, ?, ?, ?, ? FROM JBM_DUAL WHERE NOT EXISTS \n"
+" (SELECT MESSAGE_ID FROM JBM_MSG WHERE MESSAGE_ID = ?)\n"
+" \n"
+" MESSAGE_ID_COLUMN=MESSAGE_ID\n"
+" \n"
+" DELETE_MESSAGE=DELETE FROM JBM_MSG WHERE MESSAGE_ID = ? AND NOT EXISTS \n"
+" (SELECT * FROM JBM_MSG_REF WHERE JBM_MSG_REF.MESSAGE_ID = ?)\n"
+" \n"
+" INSERT_TRANSACTION=INSERT INTO JBM_TX (NODE_ID, TRANSACTION_ID, \n"
+" BRANCH_QUAL, FORMAT_ID, GLOBAL_TXID) VALUES(?, ?, ?, ?, ?)\n"
+" \n"
+" DELETE_TRANSACTION=DELETE FROM JBM_TX WHERE NODE_ID = ? \n"
+" AND TRANSACTION_ID = ?\n"
+" \n"
+" SELECT_PREPARED_TRANSACTIONS=SELECT TRANSACTION_ID, BRANCH_QUAL, \n"
+" FORMAT_ID, GLOBAL_TXID FROM JBM_TX WHERE NODE_ID = ?\n"
+" \n"
+" SELECT_MESSAGE_ID_FOR_REF=SELECT MESSAGE_ID, CHANNEL_ID \n"
+" FROM JBM_MSG_REF WHERE TRANSACTION_ID = ? AND STATE = '+' \n"
+" ORDER BY ORD\n"
+" \n"
+" SELECT_MESSAGE_ID_FOR_ACK=SELECT MESSAGE_ID, CHANNEL_ID \n"
+" FROM JBM_MSG_REF WHERE TRANSACTION_ID = ? AND STATE = '-' \n"
+" ORDER BY ORD\n"
+" \n"
+" UPDATE_COUNTER=UPDATE JBM_COUNTER SET NEXT_ID = ? WHERE NAME=?\n"
+" \n"
+" SELECT_COUNTER=SELECT NEXT_ID FROM JBM_COUNTER WHERE NAME=? FOR UPDATE\n"
+" \n"
+" INSERT_COUNTER=INSERT INTO JBM_COUNTER (NAME, NEXT_ID) VALUES (?, ?)\n"
+" \n"
+" SELECT_ALL_CHANNELS=SELECT DISTINCT(CHANNEL_ID) FROM JBM_MSG_REF\n"
+" \n"
+" UPDATE_TX=UPDATE JBM_TX SET NODE_ID=? WHERE NODE_ID=?\n"
+" \n"
+" </attribute>\n"
+" \n"
+" <!-- The maximum number of parameters to include in a prepared \n"
+" statement -->\n"
+" \n"
+" <attribute name=\"MaxParams\">500</attribute>\n"
+"\n"
+" <attribute name=\"UseNDBFailoverStrategy\">true</attribute>\n"
+" \n"
+"</mbean>\n"
+"]]>"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:601
+#, no-c-format
+msgid ""
+"When a database is created in Sybase, the maximum size of text and image "
+"datatypes is set to the default page size of <literal>2 kilobytes</literal>. "
+"Any message that exceeds this limit is truncated without any information or "
+"warning. To avoid this, edit the database parameters to set "
+"<varname>@@TEXTSIZE</varname> to a greater value."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:604
+#, no-c-format
+msgid ""
+"Truncation may also occur in the Microsoft SQL Server if "
+"<varname>@@TEXTSIZE</varname> value is set to a lesser value than the "
+"default value. For further information, see <ulink url=\"http://jira.jboss."
+"com/jira/browse/SOA-554\"></ulink>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:609
+#, no-c-format
+msgid ""
+"Microsoft SQL Server does not automatically un-allocate the hard drive space "
+"occupied by data in a database when that data is deleted. This means that, "
+"when the space is used as a data store for a service that temporarily stores "
+"many records (such as a messaging service), the disk space will quickly "
+"become much greater than the amount of data actually being stored."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:612
+#, no-c-format
+msgid ""
+"Database administrators should implement database maintenance plans to "
+"ensure that the unused space is reclaimed. Refer to your Microsoft SQL "
+"Server documentation for the DBCC commands <command>ShrinkDatabase</command> "
+"and <command>UpdateUsage</command> for guidance reclaiming the unused space. "
+"For further information about this issue, see <ulink url=\"https://jira."
+"jboss.org/jira/browse/SOA-629\"></ulink>"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:618
+#, no-c-format
+msgid "We now discuss the MBean attributes of the PersistenceManager MBean"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:624
+#, no-c-format
+msgid ""
+"When <literal>true</literal>, the persistence manager will attempt to create "
+"tables (and indexes) on startup. If tables or indexes already exist, a "
+"<exceptionname>SQLException</exceptionname> will be thrown by the JDBC "
+"driver and ignored by the persistence manager, allowing it to continue "
+"unhindered."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:628
+#, no-c-format
+msgid "By default, this parameter is set to <literal>true</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:634 Configuration.xml:714
+#, no-c-format
+msgid "UsingBatchUpdates"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:636
+#, no-c-format
+msgid ""
+"If your database supports JDBC batch updates, setting this to <literal>true</"
+"literal> will group multiple database updates in batches to improve "
+"performance. The default value is <literal>false</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:642
+#, no-c-format
+msgid "UsingBinaryStream"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:643
+#, no-c-format
+msgid ""
+"When <literal>true</literal>, messages will be stored and read with a JDBC "
+"binary stream instead of via <literal>getBytes()</literal> and "
+"<literal>setBytes()</literal>, which, in some databases, can only get or set "
+"a certain number of bytes. The default value is <literal>true</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:649
+#, no-c-format
+msgid "UsingTrailingByte"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:650
+#, no-c-format
+msgid ""
+"Some versions of Sybase will truncate a BLOB with trailing zeros. When "
+"<varname>UseTrailingByte</varname> is set to <literal>true</literal>, a "
+"trailing non-zero byte will be added to each BLOB before persistence, and "
+"removed from the BLOB following persistence, preventing truncation by the "
+"database. This is only known to be necessary for Sybase databases. By "
+"default, the value is set to <literal>false</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:656
+#, no-c-format
+msgid "SupportsBlobOnSelect"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:657
+#, no-c-format
+msgid ""
+"Some databases, specifically Oracle, do not allow BLOB insertion via an "
+"<code>INSERT INTO ... SELECT FROM</code> statement, and require two-stage "
+"conditional message insertion. When <varname>SupportsBlobOnSelect</varname> "
+"is set to <literal>false</literal>, two-stage insertion will be used. The "
+"default value is <literal>true</literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:664
+#, no-c-format
+msgid ""
+"Specifies the DDL and DML for a particular database. If a particular DDL or "
+"DML statement is not overridden, the default Hypersonic configuration will "
+"be used for that statement."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:670
+#, no-c-format
+msgid "MaxParams"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:671
+#, no-c-format
+msgid ""
+"While loading messages, the persistence manager generates prepared "
+"statements with numerous parameters. This attribute defines the maximum "
+"number of parameters allowed per prepared statement. The default value is "
+"<literal>100</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:677
+#, no-c-format
+msgid "UseNDBFailoverStrategy"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:678
+#, no-c-format
+msgid ""
+"When some databases, such as MySQL, run in clustered environments, they can "
+"fail during database transaction commits. This can happen when the database "
+"node dies during the commit, so that the final transaction state is unknown. "
+"If <varname>UseNDBFailoverStrategy</varname> is set to <literal>true</"
+"literal>, the SQL statement will be re-executed in the event that the commit "
+"fails. If a further error occurs, the persistence manager assumes the error "
+"is due to the previous transaction having committed successfully, and "
+"ignores the error. By default, this attribute is set to <literal>false</"
+"literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:690
+#, no-c-format
+msgid "Configuring the JMS user manager"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:692
+#, no-c-format
+msgid ""
+"The JMS User Manager maps preconfigured client IDs to users. It also manages "
+"user and role tables, depending on the configured login module."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:696
+#, no-c-format
+msgid ""
+"The following is an example <literal>JMSUserManager</literal> configuration:"
+msgstr ""
+
+#. Tag: programlisting
+#: Configuration.xml:700
+#, no-c-format
+msgid ""
+"<![CDATA[\n"
+"<mbean code=\"org.jboss.jms.server.plugin.JDBCJMSUserManagerService\"\n"
+" name=\"jboss.messaging:service=JMSUserManager\"\n"
+" xmbean-dd=\"xmdesc/JMSUserManager-xmbean.xml\">\n"
+" <depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>\n"
+" <depends optional-attribute-name=\"TransactionManager\">\n"
+" jboss:service=TransactionManager\n"
+" </depends>\n"
+" <attribute name=\"DataSource\">java:/DefaultDS</attribute>\n"
+" <attribute name=\"CreateTablesOnStartup\">true</attribute>\n"
+" <attribute name=\"SqlProperties\">\n"
+" CREATE_USER_TABLE=CREATE TABLE JBM_USER (USER_ID VARCHAR(32) NOT NULL,\n"
+" PASSWD VARCHAR(32) NOT NULL, CLIENTID VARCHAR(128),\n"
+" PRIMARY KEY(USER_ID)) ENGINE = INNODB\n"
+" \n"
+" CREATE_ROLE_TABLE=CREATE TABLE JBM_ROLE (ROLE_ID VARCHAR(32) NOT NULL,\n"
+" USER_ID VARCHAR(32) NOT NULL, PRIMARY KEY(USER_ID, ROLE_ID))\n"
+" ENGINE = INNODB\n"
+" \n"
+" SELECT_PRECONF_CLIENTID=SELECT CLIENTID FROM JBM_USER WHERE USER_ID=?\n"
+" \n"
+" POPULATE.TABLES.1=INSERT INTO JBM_USER (USER_ID,PASSWD,CLIENTID)\n"
+" VALUES ('dilbert','dogbert','dilbert-id') \n"
+" </attribute>\n"
+"</mbean>\n"
+"]]>"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:703
+#, no-c-format
+msgid "JMSUserManager Managed Bean Attributes"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:708
+#, no-c-format
+msgid ""
+"When set to <literal>true</literal>, the JMS User Manager attempts to create "
+"tables (and indexes) upon startup. If the tables or indexes already exist, a "
+"<exceptionname>SQLException</exceptionname> is thrown and ignored, allowing "
+"the operation to continue. The default value is <literal>true</literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:716
+#, no-c-format
+msgid ""
+"If your database supports JDBC batch updates, set this to <literal>true</"
+"literal> to have the persistence manager group database updates into batches "
+"to improve performance. The default value is <literal>false</literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:724
+#, no-c-format
+msgid ""
+"Specifies the DDL and DML for the database. If this is not overridden, the "
+"default Hypersonic configuration will be used. You can also specify default "
+"user and role data. Specify any data to be inserted with property names "
+"prefixed with <literal>POPULATE.TABLES</literal>, as in the previous example."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:736
+#, no-c-format
+msgid "Configuring Destinations"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:739
+#, no-c-format
+msgid "Pre-configured destinations"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:741
+#, no-c-format
+msgid ""
+"JBoss Messaging ships with a default set of preconfigured destinations that "
+"are deployed as the server starts up. The configuration information for "
+"these destinations can be found in the following section of "
+"<filename>destinations-service.xml</filename>:"
+msgstr ""
+
+#. Tag: programlisting
+#: Configuration.xml:745
+#, no-c-format
+msgid ""
+"<![CDATA[\n"
+" <!--\n"
+" The Default Dead Letter Queue. This destination is a dependency \n"
+" of an EJB MDB container.\n"
+" -->\n"
+"\n"
+"<mbean code=\"org.jboss.jms.server.destination.QueueService\"\n"
+" name=\"jboss.messaging.destination:service=Queue,name=DLQ\"\n"
+" xmbean-dd=\"xmdesc/Queue-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+"</mbean>\n"
+"\n"
+"\n"
+"<mbean code=\"org.jboss.jms.server.destination.TopicService\"\n"
+" name=\"jboss.messaging.destination:service=Topic,name=testTopic\"\n"
+" xmbean-dd=\"xmdesc/Topic-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"SecurityConfig\">\n"
+" <security>\n"
+" <role name=\"guest\" read=\"true\" write=\"true\"/>\n"
+" <role name=\"publisher\" read=\"true\" write=\"true\" create=\"false\"/"
+">\n"
+" <role name=\"durpublisher\" read=\"true\" write=\"true\" create=\"true"
+"\"/>\n"
+" </security>\n"
+" </attribute>\n"
+"</mbean>\n"
+"\n"
+"<mbean code=\"org.jboss.jms.server.destination.TopicService\"\n"
+" name=\"jboss.messaging.destination:service=Topic,name=securedTopic\"\n"
+" xmbean-dd=\"xmdesc/Topic-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"SecurityConfig\">\n"
+" <security>\n"
+" <role name=\"publisher\" read=\"true\" write=\"true\" create=\"false\"/"
+">\n"
+" </security>\n"
+" </attribute>\n"
+"</mbean>\n"
+"\n"
+"\n"
+"<mbean code=\"org.jboss.jms.server.destination.QueueService\"\n"
+" name=\"jboss.messaging.destination:service=Queue,name=testQueue\"\n"
+" xmbean-dd=\"xmdesc/Queue-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"SecurityConfig\">\n"
+" <security>\n"
+" <role name=\"guest\" read=\"true\" write=\"true\"/>\n"
+" <role name=\"publisher\" read=\"true\" write=\"true\" create=\"false\"/"
+">\n"
+" <role name=\"noacc\" read=\"false\" write=\"false\" create=\"false\"/"
+">\n"
+" </security>\n"
+" </attribute>\n"
+"</mbean>\n"
+"\n"
+"<mbean code=\"org.jboss.jms.server.destination.QueueService\"\n"
+" name=\"jboss.messaging.destination:service=Queue,name=A\"\n"
+" xmbean-dd=\"xmdesc/Queue-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+"</mbean>\n"
+"\n"
+"\n"
+"<!-- It's possible for indiviual queues and topics to use a specific \n"
+" queue for an expiry or DLQ -->\n"
+"\n"
+"<mbean code=\"org.jboss.jms.server.destination.QueueService\"\n"
+" name=\"jboss.messaging.destination:service=Queue,name=PrivateDLQ\"\n"
+" xmbean-dd=\"xmdesc/Queue-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+"</mbean>\n"
+"\n"
+"<mbean code=\"org.jboss.jms.server.destination.QueueService\"\n"
+" name=\"jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue"
+"\"\n"
+" xmbean-dd=\"xmdesc/Queue-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+"</mbean>\n"
+"\n"
+"<mbean code=\"org.jboss.jms.server.destination.QueueService\"\n"
+" name=\"jboss.messaging.destination:service=Queue,\n"
+" name=QueueWithOwnDLQAndExpiryQueue\"\n"
+" xmbean-dd=\"xmdesc/Queue-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"DLQ\">\n"
+" jboss.messaging.destination:service=Queue,name=PrivateDLQ\n"
+" </attribute>\n"
+" <attribute name=\"ExpiryQueue\">\n"
+" jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue\n"
+" </attribute>\n"
+"</mbean>\n"
+"\n"
+"<mbean code=\"org.jboss.jms.server.destination.TopicService\"\n"
+" name=\"jboss.messaging.destination:service=Topic,\n"
+" name=TopicWithOwnDLQAndExpiryQueue\"\n"
+" xmbean-dd=\"xmdesc/Topic-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"DLQ\">\n"
+" jboss.messaging.destination:service=Queue,name=PrivateDLQ\n"
+" </attribute>\n"
+" <attribute name=\"ExpiryQueue\">\n"
+" jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue\n"
+" </attribute>\n"
+"</mbean>\n"
+"\n"
+"\n"
+"<mbean code=\"org.jboss.jms.server.destination.TopicService\"\n"
+" name=\"jboss.messaging.destination:service=Topic,\n"
+" name=TopicWithOwnRedeliveryDelay\"\n"
+" xmbean-dd=\"xmdesc/Topic-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"RedeliveryDelay\">5000</attribute>\n"
+"</mbean>\n"
+"\n"
+"\n"
+"<mbean code=\"org.jboss.jms.server.destination.TopicService\"\n"
+" name=\"jboss.messaging.destination:service=Topic,\n"
+" name=testDistributedTopic\"\n"
+" xmbean-dd=\"xmdesc/Topic-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+" <attribute name=\"Clustered\">true</attribute>\n"
+"</mbean>\n"
+"]]>"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:751
+#, no-c-format
+msgid "Configuring Queues"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:754
+#, no-c-format
+msgid "Queue MBean Attributes"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:757 Configuration.xml:980
+#, no-c-format
+msgid "Name"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:759
+#, no-c-format
+msgid "Defines the queue name."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:763 Configuration.xml:986
+#, no-c-format
+msgid "JNDIName"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:765
+#, no-c-format
+msgid "Defines the JNDI name that binds the queue."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:769 Configuration.xml:992
+#, no-c-format
+msgid "<title>DLQ</title>"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:771
+#, no-c-format
+msgid ""
+"Defines the DLQ (Dead Letter Queue) for this queue and overrides any value "
+"set in the Server Peer configuration file."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:775 Configuration.xml:998
+#, no-c-format
+msgid "ExpiryQueue"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:777
+#, no-c-format
+msgid ""
+"Defines the expiry queue and overrides any value set in the Server Peer "
+"configuration file."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:781 Configuration.xml:1004
+#, no-c-format
+msgid "RedeliveryDelay"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:783
+#, no-c-format
+msgid ""
+"Defines the redelivery delay to be applied to this queue and overrides any "
+"value set in the Server Peer configuration file."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:787 Configuration.xml:1010
+#, no-c-format
+msgid "MaxDeliveryAttempts"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:789
+#, no-c-format
+msgid ""
+"Defines the maximum number of times message delivery is attempted before the "
+"message is sent to the DLQ, if configured. The default value, <literal>-1</"
+"literal>, means that the value from the Server Peer configuration file is "
+"used. Any other setting will override the value set in the Server Peer "
+"configuration file."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:795 Configuration.xml:1018
+#, no-c-format
+msgid "Destination Security Configuration"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:797
+#, no-c-format
+msgid ""
+"<literal>SecurityConfig</literal> determines which roles can read, write and "
+"create upon the destination. It uses the same syntax and semantics as "
+"JBossMQ destination security configuration."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:800
+#, no-c-format
+msgid ""
+"The <literal>SecurityConfig</literal> element should contain one "
+"<literal><security></literal> element, which can contain multiple "
+"<literal><role></literal> elements. A <literal><role></literal> "
+"element defines the access type for that particular role."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:803
+#, no-c-format
+msgid ""
+"If the <varname>read</varname> attribute is set to <literal>true</literal>, "
+"then that role will be able to <emphasis>read</emphasis> (create consumers, "
+"receive messages, and browse) this destination."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:806
+#, no-c-format
+msgid ""
+"If the <varname>write</varname> attribute is set to <literal>true</literal>, "
+"then that role will be able to <emphasis>write</emphasis> (create producers "
+"or send messages) to this destination."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:809
+#, no-c-format
+msgid ""
+"If the <varname>create</varname> attribute is set to <literal>true</"
+"literal>, then that role will be able to create durable subscriptions on "
+"this destination."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:812
+#, no-c-format
+msgid ""
+"Configuring security for a destination is optional. If a "
+"<literal>SecurityConfig</literal> element is not specified, then the default "
+"security configuration from the Server Peer will be used instead."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:818 Configuration.xml:1044
+#, no-c-format
+msgid "Destination paging parameters"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:820 Configuration.xml:1046
+#, no-c-format
+msgid ""
+"<emphasis>Pageable Channels</emphasis> is a new feature available in JBoss "
+"Messaging."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:823 Configuration.xml:1049
+#, no-c-format
+msgid ""
+"Previously, for an application to support a queue or subscription, the queue "
+"needed to be stored entirely in memory. This was not always possible for "
+"very large queues or subscriptions."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:826 Configuration.xml:1052
+#, no-c-format
+msgid ""
+"<emphasis>Pageable Channels</emphasis> is a new JBoss Messaging feature that "
+"lets you specify a maximum number of messages to be stored in memory at one "
+"time, on a queue-by-queue or topic-by-topic basis. JBoss Messaging then "
+"pages messages to and from storage transparently in blocks. This allows "
+"queues and subscriptions to grow to very large sizes without any degradation "
+"in performance as channel size increases. It has been tested with queues in "
+"excess of ten million 2 kilobyte messages on very basic hardware, and has "
+"the potential to scale to much greater message numbers."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:829 Configuration.xml:1055
+#, no-c-format
+msgid ""
+"The individual parameters associated with pageable channels are as follows:"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:833 Configuration.xml:1059
+#, no-c-format
+msgid ""
+"<literal>FullSize</literal> defines the maximum number of messages held by "
+"the queue or topic subscription in memory at any one time. The actual queue "
+"can hold more messages, but these are paged to and from storage as messages "
+"are added or consumed. If no value is specified, the default is "
+"<literal>75000</literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:836 Configuration.xml:1062
+#, no-c-format
+msgid ""
+"<literal>PageSize</literal> defines the maximum number of messages that are "
+"pre-loaded per operation when loading messages from the queue or "
+"subscription. If no value is specified, the default is <literal>2000</"
+"literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:839 Configuration.xml:1065
+#, no-c-format
+msgid ""
+"<literal>DownCacheSize</literal> — when messages are paged to storage "
+"from the queue, they enter a <emphasis>Down Cache</emphasis> before being "
+"written to storage. This enables the write to occur as a single operation, "
+"which aids performance. This attribute determines the maximum number of "
+"messages that the Down Cache will hold before the messages are flushed to "
+"storage. If no value is specified, the default is <literal>2000</literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:842 Configuration.xml:1068
+#, no-c-format
+msgid ""
+"Paging parameters for temporary queues must be specified on the appropriate "
+"connection factory. See the section on Connection Factory Configuration for "
+"details."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:848 Configuration.xml:1074
+#, no-c-format
+msgid "CreatedProgrammatically"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:850
+#, no-c-format
+msgid ""
+"Returns <literal>true</literal> if the queue was created programmatically."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:855
+#, no-c-format
+msgid "MessageCount"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:857
+#, no-c-format
+msgid ""
+"Returns the total number of messages in the queue. That is, the number of "
+"messages being scheduled plus the number being delivered, plus the number "
+"not being delivered."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:861
+#, no-c-format
+msgid "ScheduledMessageCount"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:863
+#, no-c-format
+msgid ""
+"Returns the number of <emphasis>scheduled messages</emphasis> in the queue. "
+"This is the number of messages scheduled to be delivered at a later date."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:865
+#, no-c-format
+msgid ""
+"Scheduled delivery lets you specify the earliest time at which a particular "
+"message will be delivered. For example, you can send a message now, and "
+"specify that it will not be delivered for two hours. To do so, you would set "
+"the following in the message header:"
+msgstr ""
+
+#. Tag: programlisting
+#: Configuration.xml:869
+#, no-c-format
+msgid ""
+"long now = System.currentTimeMillis();\n"
+"\n"
+"Message msg = sess.createMessage(); \n"
+" \n"
+"msg.setLongProperty(JBossMessage.JMS_JBOSS_SCHEDULED_DELIVERY_PROP_NAME,\n"
+" now + 1000 * 60 * 60 * 2);\n"
+"\n"
+"prod.send(msg);"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:873 Configuration.xml:1082
+#, no-c-format
+msgid "MaxSize"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:875
+#, no-c-format
+msgid ""
+"Specifies the maximum number of messages that can be held in a queue. Any "
+"excess messages will be dropped. The default value is <literal>-1</literal>, "
+"which is unbounded."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:883
+#, no-c-format
+msgid ""
+"This attribute must be set to <literal>true</literal> if the destination is "
+"clustered."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:888
+#, no-c-format
+msgid "MessageCounter"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:890
+#, no-c-format
+msgid "Each queue maintains a message counter."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:894
+#, no-c-format
+msgid "MessageCounterStatistics"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:896
+#, no-c-format
+msgid "The statistics for the message counter."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:900 Configuration.xml:1098
+#, no-c-format
+msgid "MessageCounterHistoryDayLimit"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:902
+#, no-c-format
+msgid ""
+"The maximum number of days for which to hold message counter history. "
+"Overrides any value set in the Server Peer configuration file."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:906
+#, no-c-format
+msgid "ConsumerCount"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:908
+#, no-c-format
+msgid "The number of consumers currently consuming from the queue."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:913
+#, no-c-format
+msgid "Queue Managed Bean Operations"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:916 Configuration.xml:1163
+#, no-c-format
+msgid "RemoveAllMessages"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:918
+#, no-c-format
+msgid ""
+"Removes (and deletes) all messages from the queue. <emphasis>Use with "
+"caution, as this will permanently delete all messages from the queue.</"
+"emphasis>"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:924 Configuration.xml:1212
+#, no-c-format
+msgid "ListAllMessages"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:926
+#, no-c-format
+msgid ""
+"Lists all messages currently in the queue. Using a JMS selector as an "
+"argument in this operation lets you retrieve a subset of the messages in the "
+"queue that match the given criteria."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:932 Configuration.xml:1226
+#, no-c-format
+msgid "ListDurableMessages"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:934
+#, no-c-format
+msgid ""
+"Lists all <emphasis>durable</emphasis> messages in the queue. Using a JMS "
+"selector as an argument in this operation lets you retrieve a subset of "
+"messages in the queue that match the given criteria."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:940 Configuration.xml:1218
+#, no-c-format
+msgid "ListNonDurableMessages"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:942
+#, no-c-format
+msgid ""
+"Lists all <emphasis>non-durable</emphasis> messages in a queue. Using a JMS "
+"selector as an argument in this operation lets you retrieve a subset of "
+"messages in the queue that match the given criteria."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:948
+#, no-c-format
+msgid "ResetMessageCounter"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:950
+#, no-c-format
+msgid "Resets the message counter to zero."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:954
+#, no-c-format
+msgid "ResetMessageCounterHistory"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:956
+#, no-c-format
+msgid "Resets the message counter history."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:960
+#, no-c-format
+msgid "ListMessageCounterAsHTML"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:962
+#, no-c-format
+msgid "Lists the message counter in an easily-displayed HTML format."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:966
+#, no-c-format
+msgid "ListMessageCounterHistoryAsHTML"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:968
+#, no-c-format
+msgid "Lists the message counter history in an easily-displayed HTML format."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:974
+#, no-c-format
+msgid "Configuring Topics"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:977
+#, no-c-format
+msgid "Topic Managed Bean Attributes"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:982
+#, no-c-format
+msgid "Defines the name of the topic."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:988
+#, no-c-format
+msgid "Defines the JNDI location where the topic is bound."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:994
+#, no-c-format
+msgid ""
+"Defines the Dead Letter Queue (DLQ) used for this topic and overrides any "
+"value set in the Server Peer configuration file."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1000
+#, no-c-format
+msgid ""
+"Defines the expiry queue used for this topic and overrides any value set in "
+"the Server Peer configuration file."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1006
+#, no-c-format
+msgid ""
+"Defines the delay period between redelivery attempts for this topic and "
+"overrides any value set in the Server Peer configuration file."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1012
+#, no-c-format
+msgid ""
+"Defines the maximum number of times message delivery will be attempted "
+"before the message is sent to the DLQ, if configured. The default value is "
+"<literal>-1</literal>, which specifies that the value from the Server Peer "
+"configuration file be used. Any other setting overrides the Server Peer "
+"value."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1020
+#, no-c-format
+msgid ""
+"<literal>SecurityConfig</literal> lets you define which roles can read, "
+"write and create on the destination. The syntax matches that of the security "
+"configuration in JBossMQ destinations."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1024
+#, no-c-format
+msgid ""
+"The <literal>SecurityConfig</literal> element should contain one "
+"<literal><security></literal> element, which can contain multiple "
+"<literal><role></literal> elements. Each <literal><role></"
+"literal> element defines the access type for that particular role."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1028
+#, no-c-format
+msgid ""
+"If the <varname>read</varname> attribute is set to <literal>true</literal>, "
+"that role has permission to <emphasis>read</emphasis> (create consumers, "
+"receive messages, and browse) this destination."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1032
+#, no-c-format
+msgid ""
+"If the <varname>write</varname> attribute is set to <literal>true</literal>, "
+"that role has permission to <emphasis>write</emphasis> (create producers or "
+"send messages) to this destination."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1035
+#, no-c-format
+msgid ""
+"If the <varname>create</varname> attribute is set to <literal>true</"
+"literal>, that role has permission to create durable subscriptions on this "
+"destination."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1038
+#, no-c-format
+msgid ""
+"Configuring security for destinations is optional. If a "
+"<literal>SecurityConfig</literal> element is not specified, the default "
+"security configuration from the Server Peer will be used."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1076
+#, no-c-format
+msgid ""
+"Returns <literal>true</literal> if the topic was created programmatically."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1084
+#, no-c-format
+msgid ""
+"Specifies the maximum number of messages that can be held in a topic "
+"subscription. Any excess messages will be dropped from the topic. The "
+"default value is <literal>-1</literal>, which applies no size restriction."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1092
+#, no-c-format
+msgid "Set this to <literal>true</literal> if your destination is clustered."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1100
+#, no-c-format
+msgid ""
+"Defines the maximum number of days to retain message counter history, and "
+"overrides any value set in the Server Peer configuration file."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1107
+#, no-c-format
+msgid "Returns a list of message counters for the topic's subscriptions."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1113
+#, no-c-format
+msgid "AllMessageCount"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1115
+#, no-c-format
+msgid ""
+"Returns the total number of messages in all subscriptions belonging to the "
+"topic."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1121
+#, no-c-format
+msgid "DurableMessageCount"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1123
+#, no-c-format
+msgid ""
+"Returns the total number of <emphasis>durable</emphasis> messages in all "
+"subscriptions belonging to this topic."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1129
+#, no-c-format
+msgid "NonDurableMessageCount"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1131
+#, no-c-format
+msgid ""
+"Returns the total number of <emphasis>non-durable</emphasis> messages in all "
+"subscriptions belonging to this topic."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1137
+#, no-c-format
+msgid "AllSubscriptionsCount"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1139
+#, no-c-format
+msgid "Returns a count of all subscriptions belonging to this topic."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1145
+#, no-c-format
+msgid "DurableSubscriptionsCount"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1147
+#, no-c-format
+msgid "Returns a count of all durable subscriptions belonging to this topic."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1151
+#, no-c-format
+msgid "NonDurableSubscriptionsCount"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1153
+#, no-c-format
+msgid ""
+"Returns a count of all non-durable subscriptions belonging to this topic."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1160
+#, no-c-format
+msgid "Topic Managed Bean Operations"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1165
+#, no-c-format
+msgid ""
+"Removes and deletes all messages from the subscriptions belonging to this "
+"topic. <emphasis>Use with caution, as this permanently deletes all messages "
+"from the topic.</emphasis>"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1171
+#, no-c-format
+msgid "ListAllSubscriptions"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1173
+#, no-c-format
+msgid "Lists all subscriptions belonging to this topic."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1177
+#, no-c-format
+msgid "ListDurableSubscriptions"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1179
+#, no-c-format
+msgid "Lists all durable subscriptions belonging to this topic."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1183
+#, no-c-format
+msgid "ListNonDurableSubscriptions"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1185
+#, no-c-format
+msgid "Lists all non-durable subscriptions belonging to this topic."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1189
+#, no-c-format
+msgid "ListAllSubscriptionsAsHTML"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1191
+#, no-c-format
+msgid ""
+"Lists all subscriptions belonging to this topic in an easily-displayed HTML "
+"format."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1197
+#, no-c-format
+msgid "ListDurableSubscriptionsAsHTML"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1199
+#, no-c-format
+msgid ""
+"Lists all durable subscriptions belonging to this topic in an easily-"
+"displayed HTML format."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1205
+#, no-c-format
+msgid "ListNonDurableSubscriptionsAsHTML"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1207
+#, no-c-format
+msgid ""
+"Lists all non-durable subscriptions belonging to this topic in an easily-"
+"displayed HTML format."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1214
+#, no-c-format
+msgid ""
+"Lists all messages belonging to a specified subscription. Using a JMS "
+"selector as an argument in this operation lets you retrieve a subset of "
+"messages in the queue that match the given criteria."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1220
+#, no-c-format
+msgid ""
+"Lists all non-durable messages belonging to the specified subscription. "
+"Using a JMS selector as an argument in this operation lets you retrieve a "
+"subset of messages in the queue that match the given criteria."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1228
+#, no-c-format
+msgid ""
+"Lists all durable messages belonging to the specified subscription. Using a "
+"JMS selector as an argument in this operation lets you retrieve a subset of "
+"messages in the queue that match the given criteria."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1239
+#, no-c-format
+msgid "Configuring Connection Factories"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1241
+#, no-c-format
+msgid ""
+"By default, JBoss Messaging is configured to bind two connection factories "
+"in JNDI upon startup."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1245
+#, no-c-format
+msgid ""
+"The first connection factory is the default non-clustered connection "
+"factory, which is bound into the following JNDI contexts: <literal>/"
+"ConnectionFactory</literal>, <literal>/XAConnectionFactory</literal>, "
+"<literal>java:/ConnectionFactory</literal>, and <literal>java:/"
+"XAConnectionFactory</literal>. This connection factory is provided to "
+"maintain compatibility with applications originally written against JBossMQ, "
+"which does not include automatic failover or load balancing. If you do not "
+"require client-side automatic failover or load balancing, then you should "
+"use this first connection factory."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1248
+#, no-c-format
+msgid ""
+"The second connection factory is the default clustered connection factory, "
+"which is bound into the following JNDI contexts: <literal>/"
+"ClusteredConnectionFactory</literal>, <literal>/"
+"ClusteredXAConnectionFactory</literal>, <literal>java:/"
+"ClusteredConnectionFactory</literal>, and <literal>java:/"
+"ClusteredXAConnectionFactory</literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1251
+#, no-c-format
+msgid ""
+"You may want to configure additional connection factories — for "
+"example, if you want to provide a default client ID for a connection "
+"factory, or to bind a connection factory to a different JNDI location. To "
+"deploy a new connection factory, configure a new <literal>ConnectionFactory</"
+"literal> managed bean in <filename>connection-factories-service.xml</"
+"filename>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1254
+#, no-c-format
+msgid ""
+"You can also create a new service deployment descriptor, <filename><"
+"name>-service.xml</filename>, and deploy it in <filename>$JBOSS_HOME/"
+"server/messaging/deploy</filename>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1258
+#, no-c-format
+msgid ""
+"Enable support for automatic failover or load balancing by setting the "
+"relevant attributes in your connection factory:"
+msgstr ""
+
+#. Tag: programlisting
+#: Configuration.xml:1262
+#, no-c-format
+msgid ""
+"<![CDATA[\n"
+"<mbean code=\"org.jboss.jms.server.connectionfactory.ConnectionFactory\"\n"
+" name=\"jboss.messaging.connectionfactory:service=MyConnectionFactory\"\n"
+" xmbean-dd=\"xmdesc/ConnectionFactory-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends optional-attribute-name=\"Connector\">\n"
+" jboss.messaging:service=Connector,transport=bisocket\n"
+" </depends>\n"
+" <depends>jboss.messaging:service=PostOffice</depends>\n"
+"\n"
+" <attribute name=\"JNDIBindings\">\n"
+" <bindings>\n"
+" <binding>/MyConnectionFactory</binding>\n"
+" <binding>/factories/cf</binding>\n"
+" </bindings>\n"
+" </attribute>\n"
+" \n"
+" <attribute name=\"ClientID\">myClientID</attribute>\n"
+"\n"
+" <attribute name=\"SupportsFailover\">true</attribute>\n"
+" \n"
+" <attribute name=\"SupportsLoadBalancing\">false</attribute> \n"
+" \n"
+" <attribute name=\"LoadBalancingFactory\">\n"
+" org.acme.MyLoadBalancingFactory\n"
+" </attribute>\n"
+" \n"
+" <attribute name=\"PrefetchSize\">1000</attribute> \n"
+"\n"
+" <attribute name=\"SlowConsumers\">false</attribute>\n"
+" \n"
+" <attribute name=\"StrictTck\">true</attribute>\n"
+" \n"
+" <attribute name=\"SendAcksAsync\">false</attribute>\n"
+"\n"
+" <attribute name=\"DefaultTempQueueFullSize\">50000</attribute>\n"
+" \n"
+" <attribute name=\"DefaultTempQueuePageSize\">1000</attribute> \n"
+" \n"
+" <attribute name=\"DefaultTempQueueDownCacheSize\">1000</attribute> \n"
+" \n"
+" <attribute name=\"DupsOKBatchSize\">10000</attribute> \n"
+"</mbean>\n"
+"]]>"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1264
+#, no-c-format
+msgid ""
+"The example configuration would create a connection factory with the "
+"preconfigured client ID <literal>myClientID</literal>, which would be bound "
+"to two locations in the JNDI tree: <literal>/MyConnectionFactory</literal> "
+"and <literal>/factories/cf</literal>. This connection factory overrides the "
+"default values for <varname>PreFetchSize</varname>, "
+"<varname>DefaultTempQueueFullSize</varname>, "
+"<varname>DefaultTempQueuePageSize</varname>, "
+"<varname>DefaultTempQueueDownCacheSize</varname> and "
+"<varname>DupsOKBatchSize</varname>, <varname>SupportsFailover</varname>, "
+"<varname>SupportsLoadBalancing</varname> and <varname>LoadBalancingFactory</"
+"varname>. The connection factory will use the default remoting connector. To "
+"use a different remoting connector with the connection factory, change the "
+"<literal>Connector</literal> attribute to specify the service name of the "
+"connector you wish to use."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1269
+#, no-c-format
+msgid "ConnectionFactory Managed Bean Attributes"
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1272
+#, no-c-format
+msgid "ClientID"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1274
+#, no-c-format
+msgid ""
+"You can preconfigure a connection factory with a client ID. Any connection "
+"created via this connection factory will obtain this client ID."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1280
+#, no-c-format
+msgid "JNDIBindings"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1282
+#, no-c-format
+msgid "Lists available JNDI bindings for this connection factory."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1286
+#, no-c-format
+msgid "PrefetchSize"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1288
+#, no-c-format
+msgid ""
+"Specifies how many messages the window holds at once, for consumer flow "
+"control. The window size determines the number of messages a server can send "
+"to a consumer without blocking. Each consumer maintains a buffer of messages "
+"from which it consumes."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1291
+#, no-c-format
+msgid ""
+"Transmission Control Protocol (TCP) implements its own additional flow "
+"control. Message consumption can also be blocked if the TCP window size is "
+"smaller than the PrefetchSize parameter."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1297
+#, no-c-format
+msgid "SlowConsumers"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1299
+#, no-c-format
+msgid ""
+"The allowable buffer size for slow consumers should be minimized to increase "
+"the potential for messages to be consumed by faster consumers. It is not "
+"possible to totally disable buffering, however, setting the "
+"<varname>SlowConsumers</varname> attribute to <literal>true</literal> will "
+"reduce the buffer size. Setting this attribute to <literal>true</literal> is "
+"equivalent to setting <varname>PrefetchSize</varname> to <literal>1</"
+"literal> which is the lowest possible value available."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1305
+#, no-c-format
+msgid "StrictTck"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1307
+#, no-c-format
+msgid ""
+"When set to <literal>true</literal>, strict JMS behavior (as required by the "
+"Technology Compatibility Kit) is enabled."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1311
+#, no-c-format
+msgid "SendAcksAsync"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1313
+#, no-c-format
+msgid ""
+"When set to <literal>true</literal>, acknowledgments are sent "
+"asynchronously. This can improve performance, particularly if "
+"<literal>auto_acknowledge</literal> mode is active."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1319
+#, no-c-format
+msgid "Temporary queue paging parameters"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1321
+#, no-c-format
+msgid ""
+"<varname>DefaultTempQueueFullSize</varname>, "
+"<varname>DefaultTempQueuePageSize</varname> and "
+"<varname>DefaultTempQueueDownCacheSize</varname> are optional attributes. "
+"They determine the default paging parameters used for temporary destinations "
+"that are scoped to connections created with this connection factory. See the "
+"section on Paging Channels for further information about these values."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1324
+#, no-c-format
+msgid ""
+"<varname>DefaultTempQueueFullSize</varname> defaults to <literal>200000</"
+"literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1327
+#, no-c-format
+msgid ""
+"<varname>DefaultTempQueuePageSize</varname> and "
+"<varname>DefaultTempQueueDownCacheSize</varname> default to <literal>2000</"
+"literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1333
+#, no-c-format
+msgid "DupsOKBatchSize"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1335
+#, no-c-format
+msgid ""
+"For sessions that use the <literal>DUPS_OK_ACKNOWLEDGE</literal> mode, this "
+"setting determines the number of acknowledgments that will be buffered "
+"locally before they are sent. The default value is <literal>2000</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1341
+#, no-c-format
+msgid "SupportsLoadBalancing"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1343
+#, no-c-format
+msgid ""
+"When you use a connection factory with a clustered JBoss Messaging "
+"installation, client-side load balancing is determined by the "
+"<varname>supportsLoadBalancing</varname> attribute on the connection "
+"factory. If load balancing is enabled, any connection created by that "
+"connection factory will be load-balanced across the nodes of a cluster. A "
+"connection created on a particular node remains on that node."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1346
+#, no-c-format
+msgid ""
+"The <varname>LoadBalancingFactory</varname> attribute determines whether "
+"connections are load-balanced. The default value is <literal>false</literal>"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1354
+#, no-c-format
+msgid ""
+"When you use a connection factory with a clustered JBoss Messaging "
+"installation, automatic failover on the client side is determined by the "
+"<varname>supportsFailover</varname> attribute on the connection factory. If "
+"automatic failover is enabled, when a connection problem is detected, JBoss "
+"Messaging will automatically and transparently failover to another node in "
+"the cluster."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1357
+#, no-c-format
+msgid ""
+"If automatic failover is not required, set this attribute to <literal>false</"
+"literal>. (This is the default value.) When automatic failover is disabled, "
+"the user code is responsible for catching connection exceptions in "
+"synchronous JMS operations, and a JMS <literal>ExceptionListener</literal> "
+"must be installed to catch exceptions asynchronously. When an exception is "
+"caught, the client-side code should lookup a new connection factory via "
+"HAJNDI and recreate the connection."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1363
+#, no-c-format
+msgid "DisableRemotingChecks"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1365
+#, no-c-format
+msgid ""
+"By default, when deploying a connection factory, JBoss Messaging checks that "
+"the corresponding JBoss Remoting Connector has sensible values. JBoss "
+"Messaging is very sensitive to these values, and there is rarely any need to "
+"change them. To disable this sanity checking, set "
+"<varname>DisableRemotingChecks</varname> to <literal>false</literal> (the "
+"default value)."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1369
+#, no-c-format
+msgid ""
+"There is rarely a good reason to disable checking. Only do so if you are "
+"absolutely certain it must be done."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1376
+#, no-c-format
+msgid "LoadBalancingFactory"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1378
+#, no-c-format
+msgid ""
+"If your connection factory uses client-side load balancing, you can specify "
+"how this is implemented by overriding this attribute. The value must "
+"correspond to the name of a class that implements the interface <literal>org."
+"jboss.jms.client.plugin.LoadBalancingFactory</literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1381
+#, no-c-format
+msgid ""
+"The default value is <literal>org.jboss.jms.client.plugin."
+"RoundRobinLoadBalancingFactory</literal>, which load-balances connections "
+"across the cluster in a round-robin fashion."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1387
+#, no-c-format
+msgid "Connector"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1389
+#, no-c-format
+msgid ""
+"Specifies the remoting connector used by the connection factory. Different "
+"connection factories can use different connectors, so you can deploy one "
+"connection factory that uses the HTTP transport to communicate with the "
+"server, and another that uses the bisocket transport to communicate."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1395
+#, no-c-format
+msgid "EnableOrderingGroup"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1397
+#, no-c-format
+msgid ""
+"This parameter controls whether strict message ordering is enabled on the "
+"<literal>ConnectionFactory</literal>. If set to <literal>true</literal>, any "
+"messages sent from producers which are created from the enabled connection "
+"factory become ordering group messages. The default value for this parameter "
+"is <literal>false</literal>."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1403
+#, no-c-format
+msgid "DefaultOrderingGroupName"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1405
+#, no-c-format
+msgid ""
+"This is the default name for the message ordering group which will take "
+"effect once the <literal>EnableOrderingGroup</literal> parameter is set to "
+"<literal>true</literal> . If this attribute is missing, the group name will "
+"be generated automatically."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1417
+#, no-c-format
+msgid "Configuring the Remoting Connector"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1419
+#, no-c-format
+msgid ""
+"JBoss Messaging uses JBoss Remoting for all communication between the client "
+"and the server. (For further information about JBoss Remoting configuration "
+"and capabilities, see the JBoss Remoting documentation.)"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1422
+#, no-c-format
+msgid ""
+"The default configuration includes one remoting connector, which is used by "
+"the single default connection factory. Each connection factory can be "
+"configured to use a different connector."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1425
+#, no-c-format
+msgid ""
+"The default connector is configured to use the remoting bisocket transport, "
+"a TCP socket-based transport that listens and accepts connections only on "
+"the server side. That is, connections are always initiated from the client "
+"side. This connector is ideal for typical firewall scenarios, where only "
+"inbound connections are allowed on the server, or where only outbound "
+"connections are allowed from the client."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1428
+#, no-c-format
+msgid ""
+"The bisocket transport can be configured to use SSL when a higher level of "
+"security is required."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1431
+#, no-c-format
+msgid ""
+"The other supported transport is the HTTP transport, which uses the "
+"Hypertext Transfer Protocol to communicate between client and server. The "
+"client periodically polls the server for messages to receive data. This "
+"transport is ideal when a firewall between server and client allows only "
+"incoming HTTP traffic on the server. Because of its polling behavior and the "
+"HTTP, this transport does not perform as well as the bisocket transport. It "
+"is not designed to handle high-load situations."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1434
+#, no-c-format
+msgid ""
+"No other remoting transports are currently supported by JBoss Messaging."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1438
+#, no-c-format
+msgid ""
+"Remoting configuration details can be seen in <filename>$JBOSS_HOME/server/"
+"$SERVER/deploy/jboss-messaging/remoting-bisocket-service.xml</filename>. The "
+"following code is an example of a bisocket remoting configuration:"
+msgstr ""
+
+#. Tag: programlisting
+#: Configuration.xml:1443
+#, no-c-format
+msgid ""
+"<![CDATA[ \n"
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"\n"
+"<!--\n"
+" Standard bisocket-based Remoting service deployment descriptor.\n"
+"\n"
+" $Id: remoting-bisocket-service.xml 3981 2008-03-28 18:00:41Z tf $\n"
+"-->\n"
+"\n"
+"<server>\n"
+"\n"
+" <!-- Standard bisocket connector - the bisocket transport only opens \n"
+" connection from client->server so can be used with firewalls where\n"
+" only outgoing connections are allowed. For examples of HTTP and \n"
+" SSL transports see docs/examples -->\n"
+" <mbean code=\"org.jboss.remoting.transport.Connector\"\n"
+" name=\"jboss.messaging:service=Connector,transport=bisocket\"\n"
+" display-name=\"Bisocket Transport Connector\">\n"
+" <attribute name=\"Configuration\">\n"
+" <config>\n"
+" <invoker transport=\"bisocket\">\n"
+" \n"
+" <!-- There should be no reason to change these parameters - "
+"warning!\n"
+" Changing them may stop JBoss Messaging working correctly --"
+"> \n"
+" <attribute name=\"marshaller\" isParam=\"true\">\n"
+" org.jboss.jms.wireformat.JMSWireFormat\n"
+" </attribute>\n"
+" <attribute name=\"unmarshaller\" isParam=\"true\">\n"
+" org.jboss.jms.wireformat.JMSWireFormat\n"
+" </attribute>\n"
+" <attribute name=\"dataType\" isParam=\"true\">\n"
+" jms\n"
+" </attribute>\n"
+" <attribute name=\"socket.check_connection\" isParam=\"true\">\n"
+" false\n"
+" </attribute> \n"
+" <attribute name=\"serverBindAddress\">\n"
+" ${jboss.bind.address}\n"
+" </attribute>\n"
+" <attribute name=\"serverBindPort\">\n"
+" ${jboss.messaging.connector.bisocket.port:4457}\n"
+" </attribute>\n"
+" <attribute name=\"clientSocketClass\" isParam=\"true\">\n"
+" org.jboss.jms.client.remoting.ClientSocketWrapper\n"
+" </attribute>\n"
+" <attribute name=\"serverSocketClass\">\n"
+" org.jboss.jms.server.remoting.ServerSocketWrapper\n"
+" </attribute>\n"
+" <attribute name=\"onewayThreadPool\">\n"
+" org.jboss.jms.server.remoting.DirectThreadPool\n"
+" </attribute>\n"
+"\n"
+" <!-- the following parameters are useful when there is a \n"
+" firewall between client and server. Uncomment them if so.-->\n"
+" <!-- \n"
+" <attribute name=\"numberOfCallRetries\" isParam=\"true\">\n"
+" 5\n"
+" </attribute>\n"
+" <attribute name=\"pingFrequency\" isParam=\"true\">\n"
+" 30000\n"
+" </attribute>\n"
+" <attribute name=\"pingWindowFactor\" isParam=\"true\">\n"
+" 71582\n"
+" </attribute>\n"
+" <attribute name=\"generalizeSocketException\" isParam=\"true\">\n"
+" true\n"
+" </attribute>\n"
+" -->\n"
+"\n"
+" <!-- Now remoting supports socket write timeout configuration. \n"
+" Uncomment this if you need it. -->\n"
+" <!-- \n"
+" <attribute name=\"writeTimeout\" isParam=\"true\">30000</attribute>\n"
+" -->\n"
+"\n"
+" <!-- End immutable parameters -->\n"
+" \n"
+" <attribute name=\"stopLeaseOnFailure\" isParam=\"true\">true</"
+"attribute>\n"
+" \n"
+" <!-- Periodicity of client pings. Server window by default \n"
+" is twice this figure --> \n"
+" <attribute name=\"clientLeasePeriod\" isParam=\"true\">\n"
+" 10000\n"
+" </attribute>\n"
+" <attribute name=\"validatorPingPeriod\" isParam=\"true\">\n"
+" 10000\n"
+" </attribute>\n"
+" <attribute name=\"validatorPingTimeout\" isParam=\"true\">\n"
+" 5000\n"
+" </attribute>\n"
+"\n"
+" attribute name=\"failureDisconnectTimeout\" isParam=\"true\">\n"
+" 0\n"
+" </attribute>\n"
+" <attribute name=\"callbackErrorsAllowed\">1</attribute>\n"
+" <attribute name=\"registerCallbackListener\">false</attribute>\n"
+" <attribute name=\"useClientConnectionIdentity\" isParam=\"true\">\n"
+" true\n"
+" </attribute>\n"
+" \n"
+" <attribute name=\"timeout\" isParam=\"true\">0</attribute>\n"
+"\n"
+" <!-- Max Number of connections in client pool. This should be \n"
+" significantly higher than the max number of sessions/\n"
+" consumers you expect -->\n"
+" <attribute name=\"JBM_clientMaxPoolSize\" isParam=\"true\">\n"
+" 200\n"
+" </attribute>\n"
+" \n"
+" <!-- The maximum time to wait before timing out on trying to \n"
+" write a message to socket for delivery -->\n"
+" <attribute name=\"callbackTimeout\">\n"
+" 10000\n"
+" </attribute> \n"
+" \n"
+" <!-- Use these parameters to specify values for binding and \n"
+" connecting control connections to work with your \n"
+" firewall/NAT configuration\n"
+" <attribute name=\"secondaryBindPort\">xyz</"
+"attribute> \n"
+" <attribute name=\"secondaryConnectPort\">abc</attribute> \n"
+" -->\n"
+" \n"
+" </invoker>\n"
+" <handlers>\n"
+" <handler subsystem=\"JMS\">\n"
+" org.jboss.jms.server.remoting.JMSServerInvocationHandler\n"
+" </handler>\n"
+" </handlers>\n"
+" </config>\n"
+" </attribute>\n"
+" </mbean>\n"
+"\n"
+"</server>\n"
+"]]>"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1446
+#, no-c-format
+msgid ""
+"Some attributes should not be changed unless you know exactly what you are "
+"doing. Attributes that can be changed include:"
+msgstr ""
+
+#. Tag: varname
+#: Configuration.xml:1452
+#, no-c-format
+msgid "clientLeasePeriod"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1454
+#, no-c-format
+msgid ""
+"Clients periodically return <emphasis>heartbeats</emphasis> to the server to "
+"confirm that they are still active. If the server does not receive a "
+"heartbeat after a certain period of time, it will close down the connection "
+"and remove all resources that correspond to the client's session. The "
+"<varname>clientLeasePeriod</varname> determines the period of time between "
+"heartbeats, in milliseconds. The default value is <literal>10000</literal>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1457
+#, no-c-format
+msgid ""
+"By default, the server closes a client if it does not receive a heartbeat "
+"within double the <varname>clientLeasePeriod</varname>. In reality, the "
+"period is automatically resized according to system load."
+msgstr ""
+
+#. Tag: varname
+#: Configuration.xml:1463
+#, no-c-format
+msgid "numberOfRetries"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1465
+#, no-c-format
+msgid ""
+"The number of seconds JBoss Remoting blocks on the client pool while waiting "
+"for a connection to become available. If you have a very large number of "
+"sessions concurrently accessing the server from a client and cannot obtain "
+"connections from the pool, you may want to increase this value."
+msgstr ""
+
+#. Tag: varname
+#: Configuration.xml:1471
+#, no-c-format
+msgid "clientMaxPoolSize"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1473
+#, no-c-format
+msgid ""
+"JBoss Remoting maintains a client-side pool of TCP connections on which to "
+"service requests. If you have a large number of sessions concurrently "
+"accessing the server from a client and cannot obtain connections from the "
+"pool, you may want to increase this value."
+msgstr ""
+
+#. Tag: varname
+#: Configuration.xml:1479
+#, no-c-format
+msgid "secondaryBindPort"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1481
+#, no-c-format
+msgid ""
+"The bisocket transport uses control connections to pass control messages "
+"between server and client. This attribute defines the address to which the "
+"secondary <literal>ServerSocket</literal> is bound. To work behind a "
+"firewall, you may need to specify a particular value for your firewall "
+"configuration."
+msgstr ""
+
+#. Tag: varname
+#: Configuration.xml:1487
+#, no-c-format
+msgid "secondaryConnectPort"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1489
+#, no-c-format
+msgid ""
+"The port that the client uses to connect. Specify this to let your client "
+"work with NAT routers."
+msgstr ""
+
+#. Tag: varname
+#: Configuration.xml:1495
+#, no-c-format
+msgid "maxPoolSize"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1497
+#, no-c-format
+msgid "The number of threads used on the server side to service requests."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1502
+#, no-c-format
+msgid ""
+"By default, JBoss Messaging binds to <literal>${jboss.bind.address}</"
+"literal>, which can be defined by running the <command>./run.sh -c <"
+"yourconfig> -b yourIP</command> command."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1505
+#, no-c-format
+msgid ""
+"If necessary, you can change <filename>remoting-bisocket-service.xml</"
+"filename> to use a different communication port."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1509
+#, no-c-format
+msgid ""
+"There is rarely a good reason to change values in the bisocket or "
+"sslbisocket connector configuration other than those listed previously. "
+"Changing other values can cause JBoss Messaging to stop functioning "
+"correctly."
+msgstr ""
+
+#. Tag: title
+#: Configuration.xml:1518
+#, no-c-format
+msgid "ServiceBindingManager"
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1520
+#, no-c-format
+msgid ""
+"The <literal>SeviceBindingManager</literal> provides multiple application "
+"server instances running on the same IP using different port ranges, which "
+"is useful during development. There are other ways to do this, but the "
+"<literal>ServiceBindingManager</literal> removes much hassle."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1523
+#, no-c-format
+msgid ""
+"In JBoss Messaging 4.x, the remoting configurations must match those defined "
+"in <filename>remoting-bisocket-service.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1526
+#, no-c-format
+msgid ""
+"If you are using a more recent version of JBoss Messaging in an older "
+"version of the JBoss Application Server, the example bindings in the "
+"Application Server distribution may be out of date. The relevant sections "
+"must therefore be overwritten with the remoting configuration from the JBoss "
+"Messaging distribution."
+msgstr ""
+
+#. Tag: para
+#: Configuration.xml:1529
+#, no-c-format
+msgid ""
+"See the Installation chapter for further information about setting up the "
+"<literal>ServiceBindingManager</literal> for JBoss Messaging."
+msgstr ""
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Getting_Started.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Getting_Started.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Getting_Started.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,39 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Getting_Started.xml:3
+#, no-c-format
+msgid "Download Software"
+msgstr ""
+
+#. Tag: para
+#: Getting_Started.xml:4
+#, no-c-format
+msgid ""
+"The official JBoss Messaging project page can be found at <ulink url="
+"\"http://labs.jboss.com/jbossmessaging\">http://labs.jboss.com/"
+"jbossmessaging/</ulink>."
+msgstr ""
+
+#. Tag: para
+#: Getting_Started.xml:7
+#, no-c-format
+msgid ""
+"You can download JBoss Messaging from the JBoss Labs Messaging Project "
+"download zone: <ulink url=\"http://labs.jboss.com/jbossmessaging/\">http://"
+"labs.jboss.com/jbossmessaging/downloads</ulink>"
+msgstr ""
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Installation.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Installation.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Installation.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,30 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Installation.xml:3
+#, no-c-format
+msgid "JBoss Messaging Installation"
+msgstr ""
+
+#. Tag: para
+#: Installation.xml:5
+#, no-c-format
+msgid ""
+"JBoss Enterprise Application Platform (EAP) comes with JBoss Messaging pre-"
+"installed as the default JMS provider. If you are using EAP version 4.3 or "
+"higher, there is no need to manually install JBoss Messaging."
+msgstr ""
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Introduction.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Introduction.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Introduction.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,412 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Introduction.xml:3
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:5
+#, no-c-format
+msgid ""
+"JBoss Messaging provides an open-source and standards-based messaging "
+"platform to bring enterprise-class messaging to the mass market."
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:9
+#, no-c-format
+msgid ""
+"JBoss Messaging implements a robust, high-performance messaging core "
+"designed to support Service-Oriented Architectures (SOAs), Enterprise "
+"Service Buses (ESBs), and other integration requirements regardless of the "
+"level of demand."
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:13
+#, no-c-format
+msgid ""
+"JBoss Messaging lets you distribute application load evenly across your "
+"cluster. It balances each node's CPU cycles with no single point of failure, "
+"providing a highly scalable and performant clustering implementation."
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:17
+#, no-c-format
+msgid ""
+"JBoss Messaging includes a Java Messaging Service (JMS) front-end so that "
+"messages are delivered in a standards-based format, and to enable support "
+"for other messaging protocols in the future."
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:22
+#, no-c-format
+msgid "JBoss Messaging Features"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:24
+#, no-c-format
+msgid "JBoss Messaging provides the following features:"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:28
+#, no-c-format
+msgid ""
+"A Sun-certified implementation of Java Messaging Service 1.1, which "
+"currently works with the standard installation of JBoss Enterprise "
+"Application Platform version 4.2 or later."
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:34
+#, no-c-format
+msgid ""
+"A strong focus on performance, reliability and scalability with high "
+"throughput and low latency."
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:40
+#, no-c-format
+msgid ""
+"A foundation for JBoss ESB for SOA initiatives. (JBoss ESB uses JBoss "
+"Messaging as its default JMS provider.)"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:46
+#, no-c-format
+msgid "JBoss Messaging also includes:"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:50
+#, no-c-format
+msgid "publish-subscribe and point-to-point messaging models;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:54
+#, no-c-format
+msgid "persistent and non-persistent messages;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:58
+#, no-c-format
+msgid ""
+"guaranteed message delivery that ensures messages arrive once and only once "
+"where required;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:62
+#, no-c-format
+msgid "a transactional and reliable interface that supports ACID semantics;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:66
+#, no-c-format
+msgid "a customizable JAAS-based security framework;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:70
+#, no-c-format
+msgid ""
+"complete integration with JBoss Transactions (previously Arjuna JTA) to "
+"support full transaction recovery;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:74
+#, no-c-format
+msgid "an extensive JMX management interface;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:78
+#, no-c-format
+msgid ""
+"support for most major databases, including Oracle, DB2, Sybase, Microsoft "
+"SQL Server, PostgreSQL and MySQL;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:82
+#, no-c-format
+msgid "HTTP transport, for use with firewalls that allow only HTTP traffic;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:87
+#, no-c-format
+msgid "servlet transport to allow messaging through a dedicated servlet;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:92
+#, no-c-format
+msgid "SSL transport;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:96
+#, no-c-format
+msgid "configurable DLQs (Dead Letter Queues) and Expiry Queues;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:100
+#, no-c-format
+msgid ""
+"message statistics; which provide a rolling historical view of the messages "
+"delivered to queues and subscriptions;"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:104
+#, no-c-format
+msgid ""
+"the automatic paging of messages to storage, which lets you use very large "
+"queues that would be too large to fit entirely within system memory."
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:108
+#, no-c-format
+msgid ""
+"strict message ordering which results in messages belonging to a particular "
+"message group being delivered according to the order of their arrival at the "
+"target queue."
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:114
+#, no-c-format
+msgid "JBoss Messaging also includes the following clustering features:"
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:119
+#, no-c-format
+msgid "Fully-clustered queues and topics"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:120
+#, no-c-format
+msgid ""
+"<emphasis>Logical</emphasis> queues and topics are distributed across the "
+"cluster. You can send or receive a queue or topic to or from any node on the "
+"cluster."
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:128
+#, no-c-format
+msgid "Fully-clustered durable subscriptions"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:129
+#, no-c-format
+msgid ""
+"A particular durable subscription can be accessed from any node of the "
+"cluster, letting you spread processing load from that subscription across "
+"the entire cluster."
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:137
+#, no-c-format
+msgid "Fully-clustered temporary queues"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:138
+#, no-c-format
+msgid ""
+"If a sent message includes the <literal>replyTo</literal> of a temporary "
+"queue, it can be returned on any node of the cluster."
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:146
+#, no-c-format
+msgid "Intelligent message redistribution"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:147
+#, no-c-format
+msgid ""
+"Messages are automatically moved between nodes of the cluster to take "
+"advantage of different consumer speeds on different nodes. This helps to "
+"prevent starvation or build-up of messages on a particular node."
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:155
+#, no-c-format
+msgid "Message order protection"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:156
+#, no-c-format
+msgid ""
+"Enable this to ensure that the order of messages produced by a producer is "
+"identical to the order of messages consumed by a consumer. This works even "
+"if message redistribution is active."
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:164
+#, no-c-format
+msgid "Completely transparent failover"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:165
+#, no-c-format
+msgid ""
+"When a server fails, your sessions continue exception-free on a new node. "
+"This is also completely configurable: if you do not want to implement this "
+"failover behavior, you can disable it and fall back to exceptions being "
+"thrown and manually recreating connections on a new node."
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:173
+#, no-c-format
+msgid "High availability and seamless failover"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:174
+#, no-c-format
+msgid ""
+"If the node fails, you will automatically failover to a different node "
+"without losing any persistent messages and can seamlessly continue your "
+"session. <emphasis>Once and only once</emphasis> delivery of persistent "
+"messages is respected at all times."
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:182
+#, no-c-format
+msgid "Message bridge"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:183
+#, no-c-format
+msgid ""
+"JBoss Messaging contains a message bridge component, which lets you bridge "
+"messages between any two JMS 1.1 destinations. This lets you connect "
+"geographically separate clusters and form large, globally-distributed "
+"logical queues and topics."
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:192
+#, no-c-format
+msgid "Compatibility with JBoss MQ"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:194
+#, no-c-format
+msgid ""
+"JBoss MQ was the JMS implementation shipped with Enterprise Application "
+"Platform 4.2. Since JBoss Messaging is compatible with both JMS 1.1 and JMS "
+"1.0.2b, the JMS code written against JBoss MQ will run with JBoss Messaging "
+"without any further changes."
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:198
+#, no-c-format
+msgid ""
+"JBoss Messaging has no wire format compatibility with JBoss MQ. It is "
+"therefore necessary to upgrade JBoss MQ clients with JBoss Messaging client "
+"JARs."
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:203
+#, no-c-format
+msgid ""
+"Although JBoss Messaging deployment descriptors are similar to JBoss MQ "
+"deployment descriptors, they are <emphasis>not identical</emphasis>, and "
+"will require some simple adjustments before they will work with JBoss "
+"Messaging. The database data model is completely different, so JBoss "
+"Messaging should not be used with a JBoss MQ data schema, or vice-versa."
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:210
+#, no-c-format
+msgid "System Properties used by JBoss Messaging"
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:213
+#, no-c-format
+msgid "support.bytesId"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:215
+#, no-c-format
+msgid ""
+"This system property controls the default behavior when constructing a "
+"<literal>JBossMessage</literal> object from a foreign message object. If "
+"this property is set to <literal>true</literal>, the <literal>JBossMessage</"
+"literal> constructor will try to extract the native byte[] correlation ID "
+"from the foreign message headers. If set to <literal>false</literal>, it "
+"will use the normal string type <literal>JMSCorrelationID</literal>. This "
+"property will default to <literal>true</literal> if not set or when set to "
+"something other than <literal>true</literal> or <literal>false</literal>."
+msgstr ""
+
+#. Tag: title
+#: Introduction.xml:221
+#, no-c-format
+msgid "retain.oldxabehaviour"
+msgstr ""
+
+#. Tag: para
+#: Introduction.xml:223
+#, no-c-format
+msgid ""
+"This system property controls the type of exception thrown by a JMS "
+"XAResource in the event that the prepar() method is called after the "
+"connection is broken. If this property is not defined, an "
+"<literal>XAException</literal> with an <literal>XA_RBCOMMFAIL</literal> "
+"error code will be thrown. Otherwise an <literal>XAException</literal> with "
+"an <literal>XA_RETRY</literal> error code will be thrown. It should be noted "
+"that JBoss Messaging does not define this property by default."
+msgstr ""
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/JBoss_Messaging_User_Guide.pot
===================================================================
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Ordering_Group.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Ordering_Group.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Ordering_Group.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,395 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Ordering_Group.xml:3
+#, no-c-format
+msgid "Enabling JBoss Messaging Ordering Group"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:5
+#, no-c-format
+msgid ""
+"This section describes how to use the JBoss Messaging ordering group feature "
+"to achieve strict message ordering."
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:9
+#, no-c-format
+msgid ""
+"Message ordering groups is the JBoss Messaging implementation of strict "
+"message ordering. When the ordering group feature is enabled, message "
+"priorities no longer have an influence on the order that the messages are "
+"delivered. Messages in a particular ordering group will be delivered in the "
+"exact order that they arrive at the target queue (FIFO)."
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:13
+#, no-c-format
+msgid ""
+"Ordering groups are identified by their string names and obey the following "
+"rules:"
+msgstr ""
+
+#. Tag: title
+#: Ordering_Group.xml:17
+#, no-c-format
+msgid "Rule One"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:18
+#, no-c-format
+msgid ""
+"The messages that form a part of an ordering group are delivered one at a "
+"time. The next message will not be delivered until the delivery of a "
+"previous message is completed. Message delivery completion is signaled by "
+"various means, depending on the acknowledge mode settings;"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:25
+#, no-c-format
+msgid ""
+"The <literal>CLIENT_ACKNOWLEDGE</literal> mode results in the "
+"<classname>Message</classname>.<methodname>acknowledge()</methodname> method "
+"signaling the completion state."
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:30
+#, no-c-format
+msgid ""
+"The <literal>AUTO_ACKNOWLEDGE</literal> and <literal>DUPS_OK_ACKNOWLEDGE</"
+"literal> modes result in the completion of the message being identified by "
+"either of the following;"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:35
+#, no-c-format
+msgid ""
+"a successful return from one of the <classname>MessageConsumer</classname>."
+"<methodname>receive()</methodname> methods, or"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:40
+#, no-c-format
+msgid ""
+"a successful return from the <methodname>onMessage()</methodname> call of "
+"the <literal>MessageListener()</literal>."
+msgstr ""
+
+#. Tag: title
+#: Ordering_Group.xml:48 Ordering_Group.xml:139
+#, no-c-format
+msgid "Note"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:49
+#, no-c-format
+msgid ""
+"If the message consumer is closed, the message being processed at the time "
+"of its closure will be deemed as completed. This is regardless of whether an "
+"<literal>*_ACKNOWLEGE</literal> is called prior to the closure of the "
+"consumer."
+msgstr ""
+
+#. Tag: title
+#: Ordering_Group.xml:60
+#, no-c-format
+msgid "Rule Two"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:61
+#, no-c-format
+msgid ""
+"In the case of the transactional receipt of messages, the next message will "
+"not be delivered until the transaction has been committed which includes the "
+"acknowledgment of the receipt of the current message. If the transaction is "
+"rolled back, the message will be canceled, sent back to the JMS server and "
+"made available for the next delivery."
+msgstr ""
+
+#. Tag: title
+#: Ordering_Group.xml:67
+#, no-c-format
+msgid "How to Enable Message Ordering Group"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:69
+#, no-c-format
+msgid ""
+"JBoss Messaging ordering group may be enabled by one of two means. Either "
+"using the API or by making configuration changes."
+msgstr ""
+
+#. Tag: title
+#: Ordering_Group.xml:74
+#, no-c-format
+msgid "Enabling with the API"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:75
+#, no-c-format
+msgid ""
+"To make use of JBoss Messaging's ordering group feature, it is necessary to "
+"create a <classname>JBossMessageProducer</classname> as demonstrated in the "
+"following code sample:"
+msgstr ""
+
+#. Tag: programlisting
+#: Ordering_Group.xml:80
+#, no-c-format
+msgid ""
+"JBossMessageProducer producer=(JBossMessageProducer)session.createProducer"
+"(queue);"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:82
+#, no-c-format
+msgid ""
+"Once created, JBossMessageProducer provides two methods for starting and "
+"ending an ordering group."
+msgstr ""
+
+#. Tag: title
+#: Ordering_Group.xml:83
+#, no-c-format
+msgid "enableOrderingGroup()"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:84
+#, no-c-format
+msgid ""
+"The following code sample demonstrates how to create an ordering group with "
+"the name <literal>ogrpName</literal>."
+msgstr ""
+
+#. Tag: programlisting
+#: Ordering_Group.xml:89
+#, no-c-format
+msgid "public void enableOrderingGroup(String ogrpName) throws JMSException"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:90
+#, no-c-format
+msgid ""
+"Once called, the producer will send messages on behalf of the ordering "
+"group. If a <literal>null</literal> parameter is supplied, the name of the "
+"ordering group will be automatically generated. Calling this method more "
+"than once will override any previous method calls."
+msgstr ""
+
+#. Tag: title
+#: Ordering_Group.xml:94
+#, no-c-format
+msgid "disableOrderingGroup()"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:95
+#, no-c-format
+msgid ""
+"The following code samples demonstrates how to stop producing ordering group "
+"messages."
+msgstr ""
+
+#. Tag: programlisting
+#: Ordering_Group.xml:100
+#, no-c-format
+msgid "public void disableOrderingGroup() throws JMSException"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:101
+#, no-c-format
+msgid ""
+"Once called, the producer will stop sending out ordering group messages and "
+"resume its default behavior."
+msgstr ""
+
+#. Tag: title
+#: Ordering_Group.xml:106
+#, no-c-format
+msgid "Configuration Changes"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:107
+#, no-c-format
+msgid ""
+"Users can configure a JBoss Messaging connection factory to enable the "
+"ordering group feature. To achieve this, two new attributes are added to the "
+"factory service configuration file. These are:"
+msgstr ""
+
+#. Tag: literal
+#: Ordering_Group.xml:114
+#, no-c-format
+msgid "EnableOrderingGroup;"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:118
+#, no-c-format
+msgid ""
+"set this property to <literal>true</literal> to enable the ordering group "
+"feature. The default value for this property is <literal>false</literal>."
+msgstr ""
+
+#. Tag: literal
+#: Ordering_Group.xml:126
+#, no-c-format
+msgid "DefaultOrderingGroupName;"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:130
+#, no-c-format
+msgid ""
+"the default name for the message ordering group. The group name will be "
+"generated automatically if this attribute is missing."
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:140
+#, no-c-format
+msgid ""
+"Once configured to enable the ordering group feature on a connection "
+"factory, all messages that are sent from any producers created from the "
+"connection factory become ordering group messages."
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:144
+#, no-c-format
+msgid ""
+"The following factory service configuration file sample demonstrates how to "
+"enable the ordering group feature:"
+msgstr ""
+
+#. Tag: programlisting
+#: Ordering_Group.xml:146
+#, no-c-format
+msgid ""
+"<![CDATA[\n"
+"<mbean code=\"org.jboss.jms.server.connectionfactory.ConnectionFactory\";\n"
+" name=\"jboss.messaging.connectionfactory:service=ConnectionFactory\";\n"
+" xmbean-dd=\"xmdesc/ConnectionFactory-xmbean.xml\">\n"
+" <depends optional-attribute-name=\"ServerPeer\">\n"
+" jboss.messaging:service=ServerPeer\n"
+" </depends>\n"
+" <depends optional-attribute-name=\"Connector\">\n"
+" jboss.messaging:service=Connector,transport=bisocket\n"
+" </depends>\n"
+" <depends>\n"
+" jboss.messaging:service=PostOffice\n"
+" </depends>\n"
+"\n"
+" <attribute name=\"JNDIBindings\">\n"
+" <bindings>\n"
+" <binding>/MyConnectionFactory</binding>\n"
+" <binding>/XAConnectionFactory</binding>\n"
+" <binding>java:/MyConnectionFactory</binding>\n"
+" <binding>java:/XAConnectionFactory</binding>\n"
+" </bindings>\n"
+" </attribute>\n"
+" \n"
+" <!-- This are the two properties -->\n"
+" <attribute name=\"EnableOrderingGroup\">true</attribute>\n"
+" <attribute name=\"DefaultOrderingGroupName\">MyOrderingGroup</attribute>\n"
+"</mbean>\n"
+"]]>"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:148
+#, no-c-format
+msgid ""
+"The advantage of enabling the ordering group feature by making configuration "
+"changes is the ease with which message ordering functionality can be "
+"achieved without the need for code changes."
+msgstr ""
+
+#. Tag: title
+#: Ordering_Group.xml:156
+#, no-c-format
+msgid "Notes and Limitations"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:157
+#, no-c-format
+msgid ""
+"The following points should be noted in regard to ordering group "
+"functionality:"
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:163
+#, no-c-format
+msgid ""
+"Queues must be used with the ordering group feature. The feature will not "
+"work with topics."
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:168
+#, no-c-format
+msgid ""
+"The ordering group feature should not be used in conjunction with message "
+"selectors and scheduled delivery."
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:173
+#, no-c-format
+msgid ""
+"A message is considered completed, and the next message will be available "
+"for delivery, if the original message is dead or has expired. A dead message "
+"is moved to the <literal>DLQ</literal> whereas an expired message is moved "
+"to the <literal>ExpiryQueue</literal>."
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:178
+#, no-c-format
+msgid ""
+"When using a <literal>ConnectionConsumer</literal>, the ordering of the "
+"messages will be observed. However, the <literal>ConnectionConsumer</"
+"literal> does not control which session will receive the next message."
+msgstr ""
+
+#. Tag: para
+#: Ordering_Group.xml:183
+#, no-c-format
+msgid ""
+"In the case of a Distributed Queue, the user should use "
+"<literal>HASingleton</literal> to ensure that the ordering group feature "
+"functions correctly."
+msgstr ""
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Preface.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Preface.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Preface.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,21 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Recovery_Configuration.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Recovery_Configuration.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Recovery_Configuration.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,123 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Recovery_Configuration.xml:3
+#, no-c-format
+msgid "JBoss Messaging XA Recovery Configuration"
+msgstr ""
+
+#. Tag: para
+#: Recovery_Configuration.xml:5
+#, no-c-format
+msgid ""
+"This section describes how to configure JBoss Transactions to handle XA "
+"recovery for JBoss Messaging resources in JBoss Application Server 4.x."
+msgstr ""
+
+#. Tag: para
+#: Recovery_Configuration.xml:9
+#, no-c-format
+msgid ""
+"The JBoss Transactions Recovery Manager can be configured to continually "
+"poll for and recover JBoss Messaging XA resources. This provides a high "
+"level of transaction durability."
+msgstr ""
+
+#. Tag: para
+#: Recovery_Configuration.xml:12
+#, no-c-format
+msgid ""
+"To enable JBoss Transactions Recovery Manager, add a line to <filename>"
+"$JBOSS_CONFIG/conf/jbossjta-properties.xml</filename>. The following code "
+"snippet includes the line required:"
+msgstr ""
+
+#. Tag: programlisting
+#: Recovery_Configuration.xml:15
+#, no-c-format
+msgid ""
+"<properties depends=\"arjuna\" name=\"jta\">\n"
+" <!--\n"
+" Support subtransactions in the JTA layer?\n"
+" Default is NO.\n"
+" -->\n"
+" <property name=\"com.arjuna.ats.jta.supportSubtransactions\" value=\"NO"
+"\"/>\n"
+" <property name=\"com.arjuna.ats.jta.jtaTMImplementation\"\n"
+" value=\"com.arjuna.ats.internal.jta.transaction.arjunacore."
+"TransactionManagerImple\"/>\n"
+" <property name=\"com.arjuna.ats.jta.jtaUTImplementation\"\n"
+" value=\"com.arjuna.ats.internal.jta.transaction.arjunacore."
+"UserTransactionImple\"/> \n"
+" <!--\n"
+" *** Add this line to enable recovery for JMS resources using "
+"DefaultJMSProvider ***\n"
+" -->\n"
+" <property name=\"com.arjuna.ats.jta.recovery.XAResourceRecovery."
+"JBMESSAGING1\"\n"
+" value=\"org.jboss.jms.server.recovery.MessagingXAResourceRecovery;"
+"java:/DefaultJMSProvider\"/>\n"
+"\n"
+"</properties>"
+msgstr ""
+
+#. Tag: para
+#: Recovery_Configuration.xml:17
+#, no-c-format
+msgid ""
+"Here, the Recovery Manager attempts to recover JMS resources via the JMS "
+"Provider Loader, <literal>DefaultJMSProvider</literal>."
+msgstr ""
+
+#. Tag: para
+#: Recovery_Configuration.xml:21
+#, no-c-format
+msgid ""
+"<literal>DefaultJMSProvider</literal> ships with JBoss Application Server. "
+"It is defined in <filename>jms-ds.xml</filename> (or, in a clustered "
+"environment, <filename>hajndi-jms-ds.xml</filename>). To perform recovery "
+"with a different JMS provider loader (for example, one that corresponds with "
+"a remote JMS Provider), add another line to the properties file and specify "
+"your remote provider instead of <literal>DefaultJMSProvider</literal>. Your "
+"provider's name should be listed in its managed bean configuration file."
+msgstr ""
+
+#. Tag: para
+#: Recovery_Configuration.xml:25
+#, no-c-format
+msgid ""
+"Each provider requires a unique name, for example, <literal>com.arjuna.ats."
+"jta.recovery.XAResourceRecovery.JBMESSAGING1</literal>, <literal>com.arjuna."
+"ats.jta.recovery.XAResourceRecovery.JBMESSAGING2</literal>, etc."
+msgstr ""
+
+#. Tag: para
+#: Recovery_Configuration.xml:29
+#, no-c-format
+msgid ""
+"Recovery should work with any JMS provider that implements recoverable "
+"XAResources (that is, it properly implements <literal>XAResource.recover()</"
+"literal>)."
+msgstr ""
+
+#. Tag: para
+#: Recovery_Configuration.xml:33
+#, no-c-format
+msgid ""
+"For the Recovery Manager to recover from any node of the cluster, you must "
+"add a line in the configuration for every node of the cluster."
+msgstr ""
Added: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Revision_History.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Revision_History.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Revision_History.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,27 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; 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/5.0/JBoss_Messaging_1.4.3/pot/Running_Examples.pot
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Running_Examples.pot (rev 0)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/pot/Running_Examples.pot 2009-10-23 03:44:09 UTC (rev 95460)
@@ -0,0 +1,305 @@
+# SOME DESCRIPTIVE TITLE.
+# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-10-23 01:07+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
+"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#: Running_Examples.xml:3
+#, no-c-format
+msgid "Running the Examples"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:5
+#, no-c-format
+msgid ""
+"The <filename>/doc/examples/jboss-messaging-examples/</filename> directory "
+"contains a set of examples that demonstrate the various aspects of JBoss "
+"Messaging at work."
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:9
+#, no-c-format
+msgid ""
+"Before you run these examples, deploy the <literal>jbm-examples-destinations-"
+"service</literal> located under <filename>/doc/examples/jboss-messaging-"
+"examples/destinations/</filename>."
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:13
+#, no-c-format
+msgid "The following examples are included with JBoss Messaging:"
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:19
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/queue/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:21
+#, no-c-format
+msgid ""
+"This example shows a simple send and receive to a remote queue using a JMS "
+"client."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:27
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/queue-failover/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:29
+#, no-c-format
+msgid "This example demonstrates the transparent failover of a JMS consumer."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:35
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/topic/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:37
+#, no-c-format
+msgid ""
+"This example shows a simple send and receive to a remote topic using a JMS "
+"client."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:43
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/mdb/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:45
+#, no-c-format
+msgid ""
+"This example demonstrates the use of an Enterprise JavaBean 2.1 MDB with "
+"JBoss Messaging."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:51
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/ejb3mdb/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:53
+#, no-c-format
+msgid ""
+"This example demonstrates the use of an Enterprise JavaBean 3.0 MDB with "
+"JBoss Messaging."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:59
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/stateless/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:61
+#, no-c-format
+msgid ""
+"This example demonstrates an Enterprise JavaBean 2.1 stateless session bean "
+"interacting with JBoss Messaging."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:67
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/mdb-failure/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:69
+#, no-c-format
+msgid ""
+"This example demonstrates rollback and redelivery within an Enterprise "
+"JavaBean 2.1."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:75
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/secure-socket/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:77
+#, no-c-format
+msgid ""
+"This example demonstrates a JMS client interacting with a JBoss Messaging "
+"server via SSL-encrypted transport."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:83
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/http/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:85
+#, no-c-format
+msgid ""
+"This example demonstrates a JMS client interacting with a JBoss Messaging "
+"server by tunneling traffic via HTTP."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:91
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/web-service/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:93
+#, no-c-format
+msgid ""
+"This example demonstrates the JBoss Webservice interacting with JBoss "
+"Messaging."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:99
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/distributed-queue/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:101
+#, no-c-format
+msgid ""
+"This example demonstrates a JMS client interacting with a JBoss Messaging "
+"distributed queue. Two instances of JBoss AS are required to run this "
+"example."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:107
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/distributed-topic/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:109
+#, no-c-format
+msgid ""
+"This example demonstrates a JMS client interacting with a JBoss Messaging "
+"distributed topic. Two instances of JBoss AS are required to run this "
+"example."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:115
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/stateless-clustered/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:117
+#, no-c-format
+msgid ""
+"This example demonstrates a JMS client interacting with a clustered "
+"Enterprise JavaBean 2.1 stateless session bean, which interacts in turn with "
+"JBoss Messaging. This example uses HAJNDI to locate the connection factory."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:124
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/servlet/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:126
+#, no-c-format
+msgid ""
+"This example demonstrates how to use servlet transport with JBoss Messaging. "
+"It deploys a servlet and a <literal>ConnectionFactory</literal> which uses "
+"the servlet transport."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:133
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/ordering-group/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:135
+#, no-c-format
+msgid ""
+"This example demonstrates the use of strict message ordering. It uses the "
+"JBoss Messaging ordering group API to deliver strictly ordered messages, "
+"regardless of the message priority."
+msgstr ""
+
+#. Tag: filename
+#: Running_Examples.xml:143
+#, no-c-format
+msgid "/doc/examples/jboss-messaging-examples/bridge/"
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:145
+#, no-c-format
+msgid ""
+"This example demonstrates the use of a message bridge. It deploys a message "
+"bridge within JBoss AS, which moves messages from a source to a target queue."
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:152
+#, no-c-format
+msgid "We highly recommend that you familiarize yourself with the examples."
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:154
+#, no-c-format
+msgid ""
+"Remember that you must start your server or servers before you run the "
+"examples."
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:156
+#, no-c-format
+msgid ""
+"The non-clustered examples expect an instance of JBoss AS to be running with "
+"all default settings."
+msgstr ""
+
+#. Tag: para
+#: Running_Examples.xml:160
+#, no-c-format
+msgid ""
+"Use of the clustered examples requires two instances of JBoss AS to be "
+"running with corresponding port settings of <literal>ports-01</literal> and "
+"<literal>ports-02</literal>. The default ports for a particular example can "
+"be overidden by editing the <filename>jndi.properties</filename> file in "
+"that example's root directory."
+msgstr ""
More information about the jboss-cvs-commits
mailing list