[
https://issues.apache.org/jira/browse/CXF-8897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740198#comment-17740198
]
Andriy Redko commented on CXF-8897:
-----------------------------------
[~agitatra] when you say `When calling maven on the latest master of CXF
several errors occur`, what exactly the command you use? The one which should
work is `mvn clean install`
> Several test steps fail when calling "mvn clean package verify" on CXF
> ----------------------------------------------------------------------
>
> Key: CXF-8897
> URL: https://issues.apache.org/jira/browse/CXF-8897
> Project: CXF
> Issue Type: Test
> Components: Build system
> Affects Versions: 4.0.2
> Environment: h1. OS
> Distributor ID: Ubuntu
> Description: Ubuntu 20.04.6 LTS
> Release: 20.04
> Codename: focal
> h1. Java/maven
> Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
> Maven home: /opt/maven
> Java version: 17.0.7, vendor: Private Build, runtime:
> /usr/lib/jvm/java-17-openjdk-amd64
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.4.0-153-generic", arch: "amd64", family: "unix"
> Reporter: Mark Kahl
> Priority: Major
>
> When calling maven on the latest master of CXF several errors occur
> Especially the first two issues are tricky because they only occur randomly,
> but frequently. When both do not arise, other issues follow. However, the
> latter can be solved by manual intervention.
> h1. WaitForReceiveInMessage
> This error only arises randomly but often.
> * [ERROR]
> org.apache.cxf.transport.jms.RequestResponseTest.testRequestTopicResponseStaticQueue
> [ERROR] Run 1:
> RequestResponseTest.testRequestTopicResponseStaticQueue:64->sendAndReceiveMessages:99->AbstractJMSTester.waitForReceiveInMessage:306
> Can't receive the Conduit Message in 10 seconds
> [ERROR] Run 2:
> RequestResponseTest.testRequestTopicResponseStaticQueue:64->sendAndReceiveMessages:99->AbstractJMSTester.waitForReceiveInMessage:306
> Can't receive the Conduit Message in 10 seconds
> [ERROR] Run 3:
> RequestResponseTest.testRequestTopicResponseStaticQueue:63->sendAndReceiveMessages:95->AbstractJMSTester.sendMessage:165->AbstractJMSTester.sendoutMessage:187
> » Runtime Timeout receiving messag\
> e with correlationId 966448dc1cb54df0b2da6654c31093810000000000000001
> [ERROR] Run 4:
> RequestResponseTest.testRequestTopicResponseStaticQueue:64->sendAndReceiveMessages:99->AbstractJMSTester.waitForReceiveInMessage:306
> Can't receive the Conduit Message in 10 seconds
> h1. Could not start Jetty server
> This error only arises randomly but often. The port changes between calls,
> the binding address is either: "0.0.0.0" or: "127.0.0.1"
> * Could not start Jetty server on port 54,110: Failed to bind to
> 0.0.0.0/0.0.0.0:54110
> h1. File in folder "/home/jenkins..." not found
> A testing step fails because:
> *
> /home/jenkins/workspace/CXF/CXF-JDK17-deploy/testutils/src/main/resources/wsdl/hello_world_services.wsdl
> was not found. This is normal IMHO, since not every machine features a user
> called: "jenkins". When the appropriate folder is created and the file:
> * testutils/src/main/resources/wsdl/hello_world_services.wsdl
> is copied into it, the step succeeds.
> h1. Folder
> ~/.m2/repository/org/apache/cxf/org/apache/cxf/cxf-rt-transports-http missing
> The sub-project:
> * cxf-rt-transports-http
> and all its files is created, however its content is not copied into the
> local .m2-repository. Therefore, the following steps, that rely on its
> content, fail. Manually copying the files into the local repository fixes
> this issue:
> * cp -rp
> maven-plugins/wadl2java-plugin/target/it-repo/org/apache/cxf/cxf-rt-transports-http
> ~/.m2/repository/org/apache/cxf/org/apache/cxf/cxf-rt-transports-http
> h1. WSDL and XML files are missing in folder systests/transport-hc5
> The WSDL and XML files located in:
> * testutils/target/classes/wsdl
> are not copied to:
> * systests/transport-hc5
> When copied manually the step succeeds:
> * cp testutils/target/classes/wsdl/* systests/transport-hc5
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
