New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config Apache Sling Davex Servlet fail #42
Labels
Comments
mbloch1986
added a commit
to mbloch1986/puppet-aem-resources
that referenced
this issue
Sep 27, 2018
…ions#42 * Add Check login_page_is_ready and aem_health_check_is_ok after starting bundle Davex when enabling crxde shinesolutions#42
cliffano
added a commit
that referenced
this issue
Sep 30, 2018
Add checks after starting bundle Davex when enabling CRXDE #42
cliffano
added a commit
that referenced
this issue
Sep 30, 2018
cliffano
added a commit
that referenced
this issue
Oct 1, 2018
Add checks after starting bundle Davex when enabling CRXDE #42
cliffano
added a commit
that referenced
this issue
Oct 1, 2018
Done. To be included in v3.1.2 and v2.3.2 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In certain circumstances the configuration of the davex bundle during stack provisioning may fail which cause the failing of the provisioning process on the AEM Component.
After starting the Davex bundle it may take a couple of seconds until AEM respnse. During this time AEM response with a HTTP 500 error code.
A solution would be to add checks after starting the bundle to wait until login page is ready and to run the deep health check.
The text was updated successfully, but these errors were encountered: