You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Created) (JIRA)" <ji...@apache.org> on 2011/12/28 15:50:30 UTC

[jira] [Created] (SLING-2345) Improve control port handling

Improve control port handling
-----------------------------

                 Key: SLING-2345
                 URL: https://issues.apache.org/jira/browse/SLING-2345
             Project: Sling
          Issue Type: Improvement
          Components: Launchpad
    Affects Versions: Launchpad Base 2.3.0
            Reporter: Carsten Ziegeler
             Fix For: Launchpad Base 2.4.0


Currently the port number of the control port the stop Sling or get the status has either to be specified via commandline argument or if missing a hard-coded default is used.

I think we should:
- use the provided port if specified
- use any port of not specified
- write the used port to a file inside sling home
- use the port number from the file if the port is not specified and the command is not start

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (SLING-2345) Improve control port handling

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed SLING-2345.
------------------------------------


Close after release.
                
> Improve control port handling
> -----------------------------
>
>                 Key: SLING-2345
>                 URL: https://issues.apache.org/jira/browse/SLING-2345
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>    Affects Versions: Launchpad Base 2.3.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Launchpad Base 2.4.0
>
>
> Currently the port number of the control port the stop Sling or get the status has either to be specified via commandline argument or if missing a hard-coded default is used.
> I think we should:
> - use the provided port if specified
> - use any port of not specified
> - write the used port to a file inside sling home
> - use the port number from the file if the port is not specified and the command is not start

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (SLING-2345) Improve control port handling

Posted by "Carsten Ziegeler (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler reassigned SLING-2345:
---------------------------------------

    Assignee: Carsten Ziegeler
    
> Improve control port handling
> -----------------------------
>
>                 Key: SLING-2345
>                 URL: https://issues.apache.org/jira/browse/SLING-2345
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>    Affects Versions: Launchpad Base 2.3.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Launchpad Base 2.4.0
>
>
> Currently the port number of the control port the stop Sling or get the status has either to be specified via commandline argument or if missing a hard-coded default is used.
> I think we should:
> - use the provided port if specified
> - use any port of not specified
> - write the used port to a file inside sling home
> - use the port number from the file if the port is not specified and the command is not start

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (SLING-2345) Improve control port handling

Posted by "Carsten Ziegeler (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-2345.
-------------------------------------

    Resolution: Fixed

Implemented as outlined above in revision 1227536

The control port is written to sling.home/conf/controlport
                
> Improve control port handling
> -----------------------------
>
>                 Key: SLING-2345
>                 URL: https://issues.apache.org/jira/browse/SLING-2345
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>    Affects Versions: Launchpad Base 2.3.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Launchpad Base 2.4.0
>
>
> Currently the port number of the control port the stop Sling or get the status has either to be specified via commandline argument or if missing a hard-coded default is used.
> I think we should:
> - use the provided port if specified
> - use any port of not specified
> - write the used port to a file inside sling home
> - use the port number from the file if the port is not specified and the command is not start

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira