[jboss-cvs] JBoss Messaging SVN: r5190 - projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Oct 27 22:07:42 EDT 2008
Author: irooskov at redhat.com
Date: 2008-10-27 22:07:42 -0400 (Mon, 27 Oct 2008)
New Revision: 5190
Modified:
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/bridge.xml
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/c_configuration.xml
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/configuration.xml
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/installation.xml
projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/runningexamples.xml
Log:
committing mhideo's changes
Modified: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/bridge.xml
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/bridge.xml 2008-10-27 23:18:04 UTC (rev 5189)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/bridge.xml 2008-10-28 02:07:42 UTC (rev 5190)
@@ -32,7 +32,7 @@
Messaging JMS servers, as long as they are JMS 1.1 compliant.</para>
<para>The bridge has built in resilience to failure so if the source or
- target server connetion is lost, e.g. due to network failure, the bridge
+ 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.</para>
@@ -56,7 +56,7 @@
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 avilable for
+ Hence delivery will occur at most once. This mode is available for
both persistent and non persistent messages.</para>
</listitem>
Modified: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/c_configuration.xml
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/c_configuration.xml 2008-10-27 23:18:04 UTC (rev 5189)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/c_configuration.xml 2008-10-28 02:07:42 UTC (rev 5190)
@@ -29,7 +29,7 @@
cluster.</para>
<para>If you do not want message redistribution between nodes, but still
- want to retain the other charactereristics of clustered destinations. You
+ want to retain the other characteristics of clustered destinations. You
can do this by not specifying the attribute
ClusterPullConnectionFactoryName on the server peer</para>
</section>
@@ -66,7 +66,7 @@
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
- sideeffect of setting this to true is that messages cannot be distributed
+ side effect of setting this to true is that messages cannot be distributed
as freely around the cluster</para>
</section>
Modified: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/configuration.xml
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/configuration.xml 2008-10-27 23:18:04 UTC (rev 5189)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/configuration.xml 2008-10-28 02:07:42 UTC (rev 5190)
@@ -20,7 +20,7 @@
<filename>messaging-service.xml</filename>,
<filename>remoting-bisocket-service.xml</filename>,
<filename>xxx-persistence-service.xml</filename> (where xx is the name of
- your databse) , <filename>connection-factories-service.xml</filename> and
+ your database) , <filename>connection-factories-service.xml</filename> and
<filename>destinations-service.xml</filename>.</para>
<para>The AOP client-side and server-side interceptor stacks are configured
@@ -80,7 +80,7 @@
<para>If the <literal>read</literal> attribute is
<literal>true</literal> then that role will be able to read (create
- consumers, receive messaages or browse) destinations by
+ consumers, receive messages or browse) destinations by
default.</para>
<para>If the <literal>write</literal> attribute is
@@ -341,7 +341,7 @@
<para>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 maxiumum number of days for which
+ 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.</para>
</formalpara>
@@ -354,7 +354,7 @@
</formalpara>
<para>If you wish to turn off message sucking between queues
- altogether, but retain failover, then you can ommit this attribute
+ altogether, but retain failover, then you can omit this attribute
altogether</para>
<formalpara>
@@ -493,7 +493,7 @@
storage.</para>
<para>This operation returns <literal>true</literal> if the queue
- was successfull undeployed. otherwise it returns
+ was successful undeployed. otherwise it returns
<literal>false</literal>.</para>
<formalpara>
@@ -661,7 +661,7 @@
<para>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 repesents a JMS
+ 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.</para>
@@ -884,7 +884,7 @@
<title>IDCacheSize</title>
<para>If duplicate detection is enabled. (See
- <literal>DetectDuplicates</literal>), then the server will rememeber
+ <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.</para>
@@ -1028,7 +1028,7 @@
<para>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
- occuring when using this database.</para>
+ occurring when using this database.</para>
</warning>
<para>JBoss Messaging also ships with pre-made Persistence Manager
@@ -1043,7 +1043,7 @@
release bundle.</para>
<para>Users are encouraged to contribute their own configuration files
- where we will thoroughly test them before certifying them for suppported
+ 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
@@ -1138,7 +1138,7 @@
<section id="conf.persistencemanager.sybasemssqlnotes">
<title>Important notes for Sybase and Microsoft SQL Server users</title>
- <para>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 behaviour 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"/>.
+ <para>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"/>.
</para>
<para>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"/></para>
@@ -1557,7 +1557,7 @@
<para>If the <literal>read</literal> attribute is
<literal>true</literal> then that role will be able to read (create
- consumers, receive messaages or browse) this destination.</para>
+ consumers, receive messages or browse) this destination.</para>
<para>If the <literal>write</literal> attribute is
<literal>true</literal> then that role will be able to write (create
@@ -1569,7 +1569,7 @@
<para>Note that the security configuration for a destination is
optional. If a <literal>SecurityConfig</literal> element is not
- specifed then the default security configuration from the Server
+ specified then the default security configuration from the Server
Peer will be used.</para>
<formalpara>
@@ -1603,7 +1603,7 @@
necessary as messages are added or consumed.</para>
<para><literal>PageSize</literal> - When loading messages from the
- queue or subscrition this is the maximum number of messages to
+ queue or subscription this is the maximum number of messages to
pre-load in one operation.</para>
<para><literal>DownCacheSize</literal> - When paging messages to
@@ -1844,7 +1844,7 @@
<para>If the <literal>read</literal> attribute is
<literal>true</literal> then that role will be able to read (create
- consumers, receive messaages or browse) this destination.</para>
+ consumers, receive messages or browse) this destination.</para>
<para>If the <literal>write</literal> attribute is
<literal>true</literal> then that role will be able to write (create
@@ -1856,7 +1856,7 @@
<para>Note that the security configuration for a destination is
optional. If a <literal>SecurityConfig</literal> element is not
- specifed then the default security configuration from the Server
+ specified then the default security configuration from the Server
Peer will be used.</para>
<formalpara>
@@ -1890,7 +1890,7 @@
necessary as messages are added or consumed.</para>
<para><literal>PageSize</literal> - When loading messages from the
- queue or subscrition this is the maximum number of messages to
+ queue or subscription this is the maximum number of messages to
pre-load in one operation.</para>
<para><literal>DownCacheSize</literal> - When paging messages to
@@ -2044,7 +2044,7 @@
<para>Lists all messages for the specified subscription.</para>
</formalpara>
<para>There are two overloaded versions of this operation. One that
- takes a selector and one that does not. By specifyingthe selector
+ takes a selector and one that does not. By specifying the selector
you can limit the messages returned.</para>
@@ -2055,7 +2055,7 @@
subscription.</para>
</formalpara>
<para>There are two overloaded versions of this operation. One that
- takes a selector and one that does not. By specifyingthe selector
+ takes a selector and one that does not. By specifying the selector
you can limit the messages returned.</para>
@@ -2066,7 +2066,7 @@
subscription.</para>
</formalpara>
<para>There are two overloaded versions of this operation. One that
- takes a selector and one that does not. By specifyingthe selector
+ takes a selector and one that does not. By specifying the selector
you can limit the messages returned.</para>
</section>
@@ -2218,14 +2218,14 @@
<formalpara>
<title>StrictTck</title>
- <para>Set this to true if you want strict JMS behaviour as required by
+ <para>Set this to true if you want strict JMS behavior as required by
the TCK.</para>
</formalpara>
<formalpara>
<title>SendAcksAsync</title>
- <para>Set this to true if you want acknowledgements to be sent
+ <para>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</para>
</formalpara>
@@ -2239,7 +2239,7 @@
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 ommitted.</para>
+ and 2000 respectively if omitted.</para>
</formalpara>
<formalpara>
@@ -2320,7 +2320,7 @@
</formalpara>
<para>The default value is
org.jboss.jms.client.plugin.RoundRobinLoadBalancingFactory, which load
- balances connetions across the cluster in a round-robin fashion</para>
+ balances connections across the cluster in a round-robin fashion</para>
<formalpara>
<title>Connector</title>
@@ -2357,7 +2357,7 @@
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 onlu outbound connections are allowed from the
+ the server. Or where only outbound connections are allowed from the
client.</para>
<para>The bisocket transport can be configured to use SSL where a higher
@@ -2429,7 +2429,7 @@
<itemizedlist>
<listitem>
<para>
- 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 defaut value is 10000 ms. </para>
+ 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. </para>
</listitem>
<listitem>
Modified: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/installation.xml
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/installation.xml 2008-10-27 23:18:04 UTC (rev 5189)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/installation.xml 2008-10-28 02:07:42 UTC (rev 5190)
@@ -61,7 +61,7 @@
<title>Automated Installation</title>
<para><note>
- This procedure should only be performed from a clean JBoss AS 4.2 installation. If you have modifed the JBoss AS 4.2 installation at all since installation then you will need to perform a manual clustered JBoss Messaging installation
+ This procedure should only be performed from a clean JBoss AS 4.2 installation. If you have modified the JBoss AS 4.2 installation at all since installation then you will need to perform a manual clustered JBoss Messaging installation
</note></para>
<itemizedlist>
@@ -74,7 +74,7 @@
<filename>util</filename> directory of the release bundle as
follows:</para>
- <para>If you want to create a simple non clustered installion based
+ <para>If you want to create a simple non clustered installation based
on the default configuration:</para>
<programlisting>
@@ -802,13 +802,13 @@
<literal>"DataSource connection transaction isolation should be
READ_COMMITTED, but it is currently NONE"</literal>
- is there to remind you that by default JBossAS ships with Hypersonic, an in-memory Java-based database engine, which is apropriate for demo purposes, but not for heavy load production environments. The
+ is there to remind you that by default JBossAS ships with Hypersonic, an in-memory Java-based database engine, which is appropriate for demo purposes, but not for heavy load production environments. 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 occuring when using this database.
+ wiki page outlines some of the well-known issues occurring when using this database.
</note>
<warning>
@@ -837,7 +837,7 @@
variable to point to the JBoss AS 4.x installation you've just installed
Messaging on. Navigate to the folder where you extracted the release
bundle and drill down to <filename>/examples/queue</filename>. Apache Ant
- must pe present in your path in order to be able to run the
+ must be present in your path in order to be able to run the
example.</para>
<para>Make sure you start the JBoss server before trying to run the
@@ -851,7 +851,7 @@
</programlisting>
- <para>A successfull execution log output looks similar to:</para>
+ <para>A successful execution log output looks similar to:</para>
<programlisting>
[tim at Vigor14 queue]$ ant
@@ -1020,8 +1020,8 @@
<note>substitute what ever your messaging server configuration is
above. I used the default stand alone messaging server configuration
- note: This is required to dereference the JBossMQ objects that are
- dereferenced on the JBM side. If you don't copy the jar over, you
+ note: This is required to de-reference the JBossMQ objects that are
+ de-referenced on the JBM side. If you don't copy the jar over, you
will get a "java.lang.ClassCastException: javax.naming.Reference"
exception and the bridge will not be able to start</note>
</listitem>
@@ -1055,7 +1055,7 @@
<note>you will need to change the java.naming.provider.url so that
it points to your JBossMQ machine. Everything else should remain the
- same. Keep your jms-ds.xml file open, because you will be addning
+ same. Keep your jms-ds.xml file open, because you will be adding
another entry in it for the next step.</note>
</listitem>
@@ -1091,7 +1091,7 @@
the JBossMQ remote provider. If you have a pretty stock system and
you want to move messages from JBossMQ to JBM, you will not have to
change this example except for the queue Names. If you wish to move
- from JBM to JBossMQ, just switch the soure and target
+ from JBM to JBossMQ, just switch the source and target
definitions.</note>
</listitem>
</itemizedlist>
Modified: projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/runningexamples.xml
===================================================================
--- projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/runningexamples.xml 2008-10-27 23:18:04 UTC (rev 5189)
+++ projects/eap-docs/trunk/JBoss_Messaging_User_Guide/en-US/runningexamples.xml 2008-10-28 02:07:42 UTC (rev 5190)
@@ -43,7 +43,7 @@
<listitem>
<para>docs/example/mdb-failure</para>
- <para>This example demonstrates rollback and redelivery occuring with
+ <para>This example demonstrates rollback and redelivery occurring with
an EJB2.1 MDB</para>
</listitem>
@@ -88,7 +88,7 @@
<para>docs/example/stateless-clustered</para>
<para>This example demonstrates a JMS client interacting with
- clustered EJB2.1 stateless session bean, which in turn interactes with
+ clustered EJB2.1 stateless session bean, which in turn interacts with
JBoss Messaging. The example uses HAJNDI to lookup the connection
factory</para>
</listitem>
@@ -102,7 +102,7 @@
</listitem>
</itemizedlist></para>
- <para>It is highly recommended that you familiarise yourself with the
+ <para>It is highly recommended that you familiarize yourself with the
examples.</para>
<para>Make sure you start the JBoss server(s) before running the
More information about the jboss-cvs-commits
mailing list