[jboss-cvs] JBoss Messaging SVN: r7945 - in projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ: en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Feb 16 00:59:08 EST 2010
Author: laubai
Date: 2010-02-16 00:59:08 -0500 (Tue, 16 Feb 2010)
New Revision: 7945
Added:
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/publican.cfg
Modified:
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/JBoss_Messaging_2.0.0_User_Guide.xml
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/management.xml
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/messaging-concepts.xml
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/paging.xml
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/send-guarantees.xml
Log:
Added publican configuration file; made basic tag corrections.
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/JBoss_Messaging_2.0.0_User_Guide.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/JBoss_Messaging_2.0.0_User_Guide.xml 2010-02-10 12:50:04 UTC (rev 7944)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/JBoss_Messaging_2.0.0_User_Guide.xml 2010-02-16 05:59:08 UTC (rev 7945)
@@ -46,7 +46,7 @@
<xi:include href="Logging.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Embedding_JBM.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Intercepting_Operations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Performance_Tuning.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="perf-tuning.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Project_Information.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<index />
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/management.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/management.xml 2010-02-10 12:50:04 UTC (rev 7944)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/management.xml 2010-02-16 05:59:08 UTC (rev 7945)
@@ -852,15 +852,15 @@
<para>By default, message counters are disabled as it might have a small negative effect on
memory (the metrics are kept in memory) and CPU (the queues are sampled at regular
intervals).</para>
- <para>To enable message counters, you can set it to <literal>true</literal> in <filname
- >jbm-configuration.xml</filename>:</para>
+ <para>To enable message counters, you can set it to <literal>true</literal> in
+ <filename>jbm-configuration.xml</filename>:</para>
<programlisting>
<message-counter-enabled>true</message-counter-enabled>
</programlisting>
<para>Message counters keeps a history of the queue metrics (10 days by default) and
samples all the queues at regular interval (10 seconds by default). If message counters
are enabled, these values should be configured to suit your messaging use case in
- <filname>jbm-configuration.xml</filename>:</para>
+ <filename>jbm-configuration.xml</filename>:</para>
<programlisting>
<!-- keep history for a week -->
<message-counter-max-day-history>7</message-counter-max-day-history>
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/messaging-concepts.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/messaging-concepts.xml 2010-02-10 12:50:04 UTC (rev 7944)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/messaging-concepts.xml 2010-02-16 05:59:08 UTC (rev 7945)
@@ -118,7 +118,7 @@
<para>Messaging systems typically support the sending and acknowledgement of multiple
messages in a single local transaction. JBoss Messaging also supports the sending and
acknowledgement of messages as part of a large global transaction with the Java
- mapping of <acroynym>XA</acronym>, <acroynym>JTA</acronym>.</para>
+ mapping of <acronym>XA</acronym>, <acronym>JTA</acronym>.</para>
</section>
<section>
<title>Durability</title>
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/paging.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/paging.xml 2010-02-10 12:50:04 UTC (rev 7944)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/paging.xml 2010-02-16 05:59:08 UTC (rev 7945)
@@ -19,8 +19,7 @@
<section id="paging.main.config">
<title>Configuration</title>
<para>You can configure the location of the paging folder</para>
- <para>Global paging parameters are specified on the main configuration file (<filname
- >jbm-configuration.xml</filename>):</para>
+ <para>Global paging parameters are specified on the main configuration file (<filename>jbm-configuration.xml</filename>):</para>
<programlisting language="XML" role="XML"><configuration xmlns="urn:jboss:messaging"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:jboss:messaging /schema/jbm-configuration.xsd">
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/send-guarantees.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/send-guarantees.xml 2010-02-10 12:50:04 UTC (rev 7944)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/send-guarantees.xml 2010-02-16 05:59:08 UTC (rev 7945)
@@ -9,8 +9,8 @@
until a response has been received from the server that the commit or rollback was
executed.</para>
<para>When the commit or rollback is received on the server, it will be committed to the
- journal, and depending on the value of the parameter <literal
- >journal-sync-transactional</literal> the server will ensure that the commit or
+ journal, and depending on the value of the parameter
+ <literal>journal-sync-transactional</literal> the server will ensure that the commit or
rollback is durably persisted to storage before sending the response back to the client.
If this parameter has the value <literal>false</literal> then commit or rollback may not
actually get persisted to storage until some time after the response has been sent to
@@ -31,18 +31,17 @@
the following two parameters:</para>
<itemizedlist>
<listitem>
- <para><literal>BlockOnPersistentSend</literal>. If this is set to <literal
- >true</literal> then all calls to send for persistent messages on non-
- transacted sessions will block until the message has reached the server, and a
+ <para><literal>BlockOnPersistentSend</literal>. If this is set to
+ <literal>true</literal> then all calls to send for persistent messages on
+ non-transacted sessions will block until the message has reached the server, and a
response has been sent back. The default value is <literal>false</literal>.
</para>
</listitem>
<listitem>
- <para><literal>BlockOnNonPersistentSend</literal>. If this is set to <literal
- >true</literal> then all calls to send for non-persistent messages on non-
+ <para><literal>BlockOnNonPersistentSend</literal>. If this is set to
+ <literal>true</literal> then all calls to send for non-persistent messages on non-
transacted sessions will block until the message has reached the server, and a
- response has been sent back. The default value is <literal
- >false</literal>.</para>
+ response has been sent back. The default value is <literal>false</literal>.</para>
</listitem>
</itemizedlist>
@@ -63,26 +62,27 @@
your network, rather than the bandwidth of your network. For better performance we
recommend batching multiple messages sends together in one transaction or using JBoss
Messaging's advanced <emphasis>asynchronous send acknowledgements feature</emphasis>
- described in <xref linkend="asynchronous-send-acknowledgements" />.
+ described in <xref linkend="asynchronous-send-acknowledgements" />.</para>
<para>If you are using JMS and you're using the JMS service on the server to load your JMS
connection factory instances into JNDI then these parameters can be configured in
- <literal>jbm-jms.xml</literal> using the elements <literal
- >block-on-persistent-send</literal> and <literal
- >block-on-non-persistent-send</literal>. If you're using JMS but not using JNDI then
+ <literal>jbm-jms.xml</literal> using the elements
+ <literal>block-on-persistent-send</literal> and
+ <literal>block-on-non-persistent-send</literal>. If you're using JMS but not using JNDI then
you can set these values directly on the <literal>JBossConnectionFactory</literal>
instance using the appropriate setter methods.</para>
- <para>If you're using core you can set these values directly on the <literal
- >ClientSessionFactory</literal> instance using the appropriate setter
+ <para>If you're using core you can set these values directly on the
+ <literal>ClientSessionFactory</literal> instance using the appropriate setter
methods.</para>
<para>When the server receives a message sent from a non-transactional session, and that
message is persistent and the message is routed to at least one durable queue, then the
- server will persist the message in permanent storage. If the journal parameter <literal
- >journal-sync-non-transactional</literal> is set to <literal>true</literal> the
+ server will persist the message in permanent storage. If the journal parameter
+ <literal>journal-sync-non-transactional</literal> is set to <literal>true</literal> the
server will not send a response back to the client until the message has been persisted
and the server has a guarantee that the data has been persisted to disk. The default
value for this parameter is <literal>false</literal>.</para>
</section>
+
<section id="send-guarantees.nontrans.acks">
<title>Guarantees of Non Transactional Acknowledgements</title>
<para>If you are acknowledging the delivery of a message at the client side using a non-
Added: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/publican.cfg
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/publican.cfg (rev 0)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/publican.cfg 2010-02-16 05:59:08 UTC (rev 7945)
@@ -0,0 +1,7 @@
+# Config::Simple 4.59
+# Tue Feb 16 15:48:57 2010
+
+debug: 1
+xml_lang: en-US
+brand: JBoss
+
More information about the jboss-cvs-commits
mailing list