You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "Christian Vogel (JIRA)" <ji...@apache.org> on 2013/05/25 11:01:21 UTC
[jira] [Commented] (ACE-176) Integration tests stuck
[ https://issues.apache.org/jira/browse/ACE-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667031#comment-13667031 ]
Christian Vogel commented on ACE-176:
-------------------------------------
Is this still an issue if we don't use Pax Runner anymore?
> Integration tests stuck
> -----------------------
>
> Key: ACE-176
> URL: https://issues.apache.org/jira/browse/ACE-176
> Project: ACE
> Issue Type: Bug
> Components: Build
> Reporter: Jean-Baptiste Onofré
> Fix For: 0.8.0-incubator
>
>
> The integration tests are stuck during Pax Runner shut down:
> Aug 29, 2011 12:03:34 PM org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer start
> INFO: Test container (Pax Runner 1.5.0) started in 736 millis
> Aug 29, 2011 12:03:34 PM org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer start
> INFO: Wait for test container to finish its initialization for 300000 millis
> Aug 29, 2011 12:03:35 PM org.ops4j.pax.exam.rbc.client.RemoteBundleContextClient getRemoteBundleContext
> INFO: Remote bundle context found after 543 millis
> Aug 29, 2011 12:03:35 PM org.ops4j.pax.exam.junit.internal.JUnit4TestMethod invoke
> INFO: Starting test testCreation(org.apache.ace.it.repository.RepositoryTest)
> Aug 29, 2011 12:03:37 PM org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer stop
> INFO: Shutting down the test container (Pax Runner)
> *ERROR* [org.osgi.service.cm.ManagedService, id=10, bundle=11]: Unexpected problem updating Configuration PID=org.apache.ace.repository.servlet.RepositoryServlet, factoryPID=null, bundleLocation=file:bundles/org.apache.ace.repository.servlet_0.8.1.incubator-SNAPSHOT.jar
> java.lang.IllegalStateException: Can only register services while bundle is active or activating.
> at org.apache.felix.framework.Felix.registerService(Felix.java:2832)
> at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:251)
> at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:229)
> at org.apache.felix.dm.impl.ComponentImpl.registerService(ComponentImpl.java:844)
> at org.apache.felix.dm.impl.ComponentImpl.bindService(ComponentImpl.java:608)
> at org.apache.felix.dm.impl.ComponentImpl.access$400(ComponentImpl.java:52)
> at org.apache.felix.dm.impl.ComponentImpl$7.run(ComponentImpl.java:181)
> at org.apache.felix.dm.impl.SerialExecutor$1.run(SerialExecutor.java:47)
> at org.apache.felix.dm.impl.SerialExecutor.scheduleNext(SerialExecutor.java:84)
> at org.apache.felix.dm.impl.SerialExecutor.access$000(SerialExecutor.java:33)
> at org.apache.felix.dm.impl.SerialExecutor$1.run(SerialExecutor.java:50)
> at org.apache.felix.dm.impl.SerialExecutor.scheduleNext(SerialExecutor.java:84)
> at org.apache.felix.dm.impl.SerialExecutor.execute(SerialExecutor.java:68)
> at org.apache.felix.dm.impl.ComponentImpl.calculateStateChanges(ComponentImpl.java:231)
> at org.apache.felix.dm.impl.ComponentImpl.dependencyAvailable(ComponentImpl.java:358)
> at org.apache.felix.dm.impl.dependencies.ConfigurationDependencyImpl.updated(ConfigurationDependencyImpl.java:207)
> at org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1490)
> at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104)
> at java.lang.Thread.run(Thread.java:662)
> It requires a kill of the test to get 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