svn commit: r1737815 - /sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext

[bd...@apache.org]

Author: bdelacretaz
Date: Tue Apr  5 10:03:34 2016
New Revision: 1737815

URL: http://svn.apache.org/viewvc?rev=1737815&view=rev
Log:
More control port information

Modified:
    sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext

Modified: sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext?rev=1737815&r1=1737814&r2=1737815&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext Tue Apr  5 10:03:34 2016
@@ -52,7 +52,17 @@ The Sling Standalone application looks f
 
 ### Control Port
 
-When starting the Sling Standalone Application with the `start` command line option, a TCP port is opened. The interface and port is configurable with the `-j` command line option. The actual address and port used are written to the `$\{sling.home}/conf/controlport` file. So technically the `-j` option is not required for the `status` and `stop` operations because the port information can be read from that file.
+When starting the Sling Standalone Application with the `start` command line option, a TCP control port is opened to receive simple commands which allow for stopping an instance and getting thread dumps.
+
+Currently supported commands are
+
+* `stop` to stop the Sling instance
+* `status` to get the instance status (OK or STOPPING)
+* `threads` to get a thread dump
+
+For the Whole Truth about this functionality see the [ControlListener class source code](https://svn.apache.org/repos/asf/sling/trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/app/ControlListener.java).
+
+The interface and port is configurable with the `-j` command line option. The actual address and port used are written to the `$\{sling.home}/conf/controlport` file. So technically the `-j` option is not required for the `status` and `stop` operations because the port information can be read from that file.
 
 Note that using a control connection for the Sling Standalone Application presents a potential security issue. For this reason the following defaults apply: