svn commit: r984788 - in /websites/staging/sling/trunk/content: ./ documentation/the-sling-engine/the-sling-launchpad.html

[bu...@apache.org]

Author: buildbot
Date: Tue Apr  5 10:03:42 2016
New Revision: 984788

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    websites/staging/sling/trunk/content/documentation/the-sling-engine/the-sling-launchpad.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr  5 10:03:42 2016
@@ -1 +1 @@
-1737813
+1737815

Modified: websites/staging/sling/trunk/content/documentation/the-sling-engine/the-sling-launchpad.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/the-sling-engine/the-sling-launchpad.html (original)
+++ websites/staging/sling/trunk/content/documentation/the-sling-engine/the-sling-launchpad.html Tue Apr  5 10:03:42 2016
@@ -235,7 +235,15 @@ h2:hover > .headerlink, h3:hover > .head
 <li>If none of the above resolves to a non-null value, the default value of <code>sling</code> is assumed</li>
 </ol>
 <h3 id="control-port">Control Port<a class="headerlink" href="#control-port" title="Permanent link">&para;</a></h3>
-<p>When starting the Sling Standalone Application with the <code>start</code> command line option, a TCP port is opened. The interface and port is configurable with the <code>-j</code> command line option. The actual address and port used are written to the <code>$\{sling.home}/conf/controlport</code> file. So technically the <code>-j</code> option is not required for the <code>status</code> and <code>stop</code> operations because the port information can be read from that file.</p>
+<p>When starting the Sling Standalone Application with the <code>start</code> command line option, a TCP control port is opened to receive simple commands which allow for stopping an instance and getting thread dumps.</p>
+<p>Currently supported commands are</p>
+<ul>
+<li><code>stop</code> to stop the Sling instance</li>
+<li><code>status</code> to get the instance status (OK or STOPPING)</li>
+<li><code>threads</code> to get a thread dump</li>
+</ul>
+<p>For the Whole Truth about this functionality see the <a href="https://svn.apache.org/repos/asf/sling/trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/app/ControlListener.java">ControlListener class source code</a>.</p>
+<p>The interface and port is configurable with the <code>-j</code> command line option. The actual address and port used are written to the <code>$\{sling.home}/conf/controlport</code> file. So technically the <code>-j</code> option is not required for the <code>status</code> and <code>stop</code> operations because the port information can be read from that file.</p>
 <p>Note that using a control connection for the Sling Standalone Application presents a potential security issue. For this reason the following defaults apply:</p>
 <ul>
 <li>The server side socket for a running Sling Standalone Application is not created by default, but only if the application is started with the <code>start</code> command line option.</li>
@@ -370,7 +378,7 @@ handed to the <code>Main</code> construc
 </ul>
 <p>That's it. The resulting artifact may be directly used to launch the Standalone Java Application or may directly be deployed into any Servlet API 3.0 (or later) compliant servlet container.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1737813 by bdelacretaz on Tue, 5 Apr 2016 09:53:25 +0000
+        Rev. 1737815 by bdelacretaz on Tue, 5 Apr 2016 10:03:34 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project