You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2013/03/25 16:55:14 UTC

[jira] [Created] (SLING-2797) Null dynamicClassLoaderManager in ClassLoaderWriterImpl.getOrCreateClassLoader()

Bertrand Delacretaz created SLING-2797:
------------------------------------------

             Summary: Null dynamicClassLoaderManager in ClassLoaderWriterImpl.getOrCreateClassLoader()
                 Key: SLING-2797
                 URL: https://issues.apache.org/jira/browse/SLING-2797
             Project: Sling
          Issue Type: Bug
          Components: JCR
            Reporter: Bertrand Delacretaz
            Priority: Minor
         Attachments: error.txt

I got this just once when running integration tests on revision 1460730:

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)

and that line 215 is:

final DynamicClassLoaderManager dclm = (DynamicClassLoaderManager) this.callerBundle.getBundleContext().getService(
                this.dynamicClassLoaderManager);

looks like this.dynamicClassLoaderManager is unexpectedly null. 

This happened while running org.apache.sling.launchpad.webapp.integrationtest.servlets.resolver.errorhandler.ErrorHandlingTest which installs JSP error scripts just before running, there might be a race condition here.

I won't investigate further right now, cannot reliably reproduce, saving this info in case we see this again.



--
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