[
https://issues.apache.org/jira/browse/ARIES-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291307#comment-13291307
]
John Ross commented on ARIES-859:
---------------------------------
The following snippet is from the test output. It gave up waiting for the
testbundleb service which, in turn, appears to have been waiting for namespace
handlers. Could this be related at all to the change introduced in build 1470?
[Blueprint Extender: 1] DEBUG
org.apache.aries.blueprint.container.BlueprintContainerImpl - Running blueprint
container for bundle org.apache.aries.blueprint.testbundleb in state
WaitForNamespaceHandlers
[Blueprint Extender: 1] INFO
org.apache.aries.blueprint.container.BlueprintContainerImpl - Bundle
org.apache.aries.blueprint.testbundleb is waiting for namespace handlers
[http://ns.handler.four]
[Blueprint Extender: 3] DEBUG
org.apache.aries.blueprint.container.BlueprintContainerImpl - Instantiating
components: [blueprintContainer, blueprintBundle, blueprintBundleContext,
blueprintConverter, NSHandlerOne, NSHandlerTwo, NSHandlerThree, NSHandlerFour,
NSHandlerFive, NSHandlerSix, NSHandlerSeven, .component-1, .component-2,
.component-3, .component-4, .component-5, .component-6, .component-7]
[Blueprint Extender: 1] DEBUG
org.apache.aries.blueprint.container.BlueprintEventDispatcher - Sending
blueprint container event BlueprintEvent[type=GRACE_PERIOD,
dependencies=[(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://ns.handler.four))]]
for bundle org.apache.aries.blueprint.testbundleb
[Blueprint Extender: 3] DEBUG
org.apache.aries.blueprint.container.ServiceRecipe - Retrieving service for
bundle null and service registration null
[Blueprint Extender: 3] DEBUG
org.apache.aries.blueprint.container.ServiceRecipe - Retrieving service for
bundle null and service registration null
[Blueprint Extender: 3] DEBUG
org.apache.aries.blueprint.container.ServiceRecipe - Retrieving service for
bundle null and service registration null
[Blueprint Extender: 3] DEBUG
org.apache.aries.blueprint.container.ServiceRecipe - Retrieving service for
bundle null and service registration null
[Blueprint Extender: 3] DEBUG
org.apache.aries.blueprint.container.ServiceRecipe - Retrieving service for
bundle null and service registration null
[Blueprint Extender: 3] DEBUG
org.apache.aries.blueprint.container.ServiceRecipe - Retrieving service for
bundle null and service registration null
[Blueprint Extender: 3] DEBUG
org.apache.aries.blueprint.container.ServiceRecipe - Retrieving service for
bundle null and service registration null
[Blueprint Extender: 3] DEBUG org.apache.aries.blueprint.testbundlea -
ServiceEvent REGISTERED
[Blueprint Extender: 3] DEBUG
org.apache.aries.blueprint.container.BlueprintEventDispatcher - Sending
blueprint container event BlueprintEvent[type=CREATED] for bundle
org.apache.aries.blueprint.testbundlea
[RMI Scheduler(0)] DEBUG sun.rmi.transport.tcp - RMI Scheduler(0): close
connection
Could not obtain a service in time, service-ref=null, time=1339085178282
[RMI TCP Connection(1)-67.195.138.60] DEBUG sun.rmi.server.call - RMI TCP
Connection(1)-67.195.138.60: [67.195.138.60] exception:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.ops4j.pax.exam.rbc.internal.RemoteBundleContextImpl.remoteCall(RemoteBundleContextImpl.java:80)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.injectContextAndInvoke(CallableTestMethodImpl.java:143)
at
org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.call(CallableTestMethodImpl.java:105)
... 19 more
Caused by: java.lang.RuntimeException: Gave up waiting for service
(&(objectClass=org.osgi.service.blueprint.container.BlueprintContainer)(osgi.blueprint.container.symbolicname=org.apache.aries.blueprint.testbundleb))
at
org.apache.aries.itest.RichBundleContext.getService(RichBundleContext.java:88)
at
org.apache.aries.itest.RichBundleContext.getService(RichBundleContext.java:63)
at
org.apache.aries.blueprint.itests.Helper.getBlueprintContainerForBundle(Helper.java:45)
at
org.apache.aries.blueprint.itests.ASMMultiBundleTest.multiBundleTest(ASMMultiBundleTest.java:100)
... 25 more
[org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer] : Shutting
down the test container (Pax Runner)
[RMI TCP Connection(1)-67.195.138.60] DEBUG sun.rmi.transport.tcp - RMI TCP
Connection(1)-67.195.138.60: (port 46039) op = 82
[RMI TCP Connection(1)-67.195.138.60] DEBUG sun.rmi.transport.tcp - RMI TCP
Connection(1)-67.195.138.60: (port 46039) op = 80
[org.ops4j.pax.runner.platform.DefaultJavaRunner] : Waiting for framework exit.
> Build break:
> org.apache.aries.blueprint.itests.ASMMultiBundleTest.multiBundleTest
> [equinox/3.5.0] failing
> ---------------------------------------------------------------------------------------------------------
>
> Key: ARIES-859
> URL: https://issues.apache.org/jira/browse/ARIES-859
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Reporter: Holly Cummins
> Priority: Critical
>
> The following build has a new test failure, which I can reproduce
> locally:https://builds.apache.org/job/Aries/1473/.
> It seems to be related to the following commit, under ARIES-825:
> http://svn.apache.org/viewvc?view=revision&revision=1347690
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
