Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Spelling fixes

This commit is contained in:
Ville Skyttä 2016-08-09 11:42:24 +03:00 committed by Martyn Taylor
parent abf948457e
commit 3aa6d34e3d
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
artemis-distribution/src/main/resources/README.html
View File

@ -97,7 +97,7 @@ e.g.<br><br>
$ ./artemis run --config xml:/home/artemis/bootstrap.xml<br><br> $ ./artemis run --config xml:/home/artemis/bootstrap.xml<br><br>
It is possible to configure run time paramters in the artemis.conf (artemis.conf.bat for windows) file under the "bin" directory of the broker directory. It is possible to configure run time parameters in the artemis.conf (artemis.conf.bat for windows) file under the "bin" directory of the broker directory.
<h2>Stopping the Broker</h2> <h2>Stopping the Broker</h2>

2
examples/features/ha/application-layer-failover/readme.html
View File

@ -36,7 +36,7 @@ under the License.
This listener will then be called by ActiveMQ Artemis in the event that connection failure is detected.</p> This listener will then be called by ActiveMQ Artemis in the event that connection failure is detected.</p>
<p>User code in the ExceptionListener can then recreate any JMS Connection, Session, etc on another node and the application <p>User code in the ExceptionListener can then recreate any JMS Connection, Session, etc on another node and the application
can continue.</p> can continue.</p>
<p>Application-Layer failover is an alternative approach to High Availabilty (HA).</p> <p>Application-Layer failover is an alternative approach to High Availability (HA).</p>
<p>Application-Layer failover differs from automatic failover in that some client side coding is required in order <p>Application-Layer failover differs from automatic failover in that some client side coding is required in order
to implement this. Also, with Application-Layer failover, since the old Session object dies and a new is created, any uncommitted to implement this. Also, with Application-Layer failover, since the old Session object dies and a new is created, any uncommitted
work in the old Session will be lost, and any unacknowledged messages might be redelivered.</p> work in the old Session will be lost, and any unacknowledged messages might be redelivered.</p>

2
examples/features/standard/jms-bridge/readme.html
View File

@ -48,7 +48,7 @@ under the License.
</ol> </ol>
<h3>JMS Bridge Configuration</h3> <h3>JMS Bridge Configuration</h3>
<p>The JMS Bridge is a <abbr title="Plain Old Java Object">POJO</abbr> that we configure with both source and target <p>The JMS Bridge is a <abbr title="Plain Old Java Object">POJO</abbr> that we configure with both source and target
JNDI configurations. In the actual example we are programatically creating the Bridge, however the following section JNDI configurations. In the actual example we are programmatically creating the Bridge, however the following section
describes how you would do this if you wanted to deploy with an actual ActiveMQ Artemis server via the activemq-beans.xml. describes how you would do this if you wanted to deploy with an actual ActiveMQ Artemis server via the activemq-beans.xml.
<h4>Configuring the Bridge with the JBoss Microcontainer</h4> <h4>Configuring the Bridge with the JBoss Microcontainer</h4>