[jboss-as7-dev] JMXSubsystemTestCase failure in upstream
Kabir Khan
kabir.khan at jboss.com
Thu Sep 22 11:40:20 EDT 2011
This should be fixed in upstream now
On 22 Sep 2011, at 10:06, Darran Lofthouse wrote:
> A could of us had an issue yesterday and Kabir has tried a fix, however
> it looks like it is still an issue.
>
> I am also still getting failures on two different machines.
>
> Regards,
> Darran Lofthouse.
>
>
> On 09/22/2011 07:49 AM, Jaikiran Pai wrote:
>> I am seeing this test failure in upstream since yesterday. Is it just my
>> setup or is anyone else seeing this too:
>>
>>
>> -------------------------------------------------------------------------------
>> Test set: org.jboss.as.jmx.JMXSubsystemTestCase
>> -------------------------------------------------------------------------------
>> Tests run: 12, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.747
>> sec<<< FAILURE!
>> testInstallIntoController(org.jboss.as.jmx.JMXSubsystemTestCase) Time
>> elapsed: 0.029 sec<<< ERROR!
>> java.io.IOException: Failed to retrieve RMIServer stub:
>> javax.naming.CommunicationException [Root exception is
>> java.rmi.NoSuchObjectException: no such object in table]
>> at
>> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
>> at
>> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
>> at
>> org.jboss.as.jmx.JMXSubsystemTestCase.testInstallIntoController(JMXSubsystemTestCase.java:204)
>> 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>> at
>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>> at
>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>> at
>> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>> at
>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>> at
>> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>> at
>> org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
>> at
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
>> at
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
>> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
>> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
>> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
>> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
>> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>> at
>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
>> at
>> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
>> at
>> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
>> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
>> at
>> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
>> at
>> org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172)
>> at
>> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:104)
>> at
>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70)
>> Caused by: javax.naming.CommunicationException [Root exception is
>> java.rmi.NoSuchObjectException: no such object in table]
>> at
>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
>> at
>> com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
>> at javax.naming.InitialContext.lookup(InitialContext.java:392)
>> at
>> javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886)
>> at
>> javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856)
>> at
>> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
>> ... 33 more
>> Caused by: java.rmi.NoSuchObjectException: no such object in table
>> at
>> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
>> at
>> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
>> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:359)
>> at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
>> at
>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97)
>> ... 38 more
>>
>>
>> -Jaikiran
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
More information about the jboss-as7-dev
mailing list