[
http://jira.amdatu.org/jira/browse/AMDATU-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843#comment-12843
]
Bram de Kruijff commented on AMDATU-555:
----------------------------------------
Seems the ACE build was causing the ghosts mentioned above. The error below
resulted in hung build and killing a PAX Exam 1 build leaves these ghosts.
*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
14-Mar-2012 14:33:35 java.lang.IllegalStateException: Can only register
services while bundle is active or activating.
14-Mar-2012 14:33:35 at
org.apache.felix.framework.Felix.registerService(Felix.java:2832)
14-Mar-2012 14:33:35 at
org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:251)
14-Mar-2012 14:33:35 at
org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:229)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.ComponentImpl.registerService(ComponentImpl.java:844)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.ComponentImpl.bindService(ComponentImpl.java:608)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.ComponentImpl.access$400(ComponentImpl.java:52)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.ComponentImpl$7.run(ComponentImpl.java:181)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.SerialExecutor$1.run(SerialExecutor.java:47)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.SerialExecutor.scheduleNext(SerialExecutor.java:84)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.SerialExecutor.access$000(SerialExecutor.java:33)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.SerialExecutor$1.run(SerialExecutor.java:50)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.SerialExecutor.scheduleNext(SerialExecutor.java:84)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.SerialExecutor.execute(SerialExecutor.java:68)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.ComponentImpl.calculateStateChanges(ComponentImpl.java:231)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.ComponentImpl.dependencyAvailable(ComponentImpl.java:358)
14-Mar-2012 14:33:35 at
org.apache.felix.dm.impl.dependencies.ConfigurationDependencyImpl.updated(ConfigurationDependencyImpl.java:207)
14-Mar-2012 14:33:35 at
org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1490)
14-Mar-2012 14:33:35 at
org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104)
14-Mar-2012 14:33:35 at java.lang.Thread.run(Thread.java:662)
> Investigate intermittent problems in itests
> -------------------------------------------
>
> Key: AMDATU-555
> URL: http://jira.amdatu.org/jira/browse/AMDATU-555
> Project: Amdatu
> Issue Type: Bug
> Components: Amdatu Core
> Reporter: Marcel Offermans
> Assignee: Bram de Kruijff
> Fix For: Sprint 8
>
>
> Sometimes, our itests seem to fail. This is either some concurrency or timing
> issue, or it's build setup related. On my local machine for example I could
> make a test fail the first time, but (so far) after that it works. We've seen
> issues like this in Bamboo as well and we should take a look at what's
> causing this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
