[ 
https://issues.apache.org/jira/browse/FELIX-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler updated FELIX-6659:
------------------------------------
    Affects Version/s:     (was: http.jetty-5.1.2)

> HealthCheckExecutorServlet no longer serving requests to /system/health after 
> upgrading to Jetty 5.1.2
> ------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-6659
>                 URL: https://issues.apache.org/jira/browse/FELIX-6659
>             Project: Felix
>          Issue Type: Bug
>          Components: Health Checks, HTTP Service
>    Affects Versions: healthcheck.core 2.2.0
>            Reporter: Robert Munteanu
>            Priority: Major
>             Fix For: healthcheck.core 2.2.2
>
>         Attachments: image-2023-10-11-22-17-10-606.png, 
> image-2023-10-11-22-18-13-245.png, image-2023-10-11-22-18-50-570.png
>
>
> *Summary:*
> In the Apache Sling Starter 13-SNAPSHOT, after upgrading to 
> org.apache.felix.http.jetty 5.1.2 the health checks are no longer served on 
> /system/health.
> *Steps to Reproduce:*
>  # Check out [https://github.com/apache/sling-org-apache-sling-starter]
>  # build with {{mvn clean package}}
>  # run with 
> {{target/dependency/org.apache.sling.feature.launcher/bin/launcher -f 
> target/slingfeature-tmp/feature-oak_tar.json}}
>  # wait a bit and run {{[http://localhost:8080/system/health.txt]}}
> *Expected Behaviour: (/)*
> The health check status should be returned. Instead, the SlingMainServlet 
> responds with a 404.
> *Additional Details:*
> Using the web console at [http://localhost:8080/system/console/httpservice] 
> confirms that th path is served by the Sling Main Servlet.
> *Screenshots:*
> Resolution results
> !image-2023-10-11-22-17-10-606.png!
> Sling servlet context and registration
> !image-2023-10-11-22-18-13-245.png!
> HealthCheck servlet registration using the default servlet context
> !image-2023-10-11-22-18-50-570.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to