sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-6543) slingstart-maven-plugin: Optionally make the start mojo blocking until the server is fully up and running
Date Sat, 02 Jun 2018 16:01:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16499114#comment-16499114
] 

Konrad Windszus commented on SLING-6543:
----------------------------------------

With https://github.com/apache/sling-slingstart-maven-plugin/commit/60d4d95b890723af8dd03b5fa64d4673a3b0246a
start is really blocking until the http port is bound. Further improvement (like waiting for
specific paths to be available) can be tracked in follow-up issues if really necessary.

> slingstart-maven-plugin: Optionally make the start mojo blocking until the server is
fully up and running
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-6543
>                 URL: https://issues.apache.org/jira/browse/SLING-6543
>             Project: Sling
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: Slingstart Maven Plugin 1.7.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Slingstart Maven Plugin 1.8.2
>
>
> Right now the {{start}} goal will only start the server (in a dedicated process) and
then return when the control port returns that the server is started. 
> That does not necessarily mean that all services from all bundles are already fully started.
Especially in some cases the HTTP port is not yet bound!
> It should be possible to block until the server is fully started and some services are
up and running. Otherwise follow-up processes (like {{maven-failsafe-plugin}}) will need to
implement some wait approach.
> One possibility is to issue repeated GET requests against the instance at a dedicated
URL until it reports a 200 (similar to what is done in {{SlingTestBase.waitForServerReady(...)}}
(https://github.com/apache/sling/blob/trunk/testing/tools/src/main/java/org/apache/sling/testing/tools/sling/SlingTestBase.java#L263).
The list of URLs must be configurable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message