[jboss-cvs] JBoss Messaging SVN: r7188 - in projects/eap-docs/trunk/JBoss_Messaging_User_Guide: pot and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Jun 3 22:39:49 EDT 2009
Author: irooskov at redhat.com
Date: 2009-06-03 22:39:48 -0400 (Wed, 03 Jun 2009)
New Revision: 7188
Added:
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Appendix.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Author_Group.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Book_Info.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/JBoss_Messaging_User_Guide_CP05.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Preface.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Revision_History.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/bridge.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/c_configuration.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/configuration.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/gettingstarted.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/introduction.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/ordering_group.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/recovery_config.pot
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/runningexamples.pot
Log:
updating with POT files for translation
Added: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Appendix.pot
===================================================================
Added: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Author_Group.pot
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Author_Group.pot (rev 0)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Author_Group.pot 2009-06-04 02:39:48 UTC (rev 7188)
@@ -0,0 +1,24 @@
+# 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-06-04 02:39+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: firstname
+#: Author_Group.xml:6
+#, no-c-format
+msgid ""
+"Permanent Team: Tim Fox (Project Lead), Jeff Mesnil (Core Developer), Andy "
+"Taylor (Core Developer), Clebert Suconic (Core Developer), Howard Gao (Core "
+"Developer)"
+msgstr ""
Added: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Book_Info.pot
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Book_Info.pot (rev 0)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Book_Info.pot 2009-06-04 02:39:48 UTC (rev 7188)
@@ -0,0 +1,46 @@
+# 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-06-04 02:39+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 CP05"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 5"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:12
+#, no-c-format
+msgid "This book is about JBoss Messaging 1.4"
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:18
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:23
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
Added: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/JBoss_Messaging_User_Guide_CP05.pot
===================================================================
Added: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Preface.pot
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Preface.pot (rev 0)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Preface.pot 2009-06-04 02:39:48 UTC (rev 7188)
@@ -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-06-04 02:39+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/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Revision_History.pot
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Revision_History.pot (rev 0)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/Revision_History.pot 2009-06-04 02:39:48 UTC (rev 7188)
@@ -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-06-04 02:39+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/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/bridge.pot
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/bridge.pot (rev 0)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/bridge.pot 2009-06-04 02:39:48 UTC (rev 7188)
@@ -0,0 +1,692 @@
+# 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-06-04 02:39+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:10
+#, no-c-format
+msgid ""
+"The function of the bridge is to consume messages from a source queue or "
+"topic, and send them to a target queue or topic, typically on a different "
+"server."
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:14
+#, no-c-format
+msgid ""
+"The source and target servers do not have to be in the same cluster which "
+"makes bridging suitable for reliably sending messages from one cluster to "
+"another, for instance across a WAN, and where the connection may be "
+"unreliable."
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:19
+#, no-c-format
+msgid ""
+"A bridge is deployed inside a JBoss AS instance. The instance can be the "
+"same instance as either the source or target server. Or could be on a third, "
+"separate JBoss AS instance."
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:23
+#, no-c-format
+msgid ""
+"A bridge is deployed as an MBean inside JBoss AS. Deployment is trivial - "
+"just drop the MBean descriptor into the deploy directory of a JBoss "
+"configuration which contains JBoss Messaging."
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:27
+#, no-c-format
+msgid ""
+"An example in docs/example/bridge demonstrates a simple bridge being "
+"deployed in JBoss AS, and moving messages from the source to the target "
+"destination"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:31
+#, no-c-format
+msgid ""
+"The bridge can also be used to bridge messages from other non JBoss "
+"Messaging JMS servers, as long as they are JMS 1.1 compliant."
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:34
+#, no-c-format
+msgid ""
+"The bridge has built in resilience to failure so if the source or target "
+"server connection is lost, e.g. due to network failure, the bridge will "
+"retry connecting to the source and/or target until they come back online. "
+"When it comes back online it will resume operation as normal."
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:40
+#, no-c-format
+msgid ""
+"The bridge can be configured with an optional JMS selector, so it will only "
+"consume messages matching that JMS selector"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:43
+#, no-c-format
+msgid ""
+"It can be configured to consume from a queue or a topic. When it consumes "
+"from a topic it can be configured to consume using a non durable or durable "
+"subscription"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:47
+#, no-c-format
+msgid ""
+"The bridge can be configured to bridge messages with one of three levels of "
+"quality of service, they are:"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:52
+#, no-c-format
+msgid "QOS_AT_MOST_ONCE"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:54
+#, no-c-format
+msgid ""
+"With this QoS mode messages will reach the destination from the source at "
+"most once. The messages are consumed from the source and acknowledged before "
+"sending to the destination. Therefore there is a possibility that if failure "
+"occurs between removing them from the source and them arriving at the "
+"destination they could be lost. Hence delivery will occur at most once. This "
+"mode is available for both persistent and non persistent messages."
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:64
+#, no-c-format
+msgid "QOS_DUPLICATES_OK"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:66
+#, no-c-format
+msgid ""
+"With this QoS mode, the messages are consumed from the source and then "
+"acknowledged after they have been successfully sent to the destination. "
+"Therefore there is a possibility that if failure occurs after sending to the "
+"destination but before acknowledging them, they could be sent again when the "
+"system recovers. I.e. the destination might receive duplicates after a "
+"failure. This mode is available for both persistent and non persistent "
+"messages."
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:76
+#, no-c-format
+msgid "QOS_ONCE_AND_ONLY_ONCE"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:78
+#, no-c-format
+msgid ""
+"This QoS mode ensures messages will reach the destination from the source "
+"once and only once. (Sometimes this mode is known as \"exactly once\"). If "
+"both the source and the destination are on the same JBoss Messaging server "
+"instance then this can be achieved by sending and acknowledging the messages "
+"in the same local transaction. If the source and destination are on "
+"different servers this is achieved by enlisting the sending and consuming "
+"sessions in a JTA transaction. The JTA transaction is controlled by JBoss "
+"Transactions JTA implementation which is a fully recovering transaction "
+"manager, thus providing a very high degree of durability. If JTA is required "
+"then both supplied connection factories need to be XAConnectionFactory "
+"implementations. This mode is only available for persistent messages. This "
+"is likely to be the slowest mode since it requires logging on both the "
+"transaction manager and resource side for recovery. If you require this "
+"level of QoS, please be sure to enable XA recovery with JBoss Transactions."
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:94
+#, no-c-format
+msgid ""
+"For a specific application it may possible to provide once and only once "
+"semantics without using the QOS_ONCE_AND_ONLY_ONCE QoS level. This can be "
+"done by using the QOS_DUPLICATES_OK mode and then checking for duplicates at "
+"the destination and discarding them. This may be possible to implement on "
+"the application level by maintaining a cache of received message ids on disk "
+"and comparing received messages to them. The cache would only be valid for a "
+"certain period of time so this approach is not as watertight as using "
+"QOS_ONCE_AND_ONLY_ONCE but may be a good choice depending on your specific "
+"application."
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:102
+#, no-c-format
+msgid "Bridge deployment"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:104
+#, no-c-format
+msgid ""
+"A message bridge is easily deployed by dropping the MBean descriptor in the "
+"deploy directory of your JBoss AS installation which contains JBoss Messaging"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:110
+#, no-c-format
+msgid "Bridge configuration"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:112
+#, no-c-format
+msgid "In this section we describe how to configure the message bridge"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:115
+#, no-c-format
+msgid ""
+"Here is an example of a message bridge configuration, with all the "
+"attributes shown. Note that some are commented out for this configuration, "
+"since it is not appropriate to specify them all at once. Which ones are "
+"specified depends on the configuration you want."
+msgstr ""
+
+#. Tag: programlisting
+#: bridge.xml:120
+#, no-c-format
+msgid ""
+"<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 "
+"destination --> \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 "
+"destination -->\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"
+" <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"
+" <attribute name=\"MaxBatchSize\">5</attribute> \n"
+" \n"
+" <!-- The maximum time to wait (in ms) before sending a batch to the "
+"target\n"
+" even if MaxBatchSize is not exceeded.\n"
+" -1 means wait forever --> \n"
+" <attribute name=\"MaxBatchTime\">-1</attribute>\n"
+" \n"
+" <!-- If consuming from a durable subscription this is the "
+"subscription name\n"
+" <attribute name=\"SubName\">mysub</attribute>\n"
+" -->\n"
+" \n"
+" <!-- If consuming from a durable subscription this is the client ID "
+"to use\n"
+" <attribute name=\"ClientID\">myClientID</attribute>\n"
+" -->\n"
+" \n"
+" <!-- The number of ms to wait between connection retrues in the "
+"event connections\n"
+" to source or target fail -->\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"
+" <attribute name=\"MaxRetries\">-1</attribute>\n"
+"\n"
+" <!-- If true then the message id of the message before bridging "
+"will be added\n"
+" as a header to the message so it is available to the receiver. Can "
+"then be\n"
+" sent as correlation id to correlate in a distributed request-"
+"response -->\n"
+" <attribute name=\"AddMessageIDInHeader\">false</"
+"attribute>\n"
+" \n"
+" </mbean>"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:122
+#, no-c-format
+msgid "We will now discuss each attribute"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:125
+#, no-c-format
+msgid "SourceProviderLoader"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:127
+#, no-c-format
+msgid ""
+"This is the object name of the JMSProviderLoader MBean that the bridge will "
+"use to lookup the source connection factory and source destination."
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:131 bridge.xml:157
+#, no-c-format
+msgid ""
+"By default JBoss AS ships with one JMSProviderLoader, deployed in the file "
+"<filename>jms-ds.xml</filename> - this is the default local "
+"JMSProviderLoader. (This would be in <filename>hajndi-jms-ds.xml</filename> "
+"in a clustered configuration)"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:137
+#, no-c-format
+msgid ""
+"If your source destination is on different servers or even correspond to a "
+"different, non JBoss JMS provider, then you can deploy another "
+"JMSProviderLoader MBean instance which references the remote JMS provider, "
+"and reference that from this attribute. The bridge would then use that "
+"remote JMS provider to contact the source destination"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:143 bridge.xml:169
+#, no-c-format
+msgid ""
+"Note that if you are using a remote non JBoss Messaging source or target and "
+"you wish once and only once delivery then that remote JMS provider must "
+"provide a fully functional JMS XA resource implementation that works "
+"remotely from the server - it is known that some non JBoss JMS providers do "
+"not provide such a resource"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:151
+#, no-c-format
+msgid "TargetProviderLoader"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:153
+#, no-c-format
+msgid ""
+"This is the object name of the JMSProviderLoader MBean that the bridge will "
+"use to lookup the target connection factory and target destination."
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:163
+#, no-c-format
+msgid ""
+"If your target destination is on a different server or even correspond to a "
+"different, non JBoss JMS provider, then you can deploy another "
+"JMSProviderLoader MBean instance which references the remote JMS provider, "
+"and reference that from this attribute. The bridge would then use that "
+"remote JMS provider to contact the target destination"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:177
+#, no-c-format
+msgid "SourceDestinationLookup"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:179
+#, no-c-format
+msgid ""
+"This is the full JNDI lookup for the source destination using the "
+"SourceProviderLoader"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:182
+#, no-c-format
+msgid "An example would be /queue/mySourceQueue"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:186
+#, no-c-format
+msgid "TargetDestinationLookup"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:188
+#, no-c-format
+msgid ""
+"This is the full JNDI lookup for the target destination using the "
+"TargetProviderLoader"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:191
+#, no-c-format
+msgid "An example would be /topic/myTargetTopic"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:195
+#, no-c-format
+msgid "SourceUsername"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:197
+#, no-c-format
+msgid ""
+"This optional attribute is for when you need to specify the username for "
+"creating the source connection"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:202
+#, no-c-format
+msgid "SourcePassword"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:204
+#, no-c-format
+msgid ""
+"This optional attribute is for when you need to specify the password for "
+"creating the source connection"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:209
+#, no-c-format
+msgid "TargetUsername"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:211
+#, no-c-format
+msgid ""
+"This optional attribute is for when you need to specify the username for "
+"creating the target connection"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:216
+#, no-c-format
+msgid "TargetPassword"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:218
+#, no-c-format
+msgid ""
+"This optional attribute is for when you need to specify the password for "
+"creating the target connection"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:223
+#, no-c-format
+msgid "QualityOfServiceMode"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:225
+#, no-c-format
+msgid "This integer represents the desired quality of service mode"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:227
+#, no-c-format
+msgid "Possible values are:"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:229
+#, no-c-format
+msgid "QOS_AT_MOST_ONCE = 0"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:235
+#, no-c-format
+msgid "QOS_DUPLICATES_OK = 1"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:241
+#, no-c-format
+msgid "QOS_ONCE_AND_ONLY_ONCE = 2"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:247
+#, no-c-format
+msgid ""
+"Please see <xref linkend=\"bridge.overview\"/> for an explanation of what "
+"these mean."
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:252
+#, no-c-format
+msgid "Selector"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:254
+#, no-c-format
+msgid ""
+"This optional attribute can contain a JMS selector expression used for "
+"consuming messages from the source destination. Only messages that match the "
+"selector expression will be bridged from the source to the target destination"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:259
+#, no-c-format
+msgid ""
+"Please note it is always more performant to apply selectors on source topic "
+"subscriptions to source queue consumers."
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:262
+#, no-c-format
+msgid ""
+"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: title
+#: bridge.xml:268
+#, no-c-format
+msgid "MaxBatchSize"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:270
+#, no-c-format
+msgid ""
+"This attribute specifies the maximum number of messages to consume from the "
+"source destination before sending them in a batch to the target destination. "
+"It's value must >= 1"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:276
+#, no-c-format
+msgid "MaxBatchTime"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:278
+#, no-c-format
+msgid ""
+"This attribute specifies the maximum number of milliseconds to wait before "
+"sending a batch to target, even if the number of messages consumed has not "
+"reached MaxBatchSize. It's value must can be -1 to represent 'wait forever', "
+"or >=1 to specify an actual time."
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:285
+#, no-c-format
+msgid "SubName"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:287
+#, no-c-format
+msgid ""
+"If the source destination represents a topic, and you want to consume from "
+"the topic using a durable subscription then this attribute represents the "
+"durable subscription name"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:293
+#, no-c-format
+msgid "ClientID"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:295
+#, no-c-format
+msgid ""
+"If the source destination represents a topic, and you want to consume from "
+"the topic using a durable subscription then this attribute represents the "
+"the JMS client ID to use when creating/looking up the durable subscription"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:302
+#, no-c-format
+msgid "FailureRetryInterval"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:304
+#, no-c-format
+msgid ""
+"This represents the amount of time in ms to wait between trying to recreate "
+"connections to the source or target servers when the bridge has detected "
+"they have failed"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:310
+#, no-c-format
+msgid "MaxRetries"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:312
+#, no-c-format
+msgid ""
+"This represents the number of times to attempt to recreate connections to "
+"the source or target servers when the bridge has detected they have failed. "
+"The bridge will give up after trying this number of times. -1 represents "
+"'try forever'"
+msgstr ""
+
+#. Tag: title
+#: bridge.xml:319
+#, no-c-format
+msgid "AddMessageIDInHeader"
+msgstr ""
+
+#. Tag: para
+#: bridge.xml:321
+#, no-c-format
+msgid ""
+"If true, then the original message's message id will appended in the message "
+"sent to the destination in the header JBossMessage."
+"JBOSS_MESSAGING_BRIDGE_MESSAGE_ID_LIST. If the message is bridged more than "
+"once each message-id will be appended. This enables a distributed request-"
+"response pattern to be used"
+msgstr ""
Added: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/c_configuration.pot
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/c_configuration.pot (rev 0)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/c_configuration.pot 2009-06-04 02:39:48 UTC (rev 7188)
@@ -0,0 +1,219 @@
+# 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-06-04 02:39+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 ""
+"JBoss Messaging clustering should work out of the box in most cases with no "
+"configuration changes. It is however crucial that every node is assigned a "
+"unique server id, as specified in the installation guide."
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:13
+#, no-c-format
+msgid ""
+"Every node deployed must have a unique id, including those in a particular "
+"LAN cluster, and also those only linked by mesage bridges."
+msgstr ""
+
+#. Tag: title
+#: c_configuration.xml:19
+#, no-c-format
+msgid "Clustered destinations"
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:21
+#, no-c-format
+msgid ""
+"JBoss Messaging clusters 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 designate that a particular destination is "
+"clustered simply set the clustered attribute in the destination deployment "
+"descriptor to true."
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:27
+#, no-c-format
+msgid ""
+"JBoss Messaging balances messages between nodes, catering for faster or "
+"slower consumers to efficiently balance processing load across the cluster."
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:31
+#, no-c-format
+msgid ""
+"If you do not want message redistribution between nodes, but still want to "
+"retain the other characteristics of clustered destinations. You can do this "
+"by not specifying the attribute ClusterPullConnectionFactoryName on the "
+"server peer"
+msgstr ""
+
+#. Tag: title
+#: c_configuration.xml:38
+#, no-c-format
+msgid "Clustered durable subs"
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:40
+#, no-c-format
+msgid ""
+"JBoss Messaging durable subscriptions can also be clustered. This means "
+"multiple subscribers can consume from the same durable subscription from "
+"different nodes of the cluster. A durable subscription will be clustered if "
+"it's topic is clustered"
+msgstr ""
+
+#. Tag: title
+#: c_configuration.xml:47
+#, no-c-format
+msgid "Clustered temporary destinations"
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:49
+#, no-c-format
+msgid ""
+"JBoss Messaging also supports clustered temporary topics and queues. All "
+"temporary topics and queues will be clustered if the post office is clustered"
+msgstr ""
+
+#. Tag: title
+#: c_configuration.xml:55
+#, no-c-format
+msgid "Non clustered servers"
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:57
+#, no-c-format
+msgid ""
+"If you don't want your nodes to participate in a cluster, or only have one "
+"non clustered server you can set the clustered attribute on the postoffice "
+"to false"
+msgstr ""
+
+#. Tag: title
+#: c_configuration.xml:63
+#, no-c-format
+msgid "Message ordering in the cluster"
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:65
+#, no-c-format
+msgid ""
+"If you wish to apply strict JMS ordering to messages, such that a particular "
+"JMS consumer consumes messages in the same order as they were produced by a "
+"particular producer, you can set the DefaultPreserveOrdering attribute in "
+"the server peer to true. By default this is false. The side effect of "
+"setting this to true is that messages cannot be distributed as freely around "
+"the cluster"
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:73
+#, no-c-format
+msgid ""
+"The redelivery scenario in order to guarantee message ordering is presently "
+"unsupported, however it may be supported in future releases."
+msgstr ""
+
+#. Tag: title
+#: c_configuration.xml:80
+#, no-c-format
+msgid "Idempotent operations"
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:82
+#, no-c-format
+msgid ""
+"If the call to send a persistent message to a persistent destination returns "
+"successfully with no exception, then you can be sure that the message was "
+"persisted. However if the call doesn't return successfully e.g. if an "
+"exception is thrown, then you *can't be sure the message wasn't persisted*. "
+"Since the failure might have occurred after persisting the message but "
+"before writing the response to the caller. This is a common attribute of any "
+"RPC type call: You can't tell by the call not returning that the call didn't "
+"actually succeed. Whether it's a web services call, an HTTP get request, an "
+"ejb invocation the same applies. The trick is to code your application so "
+"your operations are *idempotent* i.e. they can be repeated without getting "
+"the system into an inconsistent state. With a messaging system you can do "
+"this on the application level, by checking for duplicate messages, and "
+"discarding them if they arrive. Duplicate checking is a very powerful "
+"technique that can remove the need for XA transactions in many cases."
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:98
+#, no-c-format
+msgid ""
+"In the clustered case. JBM is by default configured to detect duplicate "
+"automatically messages by default"
+msgstr ""
+
+#. Tag: title
+#: c_configuration.xml:103
+#, no-c-format
+msgid "Clustered connection factories"
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:105
+#, no-c-format
+msgid ""
+"If the supportsLoadBalancing attribute of the connection factory is set to "
+"true then consecutive create connection attempts will round robin between "
+"available servers. The first node to try is chosen randomly"
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:109
+#, no-c-format
+msgid ""
+"If the supportsFailover attribute of the connection factory is set to true "
+"then automatic failover is enabled. This will automatically failover from "
+"one server to another, transparently to the user, in case of failure."
+msgstr ""
+
+#. Tag: para
+#: c_configuration.xml:114
+#, no-c-format
+msgid ""
+"If automatic failover is not required or you wish to do manual failover "
+"(JBoss MQ style) this can be set to false, and you can supply a standard JMS "
+"ExceptionListener on the connection which will be called in case of "
+"connection failure. You would then need to manually close the connection, "
+"lookup a new connection factory from HA JNDI and recreate the connection."
+msgstr ""
Added: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/configuration.pot
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/configuration.pot (rev 0)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/configuration.pot 2009-06-04 02:39:48 UTC (rev 7188)
@@ -0,0 +1,3839 @@
+# 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-06-04 02:39+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 JMS API specifies how a messaging client interacts with a messaging "
+"server. The exact definition and implementation of messaging services, such "
+"as message destinations and connection factories, are specific to JMS "
+"providers. JBoss Messaging has its own configuration files to configure "
+"services. If you are migrating services from JBossMQ (or other JMS provider) "
+"to JBoss Messaging, you will need to understand those configuration files."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:13
+#, no-c-format
+msgid ""
+"In this chapter, we discuss how to configure various services inside JBoss "
+"Messaging, which work together to provide JMS API level services to client "
+"applications."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:17
+#, no-c-format
+msgid ""
+"The JBoss Messaging service configuration is spread among several "
+"configuration files. Depending on the functionality provided by the services "
+"it configures, the configuration data is distributed between "
+"<filename>messaging-service.xml</filename>, <filename>remoting-bisocket-"
+"service.xml</filename>, <filename>xxx-persistence-service.xml</filename> "
+"(where xx is the name of your database) , <filename>connection-factories-"
+"service.xml</filename> and <filename>destinations-service.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:26
+#, no-c-format
+msgid ""
+"The AOP client-side and server-side interceptor stacks are configured in "
+"<filename>aop-messaging-client.xml</filename> and <filename>aop-messaging-"
+"server.xml</filename>. Normally you will not want to change them, but some "
+"of the interceptors can be removed to give a small performance increase, if "
+"you don't need them. Be very careful you have considered the security "
+"implications before removing the security interceptor."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:35
+#, no-c-format
+msgid "Configuring the ServerPeer"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:37
+#, no-c-format
+msgid ""
+"The Server Peer is the heart of the JBoss Messaging JMS facade. The server's "
+"configuration, resides in <filename>messaging-service.xml</filename> "
+"configuration file."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:41
+#, no-c-format
+msgid "All JBoss Messaging services are rooted at the server peer"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:43
+#, 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:47
+#, no-c-format
+msgid ""
+"<!-- 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 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 without specifying one --> \n"
+" \n"
+" <attribute name=\"DefaultQueueJNDIContext\">/queue</"
+"attribute>\n"
+" \n"
+" <!-- The default JNDI context to use for topics when they are "
+"deployed without specifying one --> \n"
+" \n"
+" <attribute name=\"DefaultTopicJNDIContext\">/topic</"
+"attribute>\n"
+"\n"
+" <attribute name=\"PostOffice\">jboss.messaging:"
+"service=PostOffice</attribute>\n"
+" \n"
+" <!-- The default Dead Letter Queue (DLQ) to use for destinations.\n"
+" This can be overridden on a per destinatin basis -->\n"
+" \n"
+" <attribute name=\"DefaultDLQ\">jboss.messaging.destination:"
+"service=Queue,name=DLQ</attribute>\n"
+" \n"
+" <!-- The default maximum number of times to attempt delivery of a "
+"message before sending to the DLQ (if configured).\n"
+" This can be overridden on a per destinatin basis -->\n"
+" \n"
+" <attribute name=\"DefaultMaxDeliveryAttempts\">10</"
+"attribute>\n"
+" \n"
+" <!-- The default Expiry Queue to use for destinations. This can be "
+"overridden on a per destinatin basis -->\n"
+" \n"
+" <attribute name=\"DefaultExpiryQueue\">jboss.messaging."
+"destination:service=Queue,name=ExpiryQueue</attribute>\n"
+" \n"
+" <!-- The default redelivery delay to impose. This can be overridden "
+"on a per destination basis -->\n"
+" \n"
+" <attribute name=\"DefaultRedeliveryDelay\">0</attribute>\n"
+" \n"
+" <!-- The periodicity of the message counter manager enquiring on "
+"queues for statistics -->\n"
+" \n"
+" <attribute name=\"MessageCounterSamplePeriod\">5000</"
+"attribute>\n"
+" \n"
+" <!-- The maximum amount of time for a client to wait for failover "
+"to start on the server side after\n"
+" 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 complete on the server side after\n"
+" it has detected failure -->\n"
+" \n"
+" <attribute name=\"FailoverCompleteTimeout\">300000</"
+"attribute>\n"
+" \n"
+" <!-- The maximum number of days results to maintain in the message "
+"counter history -->\n"
+" \n"
+" <attribute name=\"DefaultMessageCounterHistoryDayLimit\">-1</"
+"attribute>\n"
+" \n"
+" <!-- The name of the connection factory to use for creating "
+"connections between nodes to pull messages -->\n"
+" \n"
+" <attribute name=\"ClusterPullConnectionFactoryName\">jboss."
+"messaging.connectionfactory:service=ClusterPullConnectionFactory</"
+"attribute>\n"
+" \n"
+" <!-- When redistributing messages in the cluster. Do we need to "
+"preserve the order of messages received\n"
+" by a particular consumer from a particular producer? -->\n"
+" \n"
+" <attribute name=\"DefaultPreserveOrdering\">false</"
+"attribute>\n"
+" \n"
+" <!-- Max. time to hold previously delivered messages back waiting "
+"for 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 "
+"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\">jboss."
+"messaging:service=PersistenceManager</depends>\n"
+" \n"
+" <depends optional-attribute-name=\"JMSUserManager\">jboss."
+"messaging:service=JMSUserManager</depends>\n"
+" \n"
+" <depends>jboss.messaging:service=Connector,"
+"transport=bisocket</depends>\n"
+" <depends optional-attribute-name=\"SecurityStore\" proxy-type=\"org."
+"jboss.jms.server.SecurityStore\">jboss.messaging:"
+"service=SecurityStore</depends>\n"
+" \n"
+" </mbean>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:50
+#, no-c-format
+msgid "ServerPeer attributes"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:52
+#, no-c-format
+msgid "We now discuss the MBean attributes of the ServerPeer MBean."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:56
+#, no-c-format
+msgid "ServerPeerID"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:58
+#, no-c-format
+msgid ""
+"The unique id of the server peer. Every node you deploy MUST have a unique "
+"id. This applies whether the different nodes form a cluster, or are only "
+"linked via a message bridge. The id must be a valid integer."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:65
+#, no-c-format
+msgid "DefaultQueueJNDIContext"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:67
+#, no-c-format
+msgid ""
+"The default JNDI context to use when binding queues. Defaults to /queue."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:72
+#, no-c-format
+msgid "DefaultTopicJNDIContext"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:74
+#, no-c-format
+msgid ""
+"The default JNDI context to use when binding topics.wa Defaults to /topic."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:79
+#, no-c-format
+msgid "PostOffice"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:81
+#, no-c-format
+msgid ""
+"This is the post office that the ServerPeer uses. You will not normally need "
+"to change this attribute. The post office is responsible for routing "
+"messages to queues and maintaining the mapping between addresses and queues."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:88
+#, no-c-format
+msgid "DefaultDLQ"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:90
+#, no-c-format
+msgid ""
+"This is the name of the default DLQ (Dead Letter Queue) the server peer will "
+"use for destinations. The DLQ can be overridden on a per destination basis - "
+"see the destination MBean configuration for more details. A DLQ is a special "
+"destination where messages are sent when the server has attempted to deliver "
+"them unsuccessfully more than a certain number of times. If the DLQ is not "
+"specified at all then the message will be removed after the maximum number "
+"of delivery attempts. The maximum number of delivery attempts can be "
+"specified using the attribute DefaultMaxDeliveryAttempts for a global "
+"default or individually on a per destination basis."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:102
+#, no-c-format
+msgid ""
+"Message-Driven Bean (MDB) and JBoss Messaging (JBM) both have individual DLQ "
+"logic. You will want to be careful which one is processing your undelivered "
+"messages as a situation may occur where a process is expecting MDB DLQ logic "
+"to be used however in reality JBM DLQ logic has been given precedence and "
+"thus an error may occur."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:108
+#, no-c-format
+msgid "DefaultMaxDeliveryAttempts"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:110
+#, no-c-format
+msgid ""
+"The default for the maximum number of times delivery of a message will be "
+"attempted before sending the message to the DLQ, if configured."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:114
+#, no-c-format
+msgid "The default value is <literal>10</literal>."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:116
+#, no-c-format
+msgid "This value can also be overridden on a per destination basis."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:120
+#, no-c-format
+msgid "DefaultExpiryQueue"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:122
+#, no-c-format
+msgid ""
+"This is the name of the default expiry queue the server peer will use for "
+"destinations. The expiry can be overridden on a per destination basis - see "
+"the destination MBean configuration for more details. An expiry queue is a "
+"special destination where messages are sent when they have expired. Message "
+"expiry is determined by the value of Message::getJMSExpiration() If the "
+"expiry queue is not specified at all then the message will be removed after "
+"it is expired."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:131
+#, no-c-format
+msgid "DefaultRedeliveryDelay"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:133
+#, no-c-format
+msgid ""
+"When redelivering a message after failure of previous delivery it is often "
+"beneficial to introduce a delay perform redelivery in order to prevent "
+"thrashing of delivery-failure, delivery-failure etc"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:139
+#, no-c-format
+msgid ""
+"The default value is <literal>0</literal> which means there will be no delay."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:142
+#, no-c-format
+msgid ""
+"Change this if your application could benefit with a delay before "
+"redelivery. This value can also be overridden on a per destination basis."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:147
+#, no-c-format
+msgid "MessageCounterSamplePeriod"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:149
+#, no-c-format
+msgid ""
+"Periodically the server will query each queue to gets its statistics. This "
+"is the period."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:152
+#, no-c-format
+msgid "The default value is <literal>10000</literal> milliseconds."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:156
+#, no-c-format
+msgid "FailoverStartTimeout"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:158
+#, no-c-format
+msgid ""
+"The maximum number of milliseconds the client will wait for failover to "
+"start on the server side when a problem is detected."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:162
+#, no-c-format
+msgid "The default value is <literal>60000</literal> (one minute)."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:166
+#, no-c-format
+msgid "FailoverCompleteTimeout"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:168
+#, no-c-format
+msgid ""
+"The maximum number of milliseconds the client will wait for failover to "
+"complete on the server side after it has started."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:171
+#, no-c-format
+msgid "The default value is <literal>300000</literal> (five minutes)."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:176
+#, no-c-format
+msgid "DefaultMessageCounterHistoryDayLimit"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:178
+#, no-c-format
+msgid ""
+"JBoss Messaging provides a message counter history which shows the number of "
+"messages arriving on each queue of a certain number of days. This attribute "
+"represents the maximum number of days for which to store message counter "
+"history. It can be overridden on a per destination basis."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:186
+#, no-c-format
+msgid "ClusterPullConnectionFactory"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:188
+#, no-c-format
+msgid ""
+"The name of the connection factory to use for pulling messages between nodes."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:192
+#, no-c-format
+msgid ""
+"If you wish to turn off message sucking between queues altogether, but "
+"retain failover, then you can omit this attribute altogether"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:197
+#, no-c-format
+msgid "DefaultPreserveOrdering"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:199
+#, no-c-format
+msgid ""
+"If true, then strict JMS ordering is preserved in the cluster. See the "
+"cluster configurations section for more details. Default is false."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:205
+#, no-c-format
+msgid "RecoverDeliveriesTimeout"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:207
+#, no-c-format
+msgid ""
+"When failover occurs, already delivered messages will be kept aside, waiting "
+"for clients to reconnect. In the case that clients never reconnect (e.g. the "
+"client is dead) then eventually these messages will timeout and be added "
+"back to the queue. The value is in ms. The default is 5 mins."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:215 configuration.xml:430
+#, no-c-format
+msgid "EnableMessageCounters"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:217
+#, no-c-format
+msgid "Set this to true to enable message counters when the server starts"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:222
+#, no-c-format
+msgid "SuckerPassword"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:224
+#, no-c-format
+msgid ""
+"JBoss Messaging internally makes connections between nodes in order to "
+"redistribute messages between clustered destinations. These connections are "
+"made with the user name of a special reserved user. On this parameter you "
+"define the password used as these connections are made. After JBossMessaging "
+"1.4.1.GA you will need to define the Sucker Password on the ServerPeer and "
+"on the SecurityMetadataStore."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:232
+#, no-c-format
+msgid ""
+"This must be specified at install time, or the default password will be "
+"used. Any one who then knows the default password will be able to gain "
+"access to any destinations on the server. This value MUST be changed at "
+"install time."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:237
+#, no-c-format
+msgid "StrictTCK"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:239
+#, no-c-format
+msgid "Set to true if you want strict JMS TCK semantiocs"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:243
+#, no-c-format
+msgid "Destinations"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:245
+#, no-c-format
+msgid ""
+"Returns a list of the destinations (queues and topics) currently deployed."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:250 configuration.xml:1365
+#, no-c-format
+msgid "MessageCounters"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:252
+#, no-c-format
+msgid "JBoss Messaging provides a message counter for each queue."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:257
+#, no-c-format
+msgid "MessageCountersStatistics"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:259
+#, no-c-format
+msgid ""
+"JBoss Messaging provides statistics for each message counter for each queue."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:264 configuration.xml:1649
+#, no-c-format
+msgid "SupportsFailover"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:266
+#, no-c-format
+msgid ""
+"Set to false to prevent server side failover occurring in a cluster when a "
+"node crashes."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:271
+#, no-c-format
+msgid "PersistenceManager"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:273
+#, no-c-format
+msgid ""
+"This is the persistence manager that the ServerPeer uses. You will not "
+"normally need to change this attribute."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:278
+#, no-c-format
+msgid "JMSUserManager"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:280
+#, no-c-format
+msgid ""
+"This is the JMS user manager that the ServerPeer uses. You will not normally "
+"need to change this attribute."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:285
+#, no-c-format
+msgid "SecurityStore"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:287
+#, no-c-format
+msgid ""
+"This is the pluggable SecurityStore. If you redefine this SecurityStore, "
+"notice it will need to authenticate the MessageSucker user (\"JBM.SUCKER\") "
+"with all the special permissions required by clustering."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:294
+#, no-c-format
+msgid "We now discuss the MBean operations of the ServerPeer MBean."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:298
+#, no-c-format
+msgid "DeployQueue"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:300
+#, no-c-format
+msgid "This operation lets you programmatically deploy a queue."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:303
+#, no-c-format
+msgid "There are two overloaded versions of this operation"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:305
+#, no-c-format
+msgid ""
+"If the queue already exists but is undeployed it is deployed. Otherwise it "
+"is created and deployed."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:308 configuration.xml:364
+#, no-c-format
+msgid ""
+"The <literal>name</literal> parameter represents the name of the destination "
+"to deploy."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:311
+#, no-c-format
+msgid ""
+"The <literal>jndiName</literal> parameter (optional) represents the full "
+"jndi name where to bind the destination. If this is not specified then the "
+"destination will be bound in <DefaultQueueJNDIContext>/<name>."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:316 configuration.xml:372
+#, no-c-format
+msgid ""
+"The first version of this operation deploys the destination with the default "
+"paging parameters. The second overloaded version deploys the destination "
+"with the specified paging parameters. See the section on configuring "
+"destinations for a discussion of what the paging parameters mean."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:323
+#, no-c-format
+msgid "UndeployQueue"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:325
+#, no-c-format
+msgid "This operation lets you programmatically undeploy a queue."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:328 configuration.xml:384
+#, no-c-format
+msgid "The queue is undeployed but is NOT removed from persistent storage."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:331
+#, no-c-format
+msgid ""
+"This operation returns <literal>true</literal> if the queue was successful "
+"undeployed. otherwise it returns <literal>false</literal>."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:336
+#, no-c-format
+msgid "DestroyQueue"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:338
+#, no-c-format
+msgid "This operation lets you programmatically destroy a queue."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:341
+#, no-c-format
+msgid ""
+"The queue is undeployed and then all its data is destroyed from the database."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:345
+#, no-c-format
+msgid ""
+"Be careful when using this method since it will delete all data for the "
+"queue."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:349
+#, no-c-format
+msgid ""
+"This operation returns <literal>true</literal> if the queue was successfully "
+"destroyed. otherwise it returns <literal>false</literal>."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:354
+#, no-c-format
+msgid "DeployTopic"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:356
+#, no-c-format
+msgid "This operation lets you programmatically deploy a topic."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:359
+#, no-c-format
+msgid "There are two overloaded versions of this operation."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:361
+#, no-c-format
+msgid ""
+"If the topic already exists but is undeployed it is deployed. Otherwise it "
+"is created and deployed."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:367
+#, no-c-format
+msgid ""
+"The <literal>jndiName</literal> parameter (optional) represents the full "
+"jndi name where to bind the destination. If this is not specified then the "
+"destination will be bound in <DefaultTopicJNDIContext>/<name>."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:379
+#, no-c-format
+msgid "UndeployTopic"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:381
+#, no-c-format
+msgid "This operation lets you programmatically undeploy a topic."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:387
+#, no-c-format
+msgid ""
+"This operation returns <literal>true</literal> if the topic was successfully "
+"undeployed. otherwise it returns <literal>false</literal>."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:392
+#, no-c-format
+msgid "DestroyTopic"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:394
+#, no-c-format
+msgid "This operation lets you programmatically destroy a topic."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:397
+#, no-c-format
+msgid ""
+"The topic is undeployed and then all its data is destroyed from the database."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:401
+#, no-c-format
+msgid ""
+"Be careful when using this method since it will delete all data for the "
+"topic."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:405
+#, no-c-format
+msgid ""
+"This operation returns <literal>true</literal> if the topic was successfully "
+"destroyed. otherwise it returns <literal>false</literal>."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:410
+#, no-c-format
+msgid "ListMessageCountersHTML"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:412
+#, no-c-format
+msgid ""
+"This operation returns message counters in an easy to display HTML format."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:417 configuration.xml:423
+#, no-c-format
+msgid "ResetAllMesageCounters"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:419
+#, no-c-format
+msgid "This operation resets all message counters to zero."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:425
+#, no-c-format
+msgid "This operation resets all message counter histories to zero."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:432
+#, no-c-format
+msgid ""
+"This operation enables all message counters for all destinations. Message "
+"counters are disabled by default."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:437
+#, no-c-format
+msgid "DisableMessageCounters"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:439
+#, no-c-format
+msgid ""
+"This operation disables all message counters for all destinations. Message "
+"counters are disabled by default."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:444
+#, no-c-format
+msgid "RetrievePreparedTransactions"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:446
+#, 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:451
+#, no-c-format
+msgid "ShowPreparedTransactions"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:453
+#, no-c-format
+msgid ""
+"Retrieves a list of the Xids for all transactions currently in a prepared "
+"state on the node in an easy to display HTML format."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:461
+#, no-c-format
+msgid "Changing the Database"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:463
+#, no-c-format
+msgid ""
+"Several JBoss Messaging services interact with persistent storage. They "
+"include: The Persistence Manager, The PostOffice and the JMS User Manager. "
+"The Persistence Manager is used to handle the message-related persistence. "
+"The Post Office handles binding related persistence. The JMS User manager "
+"handles user related persistence The configuration for all these MBeans is "
+"handled in the <filename>xxx-persistence-service.xml</filename> file."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:471
+#, no-c-format
+msgid ""
+"If the database you want to switch to is one of MySQL, Oracle, PostgreSQL, "
+"MS SQL Sever or Sybase, persistence configuration files are already "
+"available in the <filename>examples/config</filename> directory of the "
+"release bundle."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:476
+#, no-c-format
+msgid ""
+"In order to enable support for one of these databases, just replace the "
+"default <filename>hsqldb-persistence-service.xml</filename> configuration "
+"file with the database-specific configuration file and restart the server."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:481
+#, no-c-format
+msgid ""
+"Also, be aware that by default, the Messaging services relying on a "
+"datastore are referencing <literal>\"java:/DefaultDS\"</literal> for the "
+"datasource. If you are deploying a datasource with a different JNDI name, "
+"you need to update all the <literal>DataSource</literal> attribute in the "
+"persistence configuration file. Example data source configurations for each "
+"of the popular databases are available in the distribution."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:490
+#, no-c-format
+msgid "Configuring the Post office"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:492
+#, no-c-format
+msgid ""
+"It is the job of the post office to route messages to their destination(s)."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:495
+#, no-c-format
+msgid ""
+"The post office maintains the mappings between addresses to which messages "
+"can be sent and their final queues."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:498
+#, no-c-format
+msgid ""
+"For example when sending a message with an address that represents a JMS "
+"queue name, the post office will route this to a single queue - the JMS "
+"queue. When sending a message with an address that represents a JMS topic "
+"name, the post office will route this to a set of queues - one for each JMS "
+"subscription."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:504
+#, no-c-format
+msgid ""
+"The post office also handles the persistence for the mapping of addresses."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:507
+#, no-c-format
+msgid ""
+"JBoss Messaging post-offices are also cluster aware. In a cluster they will "
+"automatically route and pull messages between them in order to provide fully "
+"distributed JMS queues and topics."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:511
+#, no-c-format
+msgid ""
+"The post office configuration is found in the xxx-persistence-service.xml "
+"file (where xxx is the name of your database)."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:515
+#, no-c-format
+msgid "Here is an example of a post office configuration:"
+msgstr ""
+
+#. Tag: programlisting
+#: configuration.xml:517
+#, no-c-format
+msgid ""
+"<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\">jboss.messaging:"
+"service=ServerPeer</depends>\n"
+" \n"
+" <depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</"
+"depends>\n"
+" \n"
+" <depends optional-attribute-name=\"TransactionManager\">jboss:"
+"service=TransactionManager</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 binding "
+"information --> \n"
+" \n"
+" <attribute name=\"DataSource\">java:/DefaultDS</"
+"attribute>\n"
+" \n"
+" <!-- If true will attempt to create tables and indexes on every "
+"start-up -->\n"
+" \n"
+" <attribute name=\"CreateTablesOnStartup\">true</"
+"attribute>\n"
+" \n"
+" \n"
+" <!-- If true then we will automatically detect and reject 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 "
+"messages -->\n"
+" \n"
+" <attribute name=\"IDCacheSize\">500</attribute>\n"
+" \n"
+" \n"
+" <attribute name=\"SqlProperties\"><![CDATA[\n"
+"CREATE_POSTOFFICE_TABLE=CREATE TABLE JBM_POSTOFFICE (POSTOFFICE_NAME VARCHAR"
+"(255), NODE_ID INTEGER, QUEUE_NAME VARCHAR(255), COND VARCHAR(1023), "
+"SELECTOR VARCHAR(1023), CHANNEL_ID BIGINT, CLUSTERED CHAR(1), ALL_NODES CHAR"
+"(1), PRIMARY KEY(POSTOFFICE_NAME, NODE_ID, QUEUE_NAME)) ENGINE = INNODB\n"
+"INSERT_BINDING=INSERT INTO JBM_POSTOFFICE (POSTOFFICE_NAME, NODE_ID, "
+"QUEUE_NAME, COND, SELECTOR, CHANNEL_ID, CLUSTERED, ALL_NODES) VALUES "
+"(?, ?, ?, ?, ?, ?, ?, ?)\n"
+"DELETE_BINDING=DELETE FROM JBM_POSTOFFICE WHERE POSTOFFICE_NAME=? AND "
+"NODE_ID=? AND QUEUE_NAME=?\n"
+"LOAD_BINDINGS=SELECT QUEUE_NAME, COND, SELECTOR, CHANNEL_ID, CLUSTERED, "
+"ALL_NODES FROM 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 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 office is clustered.\n"
+" You can safely comment them out if your post office is non "
+"clustered -->\n"
+" \n"
+" <!-- The JGroups group name that the post office will use --"
+"> \n"
+" \n"
+" <attribute name=\"GroupName\">${jboss.messaging.groupname:"
+"MessagingPostOffice}</attribute>\n"
+" \n"
+" <!-- Max time to wait for state to arrive when the post office "
+"joins the cluster --> \n"
+" \n"
+" <attribute name=\"StateTimeout\">5000</attribute>\n"
+" \n"
+" <!-- Max time to wait for a synchronous call to node members using "
+"the MessageDispatcher --> \n"
+" \n"
+" <attribute name=\"CastTimeout\">50000</attribute>\n"
+" \n"
+" <!-- Set this to true if you want failover of connections to occur "
+"when a node is shut down -->\n"
+" \n"
+" <attribute name=\"FailoverOnNodeLeave\">false</attribute>\n"
+" \n"
+" \n"
+" <!-- JGroups stack configuration for the data channel - used for "
+"sending 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\" "
+"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 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\" "
+"up_thread=\"false\" shun=\"true\"/>\n"
+" <VERIFY_SUSPECT timeout=\"1500\" down_thread=\"false\" "
+"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\" "
+"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"
+"\" use_flush=\"true\" flush_timeout=\"3000\"/>\n"
+" <pbcast.FLUSH down_thread=\"false\" up_thread=\"false\" "
+"timeout=\"20000\" auto_flush_conf=\"false\"/>\n"
+" </config>\n"
+" </attribute> \n"
+" \n"
+" </mbean>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:520
+#, no-c-format
+msgid "The post office has the following attributes"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:523
+#, no-c-format
+msgid "DataSource"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:525
+#, no-c-format
+msgid ""
+"The datasource the postoffice should use for persisting its mapping data."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:530 configuration.xml:812 configuration.xml:892
+#, no-c-format
+msgid "SQLProperties"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:532 configuration.xml:814 configuration.xml:894
+#, no-c-format
+msgid ""
+"This is where the DDL and DML for the particular database is specified. 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:539 configuration.xml:755 configuration.xml:870
+#, no-c-format
+msgid "CreateTablesOnStartup"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:541
+#, no-c-format
+msgid ""
+"Set this to <literal>true</literal> if you wish the post office to attempt "
+"to create the tables (and indexes) when it starts. If the tables (or "
+"indexes) already exist a <literal>SQLException</literal> will be thrown by "
+"the JDBC driver and ignored by the Persistence Manager, allowing it to "
+"continue."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:547 configuration.xml:763 configuration.xml:878
+#, no-c-format
+msgid ""
+"By default the value of <literal>CreateTablesOnStartup</literal> attribute "
+"is set to <literal>true</literal>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:551
+#, no-c-format
+msgid "DetectDuplicates"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:553
+#, no-c-format
+msgid ""
+"Set this to <literal>true</literal> if you wish the post office detect "
+"duplicate messages that may sent when a send is retried on a different node "
+"after server failure."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:557
+#, no-c-format
+msgid ""
+"By default the value of <literal>DetectDuplicates</literal> attribute is set "
+"to <literal>true</literal>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:561
+#, no-c-format
+msgid "IDCacheSize"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:563
+#, no-c-format
+msgid ""
+"If duplicate detection is enabled. (See <literal>DetectDuplicates</"
+"literal>), then the server will remember the last <literal>n</literal> "
+"message ids sent, to prevent duplicate messages sent after failover has "
+"occurred. The value of <literal>n</literal> is determined by this attribute."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:569
+#, no-c-format
+msgid ""
+"By default the value of <literal>IDCacheSize</literal> attribute is set to "
+"<literal>500</literal>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:573
+#, no-c-format
+msgid "PostOfficeName"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:575
+#, no-c-format
+msgid "The name of the post office."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:579
+#, no-c-format
+msgid "NodeIDView"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:581
+#, no-c-format
+msgid ""
+"This returns set containing the node ids of all the nodes in the cluster."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:586
+#, no-c-format
+msgid "GroupName"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:588
+#, no-c-format
+msgid ""
+"All post offices in the cluster with the same group name will form a cluster "
+"together. Make sure the group name matches with all the nodes in the cluster "
+"you want to form a cluster with."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:594 configuration.xml:1099 configuration.xml:1351
+#, no-c-format
+msgid "Clustered"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:596
+#, no-c-format
+msgid ""
+"If true the post office will take part in a cluster to form distributed "
+"queues and topics. If false then it will not participate in the cluster. If "
+"false, then all the cluster related attributes will be ignored."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:603
+#, no-c-format
+msgid "StateTimeout"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:605
+#, no-c-format
+msgid ""
+"The maximum time to wait when waiting for the group state to arrive when a "
+"node joins a pre-existing cluster."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:609 configuration.xml:618
+#, no-c-format
+msgid "The default value is <literal>5000</literal> milliseconds."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:613
+#, no-c-format
+msgid "CastTimeout"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:615
+#, no-c-format
+msgid "The maximum time to wait for a reply casting message synchronously."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:623
+#, no-c-format
+msgid "FailoverOnNodeLeave"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:625
+#, no-c-format
+msgid ""
+"If this attribute is <literal>true</literal> then if a server node is shut "
+"down cleanly, then this will cause any connections on the shutting down node "
+"to failover onto another node."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:629
+#, no-c-format
+msgid "The default value for this is attribute is <literal>false</literal>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:633
+#, no-c-format
+msgid "MaxConcurrentReplications"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:635
+#, no-c-format
+msgid ""
+"The maximum number of concurrent replication requests to make before "
+"blocking for replies to come back. This prevents us overwhelming JGroups. "
+"This is rarely a good reason to change this."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:640
+#, no-c-format
+msgid "The default value is <literal>50</literal>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:643
+#, no-c-format
+msgid "ControlChannelConfig"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:645
+#, no-c-format
+msgid ""
+"JBoss Messaging uses JGroups for all group management. This contains the "
+"JGroups stack configuration for the control channel."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:649
+#, no-c-format
+msgid ""
+"The control channel is used for sending request/receiving responses from "
+"other nodes in the cluster"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:652 configuration.xml:669
+#, no-c-format
+msgid ""
+"The details of the JGroups configuration won't be discussed here since it is "
+"standard JGroups configuration. Detailed information on JGroups can be found "
+"in JGroups release documentation or on-line at <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:660
+#, no-c-format
+msgid "DataChannelConfig"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:662
+#, no-c-format
+msgid ""
+"JBoss Messaging uses JGroups for all group management. This contains the "
+"JGroups stack configuration for the data channel."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:665
+#, no-c-format
+msgid ""
+"The data channel is used for sending sending/receiving messages from other "
+"nodes in the cluster and for replicating session data."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:679
+#, no-c-format
+msgid "Configuring the Persistence Manager"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:681
+#, no-c-format
+msgid ""
+"It is the job of the persistence manager to manage all message related "
+"persistence."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:684
+#, no-c-format
+msgid ""
+"JBoss Messaging ships with a JDBC Persistence Manager used for handling "
+"persistence of message data in a relational database accessed via JDBC. The "
+"Persistence Manager implementation is pluggable (the Persistence Manager is "
+"a Messaging server plug-in), this making possible to provide other "
+"implementations for persisting message data in non relational stores, file "
+"stores etc."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:691
+#, no-c-format
+msgid ""
+"The configuration of \"persistent\" services is grouped in a <filename>xxx-"
+"persistence-service.xml</filename> file, where xxx corresponds to the "
+"database name. By default, Messaging ships with a <filename>hsqldb-"
+"persistence-service.xml</filename>, which configures the Messaging server to "
+"use the in-VM Hypersonic database instance that comes by default with any "
+"JBossAS instance."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:699
+#, no-c-format
+msgid ""
+"The default Persistence Manager configuration is works out of the box with "
+"Hypersonic, however it must be stressed that Hypersonic should not be used "
+"in a production environment mainly due to its limited support for "
+"transaction isolation and its propensity to behave erratically under high "
+"load."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:705
+#, no-c-format
+msgid ""
+"The <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQDB"
+"\">Critique of Hypersonic</ulink> wiki page outlines some of the well-known "
+"issues occurring when using this database."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:711
+#, no-c-format
+msgid ""
+"JBoss Messaging also ships with pre-made Persistence Manager configurations "
+"for MySQL, Oracle, PostgreSQL, Sybase and MS SQL Server. The example "
+"<filename>mysql-persistence-service.xml</filename>, <filename>ndb-"
+"persistence-service.xml</filename>, <filename>oracle-persistence-service."
+"xml</filename>, <filename>postgres-persistence-service.xml</filename>, "
+"<filename>sybase-persistence-service.xml</filename>, <filename>mssql-"
+"persistence-service.xml</filename> and <filename>db2-persistence-service."
+"xml</filename> configuration files are available in the <filename>examples/"
+"config</filename> directory of the release bundle."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:722
+#, no-c-format
+msgid ""
+"Users are encouraged to contribute their own configuration files where we "
+"will thoroughly test them before certifying them for supported use with "
+"JBoss Messaging. The JDBC Persistence Manager has been designed to use "
+"standard SQL for the DML so writing a JDBC Persistence Manager configuration "
+"for another database is usually only a fairly simple matter of changing DDL "
+"in the configuration which is likely to be different for different databases."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:730
+#, no-c-format
+msgid ""
+"JBoss Messaging also ships with a Null Persistence Manager config - this can "
+"be used when you don't want any persistence at all."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:733
+#, no-c-format
+msgid "The default Hypersonic persistence configuration file is listed below:"
+msgstr ""
+
+#. Tag: programlisting
+#: configuration.xml:736
+#, no-c-format
+msgid ""
+"<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\">jboss:"
+"service=TransactionManager</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 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\"><![CDATA[\n"
+" CREATE_DUAL=CREATE TABLE JBM_DUAL (DUMMY INTEGER, PRIMARY KEY (DUMMY)) "
+"ENGINE = INNODB\n"
+" CREATE_MESSAGE_REFERENCE=CREATE TABLE JBM_MSG_REF (CHANNEL_ID BIGINT, "
+"MESSAGE_ID BIGINT, TRANSACTION_ID BIGINT, STATE CHAR(1), ORD BIGINT, "
+"PAGE_ORD BIGINT, DELIVERY_COUNT INTEGER, SCHED_DELIVERY BIGINT, PRIMARY KEY"
+"(CHANNEL_ID, MESSAGE_ID)) ENGINE = INNODB\n"
+" CREATE_IDX_MESSAGE_REF_TX=CREATE INDEX JBM_MSG_REF_TX ON JBM_MSG_REF "
+"(TRANSACTION_ID)\n"
+" CREATE_IDX_MESSAGE_REF_ORD=CREATE INDEX JBM_MSG_REF_ORD ON JBM_MSG_REF "
+"(ORD)\n"
+" CREATE_IDX_MESSAGE_REF_PAGE_ORD=CREATE INDEX JBM_MSG_REF_PAGE_ORD ON "
+"JBM_MSG_REF (PAGE_ORD)\n"
+" CREATE_IDX_MESSAGE_REF_MESSAGE_ID=CREATE INDEX JBM_MSG_REF_MESSAGE_ID ON "
+"JBM_MSG_REF (MESSAGE_ID)\n"
+" CREATE_IDX_MESSAGE_REF_SCHED_DELIVERY=CREATE INDEX "
+"JBM_MSG_REF_SCHED_DELIVERY ON JBM_MSG_REF (SCHED_DELIVERY)\n"
+" CREATE_MESSAGE=CREATE TABLE JBM_MSG (MESSAGE_ID BIGINT, RELIABLE CHAR(1), "
+"EXPIRATION BIGINT, TIMESTAMP BIGINT, PRIORITY TINYINT, TYPE TINYINT, HEADERS "
+"MEDIUMBLOB, PAYLOAD LONGBLOB, PRIMARY KEY (MESSAGE_ID)) ENGINE = INNODB\n"
+" CREATE_IDX_MESSAGE_TIMESTAMP=CREATE INDEX JBM_MSG_REF_TIMESTAMP ON "
+"JBM_MSG (TIMESTAMP)\n"
+" CREATE_TRANSACTION=CREATE TABLE JBM_TX (NODE_ID INTEGER, TRANSACTION_ID "
+"BIGINT, BRANCH_QUAL VARBINARY(254), FORMAT_ID INTEGER, GLOBAL_TXID VARBINARY"
+"(254), PRIMARY KEY (TRANSACTION_ID)) ENGINE = INNODB\n"
+" CREATE_COUNTER=CREATE TABLE JBM_COUNTER (NAME VARCHAR(255), NEXT_ID "
+"BIGINT, PRIMARY KEY(NAME)) ENGINE = INNODB\n"
+" INSERT_DUAL=INSERT INTO JBM_DUAL VALUES (1)\n"
+" CHECK_DUAL=SELECT 1 FROM JBM_DUAL\n"
+" INSERT_MESSAGE_REF=INSERT INTO JBM_MSG_REF (CHANNEL_ID, MESSAGE_ID, "
+"TRANSACTION_ID, STATE, ORD, PAGE_ORD, DELIVERY_COUNT, SCHED_DELIVERY) VALUES "
+"(?, ?, ?, ?, ?, ?, ?, ?)\n"
+" DELETE_MESSAGE_REF=DELETE FROM JBM_MSG_REF WHERE MESSAGE_ID=? AND "
+"CHANNEL_ID=? AND STATE='C'\n"
+" UPDATE_MESSAGE_REF=UPDATE JBM_MSG_REF SET TRANSACTION_ID=?, STATE='-' "
+"WHERE MESSAGE_ID=? AND CHANNEL_ID=? AND STATE='C'\n"
+" UPDATE_PAGE_ORDER=UPDATE JBM_MSG_REF SET PAGE_ORD = ? WHERE MESSAGE_ID=? "
+"AND CHANNEL_ID=?\n"
+" COMMIT_MESSAGE_REF1=UPDATE JBM_MSG_REF SET STATE='C', TRANSACTION_ID = "
+"NULL WHERE TRANSACTION_ID=? AND STATE='+'\n"
+" COMMIT_MESSAGE_REF2=DELETE FROM JBM_MSG_REF WHERE TRANSACTION_ID=? AND "
+"STATE='-'\n"
+" ROLLBACK_MESSAGE_REF1=DELETE FROM JBM_MSG_REF WHERE TRANSACTION_ID=? AND "
+"STATE='+'\n"
+" ROLLBACK_MESSAGE_REF2=UPDATE JBM_MSG_REF SET STATE='C', TRANSACTION_ID = "
+"NULL WHERE TRANSACTION_ID=? AND STATE='-'\n"
+" LOAD_PAGED_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, PAGE_ORD, "
+"SCHED_DELIVERY FROM JBM_MSG_REF WHERE CHANNEL_ID = ? AND PAGE_ORD BETWEEN ? "
+"AND ? ORDER BY PAGE_ORD\n"
+" LOAD_UNPAGED_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, SCHED_DELIVERY FROM "
+"JBM_MSG_REF WHERE STATE = 'C' AND CHANNEL_ID = ? AND PAGE_ORD IS NULL ORDER "
+"BY ORD\n"
+" LOAD_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, SCHED_DELIVERY FROM "
+"JBM_MSG_REF WHERE STATE = 'C' AND CHANNEL_ID = ? ORDER BY ORD \n"
+" UPDATE_REFS_NOT_PAGED=UPDATE JBM_MSG_REF SET PAGE_ORD = NULL WHERE "
+"PAGE_ORD BETWEEN ? AND ? AND CHANNEL_ID=?\n"
+" SELECT_MIN_MAX_PAGE_ORD=SELECT MIN(PAGE_ORD), MAX(PAGE_ORD) FROM "
+"JBM_MSG_REF WHERE CHANNEL_ID = ?\n"
+" SELECT_EXISTS_REF_MESSAGE_ID=SELECT MESSAGE_ID FROM JBM_MSG_REF WHERE "
+"MESSAGE_ID = ?\n"
+" UPDATE_DELIVERY_COUNT=UPDATE JBM_MSG_REF SET DELIVERY_COUNT = ? WHERE "
+"CHANNEL_ID = ? AND MESSAGE_ID = ?\n"
+" UPDATE_CHANNEL_ID=UPDATE JBM_MSG_REF SET CHANNEL_ID = ? WHERE CHANNEL_ID "
+"= ?\n"
+" LOAD_MESSAGES=SELECT MESSAGE_ID, RELIABLE, EXPIRATION, TIMESTAMP, "
+"PRIORITY, HEADERS, PAYLOAD, TYPE FROM JBM_MSG\n"
+" INSERT_MESSAGE=INSERT INTO JBM_MSG (MESSAGE_ID, RELIABLE, EXPIRATION, "
+"TIMESTAMP, PRIORITY, TYPE, HEADERS, PAYLOAD) VALUES "
+"(?, ?, ?, ?, ?, ?, ?, ?)\n"
+" INSERT_MESSAGE_CONDITIONAL=INSERT INTO JBM_MSG (MESSAGE_ID, RELIABLE, "
+"EXPIRATION, TIMESTAMP, PRIORITY, TYPE, INST_TIME) SELECT ?, ?, ?, ?, ?, ?, ? "
+"FROM JBM_DUAL WHERE NOT EXISTS (SELECT MESSAGE_ID FROM JBM_MSG WHERE "
+"MESSAGE_ID = ?)\n"
+" UPDATE_MESSAGE_4CONDITIONAL=UPDATE JBM_MSG SET HEADERS=?, PAYLOAD=? WHERE "
+"MESSAGE_ID=?\n"
+" INSERT_MESSAGE_CONDITIONAL_FULL=INSERT INTO JBM_MSG (MESSAGE_ID, "
+"RELIABLE, EXPIRATION, TIMESTAMP, PRIORITY, TYPE, HEADERS, PAYLOAD) "
+"SELECT ?, ?, ?, ?, ?, ?, ?, ? FROM JBM_DUAL WHERE NOT EXISTS (SELECT "
+"MESSAGE_ID FROM JBM_MSG WHERE MESSAGE_ID = ?) \n"
+" MESSAGE_ID_COLUMN=MESSAGE_ID \n"
+" DELETE_MESSAGE=DELETE FROM JBM_MSG WHERE MESSAGE_ID = ? AND NOT EXISTS "
+"(SELECT * FROM JBM_MSG_REF WHERE JBM_MSG_REF.MESSAGE_ID = ?) \n"
+" INSERT_TRANSACTION=INSERT INTO JBM_TX (NODE_ID, TRANSACTION_ID, "
+"BRANCH_QUAL, FORMAT_ID, GLOBAL_TXID) VALUES(?, ?, ?, ?, ?)\n"
+" DELETE_TRANSACTION=DELETE FROM JBM_TX WHERE NODE_ID = ? AND "
+"TRANSACTION_ID = ?\n"
+" SELECT_PREPARED_TRANSACTIONS=SELECT TRANSACTION_ID, BRANCH_QUAL, "
+"FORMAT_ID, GLOBAL_TXID FROM JBM_TX WHERE NODE_ID = ?\n"
+" SELECT_MESSAGE_ID_FOR_REF=SELECT MESSAGE_ID, CHANNEL_ID FROM JBM_MSG_REF "
+"WHERE TRANSACTION_ID = ? AND STATE = '+' ORDER BY ORD\n"
+" SELECT_MESSAGE_ID_FOR_ACK=SELECT MESSAGE_ID, CHANNEL_ID FROM JBM_MSG_REF "
+"WHERE TRANSACTION_ID = ? AND STATE = '-' ORDER BY ORD\n"
+" UPDATE_COUNTER=UPDATE JBM_COUNTER SET NEXT_ID = ? WHERE NAME=?\n"
+" SELECT_COUNTER=SELECT NEXT_ID FROM JBM_COUNTER WHERE NAME=? FOR UPDATE\n"
+" INSERT_COUNTER=INSERT INTO JBM_COUNTER (NAME, NEXT_ID) VALUES (?, ?)\n"
+" SELECT_ALL_CHANNELS=SELECT DISTINCT(CHANNEL_ID) FROM JBM_MSG_REF\n"
+" UPDATE_TX=UPDATE JBM_TX SET NODE_ID=? WHERE NODE_ID=?\n"
+" ]]></attribute>\n"
+" \n"
+" <!-- The maximum number of parameters to include in a prepared "
+"statement -->\n"
+" \n"
+" <attribute name=\"MaxParams\">500</attribute>\n"
+"\n"
+" <attribute name=\"UseNDBFailoverStrategy\">true</"
+"attribute>\n"
+" \n"
+" </mbean>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:739
+#, no-c-format
+msgid "Important notes for Sybase and Microsoft SQL Server users"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:740
+#, 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 2 KB. Any longer message "
+"payload is truncated without any information or warning. The database "
+"parameters have to be updated to set the @@TEXTSIZE parameter to a higher "
+"value. The truncation behavior may also be observed in MSSQL Server if "
+"@@TEXTSIZE is changed from its default value to a smaller one. Further "
+"information: <ulink url=\"http://jira.jboss.com/jira/browse/SOA-554\"></"
+"ulink>."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:742
+#, no-c-format
+msgid ""
+"Sybase database may fail to insert a row if the total size of the row "
+"exceeds the page size allocated for the database. A command line option "
+"passed to the dataserver command used to start the database can be used to "
+"change the page size. Further information: <ulink url=\"http://jira.jboss."
+"com/jira/browse/SOA-553\"></ulink>"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:744
+#, no-c-format
+msgid ""
+"Microsoft SQL Server does not automatically de-allocate the hard-drive space "
+"occupied by data in a database when that data is deleted. If used as a data-"
+"store for services that temporarily store many records, such as a messaging "
+"service, the disk space used will grow to be much greater than the amount of "
+"data actually being stored. Your database administrator should implement "
+"database maintenance plans to ensure that unused space is reclaimed. Please "
+"refer to your Microsoft SQL Server documentation for the DBCC commands "
+"ShrinkDatabase and UpdateUsage for guidance. <ulink url=\"https://jira.jboss."
+"org/jira/browse/SOA-629\"></ulink>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:751
+#, no-c-format
+msgid "We now discuss the MBean attributes of the PersistenceManager MBean"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:757
+#, no-c-format
+msgid ""
+"Set this to <literal>true</literal> if you wish the Persistence Manager to "
+"attempt to create the tables (and indexes) when it starts. If the tables (or "
+"indexes) already exist a <literal>SQLException</literal> will be thrown by "
+"the JDBC driver and ignored by the Persistence Manager, allowing it to "
+"continue."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:767 configuration.xml:882
+#, no-c-format
+msgid "UsingBatchUpdates"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:769 configuration.xml:884
+#, no-c-format
+msgid ""
+"Set this to <literal>true</literal> if the database supports JDBC batch "
+"updates. The JDBC Persistence Manager will then group multiple database "
+"updates in batches to aid performance."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:773 configuration.xml:888
+#, no-c-format
+msgid ""
+"By default the value of <literal>UsingBatchUpdates</literal> attribute is "
+"set to <literal>false</literal>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:777
+#, no-c-format
+msgid "UsingBinaryStream"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:779
+#, no-c-format
+msgid ""
+"Set this to <literal>true</literal> if you want messages to be store and "
+"read using a JDBC binary stream rather than using getBytes(), setBytes(). "
+"Some database has limits on the maximum number of bytes that can be get/set "
+"using getBytes()/setBytes()."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:784
+#, no-c-format
+msgid ""
+"By default the value of <literal>UsingBinaryStream</literal> attribute is "
+"set to <literal>true</literal>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:788
+#, no-c-format
+msgid "UsingTrailingByte"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:790
+#, no-c-format
+msgid ""
+"Certain version of Sybase are known to truncate blobs if they have trailing "
+"zeros. To prevent this if this attribute is set to <literal>true</literal> "
+"then a trailing non zero byte will be added and removed to each blob before "
+"and after persistence to prevent the database from truncating it. Currently "
+"this is only known to be necessary for Sybase."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:797
+#, no-c-format
+msgid ""
+"By default the value of <literal>UsingTrailingByte</literal> attribute is "
+"set to <literal>false</literal>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:801
+#, no-c-format
+msgid "SupportsBlobOnSelect"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:803
+#, no-c-format
+msgid ""
+"Oracle (and possibly other databases) is known to not allow BLOBs to be "
+"inserted using a INSERT INTO ... SELECT FROM statement, and requires a two "
+"stage conditional insert of messages. If this value is false then such a two "
+"stage insert will be used."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:808
+#, no-c-format
+msgid ""
+"By default the value of <literal>SupportsBlobOnSelect</literal> attribute is "
+"set to <literal>true</literal>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:821
+#, no-c-format
+msgid "MaxParams"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:823
+#, no-c-format
+msgid ""
+"When loading messages the persistence manager will generate prepared "
+"statements with many parameters. This value tells the persistence manager "
+"what the absolute maximum number of parameters are allowable per prepared "
+"statement."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:828
+#, no-c-format
+msgid ""
+"By default the value of <literal>MaxParams</literal> attribute is set to "
+"<literal>100</literal>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:833
+#, no-c-format
+msgid "UseNDBFailoverStrategy"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:835
+#, no-c-format
+msgid ""
+"When running in a clustered database environment it is possible that some "
+"databases, MySQL for instance, can fail during the commit of a database "
+"transaction. This can happen if the database node dies whilst committing "
+"meaning that the final state of the transaction is unknown. If this "
+"attribute is set to true and the above happens then the SQL statement will "
+"be re-executed, however if there is a further error an assumption is made "
+"that this is because the previous transaction committed successfully and the "
+"error is ignored."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:844
+#, no-c-format
+msgid ""
+"By default the value of <literal>UseNDBFailoverStrategy</literal> attribute "
+"is set to <literal>false</literal>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:855
+#, no-c-format
+msgid "Configuring the JMS user manager"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:857
+#, no-c-format
+msgid ""
+"The JMS user manager handles the mapping of pre-configured client IDs to "
+"users and also managers the user and role tables which may or may not be "
+"used depending on which login module you have configured"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:861
+#, no-c-format
+msgid "Here is an example JMSUserManager configuration"
+msgstr ""
+
+#. Tag: programlisting
+#: configuration.xml:863
+#, no-c-format
+msgid ""
+"<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\"><![CDATA[\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"
+" 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"
+" SELECT_PRECONF_CLIENTID=SELECT CLIENTID FROM JBM_USER WHERE "
+"USER_ID=?\n"
+" POPULATE.TABLES.1=INSERT INTO JBM_USER (USER_ID,PASSWD,"
+"CLIENTID)\n"
+" VALUES ('dilbert','dogbert','dilbert-id')\n"
+" ]]></attribute>\n"
+" </mbean>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:866
+#, no-c-format
+msgid "We now discuss the MBean attributes of the JMSUserManager MBean"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:872
+#, no-c-format
+msgid ""
+"Set this to <literal>true</literal> if you wish the JMS user manager to "
+"attempt to create the tables (and indexes) when it starts. If the tables (or "
+"indexes) already exist a <literal>SQLException</literal> will be thrown by "
+"the JDBC driver and ignored by the Persistence Manager, allowing it to "
+"continue."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:899
+#, no-c-format
+msgid ""
+"Default user and role data can also be specified here. Any data to be "
+"inserted must be specified with property names starting with "
+"<literal>POPULATE.TABLES</literal> as in the above example."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:910
+#, no-c-format
+msgid "Configuring Destinations"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:913
+#, no-c-format
+msgid "Pre-configured destinations"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:915
+#, no-c-format
+msgid ""
+"JBoss Messaging ships with a default set of pre-configured destinations that "
+"will be deployed during the server start up. The file that contains "
+"configuration for these destinations is <filename>destinations-service.xml</"
+"filename>. A section of this file is listed below:"
+msgstr ""
+
+#. Tag: programlisting
+#: configuration.xml:921
+#, no-c-format
+msgid ""
+"<!--\n"
+" The Default Dead Letter Queue. This destination is a dependency 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 "
+"queue for\n"
+" 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,"
+"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,"
+"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,"
+"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,"
+"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:927
+#, no-c-format
+msgid "Configuring queues"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:930
+#, no-c-format
+msgid "We now discuss the attributes of the Queue MBean"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:933 configuration.xml:1209
+#, no-c-format
+msgid "Name"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:935
+#, no-c-format
+msgid "The name of the queue"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:939 configuration.xml:1215
+#, no-c-format
+msgid "JNDIName"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:941
+#, no-c-format
+msgid "The JNDI name where the queue is bound"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:945 configuration.xml:1221
+#, no-c-format
+msgid "<title>DLQ</title>"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:947
+#, no-c-format
+msgid ""
+"The DLQ used for this queue. Overrides any value set on the ServerPeer config"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:952 configuration.xml:1228
+#, no-c-format
+msgid "ExpiryQueue"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:954
+#, no-c-format
+msgid ""
+"The Expiry queue used for this queue. Overrides any value set on the "
+"ServerPeer config"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:959 configuration.xml:1235
+#, no-c-format
+msgid "RedeliveryDelay"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:961
+#, no-c-format
+msgid ""
+"The redelivery delay to be used for this queue. Overrides any value set on "
+"the ServerPeer config"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:966 configuration.xml:1242
+#, no-c-format
+msgid "MaxDeliveryAttempts"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:968 configuration.xml:1244
+#, no-c-format
+msgid ""
+"The maximum number of times delivery of a message will be attempted before "
+"sending the message to the DLQ, if configured. If set to -1 (the default), "
+"the value from the ServerPeer config is used. Any other setting overrides "
+"the value set on the ServerPeer config."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:976 configuration.xml:1252
+#, no-c-format
+msgid "Destination Security Configuration"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:978 configuration.xml:1254
+#, no-c-format
+msgid ""
+"<literal>SecurityConfig</literal> - allows you to determine which roles are "
+"allowed to read, write and create on the destination. It has exactly the "
+"same syntax and semantics as the security configuration in JBossMQ "
+"destinations."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:983 configuration.xml:1259
+#, no-c-format
+msgid ""
+"The <literal>SecurityConfig</literal> element should contain one "
+"<literal><security></literal> element. The <literal><security></"
+"literal> element can contain multiple <literal><role></literal> "
+"elements. Each <literal><role></literal> element defines the access "
+"for that particular role."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:990 configuration.xml:1266
+#, no-c-format
+msgid ""
+"If the <literal>read</literal> attribute is <literal>true</literal> then "
+"that role will be able to read (create consumers, receive messages or "
+"browse) this destination."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:994 configuration.xml:1270
+#, no-c-format
+msgid ""
+"If the <literal>write</literal> attribute is <literal>true</literal> then "
+"that role will be able to write (create producers or send messages) to this "
+"destination."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:998 configuration.xml:1274
+#, no-c-format
+msgid ""
+"If the <literal>create</literal> attribute is <literal>true</literal> then "
+"that role will be able to create durable subscriptions on this destination."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1002 configuration.xml:1278
+#, no-c-format
+msgid ""
+"Note that the security configuration 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."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1008 configuration.xml:1284
+#, no-c-format
+msgid "Destination paging parameters"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1010 configuration.xml:1286
+#, no-c-format
+msgid ""
+"'Pageable Channels' are a sophisticated new feature available in JBoss "
+"Messaging."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1013 configuration.xml:1289
+#, no-c-format
+msgid ""
+"If your application needs to support very large queues or subscriptions "
+"containing potentially millions of messages, then it's not possible to store "
+"them all in memory at once."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1017 configuration.xml:1293
+#, no-c-format
+msgid ""
+"JBoss Messaging solves this problem but letting you specify the maximum "
+"number of messages that can be stored in memory at any one time, on a queue-"
+"by-queue, or topic-by-topic basis. JBoss Messaging then pages messages to "
+"and from storage transparently in blocks, allowing queues and subscriptions "
+"to grow to very large sizes without any performance degradation as channel "
+"size increases."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1025 configuration.xml:1301
+#, no-c-format
+msgid ""
+"This has been tested with in excess of 10 million 2K messages on very basic "
+"hardware and has the potential to scale to much larger number of messages."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1029 configuration.xml:1305
+#, no-c-format
+msgid "The individual parameters are:"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1031 configuration.xml:1307
+#, no-c-format
+msgid ""
+"<literal>FullSize</literal> - this is the maximum number of messages held by "
+"the queue or topic subscriptions in memory at any one time. The actual queue "
+"or subscription can hold many more messages than this but these are paged to "
+"and from storage as necessary as messages are added or consumed."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1037 configuration.xml:1313
+#, no-c-format
+msgid ""
+"<literal>PageSize</literal> - When loading messages from the queue or "
+"subscription this is the maximum number of messages to pre-load in one "
+"operation."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1041 configuration.xml:1317
+#, no-c-format
+msgid ""
+"<literal>DownCacheSize</literal> - When paging messages to storage from the "
+"queue they first go into a \"Down Cache\" before being written to storage. "
+"This enables the write to occur as a single operation thus aiding "
+"performance. This setting determines the max number of messages that the "
+"Down Cache will hold before they are flushed to storage."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1048 configuration.xml:1324
+#, no-c-format
+msgid ""
+"If no values for <literal>FullSize</literal>, <literal>PageSize</literal>, "
+"or <literal>DownCacheSize</literal> are specified they will default to "
+"values 75000, 2000, 2000 respectively."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1053 configuration.xml:1329
+#, no-c-format
+msgid ""
+"If you want to specify the paging parameters used for temporary queues then "
+"you need to specify them on the appropriate connection factory. See "
+"connection factory configuration for details."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1059 configuration.xml:1335
+#, no-c-format
+msgid "CreatedProgrammatically"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1061
+#, no-c-format
+msgid ""
+"Returns <literal>true</literal> if the queue was created programmatically"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1066
+#, no-c-format
+msgid "MessageCount"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1068
+#, no-c-format
+msgid ""
+"Returns the total number of messages in the queue = number not being "
+"delivered + number being delivered + number being scheduled"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1074
+#, no-c-format
+msgid "ScheduledMessageCount"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1076
+#, no-c-format
+msgid ""
+"Returns the number of scheduled messages in the queue. This is the number of "
+"messages scheduled to be delivered at a later date."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1080
+#, no-c-format
+msgid ""
+"Scheduled delivery is a feature of JBoss Messaging where you can send a "
+"message and specify the earliest time at which it will be delivered. E.g. "
+"you can send a message now, but the message won't actually be delivered "
+"until 2 hours time."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1085
+#, no-c-format
+msgid ""
+"To do this, you just need to set the following header in the message before "
+"sending:"
+msgstr ""
+
+#. Tag: programlisting
+#: configuration.xml:1088
+#, 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:1091 configuration.xml:1342
+#, no-c-format
+msgid "MaxSize"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1093
+#, no-c-format
+msgid ""
+"A maximum size (in number of messages) can be specified for a queue. Any "
+"messages that arrive beyond this point will be dropped. The default is "
+"<literal>-1</literal> which is unbounded."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1101
+#, no-c-format
+msgid "Clustered destinations must have this set to <literal>true</literal>."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1106
+#, no-c-format
+msgid "MessageCounter"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1108
+#, no-c-format
+msgid "Each queue maintains a message counter."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1112
+#, no-c-format
+msgid "MessageCounterStatistics"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1114
+#, no-c-format
+msgid "The statistics for the message counter"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1118 configuration.xml:1358
+#, no-c-format
+msgid "MessageCounterHistoryDayLimit"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1120 configuration.xml:1360
+#, no-c-format
+msgid ""
+"The maximum number of days to hold message counter history for. Overrides "
+"any value set on the ServerPeer."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1125
+#, no-c-format
+msgid "ConsumerCount"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1127
+#, no-c-format
+msgid "The number of consumers currently consuming from the queue."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1133
+#, no-c-format
+msgid "We now discuss the MBean operations of the Queue MBean"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1136 configuration.xml:1416
+#, no-c-format
+msgid "RemoveAllMessages"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1138
+#, no-c-format
+msgid "Remove (and delete) all messages from the queue."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1140
+#, no-c-format
+msgid ""
+"Use this with caution. It will permanently delete all messages from the "
+"queue."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1144 configuration.xml:1463
+#, no-c-format
+msgid "ListAllMessages"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1146
+#, no-c-format
+msgid "List all messages currently in the queue"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1148 configuration.xml:1158 configuration.xml:1169
+#, no-c-format
+msgid ""
+"There are two overloaded versions of this operation: One takes a JMS "
+"selector as an argument, the other does not. By using the selector you can "
+"retrieve a subset of the messages in the queue that match the criteria"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1154 configuration.xml:1484
+#, no-c-format
+msgid "ListDurableMessages"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1156
+#, no-c-format
+msgid "As listAllMessages but only lists the durable messages"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1164 configuration.xml:1473
+#, no-c-format
+msgid "ListNonDurableMessages"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1166
+#, no-c-format
+msgid "As listAllMessages but only lists the non durable messages"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1175
+#, no-c-format
+msgid "ResetMessageCounter"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1177
+#, no-c-format
+msgid "Resets the message counter to zero."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1181
+#, no-c-format
+msgid "ResetMessageCounterHistory"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1183
+#, no-c-format
+msgid "Resets the message counter history."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1187
+#, no-c-format
+msgid "ListMessageCounterAsHTML"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1189
+#, no-c-format
+msgid "Lists the message counter in an easy to display HTML format"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1194
+#, no-c-format
+msgid "ListMessageCounterHistoryAsHTML"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1196
+#, no-c-format
+msgid "Lists the message counter history in an easy to display HTML format"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1203
+#, no-c-format
+msgid "Configuring topics"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1206
+#, no-c-format
+msgid "We now discuss the MBean attributes of the Topic MBean"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1211
+#, no-c-format
+msgid "The name of the topic"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1217
+#, no-c-format
+msgid "The JNDI name where the topic is bound"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1223
+#, no-c-format
+msgid ""
+"The DLQ used for this topic. Overrides any value set on the ServerPeer config"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1230
+#, no-c-format
+msgid ""
+"The Expiry queue used for this topic. Overrides any value set on the "
+"ServerPeer config"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1237
+#, no-c-format
+msgid ""
+"The redelivery delay to be used for this topic. Overrides any value set on "
+"the ServerPeer config"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1337
+#, no-c-format
+msgid ""
+"Returns <literal>true</literal> if the topic was created programmatically"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1344
+#, no-c-format
+msgid ""
+"A maximum size (in number of messages) can be specified for a topic "
+"subscription. Any messages that arrive beyond this point will be dropped. "
+"The default is <literal>-1</literal> which is unbounded."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1353
+#, no-c-format
+msgid "Clustered destinations must have this set to <literal>true</literal>"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1367
+#, no-c-format
+msgid ""
+"Return a list of the message counters for the subscriptions of this topic."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1372
+#, no-c-format
+msgid "AllMessageCount"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1374
+#, no-c-format
+msgid "Return the total number of messages in all subscriptions of this topic."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1379
+#, no-c-format
+msgid "DurableMessageCount"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1381
+#, no-c-format
+msgid ""
+"Return the total number of durable messages in all subscriptions of this "
+"topic."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1386
+#, no-c-format
+msgid "NonDurableMessageCount"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1388
+#, no-c-format
+msgid ""
+"Return the total number of non durable messages in all subscriptions of this "
+"topic."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1393
+#, no-c-format
+msgid "AllSubscriptionsCount"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1395
+#, no-c-format
+msgid "The count of all subscriptions on this topic"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1399
+#, no-c-format
+msgid "DurableSubscriptionsCount"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1401
+#, no-c-format
+msgid "The count of all durable subscriptions on this topic"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1405
+#, no-c-format
+msgid "NonDurableSubscriptionsCount"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1407
+#, no-c-format
+msgid "The count of all non durable subscriptions on this topic"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1413
+#, no-c-format
+msgid "We now discuss the MBean operations of the Topic MBean"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1418
+#, no-c-format
+msgid "Remove (and delete) all messages from the subscriptions of this topic."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1419
+#, no-c-format
+msgid ""
+"Use this with caution. It will permanently delete all messages from the "
+"topic."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1424
+#, no-c-format
+msgid "ListAllSubscriptions"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1426
+#, no-c-format
+msgid "List all subscriptions of this topic"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1430
+#, no-c-format
+msgid "ListDurableSubscriptions"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1432
+#, no-c-format
+msgid "List all durable subscriptions of this topic"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1436
+#, no-c-format
+msgid "ListNonDurableSubscriptions"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1438
+#, no-c-format
+msgid "List all non durable subscriptions of this topic"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1442
+#, no-c-format
+msgid "ListAllSubscriptionsAsHTML"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1444
+#, no-c-format
+msgid "List all subscriptions of this topic in an easy to display HTML format"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1449
+#, no-c-format
+msgid "ListDurableSubscriptionsAsHTML"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1451
+#, no-c-format
+msgid ""
+"List all durable subscriptions of this topic in an easy to display HTML "
+"format"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1456
+#, no-c-format
+msgid "ListNonDurableSubscriptionsAsHTML"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1458
+#, no-c-format
+msgid ""
+"List all non durable subscriptions of this topic in an easy to display HTML "
+"format"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1465
+#, no-c-format
+msgid "Lists all messages for the specified subscription."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1467 configuration.xml:1478 configuration.xml:1489
+#, no-c-format
+msgid ""
+"There are two overloaded versions of this operation. One that takes a "
+"selector and one that does not. By specifying the selector you can limit the "
+"messages returned."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1475
+#, no-c-format
+msgid "Lists all non durable messages for the specified subscription."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1486
+#, no-c-format
+msgid "Lists all durable messages for the specified subscription."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1500
+#, no-c-format
+msgid "Configuring Connection Factories"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1502
+#, no-c-format
+msgid ""
+"With the default configuration JBoss Messaging binds two connection "
+"factories in JNDI at start-up."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1505
+#, no-c-format
+msgid ""
+"The first connection factory is the default non-clustered connection factory "
+"and is bound into the following JNDI contexts: <literal>/ConnectionFactory, /"
+"XAConnectionFactory, java:/ConnectionFactory, java:/XAConnectionFactory</"
+"literal>. This connection factory is provided to maintain compatibility with "
+"applications originally written against JBoss MQ which has no automatic "
+"failover or load balancing. This connection factory should be used if you do "
+"not require client side automatic failover or load balancing."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1514
+#, no-c-format
+msgid ""
+"The second connection factory is the default clustered connection factory "
+"and is bound into the following JNDI contexts <literal>/"
+"ClusteredConnectionFactory, /ClusteredXAConnectionFactory, java:/"
+"ClusteredConnectionFactory, java:/ClusteredXAConnectionFactory</literal>."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1520
+#, no-c-format
+msgid ""
+"You may want to configure additional connection factories, for instance if "
+"you want to provide a default client id for a connection factory, or if you "
+"want to bind it in different places in JNDI, if you want different "
+"connection factories to use different transports, or if you want to "
+"selective enable or disable load-balancing and/or automatic failover for a "
+"particular connection factory. Deploying a new connection factory is "
+"equivalent with adding a new ConnectionFactory MBean configuration to "
+"<filename>connection-factories-service.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1530
+#, no-c-format
+msgid ""
+"It is also possible to create an entirely new service deployment descriptor "
+"<filename>xxx-service.xml</filename> altogether and deploy it in <filename>"
+"$JBOSS_HOME/server/messaging/deploy</filename>."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1534
+#, no-c-format
+msgid ""
+"Connection factories can support automatic failover and/or load-balancing by "
+"setting the corresponding attributes"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1537
+#, no-c-format
+msgid "An example connection factory configuration is presented below:"
+msgstr ""
+
+#. Tag: programlisting
+#: configuration.xml:1540
+#, no-c-format
+msgid ""
+"<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\">org.acme."
+"MyLoadBalancingFactory</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>"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1542
+#, no-c-format
+msgid ""
+"The above example would create a connection factory with pre-configured "
+"client ID <literal>myClientID</literal> and bind the connection factory in "
+"two places in the JNDI tree: <literal>/MyConnectionFactory</literal> and "
+"<literal>/factories/cf</literal>. The connection factory overrides the "
+"default values for PreFetchSize, DefaultTempQueueFullSize, "
+"DefaultTempQueuePageSize, DefaultTempQueueDownCacheSize and DupsOKBatchSize, "
+"SupportsFailover, SupportsLoadBalancing and LoadBalancingFactory. 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:1556
+#, no-c-format
+msgid "We now discuss the MBean attributes of the ConnectionFactory MBean"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1560
+#, no-c-format
+msgid "ClientID"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1562
+#, no-c-format
+msgid ""
+"Connection factories can be pre-configured with a client id. Any connections "
+"created using this connection factory will obtain this client id"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1568
+#, no-c-format
+msgid "JNDIBindings"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1570
+#, no-c-format
+msgid "The list of the JNDI bindings for this connection factory"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1574
+#, no-c-format
+msgid "PrefetchSize"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1576
+#, no-c-format
+msgid ""
+"This parameter specifies the window size in numbers of messages, 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. Please note that TCP also "
+"implements its own flow control, so if you set this to too large a number, "
+"then the TCP window size may be hit before the prefetchSize, which can cause "
+"writes to block."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1586
+#, no-c-format
+msgid "SlowConsumers"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1588
+#, no-c-format
+msgid ""
+"If you have very slow consumers, then you probably want to make sure they "
+"don't buffer any messages. Since this can prevent them from being consumed "
+"by faster consumers. Setting this to true is equivalent to setting "
+"PrefetchSize to 1"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1595
+#, no-c-format
+msgid "StrictTck"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1597
+#, no-c-format
+msgid ""
+"Set this to true if you want strict JMS behavior as required by the TCK."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1602
+#, no-c-format
+msgid "SendAcksAsync"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1604
+#, no-c-format
+msgid ""
+"Set this to true if you want acknowledgments to be sent asynchronously. This "
+"can speed up performance especially if you are using auto_acknowledge mode"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1610
+#, no-c-format
+msgid "Temporary queue paging parameters"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1612
+#, no-c-format
+msgid ""
+"DefaultTempQueueFullSize, DefaultTempQueuePageSize, "
+"DefaultTempQueueDownCacheSize are optional attributes that determine the "
+"default paging parameters to be used for any temporary destinations scoped "
+"to connections created using this connection factory. See the section on "
+"paging channels for more information on what these values mean. They will "
+"default to values of 200000, 2000 and 2000 respectively if omitted."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1622
+#, no-c-format
+msgid "DupsOKBatchSize"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1624
+#, no-c-format
+msgid ""
+"When using a session with acknowledge mode of DUPS_OK_ACKNOWLEDGE this "
+"setting determines how many acknowledgments it will buffer locally before "
+"sending. The default value is <literal>2000</literal>"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1631
+#, no-c-format
+msgid "SupportsLoadBalancing"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1633
+#, no-c-format
+msgid ""
+"When using a connection factory with a clustered JBoss Messaging "
+"installation you can choose whether to enable client side connection load-"
+"balancing. This is determined by setting the attribute supportsLoadBalancing "
+"on the connection factory."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1638
+#, no-c-format
+msgid ""
+"If load balancing is enabled on a connection factory then any connections "
+"created with that connection factory will be load-balanced across the nodes "
+"of the cluster. Once a connection is created on a particular node, it stays "
+"on that node."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1643
+#, no-c-format
+msgid ""
+"The exact policy that determines how connections are load balanced is "
+"determined by the LoadBalancingFactory attribute"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1646 configuration.xml:1673 configuration.xml:1686
+#, no-c-format
+msgid "The default value is <literal>false</literal>"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1651
+#, no-c-format
+msgid ""
+"When using a connection factory with a clustered JBoss Messaging "
+"installation you can choose whether to enable client side automatic "
+"failover. This is determined by setting the attribute supportsFailover on "
+"the connection factory."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1656
+#, no-c-format
+msgid ""
+"If automatic failover is enabled on a connection factory, then if a "
+"connection problem is detected with the connection then JBoss Messaging will "
+"automatically and transparently failover to another node in the cluster."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1661
+#, no-c-format
+msgid ""
+"The failover is transparent meaning the user can carry on using the "
+"sessions, consumers, producers and connection objects as before."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1665
+#, no-c-format
+msgid ""
+"If automatic failover is not required, then this attribute can be set to "
+"false. With automatic failover disabled it is up to the user code to catch "
+"connection exceptions in synchronous JMS operations and install a JMS "
+"ExceptionListener to catch exceptions asynchronously. When a connection is "
+"caught, the client side code should lookup a new connection factory using "
+"HAJNDI and recreate the connection using that."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1676
+#, no-c-format
+msgid "DisableRemotingChecks"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1678
+#, 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 the values and for many of them there's "
+"rarely a good reason to change them. To disable such sanity checking set "
+"this to false."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1682
+#, no-c-format
+msgid ""
+"There is rarely a good reason to disable checking. Only do so if you are "
+"absolutely sure in what you are doing."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1689
+#, no-c-format
+msgid "LoadBalancingFactory"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1691
+#, no-c-format
+msgid ""
+"If you are using a connection factory with client side load balancing then "
+"you can specify how the load balancing is implemented by overriding this "
+"attribute. The value must correspond to the name of a class which implements "
+"the interface org.jboss.jms.client.plugin.LoadBalancingFactory"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1697
+#, no-c-format
+msgid ""
+"The default value is org.jboss.jms.client.plugin."
+"RoundRobinLoadBalancingFactory, which load balances connections across the "
+"cluster in a round-robin fashion"
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1702
+#, no-c-format
+msgid "Connector"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1704
+#, no-c-format
+msgid ""
+"This specifies which remoting connector this connection factory uses. "
+"Different connection factories can use different connectors."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1708
+#, no-c-format
+msgid ""
+"For instance you could deploy one connection factory that creates "
+"connections that use the HTTP transport to communicate to the server and "
+"another that creates connections that use the bisocket transport to "
+"communicate."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1715
+#, no-c-format
+msgid "EnableOrderingGroup"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1717
+#, no-c-format
+msgid ""
+"This parameter controls whether the strict message ordering is enabled or "
+"not on the ConnectionFactory. If set to 'true', all messages that are sent "
+"from any producers created from this connection factory become ordering "
+"group messages."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1721
+#, no-c-format
+msgid "The default value is false."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1725
+#, no-c-format
+msgid "DefaultOrderingGroupName"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1727
+#, no-c-format
+msgid ""
+"the default name for the message ordering group. If absent, the group name "
+"will be generated automatically."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1730
+#, no-c-format
+msgid ""
+"This attribute takes effect only if the EnableOrderingGroup attribute is "
+"true."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1739
+#, no-c-format
+msgid "Configuring the remoting connector"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1741
+#, no-c-format
+msgid ""
+"JBoss Messaging uses JBoss Remoting for all client to server communication. "
+"For full details of what JBoss Remoting is capable of and how it is "
+"configured please consult the JBoss Remoting documentation."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1746
+#, no-c-format
+msgid ""
+"The default configuration includes a single remoting connector which is used "
+"by the single default connection factory. Each connection factory can be "
+"configured to use its own connector."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1750
+#, no-c-format
+msgid ""
+"The default connector is configured to use the remoting bisocket transport. "
+"The bisocket transport is a TCP socket based transport which only listens "
+"and accepts connections on the server side. I.e. connections are always "
+"initiated from the client side. This means it works well in 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:1758
+#, no-c-format
+msgid ""
+"The bisocket transport can be configured to use SSL where a higher level of "
+"security is required."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1761
+#, no-c-format
+msgid ""
+"The other supported transport is the HTTP transport. This uses the HTTP "
+"protocol to communicate between client and server. Data is received on the "
+"client by the client periodically polling the server for messages. This "
+"transport is well suited to situations where there is a firewall between "
+"client and server which only allows incoming HTTP traffic on the server. "
+"Please note this transport will not be as performant as the bisocket "
+"transport due to the nature of polling and the HTTP protocl. Also please "
+"note it is not designed for high load situations."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1770
+#, no-c-format
+msgid "No other remoting transports are currently supported by JBoss Messaging"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1773
+#, no-c-format
+msgid "You can look at remoting configuration under:"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1775
+#, no-c-format
+msgid ""
+"<JBoss>/server/<YourMessagingServer>/deploy/jboss-messaging.sar/"
+"remoting-bisocket-service.xml"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1777
+#, no-c-format
+msgid "Here is an example bisocket remoting configuration:"
+msgstr ""
+
+#. Tag: programlisting
+#: configuration.xml:1777
+#, no-c-format
+msgid ""
+"<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\">org."
+"jboss.jms.wireformat.JMSWireFormat</attribute>\n"
+" <attribute name=\"unmarshaller\" isParam=\"true\">org."
+"jboss.jms.wireformat.JMSWireFormat</attribute>\n"
+" <attribute name=\"dataType\" isParam=\"true\">jms</"
+"attribute>\n"
+" <attribute name=\"socket.check_connection\" isParam=\"true"
+"\">false</attribute>\n"
+" <attribute name=\"timeout\" isParam=\"true\">0</"
+"attribute>\n"
+" <attribute name=\"serverBindAddress\">${jboss.bind."
+"address}</attribute>\n"
+" <attribute name=\"serverBindPort\">4457</"
+"attribute>\n"
+" <attribute name=\"clientSocketClass\" isParam=\"true\">"
+"org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>\n"
+" <attribute name=\"serverSocketClass\" isParam=\"true\">"
+"org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>\n"
+" <attribute name=\"numberOfCallRetries\" isParam=\"true"
+"\">1</attribute>\n"
+" <attribute name=\"pingFrequency\" isParam=\"true"
+"\">214748364</attribute>\n"
+" <attribute name=\"pingWindowFactor\" isParam=\"true"
+"\">10</attribute>\n"
+" <attribute name=\"onewayThreadPool\">org.jboss.jms."
+"server.remoting.DirectThreadPool</attribute>\n"
+" \n"
+" <!-- Periodicity of client pings. Server window by default "
+"is twice this figure --> \n"
+" <attribute name=\"clientLeasePeriod\" isParam=\"true"
+"\">10000</attribute>\n"
+"\n"
+" <!-- Number of seconds to wait for a connection in the "
+"client pool to become free -->\n"
+" <attribute name=\"numberOfRetries\" isParam=\"true"
+"\">10</attribute>\n"
+"\n"
+" <!-- Max Number of connections in client pool. This should "
+"be significantly higher than\n"
+" the max number of sessions/consumers you expect -->\n"
+" <attribute name=\"clientMaxPoolSize\" isParam=\"true"
+"\">200</attribute>\n"
+" \n"
+" <!-- Use these parameters to specify values for binding "
+"and connecting control connections to \n"
+" work with your 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\">org.jboss.jms.server."
+"remoting.JMSServerInvocationHandler</handler>\n"
+" </handlers>\n"
+" </config>"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1779
+#, no-c-format
+msgid ""
+"Please note that some of the attributes should not be changed unless you "
+"know exactly what you are doing. We will discuss the attributes that you may "
+"have a good reason to change:"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1785
+#, no-c-format
+msgid ""
+"clientLeasePeriod - Clients periodically send heartbeats to the server to "
+"tell the server they are still alive. If the server does not receive a "
+"heartbeat after a certain time it will close down the connection and remove "
+"all resources on the server corresponding to the client's session. The "
+"clientLeasePeriod determines the period of heartbeats. The server will (by "
+"default) close a client if it does not receive a heartbeat in 2 * "
+"clientLeasePeriod ms. The actual factor gets automatically resized according "
+"to system load. The value is in milliseconds. The default value is 10000 ms."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1790
+#, no-c-format
+msgid ""
+"numberOfRetries - This effectively corresponds to the number of seconds "
+"JBoss Remoting will block on the client connection pool waiting for a "
+"connection to become free. If you have a very large number of sessions "
+"concurrently accessing the server from a client and you are experiencing "
+"issues due to not being able to obtain connections from the pool, you may "
+"want to consider increasing this value."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1795
+#, no-c-format
+msgid ""
+"clientMaxPoolSize - JBoss Remoting maintains a client side pool of TCP "
+"connections on which to service requests. If you have a very large number of "
+"sessions concurrently accessing the server from a client and you are "
+"experiencing issues due to not being able to obtain connections from the "
+"pool in a timely manner, you may want to consider increasing this value."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1800
+#, no-c-format
+msgid ""
+"secondaryBindPort - The bisocket transport uses control connections to pass "
+"control messages between server and client. If you want to work behind a "
+"firewall you may want to specify a particular value for this according to "
+"your firewall configuration. This is the address the secondary ServerSocket "
+"binds to."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1805
+#, no-c-format
+msgid ""
+"secondaryConnectPort - This is the port the client uses to connect. You may "
+"want to specify this to allow clients to work with NAT routers."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1810
+#, no-c-format
+msgid ""
+"maxPoolSize - This is the number of threads used on the server side to "
+"service requests."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1815
+#, no-c-format
+msgid ""
+"By default JBoss Messaging binds to ${jboss.bind.address} which can be "
+"defined by: ./run.sh -c <yourconfig> -b yourIP."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1818
+#, no-c-format
+msgid ""
+"You can change remoting-bisocket-service.xml if you want for example use a "
+"different communication port."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1822
+#, no-c-format
+msgid ""
+"There is rarely a good reason to change values in the the bisocket or "
+"sslbisocket connector configuration apart from clientLeasePeriod, "
+"clientMaxPoolSize, maxRetries, numberOfRetries, secondaryBindPort or "
+"secondaryConnectPort. Changing them can cause JBoss Messaging to stop "
+"functioning correctly."
+msgstr ""
+
+#. Tag: title
+#: configuration.xml:1831
+#, no-c-format
+msgid "ServiceBindingManager"
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1833
+#, no-c-format
+msgid ""
+"If you are using the JBoss AS ServiceBindingManager to provide different "
+"servers with different port ranges, then you must make sure that the JBoss "
+"Messaging remoting configuration specified in the JBoss Messaging section of "
+"the ServiceBindingManager xml file exactly matches that in remoting-bisocket-"
+"service.xml."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1839
+#, no-c-format
+msgid ""
+"If you are using a newer version of JBM in an older version of JBAS then the "
+"example bindings in the AS distribution may well be out of date. It is "
+"therefore imperative that the relevant sections are overwritten with the "
+"remoting configuration from the JBM distribution."
+msgstr ""
+
+#. Tag: para
+#: configuration.xml:1844
+#, no-c-format
+msgid ""
+"See the chapter on installation for a description of how to set-up the "
+"service binding manager for JBoss Messaging"
+msgstr ""
Added: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/gettingstarted.pot
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/gettingstarted.pot (rev 0)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/gettingstarted.pot 2009-06-04 02:39:48 UTC (rev 7188)
@@ -0,0 +1,58 @@
+# 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-06-04 02:39+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
+#: gettingstarted.xml:3
+#, no-c-format
+msgid "Download Software"
+msgstr ""
+
+#. Tag: para
+#: gettingstarted.xml:4
+#, no-c-format
+msgid ""
+"The official JBoss Messaging project page is <ulink url=\"http://labs.jboss."
+"com/jbossmessaging\">http://labs.jboss.com/jbossmessaging/</ulink>."
+msgstr ""
+
+#. Tag: para
+#: gettingstarted.xml:6
+#, no-c-format
+msgid ""
+"The download location is the JBoss Labs Messaging Project download zone: "
+"<ulink url=\"http://labs.jboss.com/jbossmessaging/\">http://labs.jboss.com/"
+"jbossmessaging/downloads</ulink>"
+msgstr ""
+
+#. Tag: title
+#: gettingstarted.xml:10
+#, no-c-format
+msgid "SVN Access"
+msgstr ""
+
+#. Tag: para
+#: gettingstarted.xml:11
+#, no-c-format
+msgid ""
+"If you want to experiment with the latest developments you may checkout the "
+"latest code from the Messaging SVN trunk. Be aware that the information "
+"provided in this manual might then not be accurate. For the latest "
+"instructions on how to check out and build source code, please go to <ulink "
+"url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingDevelopment\"> "
+"Messaging Development wiki page</ulink>, specifically <ulink url=\"http://"
+"wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingBuildInstructions\"> "
+"\"Building and Running JBoss Messaging\"</ulink> section."
+msgstr ""
Added: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/introduction.pot
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/introduction.pot (rev 0)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/introduction.pot 2009-06-04 02:39:48 UTC (rev 7188)
@@ -0,0 +1,489 @@
+# 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-06-04 02:39+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 that brings enterprise-class messaging to the mass market."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:8
+#, no-c-format
+msgid ""
+"JBoss Messaging implements a high performance, robust messaging core that is "
+"designed to support the largest and most heavily utilized SOAs, enterprise "
+"service buses (ESBs) and other integration needs ranging from the simplest "
+"to the highest demand networks."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:13
+#, no-c-format
+msgid ""
+"It will allow you to smoothly distribute your application load across your "
+"cluster, intelligently balancing and utilizing each nodes CPU cycles, with "
+"no single point of failure, providing a highly scalable and performant "
+"clustering implementation."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:18
+#, no-c-format
+msgid ""
+"JBoss Messaging includes a JMS front-end to deliver messaging in a standards-"
+"based format as well as being designed to be able to support other messaging "
+"protocols in the future."
+msgstr ""
+
+#. Tag: title
+#: introduction.xml:23
+#, no-c-format
+msgid "JBoss Messaging Features"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:25
+#, no-c-format
+msgid "JBoss Messaging provides:"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:29
+#, no-c-format
+msgid ""
+"A fully compatible and Sun certified JMS 1.1 implementation, that currently "
+"works with a standard 4.2 or later JBoss Application Server installation."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:35
+#, 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:45
+#, no-c-format
+msgid "Other JBoss Messaging features include:"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:49
+#, no-c-format
+msgid "Publish-subscribe and point-to-point messaging models"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:53
+#, no-c-format
+msgid "Persistent and non-persistent messages"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:57
+#, no-c-format
+msgid ""
+"Guaranteed message delivery that ensures that messages arrive once and only "
+"once where required"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:62
+#, no-c-format
+msgid "Transactional and reliable - supporting ACID semantics"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:66
+#, no-c-format
+msgid "Customizable security framework based on JAAS"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:70
+#, no-c-format
+msgid ""
+"Fully integrated with JBoss Transactions (formerly known as Arjuna JTA) for "
+"full transaction recoverability."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:75
+#, no-c-format
+msgid "Extensive JMX management interface"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:79
+#, no-c-format
+msgid ""
+"Support for most major databases including Oracle, DB2, Sybase, MS SQL "
+"Server, PostgreSQL and MySQL"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:84
+#, no-c-format
+msgid ""
+"HTTP transport to allow use through firewalls that only allow HTTP traffic"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:89
+#, no-c-format
+msgid "Servlet transport to allow messaging through a dedicated servlet."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:93
+#, no-c-format
+msgid "SSL transport"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:97
+#, no-c-format
+msgid "Configurable DLQs (Dead Letter Queues) and Expiry Queues"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:101
+#, no-c-format
+msgid ""
+"Message statistics. Gives you a rolling historical view of what messages "
+"were delivered to what queues and subscriptions"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:106
+#, no-c-format
+msgid ""
+"Automatic paging of messages to storage. Allows the use of very large queues "
+"- too large to fit in memory at once"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:111
+#, no-c-format
+msgid ""
+"Strict message ordering. JBoss Messaging's implementation of strict message "
+"ordering is called message ordering groups. Messages in one ordering group "
+"obey strict delivering order, which means that messages in an ordering group "
+"will be delivered exactly in the order of their arrival at the target queue "
+"(FIFO). Ordering groups can be enabled by either programming APIs or "
+"configuration."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:119
+#, no-c-format
+msgid "Clustering features:"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:123
+#, no-c-format
+msgid ""
+"Fully clustered queues and topics. \"Logical\" queues and topics are "
+"distributed across the cluster. You can send to a queue or a topic from any "
+"node, and receive from any other."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:129
+#, no-c-format
+msgid ""
+"Fully clustered durable subscriptions. A particular durable subscription can "
+"be accessed from any node of the cluster - allowing you to spread processing "
+"load from that subscription across the cluster."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:136
+#, no-c-format
+msgid ""
+"Fully clustered temporary queues. Send a message with a replyTo of a temp "
+"queue and it can be sent back on any node of the cluster."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:142
+#, no-c-format
+msgid ""
+"Intelligent message redistribution. Messages are automatically moved between "
+"different nodes of the cluster if consumers are faster on one node than "
+"another. This can help prevent starvation or build up of messages on "
+"particular nodes."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:149
+#, no-c-format
+msgid ""
+"Message order protection. If you want to ensure that the order of messages "
+"produced by a producer is the same as is consumed by a consumer then you can "
+"set this to true. This works even in the presence of message redistribution."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:156
+#, no-c-format
+msgid ""
+"Fully transparent failover. When a server fails, your sessions continue "
+"without exceptions on a new node as if nothing happened. (Fully configurable "
+"- If you don't want this you can fall back to exceptions being thrown and "
+"manually recreation of connections on another node)"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:164
+#, no-c-format
+msgid ""
+"High availability and seamless fail-over. If the node you are connected to "
+"fails, you will automatically fail over to another node and will not lose "
+"any persistent messages. You can carry on with your session seamlessly where "
+"you left off. Once and only once delivery of persistent messages is "
+"respected at all times."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:172
+#, no-c-format
+msgid ""
+"Message bridge. JBoss Messaging contains a message bridge component which "
+"enables you to bridge messages between any two JMS1.1 destinations on the "
+"same or physical separate locations. (E.g. separated by a WAN). This allows "
+"you to connect geographically separate clusters, forming huge globally "
+"distributed logical queues and topics."
+msgstr ""
+
+#. Tag: title
+#: introduction.xml:182
+#, no-c-format
+msgid "Clustering Features"
+msgstr ""
+
+#. Tag: title
+#: introduction.xml:184
+#, no-c-format
+msgid "Fully clustered queues and topics"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:185
+#, no-c-format
+msgid ""
+"\"Logical\" queues and topics are distributed across the cluster. You can "
+"send to a queue or a topic from any node, and receive from any other."
+msgstr ""
+
+#. Tag: title
+#: introduction.xml:190
+#, no-c-format
+msgid "Fully clustered durable subscriptions"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:191
+#, no-c-format
+msgid ""
+"A particular durable subscription can be accessed from any node of the "
+"cluster - allowing you to spread processing load from that subscription "
+"across the cluster."
+msgstr ""
+
+#. Tag: title
+#: introduction.xml:196
+#, no-c-format
+msgid "Fully clustered temporary queues"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:197
+#, no-c-format
+msgid ""
+"Send a message with a <literal>replyTo</literal> of a temp queue and it can "
+"be sent back on any node of the cluster."
+msgstr ""
+
+#. Tag: title
+#: introduction.xml:202
+#, no-c-format
+msgid "Intelligent message redistribution"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:203
+#, no-c-format
+msgid ""
+"Messages are automatically moved between different nodes of the cluster if "
+"consumers are faster on one node than another. This can help prevent "
+"starvation or build up of messages on particular nodes."
+msgstr ""
+
+#. Tag: title
+#: introduction.xml:208
+#, no-c-format
+msgid "Message order protection"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:209
+#, no-c-format
+msgid ""
+"If you want to ensure that the order of messages produced by a producer is "
+"the same as is consumed by a consumer then you can set this to true. This "
+"works even in the presence of message redistribution."
+msgstr ""
+
+#. Tag: title
+#: introduction.xml:214
+#, no-c-format
+msgid "Fully transparent failover"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:215
+#, no-c-format
+msgid ""
+"When a server fails, your sessions continue without exceptions on a new node "
+"as if nothing happened. (Fully configurable - If you don't want this you can "
+"fall back to exceptions being thrown and manually recreation of connections "
+"on another node)"
+msgstr ""
+
+#. Tag: title
+#: introduction.xml:220
+#, no-c-format
+msgid "High availability and seamless fail-over"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:221
+#, no-c-format
+msgid ""
+"If the node you are connected to fails, you will automatically fail over to "
+"another node and will not lose any persistent messages. You can carry on "
+"with your session seamlessly where you left off. Once and only once delivery "
+"of persistent messages is respected at all times."
+msgstr ""
+
+#. Tag: title
+#: introduction.xml:226
+#, no-c-format
+msgid "Message bridge"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:227
+#, no-c-format
+msgid ""
+"JBoss Messaging contains a message bridge component which enables you to "
+"bridge messages between any two JMS1.1 destinations on the same or physical "
+"separate locations. (E.g. separated by a WAN). This allows you to connect "
+"geographically separate clusters, forming huge globally distributed logical "
+"queues and topics."
+msgstr ""
+
+#. Tag: title
+#: introduction.xml:233
+#, no-c-format
+msgid "Compatibility with JBossMQ"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:235
+#, no-c-format
+msgid ""
+"JBoss MQ is the JMS implementation currently shipped within JBoss AS. Since "
+"JBoss Messaging is JMS 1.1 and JMS 1.0.2b compatible, the JMS code written "
+"against JBossMQ will run with JBoss Messaging without any changes."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:240
+#, no-c-format
+msgid ""
+"JBoss Messaging does not have wire format compatibility with JBoss MQ so it "
+"would be necessary to upgrade JBoss MQ clients with JBoss Messaging client "
+"jars"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:245
+#, no-c-format
+msgid ""
+"Even if JBoss Messaging deployment descriptors are very similar to JBoss MQ "
+"deployment descriptors, they are <emphasis>not</emphasis> identical, so they "
+"will require some simple adjustments to get them to work with JBoss "
+"Messaging. Also, the database data model is completely different, so don't "
+"attempt to use JBoss Messaging with a JBoss MQ data schema and vice-versa."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:253
+#, no-c-format
+msgid ""
+"JBoss Messaging is built against the JBoss AS 4.2 libraries which are built "
+"using Java 5. Therefore JBoss Messaging only runs with Java 5 or later."
+msgstr ""
+
+#. Tag: title
+#: introduction.xml:259
+#, no-c-format
+msgid "Limitations of JBossMQ"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:260
+#, no-c-format
+msgid "JBossMQ has two fundamental limitations:"
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:264
+#, no-c-format
+msgid ""
+"JBossMQ is based on SpyderMQ (the open source project) which is a non-"
+"clustered broker."
+msgstr ""
+
+#. Tag: para
+#: introduction.xml:269
+#, no-c-format
+msgid ""
+"The threading model and the overall design of the non-clustered broker leads "
+"to performance limitations in certain high load usage scenarios."
+msgstr ""
Added: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/ordering_group.pot
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/ordering_group.pot (rev 0)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/ordering_group.pot 2009-06-04 02:39:48 UTC (rev 7188)
@@ -0,0 +1,307 @@
+# 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-06-04 02:39+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 JBoss Messaging ordering group feature to "
+"achieve strict message ordering."
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:8
+#, no-c-format
+msgid ""
+"JBoss Messaging's implementation of strict message ordering is called "
+"message ordering groups. Messages in one orddering group obey strict "
+"delivering order, which means that messages in an ordering group will be "
+"delivered exactly in the order of their arrival at the target queue (FIFO). "
+"Ordering groups are identified by their string names."
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:12
+#, no-c-format
+msgid ""
+"When ordering group is enabled, message priorities will not take any effect "
+"on the ordering of the messages. Message ordering groups obey the following "
+"rules:"
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:14
+#, no-c-format
+msgid ""
+"Rule 1. Messages in the ordering group are delivered one at a time. Next "
+"message will not be delivered until the delivery of previous message is "
+"completed."
+msgstr ""
+
+#. Tag: listitem
+#: ordering_group.xml:17
+#, no-c-format
+msgid ""
+"For CLIENT_ACKNOWLEDGE mode, the Message.acknowledge() method signals the "
+"completion state."
+msgstr ""
+
+#. Tag: listitem
+#: ordering_group.xml:18
+#, no-c-format
+msgid ""
+"For AUTO_ACKNOWLEDGE and DUPS_OK_ACKNOWLEDGE modes, the completion of the "
+"message is identified by either"
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:20
+#, no-c-format
+msgid "1) successful returning from the MessageConsumer.receive() methods, or"
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:21
+#, no-c-format
+msgid ""
+"2) successful returning from the onMessage() call of the MessageListener();"
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:26
+#, no-c-format
+msgid ""
+"If the message consumer is closed, the current message processing is deemed "
+"to be finished, even if the acknowledge is not called before consumer close."
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:28
+#, no-c-format
+msgid ""
+"Rule 2. In case of transactional receiving, the next message will not be "
+"delivered until the transaction that includes the receiving of the previous "
+"message has been committed. If the transaction is rolled back, the previous "
+"message will be cancelled back to the JMS server and thus available for the "
+"next delivery."
+msgstr ""
+
+#. Tag: title
+#: ordering_group.xml:32
+#, no-c-format
+msgid "How to Enable Message Ordering Group"
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:34
+#, no-c-format
+msgid ""
+"There are two ways to use message ordering group: through programming and "
+"through configuration."
+msgstr ""
+
+#. Tag: listitem
+#: ordering_group.xml:37
+#, no-c-format
+msgid "The Programming Way"
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:40
+#, no-c-format
+msgid ""
+"To make use of JBoss Messaging's ordering group feature, one has to obtain a "
+"JBossMessageProducer."
+msgstr ""
+
+#. Tag: programlisting
+#: ordering_group.xml:42
+#, no-c-format
+msgid ""
+"JBossMessageProducer producer = (JBossMessageProducer)session.createProducer"
+"(queue);"
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:44
+#, no-c-format
+msgid ""
+"JBossMessageProducer has two methods for starting/ending an ordering group."
+msgstr ""
+
+#. Tag: programlisting
+#: ordering_group.xml:46
+#, no-c-format
+msgid "public void enableOrderingGroup(String ogrpName) throws JMSException"
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:48
+#, no-c-format
+msgid ""
+"Creating a ordering group with name ogrpName. Once called, the producer will "
+"send messages on behave of the ordering group. If null parameter is given, "
+"the name of the ordering group will be automatically generated. Calling this "
+"method more than once will always override the previous calls."
+msgstr ""
+
+#. Tag: programlisting
+#: ordering_group.xml:50
+#, no-c-format
+msgid "public void disableOrderingGroup() throws JMSException"
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:52
+#, no-c-format
+msgid ""
+"Stop producing ordering group messages. Once called, the producer will stop "
+"sending out ordering group messages and return to its normal behavior."
+msgstr ""
+
+#. Tag: listitem
+#: ordering_group.xml:55
+#, no-c-format
+msgid "The Configuration Way"
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:58
+#, no-c-format
+msgid ""
+"Users can configure a JBoss Messaging connection factory to enable ordering "
+"group. Two new attributes are added to the factory service configuration "
+"file."
+msgstr ""
+
+#. Tag: programlisting
+#: ordering_group.xml:60
+#, no-c-format
+msgid ""
+"EnableOrderingGroup -- set this property to true to enable the ordering "
+"group. Default is false; and\n"
+"DefaultOrderingGroupName -- the default name for the message ordering group. "
+"If absent, the group \n"
+" name will be generated automatically."
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:62
+#, no-c-format
+msgid ""
+"Once configured to enable ordering group on a connection factory, all "
+"messages that are sent from any producers created from this connection "
+"factory become ordering group messages."
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:64
+#, no-c-format
+msgid "Example:"
+msgstr ""
+
+#. Tag: programlisting
+#: ordering_group.xml:66
+#, no-c-format
+msgid ""
+"<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">jboss."
+"messaging:service=ServerPeer</depends>\n"
+" <depends optional-attribute-name="Connector">jboss."
+"messaging:service=Connector,transport=bisocket</depends>\n"
+" <depends>jboss.messaging:service=PostOffice</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>"
+msgstr ""
+
+#. Tag: para
+#: ordering_group.xml:68
+#, no-c-format
+msgid ""
+"The good thing about this way is the user doesn't need to make any coding "
+"effort to get message ordering functionality."
+msgstr ""
+
+#. Tag: title
+#: ordering_group.xml:73
+#, no-c-format
+msgid "Notes and Limitations"
+msgstr ""
+
+#. Tag: listitem
+#: ordering_group.xml:77
+#, no-c-format
+msgid ""
+"Ordering group doesn't work with topics. Users requiring order groups have "
+"to user queues."
+msgstr ""
+
+#. Tag: listitem
+#: ordering_group.xml:78
+#, no-c-format
+msgid ""
+"Ordering group shouldn't be used together with message selectors and "
+"scheduled delivery."
+msgstr ""
+
+#. Tag: listitem
+#: ordering_group.xml:79
+#, no-c-format
+msgid ""
+"If a message is 'dead' (goes to DLQ) or expired (goes to ExpiryQueue), this "
+"message is considered completed and next message will be available for "
+"delivery."
+msgstr ""
+
+#. Tag: listitem
+#: ordering_group.xml:80
+#, no-c-format
+msgid ""
+"When using a ConnectionConsumer, ordering of the messages will be observed. "
+"However, it doesn't control which session will be receiving the next message."
+msgstr ""
+
+#. Tag: listitem
+#: ordering_group.xml:81
+#, no-c-format
+msgid ""
+"In case of Distributed Queue, user should use HASingleton to make sure "
+"ordering group works properly."
+msgstr ""
Added: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/recovery_config.pot
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/recovery_config.pot (rev 0)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/recovery_config.pot 2009-06-04 02:39:48 UTC (rev 7188)
@@ -0,0 +1,131 @@
+# 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-06-04 02:39+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_config.xml:3
+#, no-c-format
+msgid "JBoss Messaging XA Recovery Configuration"
+msgstr ""
+
+#. Tag: para
+#: recovery_config.xml:5
+#, no-c-format
+msgid ""
+"This section describes how to configure JBoss Transactions in JBoss AS 4.2.0 "
+"to handle XA recovery for JBoss Messaging resources."
+msgstr ""
+
+#. Tag: para
+#: recovery_config.xml:8
+#, no-c-format
+msgid ""
+"JBoss Transactions recovery manager can easily be configured to continually "
+"poll for and recover JBoss Messaging XA resources, this provides an "
+"extremely high level of durability of transactions."
+msgstr ""
+
+#. Tag: para
+#: recovery_config.xml:12
+#, no-c-format
+msgid ""
+"Enabling JBoss Transactions Recovery Manager to recover JBoss Messaging "
+"resources is a very simple matter and involves adding a line to the file "
+"${JBOSS_CONFIG}/conf/jbossjta-properties.xml"
+msgstr ""
+
+#. Tag: para
+#: recovery_config.xml:16
+#, no-c-format
+msgid ""
+"Here's an example section of a jbossjta-properties.xml file with the line "
+"added (note the whole file is not shown)"
+msgstr ""
+
+#. Tag: programlisting
+#: recovery_config.xml:19
+#, 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_config.xml:21
+#, no-c-format
+msgid ""
+"In the above example the recovery manager will attempt to recover JMS "
+"resources using the JMSProviderLoader \"DefaultJMSProvider\""
+msgstr ""
+
+#. Tag: para
+#: recovery_config.xml:24
+#, no-c-format
+msgid ""
+"DefaultJMSProvider is the default JMS provider loader that ships with JBoss "
+"AS and is defined in jms-ds.xml (or hajndi-jms-ds.xml in a clustered "
+"configuration). If you want to recovery using a different JMS provider "
+"loader - e.g. one corresponding to a remote JMS provider then just add "
+"another line and instead of DefaultJMSProvider specify the name of the "
+"remote JMS provider as specified in it's MBean configuration."
+msgstr ""
+
+#. Tag: para
+#: recovery_config.xml:31
+#, no-c-format
+msgid ""
+"For each line you add, the name must be unique, so you could specify \"com."
+"arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1\", \"com.arjuna.ats."
+"jta.recovery.XAResourceRecovery.JBMESSAGING2, ...\" etc."
+msgstr ""
+
+#. Tag: para
+#: recovery_config.xml:36
+#, no-c-format
+msgid ""
+"In actual fact, the recovery also should work with any JMS provider that "
+"implements recoverable XAResources (i.e. it properly implements XAResource."
+"recover()) , not just JBoss Messaging"
+msgstr ""
+
+#. Tag: para
+#: recovery_config.xml:40
+#, no-c-format
+msgid ""
+"Please note that to configure the recovery manager to recovery transactions "
+"from any node of the cluster it will be necessary to specify a line in the "
+"configuration for every node of the cluster"
+msgstr ""
Added: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/runningexamples.pot
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/runningexamples.pot (rev 0)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/pot/runningexamples.pot 2009-06-04 02:39:48 UTC (rev 7188)
@@ -0,0 +1,288 @@
+# 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-06-04 02:39+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
+#: runningexamples.xml:3
+#, no-c-format
+msgid "Running the Examples"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:5
+#, no-c-format
+msgid ""
+"In the directory <literal>docs/examples</literal>, you will find a set of "
+"examples demonstrating JBoss Messaging working in various examples."
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:8
+#, no-c-format
+msgid ""
+"Before running these examples, you must deploy the example-destinations "
+"located under <filename>/docs/examples/destinations</filename>"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:9
+#, no-c-format
+msgid "Examples list:"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:12
+#, no-c-format
+msgid "docs/example/queue"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:14
+#, no-c-format
+msgid ""
+"This example shows a simple send and receive to a remote queue using a JMS "
+"client"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:19
+#, no-c-format
+msgid "docs/example/topic"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:21
+#, no-c-format
+msgid ""
+"This example shows a simple send and receive to a remote topic using a JMS "
+"client"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:26
+#, no-c-format
+msgid "docs/example/mdb"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:28
+#, no-c-format
+msgid "This example demonstrates usage of an EJB2.1 MDB with JBoss Messaging"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:33
+#, no-c-format
+msgid "docs/example/ejb3mdb"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:35
+#, no-c-format
+msgid "This example demonstrates usage of an EJB3 MDB with JBoss Messaging"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:40
+#, no-c-format
+msgid "docs/example/stateless"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:42
+#, no-c-format
+msgid ""
+"This example demonstrates an EJB2.1 stateless session bean interacting with "
+"JBoss Messaging"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:47
+#, no-c-format
+msgid "docs/example/mdb-failure"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:49
+#, no-c-format
+msgid ""
+"This example demonstrates rollback and redelivery occuring with an EJB2.1 MDB"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:54
+#, no-c-format
+msgid "docs/example/secure-socket"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:56
+#, no-c-format
+msgid ""
+"This example demonstrates a JMS client interacting with a JBoss Messaging "
+"server using SSL encrypted transport"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:61
+#, no-c-format
+msgid "docs/example/http"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:63
+#, no-c-format
+msgid ""
+"This example demonstrates a JMS client interacting with a JBoss Messaging "
+"server tunneling traffic over the HTTP protocol"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:68
+#, no-c-format
+msgid "docs/example/web-service"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:70
+#, no-c-format
+msgid ""
+"This example demonstrates JBoss web-service interacting with JBoss Messaging"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:75
+#, no-c-format
+msgid "docs/example/distributed-queue"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:77
+#, no-c-format
+msgid ""
+"This example demonstrates a JMS client interacting with a JBoss Messaging "
+"distributed queue - it requires two JBoss AS instances to be running"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:83
+#, no-c-format
+msgid "docs/example/distributed-topic"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:85
+#, no-c-format
+msgid ""
+"This example demonstrates a JMS client interacting with a JBoss Messaging "
+"distributed topic - it requires two JBoss AS instances to be running"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:91
+#, no-c-format
+msgid "docs/example/stateless-clustered"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:93
+#, no-c-format
+msgid ""
+"This example demonstrates a JMS client interacting with clustered EJB2.1 "
+"stateless session bean, which in turn interacts with JBoss Messaging. The "
+"example uses HAJNDI to lookup the connection factory"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:100
+#, no-c-format
+msgid "docs/example/bridge"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:102
+#, no-c-format
+msgid ""
+"This example demonstrates using a message bridge. It deploys a message "
+"bridge in JBoss AS which then proceeds to move messages from a source to a "
+"target queue"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:108
+#, no-c-format
+msgid "docs/example/servlet"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:110
+#, no-c-format
+msgid ""
+"This example demonstrates how to use servlet transport with JBoss Messaging. "
+"It deploys a servlet and a ConnectionFactory that uses the servlet transport."
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:116
+#, no-c-format
+msgid "docs/example/ordering-group"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:118
+#, no-c-format
+msgid ""
+"This example demonstrates using strict message ordering with JBoss "
+"Messaging. It uses JBoss Messaging ordering group API to deliver strictly "
+"ordered messages, regardless of their priorities."
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:124
+#, no-c-format
+msgid ""
+"It is highly recommended that you familiarize yourself with the examples."
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:127
+#, no-c-format
+msgid "Make sure you start the JBoss server(s) before running the examples!"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:130
+#, no-c-format
+msgid ""
+"The non clustered examples expect a JBoss AS instance to be running with all "
+"the default settings"
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:133
+#, no-c-format
+msgid ""
+"The clustered examples expect two JBoss AS instances to running with ports "
+"settings as per ports-01 and ports-02."
+msgstr ""
+
+#. Tag: para
+#: runningexamples.xml:136
+#, no-c-format
+msgid ""
+"For each example, you can always override the default ports it will try to "
+"connect to by editing the <filename>jndi.properties</filename> file in the "
+"particular example directory"
+msgstr ""
More information about the jboss-cvs-commits
mailing list