You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by bu...@apache.org on 2015/01/30 13:21:55 UTC

svn commit: r938367 - in /websites/production/activemq/content: cache/main.pageCache unix-shell-script.html

Author: buildbot
Date: Fri Jan 30 12:21:54 2015
New Revision: 938367

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/unix-shell-script.html

Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/activemq/content/unix-shell-script.html
==============================================================================
--- websites/production/activemq/content/unix-shell-script.html (original)
+++ websites/production/activemq/content/unix-shell-script.html Fri Jan 30 12:21:54 2015
@@ -85,7 +85,7 @@
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[$ bin/activemq start xbean:conf/activemq-stomp.xml]]></script>
 </div></div><ul><li><strong>console</strong> - starts the broker in foreground. It is basically the replacement for the old <code>activemq</code> script</li></ul><ul><li><strong>stop</strong> - stops the broker that is running in the background. It tries first to stop the broker using <a shape="rect" href="activemq-command-line-tools-reference.html#ActiveMQCommandLineToolsReference-shutdown">shutdown</a> task. If that task doesn't return in 30 seconds (configurable), it will kill the process.</li></ul><ul><li><strong>restart</strong> - stops the running instance (if there's one) and starts the new one</li></ul><ul><li><strong>status</strong> - checks if activemq process is running</li></ul><ul><li><strong>create</strong> - create an ACTIVEMQ_BASE directory that separates a broker instance from its binaries, i.e., it creates copies of the ActiveMQ configuration files into the command-line specified directory and points to the binaries. You can start the broker with the <code>/bin</co
 de> scripts in the newly created instance.</li></ul><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[$ ACTIVEMQ_HOME/bin/activemq create /path/to/brokers/mybroker ]]></script>
-</div></div><h2 id="UnixShellScript-Configuringthescript"><strong>Configuring the script</strong></h2><p>For ActiveMQ server to run properly some basic system variables must be set. These variables define how much memory broker will have, SSL, logging, JAAS options and similar. Prior to version 5.11.0 these parameters were configurable in <code>activemq</code> script itself. You could use setup command to create additional system wide scripts to configure the broker.</p><p><strong>setup</strong> - create the specified configuration file for this Unix script. The configuration of the script can be placed at <code>/etc/default/activemq</code> or <code>$HOME/.activemqrc</code>. Note, this is the configuration for the <em>script</em> not for configuring ActiveMQ.</p><p>To use addtional configurations for running multiple instances on the same operating system rename or symlink script to a name matching to <code>activemq-instance-&lt;INSTANCENAME&gt;</code>. This changes the configuratio
 n location to <code>/etc/default/activemq-instance-&lt;INSTANCENAME&gt;</code> and <code>$HOME/.activemqrc-instance-&lt;INSTANCENAME&gt;</code>. Configuration files in /etc have higher precedence.</p><p>Since <strong>5.11.0</strong>, all configuration variables are moved to the new <code>env</code> script, so that they can be easily configured at one place. This script can be copied to&#160;<code>/etc/default/activemq</code> or <code>$HOME/.activemqrc</code>&#160;to provide system-wide settings.</p></div>
+</div></div><h2 id="UnixShellScript-Configuringthescript"><strong>Configuring the script</strong></h2><p>For ActiveMQ server to run properly some basic system variables must be set. These variables define how much memory broker will have, SSL, logging, JAAS options and similar. Prior to version 5.11.0 these parameters were configurable in <code>activemq</code> script itself. You could use <code>setup</code> command to create additional system wide scripts to configure the broker.</p><p><strong>setup</strong> - create the specified configuration file for this Unix script. The configuration of the script can be placed at <code>/etc/default/activemq</code> or <code>$HOME/.activemqrc</code>. Note, this is the configuration for the <em>script</em> not for configuring ActiveMQ.</p><p>To use addtional configurations for running multiple instances on the same operating system rename or symlink script to a name matching to <code>activemq-instance-&lt;INSTANCENAME&gt;</code>. This changes the
  configuration location to <code>/etc/default/activemq-instance-&lt;INSTANCENAME&gt;</code> and <code>$HOME/.activemqrc-instance-&lt;INSTANCENAME&gt;</code>. Configuration files in /etc have higher precedence.</p><p>Since <strong>5.11.0</strong>, all configuration variables are moved to the new <code>env</code> script, so that they can be easily configured at one place. This script can be copied to&#160;<code>/etc/default/activemq</code> or <code>$HOME/.activemqrc</code>&#160;to provide system-wide settings, so the <code>setup</code> command has been removed. System variables set in the environment will take precedence.&#160;</p></div>
         </td>
         <td valign="top">
           <div class="navigation">