[
https://issues.apache.org/jira/browse/SLING-7058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130354#comment-16130354
]
Ruben Reusser commented on SLING-7058:
--------------------------------------
it seems this issue is due to the logic in
https://github.com/apache/sling/blob/trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/app/Main.java
as it only initializes the ControlListener if the command start is passed to
sling. This may of course be intentional
> the stop command line option does not seem to work
> --------------------------------------------------
>
> Key: SLING-7058
> URL: https://issues.apache.org/jira/browse/SLING-7058
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Reporter: Ruben Reusser
> Priority: Minor
>
> as per
> https://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html#command-line-options
> a user should be able to stop a running sling instance by calling
> {code:java}
> java -jar sling-9.jar stop
> {code}
> Sling is supposed to write a file at startup with the chosen control port and
> the secret key at
> `$\{sling.home}/conf/controlport`
> I do not see that file created nor does the above command work to stop a
> running sling instance.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
