On Sun, Jan 31, 2010 at 2:46 PM, Frederic Meyer <[email protected]> wrote:
> On Sat, Jan 30, 2010 at 8:22 PM, Simon Laws <[email protected]> wrote:
>> Hi Frederic
>>
>> Welcome!
>
> Thanks!
>
>> The output you're seeing is just a test artifact. The test is
>> working OK. I've just run it and seen the same. It's happening because
>> this test uses some XML data that contains test elements/attributes
>> for which there are no Tuscany XML processors registered.
>
> Well ok... but continuing further, the test output really produces
> tons of similar messages.
> But you are right, maven do report that all tests pass with success.
>
> Even on the Tuscany SCA JSE built-in CORBA Host test where I have the
> following exception:
>
> ...
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.apache.tuscany.sca.host.corba.testing.DefaultCorbaHostTestCase
> 30 janv. 2010 19:24:56
> com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl <init>
> ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure:
> socketType: IIOP_CLEAR_TEXT; hostname: nonexistingone; port: 11100"
> org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
>        at 
> com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2200)
>        at 
> com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2221)
>        at 
> com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:205)
>        at 
> com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:218)
>        at 
> com.sun.corba.se.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:101)
>        at 
> com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:152)
>        at 
> com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:118)
>        at 
> com.sun.corba.se.impl.resolver.BootstrapResolverImpl.invoke(BootstrapResolverImpl.java:74)
>        at 
> com.sun.corba.se.impl.resolver.BootstrapResolverImpl.resolve(BootstrapResolverImpl.java:107)
>        at 
> com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:22)
>        at 
> com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:22)
>        at 
> com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:22)
>        at 
> com.sun.corba.se.impl.orb.ORBImpl.resolve_initial_references(ORBImpl.java:1138)
>        at 
> org.apache.tuscany.sca.host.corba.jse.DefaultCorbaHost.getNamingContext(DefaultCorbaHost.java:58)
>        at 
> org.apache.tuscany.sca.host.corba.jse.DefaultCorbaHost.lookup(DefaultCorbaHost.java:120)
>        at 
> org.apache.tuscany.sca.host.corba.testing.DefaultCorbaHostTestCase.test_getNonExistingObject(DefaultCorbaHostTestCase.java:141)
>        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.runChild(BlockJUnit4ClassRunner.java:73)
>        at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
>        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
>        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
>        at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
>        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:220)
>        at 
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>        at 
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
>        at 
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
>        at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
>        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:308)
>        at 
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
> Caused by: java.nio.channels.UnresolvedAddressException
>        at sun.nio.ch.Net.checkAddress(Net.java:30)
>        at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:487)
>        at java.nio.channels.SocketChannel.open(SocketChannel.java:146)
>        at 
> com.sun.corba.se.impl.transport.DefaultSocketFactoryImpl.createSocket(DefaultSocketFactoryImpl.java:60)
>        at 
> com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:188)
>        ... 41 more
> ...
>
> This one looks like a server piece is missing, hence the connection failure.
> But if it's safe to ignore... that's ok.
>
> Regards,
> Frederic
>

When having issues with the build, the best way is to use something like :

mvn -fae clean install

This should allow errors to be reported in the end, and hopefully, if
there is only an issue in a module that is not impacting other places,
allow you to proceed...
-- 
Luciano Resende
http://people.apache.org/~lresende
http://lresende.blogspot.com/

Reply via email to