aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Ross (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ARIES-931) NPE in Application iTests
Date Tue, 02 Oct 2012 21:21:10 GMT
John Ross created ARIES-931:
-------------------------------

             Summary: NPE in Application iTests
                 Key: ARIES-931
                 URL: https://issues.apache.org/jira/browse/ARIES-931
             Project: Aries
          Issue Type: Bug
          Components: Application
            Reporter: John Ross


The following NPE from application-itests will occasionally occur during the Aries build.

java.lang.NullPointerException
	at org.apache.aries.application.runtime.framework.management.SharedFrameworkPreResolveHook.collectFakeResources(SharedFrameworkPreResolveHook.java:161)

The NPE occurs because fwMgr.getSharedBundleFramework() returns null since the shared bundle
framework was not created earlier.

org.apache.aries.application.runtime.framework.management.BundleFrameworkManagerImpl - Caught
exception
org.apache.aries.application.management.spi.repository.ContextException: Unable to create
or start the shared framework composite bundle null
	at org.apache.aries.application.runtime.framework.management.SharedBundleFramework.createSharedBundleFramework(SharedBundleFramework.java:83)

The shared bundle framework was not created due to a ConcurrentModificationException in the
Equinox framework.

Caused by: java.util.ConcurrentModificationException
	at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
	at java.util.Hashtable.putAll(Hashtable.java:465)
	at org.eclipse.osgi.framework.internal.core.FrameworkProperties.internalGetProperties(FrameworkProperties.java:82)
	at org.eclipse.osgi.framework.internal.core.FrameworkProperties.setProperties(FrameworkProperties.java:95)
	at org.eclipse.osgi.framework.internal.core.EquinoxLauncher.internalInit(EquinoxLauncher.java:64)
	at org.eclipse.osgi.framework.internal.core.EquinoxLauncher.init(EquinoxLauncher.java:38)
	at org.eclipse.osgi.launch.Equinox.init(Equinox.java:89)
	at org.eclipse.osgi.internal.composite.CompositeImpl.findCompanionFramework(CompositeImpl.java:64)
	at org.eclipse.osgi.internal.composite.CompositeBase.<init>(CompositeBase.java:37)
	at org.eclipse.osgi.internal.composite.CompositeImpl.<init>(CompositeImpl.java:37)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.createBundle(AbstractBundle.java:69)
	at org.eclipse.osgi.framework.internal.core.Framework.createAndVerifyBundle(Framework.java:712)
	at org.eclipse.osgi.framework.internal.core.Framework.installWorkerPrivileged(Framework.java:923)
	... 49 more

The CME is a known issue and was fixed as of Equinox 3.7.2. Currently, the application-itests
run against both Equinox 3.5.0 and 3.7.0, which are subject to the CME. Unless running against
these frameworks is absolutely necessary, I'd like to propose that the itests be executed
against 3.8, available in Maven Central, instead in order to avoid these potential "false
positives" in the Aries build test results. The other configurations can remain in order to
run locally when necessary but would be commented out.

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

Mime
View raw message