You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Dan Wlodarski <dw...@tdkc.com> on 2016/03/12 22:27:00 UTC
Errors building CXF from git repo
To anyone whom may have insight:
The relevant environment info:
CXF version: direct from the CXF Git repository
Platform: Ubuntu Server 14.04.04 64b guest OS running under Windows VirtualBox v5.0.16
JDK: v1.8.0_74 (Oracle-official)
I am looking to implement a custom build of CXF to simulate an external SOAP server. The CXF build needs to support multiple web services and export of a standalone server for machine-local testing. However, I can't even get the build to complete.
A couple of minutes after calling the Maven install target, the build fails on the "Apache CXF Runtime JMS Transport" step. The two specific tests that fail:
* RequestResponseTest.testRequestTopicResponseStaticQueue:90->sendAndReceiveMessages:134->AbstractJMSTester.sendMessage:129->AbstractJMSTester.sendoutMessage:152 > Runtime
* RequestResponseTest.testRequestTopicResponseTempQueue:83->sendAndReceiveMessages:134->AbstractJMSTester.sendMessage:129->AbstractJMSTester.sendoutMessage:152 > Runtime
As this will be a development server to be pushed to a production tier, it is required that it passes all unit tests.
Thanks for any guidance,
Dan C. Wlodarski
The Design Knowledge Company
3100 Presidential Drive
Suite 103
Fairborn, Ohio 45324
Phone: 937-427-4276 x175
Fax: 937-427-1242
dwlodarski@tdkc.com
www.tdkc.com
RE: Errors building CXF from git repo
Posted by Dan Wlodarski <dw...@tdkc.com>.
Christian:
Thank you for your response. I will be patching functionality into CXF as my project needs them, so I'll download a commit tagged for release. Are they obvious?
It may be possible the ports are unavailable for listening, but I've tried these tests on server and desktop host OSes. Are the ports CXF using in the reserved range?
The stack traces of the errors follow:
testRequestTopicResponseTempQueue(org.apache.cxf.transport.jms.RequestResponseTest) Time elapsed: 60.058 sec <<< ERROR!
java.lang.RuntimeException: Timeout receiving message with correlationId d4873fdf61f6477d904133c6b17084080000000000000001
at org.apache.cxf.transport.jms.JMSConduit.sendAndReceiveMessage(JMSConduit.java:236)
at org.apache.cxf.transport.jms.JMSConduit.sendExchange(JMSConduit.java:145)
at org.apache.cxf.transport.jms.MessageStreamUtil$SendingOutputStream.doClose(MessageStreamUtil.java:81)
at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:213)
at org.apache.cxf.transport.jms.AbstractJMSTester.sendoutMessage(AbstractJMSTester.java:152)
at org.apache.cxf.transport.jms.AbstractJMSTester.sendMessage(AbstractJMSTester.java:129)
at org.apache.cxf.transport.jms.RequestResponseTest.sendAndReceiveMessages(RequestResponseTest.java:134)
at org.apache.cxf.transport.jms.RequestResponseTest.testRequestTopicResponseTempQueue(RequestResponseTest.java:83)
testRequestTopicResponseStaticQueue(org.apache.cxf.transport.jms.RequestResponseTest) Time elapsed: 60.055 sec <<< ERROR!
java.lang.RuntimeException: Timeout receiving message with correlationId ee90cde9f42747de90e773e00ec1dfae0000000000000001
at org.apache.cxf.transport.jms.JMSConduit.sendAndReceiveMessage(JMSConduit.java:236)
at org.apache.cxf.transport.jms.JMSConduit.sendExchange(JMSConduit.java:145)
at org.apache.cxf.transport.jms.MessageStreamUtil$SendingOutputStream.doClose(MessageStreamUtil.java:81)
at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:213)
at org.apache.cxf.transport.jms.AbstractJMSTester.sendoutMessage(AbstractJMSTester.java:152)
at org.apache.cxf.transport.jms.AbstractJMSTester.sendMessage(AbstractJMSTester.java:129)
at org.apache.cxf.transport.jms.RequestResponseTest.sendAndReceiveMessages(RequestResponseTest.java:134)
at org.apache.cxf.transport.jms.RequestResponseTest.testRequestTopicResponseStaticQueue(RequestResponseTest.java:90)
-----Original Message-----
From: Christian Schneider [mailto:cschneider111@gmail.com] On Behalf Of Christian Schneider
Sent: Sunday, March 13, 2016 1:56 AM
To: dev@cxf.apache.org
Subject: Re: Errors building CXF from git repo
Hi,
you can look at
https://builds.apache.org/me/my-views/view/My/job/CXF-Trunk-JDK18 to see the current status of the CXF build. At the moment there are test failures even there.
As CXF is actively developed you can not expect the build to always succeed. Do you need the custom build because you need to apply some patche of your own?
If yes then the best option is to start with a release tag of CXF and apply you patches to it. Beware though that even a release is not required to run all tests succesfully.
The most common reason for build failures on a test server (except actual errors in the code) is that ports are not available. So check which ports the test uses and check if these ports a maybe used on your system.
Abot the failures you reported. Can you give the full stack trace of the errors. They sometimes show what is wrong.
Christian
On 12.03.2016 22:27, Dan Wlodarski wrote:
> To anyone whom may have insight:
>
> The relevant environment info:
>
> CXF version: direct from the CXF Git repository
> Platform: Ubuntu Server 14.04.04 64b guest OS running under Windows
> VirtualBox v5.0.16
> JDK: v1.8.0_74 (Oracle-official)
>
> I am looking to implement a custom build of CXF to simulate an external SOAP server. The CXF build needs to support multiple web services and export of a standalone server for machine-local testing. However, I can't even get the build to complete.
>
> A couple of minutes after calling the Maven install target, the build fails on the "Apache CXF Runtime JMS Transport" step. The two specific tests that fail:
>
>
> * RequestResponseTest.testRequestTopicResponseStaticQueue:90->sendAndReceiveMessages:134->AbstractJMSTester.sendMessage:129->AbstractJMSTester.sendoutMessage:152 > Runtime
>
> * RequestResponseTest.testRequestTopicResponseTempQueue:83->sendAndReceiveMessages:134->AbstractJMSTester.sendMessage:129->AbstractJMSTester.sendoutMessage:152 > Runtime
>
> As this will be a development server to be pushed to a production tier, it is required that it passes all unit tests.
>
> Thanks for any guidance,
>
> Dan C. Wlodarski
> The Design Knowledge Company
> 3100 Presidential Drive
> Suite 103
> Fairborn, Ohio 45324
>
> Phone: 937-427-4276 x175
> Fax: 937-427-1242
> dwlodarski@tdkc.com
> www.tdkc.com
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: Errors building CXF from git repo
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi,
you can look at
https://builds.apache.org/me/my-views/view/My/job/CXF-Trunk-JDK18 to see
the current status of the CXF build. At the moment
there are test failures even there.
As CXF is actively developed you can not expect the build to always
succeed. Do you need the custom build because you need to apply some
patche of your own?
If yes then the best option is to start with a release tag of CXF and
apply you patches to it. Beware though that even a release is not
required to run all tests succesfully.
The most common reason for build failures on a test server (except
actual errors in the code) is that ports are not available. So check
which ports the test uses and check if these ports a maybe used on your
system.
Abot the failures you reported. Can you give the full stack trace of the
errors. They sometimes show what is wrong.
Christian
On 12.03.2016 22:27, Dan Wlodarski wrote:
> To anyone whom may have insight:
>
> The relevant environment info:
>
> CXF version: direct from the CXF Git repository
> Platform: Ubuntu Server 14.04.04 64b guest OS running under Windows VirtualBox v5.0.16
> JDK: v1.8.0_74 (Oracle-official)
>
> I am looking to implement a custom build of CXF to simulate an external SOAP server. The CXF build needs to support multiple web services and export of a standalone server for machine-local testing. However, I can't even get the build to complete.
>
> A couple of minutes after calling the Maven install target, the build fails on the "Apache CXF Runtime JMS Transport" step. The two specific tests that fail:
>
>
> * RequestResponseTest.testRequestTopicResponseStaticQueue:90->sendAndReceiveMessages:134->AbstractJMSTester.sendMessage:129->AbstractJMSTester.sendoutMessage:152 > Runtime
>
> * RequestResponseTest.testRequestTopicResponseTempQueue:83->sendAndReceiveMessages:134->AbstractJMSTester.sendMessage:129->AbstractJMSTester.sendoutMessage:152 > Runtime
>
> As this will be a development server to be pushed to a production tier, it is required that it passes all unit tests.
>
> Thanks for any guidance,
>
> Dan C. Wlodarski
> The Design Knowledge Company
> 3100 Presidential Drive
> Suite 103
> Fairborn, Ohio 45324
>
> Phone: 937-427-4276 x175
> Fax: 937-427-1242
> dwlodarski@tdkc.com
> www.tdkc.com
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com