On Mon, May 17, 2010 at 11:07 AM, Simon Laws <[email protected]> wrote:
> On Mon, May 17, 2010 at 11:03 AM, ant elder <[email protected]> wrote:
>> I'm guessing that will be because there is already a previous runtime
>> up somewhere, i've not got that one but i'm having tests fail as
>> there's already something uisng 8085 on a full build but not when run
>> individually. I guess some previous test is not shutting down
>> properly. (I'm also wondering if we need to be calling
>> NodeFactory.destroy everywhere now as the NodeFactory is the runtime
>> so just stopping individual nodes may not always be enough).
>>
>>   ...ant
>>
>> On Mon, May 17, 2010 at 10:53 AM, Simon Laws <[email protected]> 
>> wrote:
>>> This morning from itest\scaclient-api-remote I'm seeing...
>>>
>>>  <testcase time="8.609" classname="test.scaclient.SCAClientTestCase"
>>> name="testURIconfig">
>>>    <error 
>>> type="java.lang.reflect.UndeclaredThrowableException">java.lang.reflect.UndeclaredThrowableException
>>>        at $Proxy11.sayHello(Unknown Source)
>>>        at 
>>> test.scaclient.SCAClientTestCase.testURIconfig(SCAClientTestCase.java:71)
>>>        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.RunAfters.evaluate(RunAfters.java:31)
>>>        at 
>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
>>>        at 
>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>>>        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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>>>        at 
>>> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>>>        at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>>>        at 
>>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>>>        at 
>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
>>>        at 
>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
>>>        at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
>>>        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.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
>>>        at 
>>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
>>> Caused by: org.oasisopen.sca.NoSuchDomainException: somedomain
>>>        at 
>>> org.apache.tuscany.sca.client.impl.SCAClientHandler.invoke(SCAClientHandler.java:101)
>>>        ... 31 more
>>> Caused by: java.lang.RuntimeException: Wrong group name and password.
>>>        at 
>>> com.hazelcast.client.HazelcastClient.&lt;init&gt;(HazelcastClient.java:79)
>>>        at 
>>> com.hazelcast.client.HazelcastClient.newHazelcastClient(HazelcastClient.java:160)
>>>        at 
>>> com.hazelcast.client.HazelcastClient.newHazelcastClient(HazelcastClient.java:138)
>>>        at 
>>> com.hazelcast.client.HazelcastClient.newHazelcastClient(HazelcastClient.java:116)
>>>        at 
>>> org.apache.tuscany.sca.endpoint.hazelcast.client.HazelcastClientEndpointRegistry.initHazelcastClientInstance(HazelcastClientEndpointRegistry.java:84)
>>>        at 
>>> org.apache.tuscany.sca.endpoint.hazelcast.client.HazelcastClientEndpointRegistry.start(HazelcastClientEndpointRegistry.java:57)
>>>        at 
>>> org.apache.tuscany.sca.runtime.BaseDomainRegistryFactory.getEndpointRegistry(BaseDomainRegistryFactory.java:67)
>>>        at 
>>> org.apache.tuscany.sca.runtime.ExtensibleDomainRegistryFactory.getEndpointRegistry(ExtensibleDomainRegistryFactory.java:102)
>>>        at 
>>> org.apache.tuscany.sca.client.impl.SCAClientHandler.invoke(SCAClientHandler.java:99)
>>>        ... 31 more
>>> </error>
>>>
>>> Fails on full build works if I run it locally. Anyone else seeing this
>>> kind of thing?
>>>
>>> Simon
>>>
>>> --
>>> Apache Tuscany committer: tuscany.apache.org
>>> Co-author of a book about Tuscany and SCA: tuscanyinaction.com
>>>
>>
>
> yes, looking at the next failure I have that seems to hold true, i.e.
> failing on a port already in us.It may be some of the sample stuff
> I've changed as this is a fairly recent issue (last day or so).
>
> Simon
>
>
> --
> Apache Tuscany committer: tuscany.apache.org
> Co-author of a book about Tuscany and SCA: tuscanyinaction.com
>

Somehow it seems to be itest/distribution/calculator-rmi that's
causing the problem. Just running the itests this is what causes the
problem with the ws policy itest that comes later. Am doing a full
build with that commented out.

Simon

-- 
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com

Reply via email to