5 Replies Latest reply on May 26, 2015 8:59 AM by bjornbak

    Trying to install JBossWS 5.0 results in error

    bjornbak
    bjornbak May 22, 2015 2:06 AM

      Hi

       

      I'm trying to install JBossWS 5.0 on Wildfly 8.2 but the tests results in an error in the UDP test.

       

      I download jbossws-cxf-5.0.0.Final.zip, unzip and run mvn -Pwildfly820 -Dserver.home=/srv/wildfly/8180/ package but it results in the error below.

       

      Seeing "Setting the server's publish address to be udp://:9434" I expected a wrong endpoint address could be the reason.

       

      I found an ipv4 profile in the pom.xml and wanted to remove any misconfiguration in my wildfly from the equation so I tried mvn -Pipv4,wildfly820 package same error.

       

      I also tried the wildfly900 profile with same result.

       

      Can anyone help me how to make the tests succeed?

       

      Thanks, Christian Bjørnbak

       

      -------------------------------------------------------

      T E S T S

      -------------------------------------------------------

      Running org.jboss.wsf.stack.cxf.addons.transports.udp.UDPTransportTest

      May 22, 2015 7:56:57 AM org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean buildServiceFromClass

      INFO: Creating Service {http://apache.org/hello_world/services}SOAPService from class org.jboss.wsf.stack.cxf.addons.transports.udp.Greeter

      May 22, 2015 7:56:57 AM org.apache.cxf.endpoint.ServerImpl initDestination

      INFO: Setting the server's publish address to be udp://:9434

      May 22, 2015 7:56:57 AM org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean buildServiceFromClass

      INFO: Creating Service {http://udp.transports.addons.cxf.stack.wsf.jboss.org/}GreeterService from class org.jboss.wsf.stack.cxf.addons.transports.udp.Greeter

      May 22, 2015 7:56:57 AM org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean buildServiceFromClass

      INFO: Creating Service {http://udp.transports.addons.cxf.stack.wsf.jboss.org/}GreeterService from class org.jboss.wsf.stack.cxf.addons.transports.udp.Greeter

      May 22, 2015 7:56:57 AM org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean buildServiceFromClass

      INFO: Creating Service {http://udp.transports.addons.cxf.stack.wsf.jboss.org/}GreeterService from class org.jboss.wsf.stack.cxf.addons.transports.udp.Greeter

      May 22, 2015 7:57:27 AM org.apache.cxf.phase.PhaseInterceptorChain doDefaultLogging

      WARNING: Interceptor for {http://udp.transports.addons.cxf.stack.wsf.jboss.org/}GreeterService#{http://udp.transports.addons.cxf.stack.wsf.jboss.org/}greetMe has thrown exception, unwinding now

      org.apache.cxf.interceptor.Fault: Could not send Message.

              at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)

              at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)

              at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:516)

              at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:425)

              at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:326)

              at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:279)

              at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)

              at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:138)

              at com.sun.proxy.$Proxy39.greetMe(Unknown Source)

              at org.jboss.wsf.stack.cxf.addons.transports.udp.UDPTransportTest.testBroadcastUDP(UDPTransportTest.java:107)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

              at java.lang.reflect.Method.invoke(Method.java:497)

              at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)

              at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)

              at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)

              at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)

              at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)

              at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)

              at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)

              at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)

              at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)

              at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)

              at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)

              at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)

              at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)

              at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)

              at org.junit.runners.ParentRunner.run(ParentRunner.java:363)

              at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)

              at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)

              at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

              at java.lang.reflect.Method.invoke(Method.java:497)

              at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)

              at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:158)

              at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)

              at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)

              at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95)

      Caused by: java.net.SocketTimeoutException: Receive timed out

              at java.net.PlainDatagramSocketImpl.receive0(Native Method)

              at java.net.AbstractPlainDatagramSocketImpl.receive(AbstractPlainDatagramSocketImpl.java:144)

              at java.net.DatagramSocket.receive(DatagramSocket.java:812)

              at org.jboss.wsf.stack.cxf.addons.transports.udp.UDPConduit$SocketOutputStream.close(UDPConduit.java:202)

              at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)

              at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)

              ... 40 more

       

       

      Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 31.035 sec <<< FAILURE!

      testBroadcastUDP(org.jboss.wsf.stack.cxf.addons.transports.udp.UDPTransportTest)  Time elapsed: 30.045 sec  <<< ERROR!

      javax.xml.ws.WebServiceException: Could not send Message.

              at java.net.PlainDatagramSocketImpl.receive0(Native Method)

              at java.net.AbstractPlainDatagramSocketImpl.receive(AbstractPlainDatagramSocketImpl.java:144)

              at java.net.DatagramSocket.receive(DatagramSocket.java:812)

              at org.jboss.wsf.stack.cxf.addons.transports.udp.UDPConduit$SocketOutputStream.close(UDPConduit.java:202)

              at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)

              at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)

              at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)

              at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:516)

              at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:425)

              at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:326)

              at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:279)

              at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)

              at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:138)

              at com.sun.proxy.$Proxy39.greetMe(Unknown Source)

              at org.jboss.wsf.stack.cxf.addons.transports.udp.UDPTransportTest.testBroadcastUDP(UDPTransportTest.java:107)

       

       

       

       

      Results :

       

       

      Tests in error:

        UDPTransportTest.testBroadcastUDP:107 » WebService Could not send Message.

       

       

      Tests run: 3, Failures: 0, Errors: 1, Skipped: 0

        • 1. Re: Trying to install JBossWS 5.0 results in error
          asoldano
          asoldano May 22, 2015 3:27 AM (in response to bjornbak)

          Failures in the UDP tests are usually caused by UDP broadcast being disabled on the local network, please check and modify your firewall rules (note, by default UDP broadcast is disabled on most recent Linux distributions).

          You can skip UDP tests by using the -Dexclude-udp-tests option when running the testsuite.

            • Actions
          • 2. Re: Trying to install JBossWS 5.0 results in error
            bjornbak
            bjornbak May 22, 2015 5:09 AM (in response to asoldano)

            Hi Alessio,

             

            Thanks for your answer. I had tried to turn off the firewall with luck but anyway using the option worked..

             

            Now I get a new error further down the testing:

             

            [INFO] ------------------------------------------------------------------------

            [INFO] Building JBoss Web Services - Stack CXF Specific Tests 5.0.0.Final

            [INFO] ------------------------------------------------------------------------

            [WARNING] The POM for org.jboss.security:jbossxacml:jar:2.0.8.Final is missing, no dependency information available

            [INFO] ------------------------------------------------------------------------

            [INFO] Reactor Summary:

            [INFO]

            [INFO] JBoss Web Services - Stack CXF ..................... SUCCESS [  0.452 s]

            [INFO] JBoss Web Services - Stack CXF JASPI ............... SUCCESS [  3.110 s]

            [INFO] JBoss Web Services - Endorsed factories ............ SUCCESS [  0.082 s]

            [INFO] JBoss Web Services - Stack CXF Add-ons ............. SUCCESS [  0.011 s]

            [INFO] JBoss Web Services - Stack CXF UDP transport ....... SUCCESS [  0.361 s]

            [INFO] JBoss Web Services - Stack CXF Undertow http transport SUCCESS [  1.556 s]

            [INFO] JBoss Web Services - Stack CXF Runtime Client ...... SUCCESS [  4.981 s]

            [INFO] JBoss Web Services - Stack CXF Server .............. SUCCESS [  2.522 s]

            [INFO] JBoss Web Services - Stack CXF Resources ........... SUCCESS [  0.806 s]

            [INFO] JBoss Web Services - Stack CXF Test utils .......... SUCCESS [  0.326 s]

            [INFO] JBoss Web Services - Stack CXF Distribution ........ SUCCESS [  8.131 s]

            [INFO] JBoss Web Services - Stack CXF Testsuite ........... SUCCESS [  0.497 s]

            [INFO] JBoss Web Services - Stack CXF Specific Tests ...... FAILURE [  0.123 s]

            [INFO] JBoss Web Services - Stack Agnostic Tests .......... SKIPPED

            [INFO] ------------------------------------------------------------------------

            [INFO] BUILD FAILURE

            [INFO] ------------------------------------------------------------------------

            [INFO] Total time: 25.567 s

            [INFO] Finished at: 2015-05-22T11:07:08+02:00

            [INFO] Final Memory: 92M/1440M

            [INFO] ------------------------------------------------------------------------

            [ERROR] Failed to execute goal on project jbossws-cxf-specific-tests: Could not resolve dependencies for project org.jboss.ws.cxf:jbossws-cxf-specific-tests:jar:5.0.0.Final: Could not find artifact org.jboss.security:jbossxacml:jar:2.0.8.Final in central (https://repo.maven.apache.org/maven2) -> [Help 1]    

             

            Should I add an extra maven repository to the pom.xml or is there an option to turn off CXF Specific Tests too?

             

            Thanks, Christian

              • Actions
            • 3. Re: Trying to install JBossWS 5.0 results in error
              bjornbak
              bjornbak May 26, 2015 5:43 AM (in response to bjornbak)

              Does anyone has the solution for the dependency error?

                • Actions
              • 4. Re: Trying to install JBossWS 5.0 results in error
                asoldano
                asoldano May 26, 2015 6:37 AM (in response to bjornbak)

                The issue comes from the org.jboss.security:jbossxacml:jar:2.0.8.Final artifact not being available in Maven central repository. So you need to configure your local maven installation to use the JBoss Nexus repositories too. See https://developer.jboss.org/wiki/JBossWS-Mavenization#jive_content_id_Create_or_Update_Maven_Settings_JBoss_Nexus_Maven_… for some info.

                  • Actions
                • 5. Re: Trying to install JBossWS 5.0 results in error
                  bjornbak
                  bjornbak May 26, 2015 8:59 AM (in response to asoldano)

                  Excuse me for being noob!

                   

                  I knew that the problem was maven looked in the wrong repository but I was not aware that one can add repositories in a global settings.xml.

                   

                  In our projects we add the extra repositories in pom.xml..

                   

                  Adding the suggested repository to ~/.m2/settings.xml works.

                   

                  Thanks for your help!

                    • Actions