[GitHub] [sling-org-apache-sling-jcr-contentloader] enapps-enorman edited a comment on pull request #13: SLING-11189 Race condition registering readers vs. loading content

[GitBox <gi...@apache.org>]

enapps-enorman edited a comment on pull request #13:
URL: https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/13#issuecomment-1064413713


   @stefanseifert Thanks for confirming that it eventually gets into the right state.  I've made another adjustment that should reduce the log message noise.  Does this resolve your concerns?
   
   You should now get one WARN message (no stacktrace) per bundle the first time it fails and then one INFO message per bundle after the retry logic is successful.
   
   For example:
   `[main] WARN org.apache.sling.jcr.contentloader.internal.BundleContentLoader - Cannot load initial content for bundle mock-bundle : Unable to locate a required content reader for entry SLING-INF/libs/app.xml
   
   [main] INFO org.apache.sling.jcr.contentloader.internal.BundleContentLoader - Retrying to load initial content for bundle mock-bundle succeeded.
   `


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@sling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org