[
https://issues.apache.org/jira/browse/SLING-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648225#comment-13648225
]
Bertrand Delacretaz commented on SLING-2818:
--------------------------------------------
Indeed, thanks for the stack trace:
java.lang.NullPointerException: Specified service reference cannot be null.
at
org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:458)
at
org.apache.sling.jcr.classloader.internal.ClassLoaderWriterImpl.getOrCreateClassLoader(ClassLoaderWriterImpl.java:215)
...
Looks like something causes the DynamicClassLoaderManager that the
ClassLoaderWriterImpl uses to go away before the test runs.
> ErrorHandlingTest often fails
> -----------------------------
>
> Key: SLING-2818
> URL: https://issues.apache.org/jira/browse/SLING-2818
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Reporter: Bertrand Delacretaz
> Priority: Minor
> Attachments: error-message.txt
>
>
> At least at https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6
> the
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolver.errorhandler.ErrorHandlingTest
> often fails, sometimes for unclear reasons (timing?).
> Recent error messages include
> At ErrorHandlingTest.setUp:
> mkdir(http://localhost:42232/apps/servlets/errorhandler) failed, status
> code=503
> At ErrorHandlingTest.test_500_errorhandling:
> Error 503 AuthenticationSupport service missing. Cannot authenticate request
> It looks like something (maybe the test's setup itself) causes Sling to go
> 503 just before the test.
> The test that runs just before is
> org.apache.sling.launchpad.webapp.integrationtest.CreateNodeTest which
> shouldn't cause a 503 status.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
